LearnAudio foundations

What is an audio bus?

An audio bus is a virtual output you route one or more sources into, so you can treat a whole group of sounds as a single stream and hand that stream to another app.

The short answer

An audio bus is a destination you send sound to. On a physical mixing board, a bus is a shared wire that several channels can feed at once, so you can control the whole group with one fader. In software the idea is the same, except the wire is virtual. You point a few sources at a bus, and everything you send arrives there mixed together as a single stream.

The key trick is what a bus does next. A software bus can present itself to the rest of your PC as if it were a real recording device. So the mix you build, your voice plus your game plus your music, shows up as a microphone that any other app can select. You assemble the sound you want, and hand the finished bus to OBS, to a call, or to a recorder as its input.

Hardware outputs versus buses

3 hardware outs
3 buses
One source, both kinds of destination. Playback lit green plays out loud for your ears; Bus 1 lit cyan collects the same sound into a feed another app can pick up.

It helps to split every destination into two kinds. A hardware output is a real device you can hear: your headphones, your speakers. When you route a source there, sound comes out of a physical thing. A bus is a virtual output. Nothing plays out loud when audio hits a bus; instead it collects into a feed that another program can pick up.

Because these are two different jobs, a single source can go to both at once. You send your game to your headphones so you can play, and to a bus so your stream captures it, at the same time. Getting comfortable with that split is most of what audio routing is really about.

Why a bus appears as a microphone

This is the part that makes buses genuinely useful. Windows lets programs choose a recording device, and it does not care whether that device is a physical microphone or a virtual one. A bus registers itself as a recording device, so from the perspective of OBS or Discord or Zoom, the bus simply looks like another mic in the dropdown.

your recording app's settings
To the rest of your PC, a bus is just another mic. Patchd Bus 1 sits in the input list beside the real microphone, and selecting it hands the app the exact mix you routed onto that bus.

That means you get to decide, precisely, what the far side hears. Instead of handing a call your raw microphone and hoping for the best, you feed the call a bus. Onto that bus you put a cleaned-up copy of your voice, and maybe a shared music track, and nothing else. Your notifications, your private second monitor audio, a side conversation, none of it reaches the bus unless you route it there.

  • Submix bus. A bus that carries a subgroup rather than the whole show. Group all your game and app sounds onto one submix so a single control rides them together.
  • Program bus. The finished mix you send out, the one an app treats as its microphone.
  • Monitor path. A hardware output you keep for your own ears, separate from anything you send away.

Buses in patchd

Bus 1
The bus is a strip of its own. A cyan Bus 1 header, a live meter carrying the mix, and no device picker, because the bus IS the device.

In patchd, buses are first-class. You get three virtual buses on the free tier, and every strip in the mixer can route to any of them with a click. The buses are color-coded, cyan, violet, and magenta, so a glance at a channel tells you which mix it is feeding. Hardware outputs live in their own colors, green, amber, and coral, which keeps the thing you hear visually distinct from the thing you send.

Since each bus shows up as a selectable microphone, a common setup is one bus for your broadcast, one for a call, and one for a recording, each carrying a different combination of sources. You build those combinations by clicking routing pills on the strips, not by wiring cables in your head. If you want a worked example of splitting one app onto its own path, see how to route audio per app.

A bus is one piece of the mixer

A bus on its own is just a pipe. What makes it powerful is everything the mixer does before the sound reaches it. Each channel in patchd has a free effects rack, a noise gate, EQ, compressor, de-esser, AI noise suppression, saturator, and more, that you reorder by dragging. So the voice that lands on your bus can already be gated, evened out, and cleaned of hiss before any other app ever sees it.

The engine runs in real time, and the processing it adds through a bus is small, about 10.7 ms at a 512 buffer, and smaller ASIO buffers take it lower, which stays comfortable for live use. To see how the whole picture fits together, channels, effects, outputs, and buses, start with what a virtual audio mixer is.

The takeaway

A bus is a virtual output. You route sources into it, the mixer shapes them, and the bus hands the finished stream to another app as if it were a microphone. That single idea is what lets one PC send a clean, deliberate mix to a stream, a call, and a recording all at once, without any of them stepping on the others.

patchd gives you three color-coded buses free, on top of an effects rack on every channel. It is in development now. Join the waitlist and we will let you know the moment it is ready to install.

every signal has a destination

Stop fighting your audio.

Whether you are producing, podcasting, streaming, or gaming, patchd is the audio mixer your setup deserves. Join the waitlist to be the first to know when it ships.

Already convinced? See pricing