A streamer can have pixel-perfect privacy and still leak everything through the speakers. Voice comms are the most personal audio you produce — real names, strategy, arguments, off-color jokes meant for three friends, not three thousand viewers. And audio leaks are harder to spot than visual ones, because you can't see your own leak.
How Audio Actually Reaches the Stream
OBS receives audio on two default channels: Desktop Audio (everything your PC outputs) and Mic/Aux (your microphone). The problem is structural: if Discord plays through Desktop Audio, Discord is the stream. Every call, every DM ping sound, every friend's comment about their day goes to your audience in perfect fidelity.
The common failure sequence:
- Streamer sets up OBS quickly. Desktop Audio on, "it captures the game, good enough."
- Discord runs through the same output as the game.
- Teammate joins voice. Now their voice — and everything said in comms — is broadcast.
- Nobody notices for hours, because the streamer hears their own comms normally and viewers only clip the funny parts.
The Partial Fixes (And Their Gaps)
"Push-to-talk and discipline." Controls your mic. Does nothing about your teammates' open mics, or Discord's notification sounds, or a friend's speaker bleed.
"Discord volume low in the mix." Viewers turn up their volume. Quiet leaks are still leaks.
"Use a separate Discord client / phone." Effective and miserable. Reading comms off a phone mid-fight costs real attention, and you lose push-to-talk on your mouse.
"OBS application audio capture." Modern OBS can capture per-app audio. Genuinely useful — but it routes what enters OBS. It does nothing for clipping software, Discord's own streaming features, or capture cards that take the whole audio feed.
The Two-Layer Audio Architecture
Layer 1 — routing: Game and music to the broadcast channel. Discord and system alerts to your headphones only. OBS application audio capture, or a virtual audio cable setup, achieves this. It decides what can reach the stream.
Layer 2 — surface protection: Even with correct routing, Discord's visual surfaces — the call window, notification banners with message previews, the ringing dialog — remain screen-level leaks. That's where OS-level cloaking and notification shielding take over, below the audio stack entirely.
Audio routing without surface protection leaves the window open. Surface protection without audio routing leaves the microphone open. You need both, and they're independent.
The Roommate Variable
One more leak most guides ignore: your teammates hear your room. An open mic picks up your phone call, your roommate, your TV. Routing and cloaking can't fix the physical layer — that's push-to-talk, gate settings, and a headset instead of speakers. Professional comms hygiene is the human layer doing its actual job: the last net, not the first wall.
The Bottom Line
Your audience should hear the game and you. Everything else — comms, pings, music, system sounds — is a routing decision you either make deliberately or make by accident. Make it deliberately, then protect the surfaces routing can't reach.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
