PullzeAudio / Journal

Discord Ducking Without Losing Game Audio

Ducking steps your game mix back whenever a voice arrives, which keeps callouts readable over gunfire, but pushed too far it takes the sounds you still need with it. Here is how to enable it, keep the reduction moderate, and get the trigger clean.

A squad-mate starts relaying a rotation and the rifle fire swallows the second half of it. Now you are watching a doorway nobody is walking through. The feature that addresses this is ducking: the game mix steps back whenever a voice comes through, so speech stays on top. Plenty of people never switch it on at all, and plenty more push it far enough that the audio they still need disappears instead. The following walks through the middle ground.

Locate Discord’s Ducking Control

Open Discord, then User Settings, then Voice & Video. Further down that page is a block describing how the app handles sound from everything else running on the machine. Both ducking controls sit inside it: a switch that steps other audio back while somebody speaks, and a slider deciding how far back it goes. Nothing else is involved. The rest of the tuning here is only about making that pair behave in a way you can live with.

Leave The Slider Some Headroom

Your hand will want to pull that slider to the top, on the theory that voices should win every time. Pulling it there costs more than it gives. When the reduction is severe, each bit of chatter from the call mutes the game for a beat or longer, and that beat is when somebody pushes through your flank. A mechanical keyboard clicking two seats over can trigger it just as easily. Land somewhere in the middle, where a shout is easy to pick out against gunfire but the rest of the mix does not vanish every time a squad-mate clears their throat.

Fix The Real Problem: Mics That Hear The Room

The reduction should react to voices and to nothing else. If a headset is also hearing a desk fan, a chair squeak, or someone typing, then your game audio dips for signals carrying no information at all. That is a microphone problem wearing a ducking costume. Have everyone switch on Discord’s built-in suppression and set sensitivity manually instead of trusting the automatic pick, and ask people to keep their mic away from the keyboard. Tidy inputs are what make the reduction land on cue rather than at random.

Priority Speaker When You Call The Plays

There is a second control, Priority Speaker, which sits apart from the general ducking above. Its purpose is different: while your own mic is live it steps everyone else down, which suits whoever is running the plays and cannot afford to be talked over. Give it a hotkey close to your movement hand, in the same spirit as any other ability you fire by reflex.

  • Enable ducking in Voice & Video, with the slider at a middling value rather than the top.
  • Sort the inputs first: suppression enabled, sensitivity chosen by hand, no mic sitting beside a fan or a keyboard.
  • Put Priority Speaker on a key if you are the one giving orders.
  • Run it live in a custom match and note which sounds disappear while people talk.

Prove It In A Live Match

A menu makes everything feel settled; a firefight with three voices overlapping does not. Set up a private match, get a friend to call as the shooting starts, and retune from what you actually hear. The quality of the source signal matters here too. PullzeAudio is built to hold footstep and cue detail together while ducking pushes the rest of the mix down and releases it, so the two behaviours are not working against each other halfway through a round. Spend an evening getting this right and the calls survive, and so do the footsteps.