Slapback · 2026-09-20

Echo suddenly started? Something changed — find it

By the Echobreak team

The most useful sentence in audio troubleshooting is one people say apologetically, as if it weren't evidence: "it was fine until last week." That sentence is the whole case file. Echo doesn't condense out of the atmosphere — a working audio path stays working until something in it moves. If calls were clean and now they aren't, your job isn't "fix echo"; it's "find the change." Here's the suspect list, ordered by how often each one turns out to be guilty.

Before the list — confirm whose change it is. If you hear echo, the loop is probably on another participant's machine, and the thing that changed may be their new speakers, not anything of yours (the asymmetry, explained). Sudden echo in every meeting with different people → the common factor is you; sudden echo only in meetings with Dave → it's Dave. Group case: two-minute culprit hunt first, then hand the culprit this checklist.

The suspect list, in order

A new audio device became the default. The commonest one by a mile. A new webcam, dock, monitor with speakers, or Bluetooth gadget quietly claimed "default output" or "default input," and now sound plays from somewhere your canceller isn't modeling — a monitor's speakers a meter from a webcam mic is a textbook loop. Check both defaults in your system sound settings; make the calling app's device choices explicit rather than "system default" so the next gadget can't hijack them.
Bluetooth reconnected in a different mode. Wireless audio devices juggle profiles (media vs call), and a mid-day reconnect can land in the wrong one, changing what the canceller sees — echo, robot voice, or sudden self-hearing follow. Fix: disconnect/reconnect, or re-select the device inside the calling app. Chronic offenders deserve a wired week as a test.
New software inserted itself into the audio path. Virtual devices ship with more things than people expect — mixers, recording suites, some game launchers and "enhancement" utilities. Anything that adds a virtual mic/speaker or a loopback can starve the canceller of its reference signal (why that breaks subtraction) or, worse, route output straight into input. Sort installs by date; anything audio-adjacent from the echo's birth week is suspect number one. Uninstall or bypass for calls, test, reinstall if innocent.
An update reset settings you'd tuned. OS and app updates re-enable "enhancements," reset device selections, and occasionally reintroduce processing you'd disabled. If the echo's birthday matches patch Tuesday, walk the calling app's audio settings and the per-device driver options and re-assert your choices.
The physical desk changed. Speakers turned up for music and never turned back down; the mic knocked behind a speaker; furniture moved so speakers now face the mic; a second person now takes calls in the same room (two-device loops arrive exactly this way). Reversible in thirty seconds once noticed — the trick is noticing, because nobody logs "I nudged the mic."
A new meeting platform or a browser join. New job tool, or you joined from the browser instead of the app? Different canceller, different tuning — a setup the old stack coped with may sit just outside the new one's comfort zone. Not really "something broke," more "your margin was thinner than you knew." The geometry pass in the speakers-only playbook rebuilds the margin; a system-wide cancellation layer makes it platform-independent so the next migration can't do this to you again.

The five-minute reset

No memory of any change and no patience for forensics? Brute-force the path back to known-good: set system output and input to the built-in hardware, quit everything audio-touching except the calling app, volume to two-thirds, run the app's own mic/speaker test, then a test call. Clean? Reintroduce your usual devices and tools one at a time until the echo returns — the last thing added is your culprit, and it earns either a settings fix from the list above or eviction. Still echoing even in the minimal configuration? Then it was never your machine: back to the hunt.