How to stop your mic picking up game audio

First, find out which problem you have

Game sound can only reach your teammates through your mic in two ways. Either it travels through the air, out of your speakers and back in through the microphone capsule, or it travels through wiring, a device or setting inside Windows that mixes what your PC plays into the signal your apps treat as your microphone. The two fixes have nothing in common, so spend thirty seconds finding out which one you have before you change anything.

The test is to take the microphone out of the picture physically and see whether the game survives. Use the mute switch on the mic or headset itself, or unplug it. Do not use the mute button in your call app, because that button mutes whatever input the app is using, and the entire question is whether that input is really your mic.

1. Join a call with a friend, or start a recording in any app pointed at the same input device your call app uses.
2. Play loud game audio and say nothing.
3. Mute the mic at the hardware, wait a few seconds, and ask what happened to the game sound.

If the game vanished the moment the mic died, the sound was arriving through the air, and the next section is your fix. If the game kept playing through a muted microphone, no air is involved: something is wired wrong, and you can skip straight to the wiring section.

The air problem: speakers bleeding into your mic

This one is ordinary physics. Your microphone hears the room, the game is playing into the room through your speakers, so the game is in your signal right alongside your voice. It is the same mechanism that causes call echo, just with a game coming out of the speakers instead of a person.

1. Wear headphones. The complete fix. If the game never enters the room, the mic cannot pick it up, and there is nothing left to tune.
2. If speakers are non-negotiable, turn them down, angle them away from the mic, and move the mic closer to your mouth. A closer mic needs less gain, and less gain makes everything that is not your voice quieter in the signal.
3. Use a directional pickup pattern if your mic has one. A cardioid pattern rejects sound arriving from behind the mic, so point that dead side at the speakers.

If what the call actually complains about is hearing their own voices come back, that is echo rather than game bleed, a sibling problem with its own set of causes and fixes.

The wiring problem: an input that records everything you hear

Most sound cards ship a special recording device whose entire job is to capture what your PC plays. Realtek calls it Stereo Mix, Sound Blaster calls it What U Hear, and older drivers say Wave Out Mix. It is not a microphone. It is a copy of your playback, presented to Windows as if it were one, and if an app has it selected as its input device, that app transmits your game, your music, and your notification pings instead of your voice. That is exactly the configuration that survives the mute test: the physical mic goes dead and the game keeps flowing, because the mic was never in the path to begin with.

How patchd makes the two paths impossible to cross

patchd is a virtual audio mixer, a piece of software that sends sound between your apps and devices, and it deals with this entire page by giving every sound its own lane. The game plays into Patchd Cable, a virtual output, and shows up in the mixer as its own strip with its own live meter. Your mic is another strip. Destinations, meaning your headphones and the buses that other apps see as microphones, are colored pills on each strip: a lit pill is a route, an unlit pill is a wall.

Your call app selects Patchd Bus 1 as its microphone. From that moment the question of what the call can hear has a visible answer: exactly the strips whose cyan Bus 1 pill is lit, and nothing else.

The meters turn the mute test into a glance. The game strip dances while the mic strip's meter sits at the floor, which is the separation proved live: if game sound ever does show up on the mic strip's meter, it can only have arrived through the air, because no wiring reaches that strip. And if you record as well as talk, the same lanes split cleanly into tracks, which is the subject of how to separate game audio and voice.

A gate for the last few decibels

Once the wiring is clean and the headphones are on, a trace of bleed can still survive: leaky open-back headphones at high volume, or speakers you decided to keep. A noise gate on the mic strip handles the audible part of that. In patchd the gate is a free node in the effects rack on every channel, and its defaults are already aimed at this job. The threshold sits at -45 dB, the gate opens in about a millisecond when you speak, holds for 100 ms through the small dips inside a sentence, then releases over 150 ms. Bleed quiet enough to sit under that threshold simply never leaves your channel between words.

Be honest about the limit: a gate judges loudness only. While you talk it is open, and any bleed rides along underneath your voice, mostly masked but present. If what remains still bothers you, the layered approach in how to reduce background noise on your mic stacks suppression and the gate in the right order.

The short version

• Hardware-mute the mic first. Game gone means air; game still there means wiring.
• Air: wear headphones, then close the distance between mouth and mic so you can run less gain.
• Wiring: hunt the loopback. Deselect Stereo Mix or What U Hear everywhere, check the Windows default input, and switch off monitoring toggles.
• In patchd, lanes replace luck. The game strip feeds your ears, the mic strip feeds Bus 1, and the meters prove the two never touch.
• Gate the residue. The free noise gate mutes the quiet bleed between your words.

patchd makes this fix structural instead of forensic: every sound on its own strip, every destination an explicit pill, and live meters that show the separation working. It is in development now. Join the waitlist and we will tell you the moment it is ready to install.