An audio bus is a shared signal path in a mixing console or digital audio workstation into which several channels are routed, so that their combined signal can be processed, metered and controlled as one. In mixing, buses carry groups of instruments, effect returns, monitor feeds and finally the main stereo output, and they define how individual tracks become a finished mix.
The word comes from electrical engineering, where a bus bar is a conductor that collects current from several circuits. On an analog console it is a physical wire running across all channel strips; in software it is a summing point where samples from the routed channels are added together.
How an audio bus combines signals
A bus sums its inputs: at each sample, the values of every routed channel are added, and the result passes through the bus channel strip with its own inserts, fader and output assignment. Because the bus receives post-fader signals in most setups, the channel faders still set the internal balance of the group while the bus fader sets the level of the group as a whole.
Signals reach a bus in two basic ways. A channel’s output assignment sends its entire signal to the bus, removing it from the main mix unless the bus itself feeds the main mix. An aux send taps a copy of the signal at an adjustable level, leaving the original path intact, which is the standard method for shared reverb and delay effects.
In a workstation, internal summing usually happens in 32-bit or 64-bit floating point, which makes clipping inside a bus practically impossible, although the bus meter can still read above 0 dBFS. On analog consoles, the summing amplifier has a real headroom limit, typically around +20 to +28 dBu, so overloaded buses distort audibly.
Types of audio buses in a mix
Mixing systems use buses for several distinct jobs. The names vary between consoles and workstations, but the functions are consistent, as the following table shows.
| Bus type | How signals arrive | Typical purpose |
|---|---|---|
| Group or subgroup bus | Channel output assignment | Control drums or vocals as one unit |
| Aux or effects bus | Aux sends from channels | Shared reverb, delay or parallel processing |
| Monitor bus | Pre-fader aux sends | Headphone or stage mixes for performers |
| Master or mix bus | All groups and channels | Final stereo or surround output |
| Sidechain bus | Send to a detector input | Key a compressor or gate from another source |
| Stem bus | Output assignment by category | Print stems for delivery or mastering |
The mix bus, sometimes called the master bus or stereo bus, deserves special attention. Light compression or EQ placed there affects every element at once, which can glue a mix together but also magnifies any mistake across the whole song.
Audio bus compared with related routing tools
Buses are often confused with VCA groups and with simple track folders. The difference lies in whether audio is actually summed through a new path.
| Tool | Sums audio | Can hold processing | Main use |
|---|---|---|---|
| Audio bus | Yes | Yes, inserts on the bus | Shared processing and level control |
| VCA group | No | No | Move several faders together |
| Track folder | Depends on the DAW | Only when it acts as a bus | Visual organization |
| Aux send | Yes, as a copy | On the receiving bus | Feed effects or monitors |
A practical consequence is that post-fader sends follow a VCA move but not a bus fader move. If a vocal group is lowered on its bus fader, the reverb sends from the individual vocal tracks stay at the old level, and the vocals become wetter. A VCA instead lowers each channel fader, so their sends drop together with them.
Setting up buses in practice
A well-planned bus structure makes a mix faster and more consistent. A common template routes tracks into instrument groups, routes those groups into the mix bus and keeps two or three shared effect buses for reverbs and delays.
| Goal | Bus setup | Reason |
|---|---|---|
| Cohesive drum sound | All drum tracks to a drum bus with gentle compression | Treats the kit as one instrument |
| Consistent ambience | One or two reverb buses fed by sends | Places sources in a shared space |
| Parallel compression | Send to a bus with heavy compression, blend back | Adds density while keeping transients |
| Ducking music under dialogue | Dialogue bus keys the music compressor | Automatic level reduction |
| Stem delivery | Separate buses for dialogue, music and effects | Clean exports for later revisions |
Effect buses are normally set to 100 percent wet, with the dry signal coming from the original channel. A high-pass filter on a reverb bus, often around 150 to 300 Hz, keeps low-frequency reverberation from muddying the mix.
In workstations, plugin delay compensation must account for the latency of every insert on every bus. Most programs handle this automatically, but bus structures with sidechain paths or hardware inserts can still produce small timing offsets that cause phase problems between parallel paths.
Common bus mistakes
Most bus problems come from routing that is no longer understood. Large sessions accumulate buses that feed other buses, and a single wrong assignment can double a signal or remove it from the mix.
- Double routing: a track assigned to a group and also sent to the mix bus directly plays twice and creates phase or level jumps.
- Feedback loops: a bus that sends back into one of its own sources creates runaway oscillation.
- Pre-fader sends left by mistake keep effect levels constant when a track is muted or faded, so reverb tails remain audible.
- Heavy mix bus processing early in the mix forces every later decision to compensate for it.
- Unlabeled buses make sessions hard to revise, especially when another engineer opens them later.
Explained without jargon
An audio bus works like a collecting pipe. Several streams of sound flow into it, mix together and continue as one stream that can be turned up, turned down or treated as a whole.
Instead of adjusting eight drum microphones one by one, a mixer sends all of them into a drum bus and moves one fader for the entire kit. In the same way, many instruments can share one reverb by sending a little of their sound into the same effect bus.
A typical use case
A mixing engineer receives a pop song with 48 tracks. Before balancing anything, she builds a template: drums, bass, guitars, keyboards, backing vocals and lead vocal each go to their own group bus, and all groups feed the mix bus. Two reverb buses, a short room and a long plate, plus one tempo-synced delay bus, receive aux sends from the tracks that need space.
On the drum bus she adds gentle compression with about 2 to 3 dB of gain reduction, which makes the kit sound unified. When the producer later asks for the backing vocals to be slightly quieter in the chorus, she automates only the backing vocal bus fader. The client also needs stems, so each group bus is printed separately, giving six clean stems that sum back exactly to the approved mix.