Play music on stream that only you can hear

Why music on the broadcast costs you

Nobody gets in trouble for listening to music while they stream. The trouble starts when the music rides along on the broadcast. Platform copyright systems scan VODs and clips for recognizable tracks, and when they find one the result is some mix of muted sections, deleted clips, demonetization, and strikes against the channel. The frustrating part is that the music was never for your viewers in the first place. It was for you, to stay in the pocket during a six hour session, and it leaked onto the recording only because everything on your PC was funneled into one output.

So the goal is precise: your ears get game, voice chat, and your full music library. The broadcast gets game and mic, and the music never touches it. Not muted, not turned down low, simply never present on the feed your streaming software captures.

The fix is routing, not willpower

Windows by itself pushes everything to one default output, which is why your desktop capture picks up whatever you happen to be playing. A virtual audio mixer changes the shape of the problem. Every source becomes its own strip, every destination has its own routing button on that strip, and a destination receives exactly the sources you route to it. Different mixes differ by which sources are included, not by fader tricks. That means the private music mix is not something you maintain during the stream. You build it once, and the broadcast cannot hear the music for the same reason your neighbor cannot: no route exists.

The rest of this guide uses patchd, a Windows mixer built around this inclusion model. patchd is in development, so the steps below describe how the workflow works when it ships; the Windows level workaround near the end is something you can try today.

Step 1: give your music app its own strip

Out of the box, your music app plays into the Desktop strip along with the game and everything else your system plays. As long as it lives there, it goes wherever Desktop goes, and Desktop is exactly what your stream needs. So the first move is separation: pull the music app onto its own strip with a virtual cable, a small piece of software that carries one app's sound into the mixer as its own channel. Point your music app's output at the cable in Windows' per app sound settings, and it leaves the Desktop strip and shows up in patchd on a strip of its own, with its own volume slider and meter. The walkthrough in how to route audio per app on Windows covers the per app part in detail.

On patchd's free tier you get your mic plus one virtual cable on top of the fixed Desktop and Communications strips. One cable is exactly what this setup needs: the music app is the thing worth isolating. The Studio tier raises that to four cables in total if you also want the game or a browser on separate strips.

Step 2: light your headphones, leave the stream bus dark

Every strip in patchd carries a row of colored routing pills under two headers: HW for real hardware outputs like your headphones, and BUS for virtual outputs that other apps can treat as a microphone. On the music strip, light the green pill for your headphone output. Do not light the cyan pill for Bus 1, the bus your stream will use. That is the entire trick. The lit green pill is why you hear your library; the unlit cyan pill is why your viewers never will.

Notice what this is not: it is not a second volume you have to manage. Each strip has one fader for its level and on or off routing per destination. There is nothing to ride down when you go live and nothing to forget to mute, because the music was never on the broadcast path to begin with.

Step 3: build the broadcast mix and hand it to your streaming app

Now route the sources your viewers should hear onto Bus 1: the Desktop strip for your game and the mic strip for your voice. A bus in patchd can present itself to other apps as a microphone, so in your streaming software you select the patchd bus as your mic input and disable its own desktop capture. Your broadcast now receives one finished mix that contains game and voice and structurally cannot contain the music. If the bus as mic idea is new, the use any app as your microphone guide walks through it from the other direction.

The same pattern handles private voice chat. patchd's fixed Communications strip carries your chat apps, and routing it to your headphones while leaving it off the stream bus keeps a group call in your ears and off the VOD. The stream hearing Discord audio fix is this exact move with a chat flavored problem.

The honest edge: music inside the game

One limit worth being clear about. This technique isolates a separate music app. If the music is coming from inside the game itself, a licensed soundtrack, an in game radio station, a rhythm section in the gameplay, then it is part of the game's own audio and it travels with the game on the Desktop strip. No external router can split a game's music from its gunfire, because the game mixes them together before Windows ever sees the sound. For those titles, use the game's own settings: most games with licensed music offer a streamer mode or a music volume slider precisely because of copyright scans.

What you can do on Windows today

While patchd is in development, Windows itself offers a rougher version of the split that works right now if you have two output devices. Open Settings, then System, then Sound, then Volume mixer, and set your music app's output device to something your streaming software does not capture, for example USB headphones while your desktop capture follows a different default device. It works, but it is fragile: some apps ignore the per app assignment until restarted, you get no meters and no single view of what goes where, and one wrong default device change puts the music back on the broadcast silently. The mixer approach exists because the stakes here are strikes, not just annoyance.

Where patchd is today

patchd is built around the inclusion model this guide leans on: strips for every source, color coded routing pills for every destination, and a free tier that covers this exact setup with your mic, one cable for the music app, three hardware outputs, and three buses. It is in development now. Join the waitlist and we will tell you the moment it is ready.