Why Windows makes this hard
By default, Windows has one job when it comes to output: pick a single default device and send everything to it. Your game, your browser, your music, and your voice call all pour into the same stream and out the same headphones. That is fine until you want two apps to go to two different places at once, and then Windows quietly fights you.
The usual thing people reach for is the built-in Volume Mixer (right click the speaker icon, open Volume mixer). It looks promising because it lists your apps one by one. But look closer: all it does is set a level for each app. It cannot send one app to your headphones and another to a recorder. Newer Windows builds added a per-app output picker in Sound settings, and that is a real step forward: expand an app's row, Spotify say, and an Output device dropdown appears. Yet the picker only chooses between devices that already exist. There is no way to build a fresh, separate destination for a single app, which is exactly what you need the moment you want to record one program cleanly or feed one app into a stream.
What routing per app actually means
Routing is not the same as volume. Volume answers how loud. Routing answers where does this sound go. Real per-app routing means you can take one program, say a music player, and send it to your speakers and your stream, while a private call goes only to your headphones and never touches the recording. If you want the deeper background, we wrote a plain-English explainer on what audio routing is.
The manual workaround: a virtual cable per app
Before dedicated tools existed, the classic fix was the virtual audio cable: a fake sound device that carries audio between programs instead of to a speaker. The recipe goes like this. Install a virtual cable so a new playback device appears. In the app you want to isolate, set that cable as its output. Now that one app plays into the cable instead of your speakers. Then open something that can listen to the cable, a recorder or broadcast tool, and point it at the cable as an input.
It works, but the pain adds up fast. Each app you want to separate needs its own cable, so you end up installing several and trying to remember which is which. The instant an app plays into a cable, you stop hearing it yourself, so you have to build a second path just to monitor your own audio. There are no levels, no effects, and no picture of the whole setup. One wrong device selection and something goes silent with no obvious reason why. It is a workaround, not a workflow.
The clean way: pull each app onto its own strip
Patchd is a virtual audio mixer built around this exact problem. Instead of juggling loose cables and hidden device menus, every source lives on its own strip, and you route it by clicking a colored pill. Two strips are always present, Desktop (all your system audio) and Communications (your chat apps), and the rest you add: your mic, plus virtual cables that each pull one app onto its own strip. Every destination owns one fixed color, so the routing is something you can see rather than something you have to remember.
Here is the flow, concretely. Add a virtual cable strip for the app you want to separate, then go back to that Windows per-app picker and set the app's output device to Patchd Cable 1 so its sound lands on that strip and nowhere else. Now that program has a dedicated row with its own fader, its own meter, and its own effects. Under the HW header on that strip (HW is short for hardware, meaning your real headphones or speakers), click the green pill showing your headphones' device name to send it to them so you can still hear it. Under the BUS header, click the cyan Bus 1 pill to also send it to a bus, a virtual output that other apps can pick up as a microphone. You just split one app two ways with two clicks, and both routes are lit in their colors.
Send a bus into another app as a microphone
The part that makes this genuinely useful: because a bus shows up as a microphone inside another app, once you have a source routed to Bus 1 you can open your voice chat app and select Patchd Bus 1 as your microphone. Whatever you route to that bus, one app, a blend of apps, your voice, becomes the input that program hears. For a stream, give each source a bus of its own and add each bus to OBS as its own source, so your game and your mic arrive on separate faders: OBS audio setup. Leave a private call off every bus and it stays out of the broadcast entirely.
Because each route is a single colored click, changing your mind is easy. Want the music out of the recording but still in your ears? Turn off its cyan bus pill and keep the green one lit. Nothing gets reinstalled, nothing goes mysteriously silent, and you can read the whole picture the entire time.
What you get for free
The free tier of Patchd is the full mixer, not a demo. You get your mic plus four virtual cables (on top of Desktop and Communications), three hardware outputs, six buses, color-coded routing, per-app volume, and a real effects rack on every channel. That is enough to separate four apps, monitor them yourself, and feed clean buses into your chat and capture tools.
Per-app routing on Windows is not really a setting you flip; it is a pipeline you build. Patchd just makes that pipeline visible and quick. If you are wiring up a broadcast from scratch, the full walkthrough lives in our streaming audio setup guide, and if noise is your real problem, see how to clean up your mic first.
Get early access
Patchd is in open beta now, and if you clear the terms your invitation arrives straight away, so you can stop fighting the default output and send every app exactly where it belongs.