We installed EchoControl on a computer that had never seen the app before. Double-click. The splash screen just sits there, empty, no sound coming in from anywhere. This didn't happen on some random test machine. It happened on the exact computer we were about to use to record the next release video.
For weeks, we'd been shipping builds with the microphone silently off, with no visible error at all. No crash. No message. Just silence, exactly where there should have been sound.
What actually happened
We were shrinking the installer. Every new version weighed a little more than the last one, and at some point someone has to sit down and look at what's left over. Part of that cleanup meant removing a piece of code we assumed nobody used anymore — an old leftover from an earlier version of the audio system, no longer showing up anywhere obvious in the project.
It turned out something deep in the audio system, in a corner that had nothing to do with that cleanup, needed that exact piece — the part that opens the microphone the first time the operating system asks for it. We didn't know that. There was no comment in the code warning us, no test covering it.
On our own computers, this problem never showed up. We'd already set everything up before, so the missing piece was never needed: Windows had already granted us that permission months earlier, on another build, and remembered it. The bug only showed up on a truly fresh Windows install — the exact situation any real customer is in the first time they download EchoControl.
How we found it
We found it by luck, not by skill. Right before a real release, we ran the full install on a clean computer, the way an actual buyer would.
We usually tested on machines that already had months of setup on them. This time we didn't. The app opened. The splash screen stayed empty. Nothing happened next. No error, no crash, just silence — because the microphone never opened at all.
The first reaction was to assume the test machine was set up wrong. We reinstalled. Same result. Only when someone asked "what if the problem is ours, not the computer's" did we start looking in the right direction.
The second bug, hiding behind the first
That same test found a second, completely separate problem, right after we fixed the first one. On a fresh Windows install, a security check failed — one that decides whether the operating system trusts the installer. It had never failed on our own computers, because our computers already trusted something a brand-new Windows doesn't trust yet — the exact same logic that had fooled us on the microphone, repeated in a different part of the app.
Two real bugs. Both invisible on a developer's computer. Both visible only on the exact setup a real customer actually has.
What changed because of this
We didn't fix it by adding more automated tests, though we added a few of those too. What actually changed was a rule: before anything ships, someone installs it on a computer that has never seen EchoControl before. No shortcut. No computer that's "close enough."
The two bugs made that case on their own:
- The microphone bug could have been caught by an automated test, if anyone had thought to write it.
- The security-check bug couldn't — it only shows up on a customer's real combination of hardware and operating system, never in a simulated test environment.
A cleanup that looked completely safe had turned off the one feature the whole product depends on. The only way we found it was by refusing to trust "it works on my computer."
If you've ever installed something and hit a strange silent freeze for no reason, this is usually why. The software was tested on a computer that wasn't really starting from zero. We almost shipped ours the exact same way — and the odd part is that almost nobody tests this way on purpose, because an "already set up" computer is exactly the one every team has closest at hand. The clean one has to be sought out, or rebuilt from scratch every time on a virtual machine.
And since then, every release goes through that same clean computer before it leaves here — the same one that started all of this.
If your own microphone isn't being picked up, the setup guide covers what to check first.
Try EchoControl and check for yourself that the microphone opens on the first try.