Routing & Workflow
What is a bus in mixing? Routing explained properly
On this page7 sections
A bus is a channel that other channels feed into. That is the entire definition. Everything useful about session structure follows from it.
Route eight drum channels to a bus and you get one fader for the whole kit, one place to process the kit as a unit, and one signal the rest of the mix reacts to.
Bus, send and group
These three words get used interchangeably and they are not the same thing.
| Term | What happens to the signal | Typical use |
|---|---|---|
| Bus | The channel’s output goes here instead of to the master | Grouping, shared processing |
| Send | A copy is split off at an adjustable level; the original continues | Reverb, delay, parallel effects |
| Group | A DAW feature that links faders or folds channels visually | Organisation, sometimes also a bus |
The practical distinction: a bus carries all of the signal, a send carries some of it while the original keeps going.
When you want the whole drum kit compressed together, that is a bus. When you want four instruments sharing one reverb, that is a send — covered in when to use send channels.
Why bus processing behaves differently
This is the part worth understanding.
A compressor on a snare channel reacts to the snare. A compressor on the drum bus reacts to the sum of the kick, snare, hats, toms and room mics. So when the kick hits, the bus compressor reduces gain on everything — including the snare, the hats and the room.
That interaction is what “glue” means. The parts move together because one processor is applying the same gain change to all of them at the same instant. It makes a kit sound like one instrument rather than eight recordings.
It also explains the failure mode: too much bus compression and the whole kit ducks on every kick, so the mix pumps and the snare feels weaker every time the kick lands.
The same logic applies to saturation, EQ and anything else on a bus. You are processing a relationship, not a sound.
A structure that works
A four-bus layout covers most productions:
- Drums — everything percussive
- Bass — bass, sub, any low-end layers
- Instruments — synths, guitars, keys, pads
- Vocals — lead and backing
Each of those goes to the master. That gives you four faders to balance the whole record, four places to apply group processing, and a fast way to check what any section contributes by muting it.
Add more buses only when you need them. A backing-vocal bus inside the vocal bus is useful when you have twelve stacked harmonies. It is pointless when you have two.
Why the structure helps beyond processing
Balance becomes fast. Adjusting one drum bus fader is one decision instead of eight coordinated ones, and it preserves the internal balance you already set.
Automation becomes simple. Riding the instrument bus down under the chorus vocal is one automation lane instead of six.
Comparisons become possible. Mute the instrument bus and hear what the rhythm section is doing. That is much harder without structure.
Printing becomes practical. A finished bus is one thing to render when a project gets heavy — see printing effects to audio.
Gain staging through buses
Every stage where signals sum is a stage where level increases. Eight drum channels summing into a bus produce a hotter signal than any one of them.
Two habits prevent most of the trouble:
- Keep channel levels sensible before they hit the bus, so the bus is not receiving something extreme.
- Use the bus’s own output gain to bring the level back to where the next stage expects it.
If your master is clipping and you have not touched it, the summing along the way is usually why.
Common mistakes
Buses with nothing on them. If a bus has no processing and never gets a fader move, it is adding routing complexity for no return. Delete it.
Processing the bus before balancing the channels. Bus processing reacts to the sum, so it has to be set on a sum that resembles the final one. Balance first.
Duplicating the same plugin on every channel and the bus. Pick where the job belongs. Usually the bus, because one instance replaces eight.
Routing sends into buses accidentally. A reverb return that feeds the drum bus will be compressed by the drum bus compressor. Sometimes that is what you want. Usually it is a mistake nobody notices for an hour.
Where to go next
- What is a drum bus for the most important one.
- How to build a drum bus for the step-by-step.
- When to use send channels for the other half of routing.
If you want per-band routing rather than per-channel — splitting one source into frequency bands and treating each one as its own path — SPC Lumen Relay does that with internal mixer tracks and nested effect racks, which is a bus structure inside a single plugin.
Frequently asked questions
What is an audio bus?
A bus is a channel that receives the output of other channels and sums them into one signal. Processing on the bus affects everything feeding it, and the fader controls all of them together.
What is the difference between a bus and a send?
A bus normally carries the whole signal: the source's output goes to the bus instead of directly to the master. A send carries a copy at an adjustable level while the original continues on its own path. Buses are for grouping, sends are for shared effects.
Why does bus compression sound different from channel compression?
Because the bus compressor reacts to the summed signal, so every source influences the gain reduction applied to all of them. That interaction is what people mean by glue, and it is also why heavy bus compression can make a mix feel unstable.
How many buses should a mix have?
As many as give you useful control and no more. Drums, bass, instruments and vocals is a common four-bus structure. Buses that never receive processing or a fader move are just extra routing.
Does routing through buses affect sound quality?
Summing itself is transparent in a modern DAW. What changes the sound is the processing you place on the bus and any gain changes along the way.