How to use group buses and sends to organize a mix

By Tongkit Leong · July 6, 2026 · 7 min read

A group bus collects several tracks — say, every drum track — and routes them through one shared fader and effect chain instead of the master output, so you can control a whole section of the mix with one move. A send does something similar for effects: it lets many tracks share a single reverb or delay instead of each carrying its own copy. In Tracks, both are set up in the mixer with no extra plugins.

Why a flat mix gets hard to control

A song with twenty tracks — four drum sounds, three vocal takes, a bass, five synth layers, some percussion — is manageable at the individual-track level for a while. Then you need the whole drum section to come down 1 dB for the verse, or you want every backing vocal to share the exact same reverb, or you want one compressor gluing the rhythm section together. Doing any of that one track at a time is slow and easy to get inconsistent — you nudge one hi-hat fader, forget the shaker, and the balance you had is gone.

Group buses and sends solve two different problems, and it helps to keep them separate in your head:

• A group bus is for tracks that should move together as a unit — turn the group up or down, or process the group with one EQ or compressor, and every track inside it follows.
• A send is for an effect that many tracks should share — one reverb, one delay — rather than each track running its own separate copy of that effect.

Tracks supports both directly in the mixer, alongside per-track EQ, compression, gating, and full automation.

Setting up a group bus

Step 1: Decide what belongs together

Group tracks by function, not by instrument type alone. Common groupings:

• Drums — kick, snare, hi-hat, percussion, drum loop layers.
• Bass — sub bass and mid bass layers, if you are running more than one.
• Vocals — lead vocal takes and doubles, kept separate from backing vocals if those need their own treatment.
• Backing vocals — harmonies and adlibs that should sit as one block behind the lead.
• Synths / music — pads, chords, arpeggios, and other harmonic layers that are not drums or vocals.

You do not need a bus for every category on every project — a simple beat might only need a drum bus. A dense arrangement with a dozen synth layers benefits from splitting those into two or three buses of their own.

Step 2: Create the bus and route tracks to it

In the Tracks mixer, add a group bus channel and route the output of each track in that group to the bus instead of straight to the master. The bus then feeds the master output on its own. Once routed, muting, soloing, or moving the bus fader affects every track feeding into it at once.

Step 3: Process and control the group as one

With the group routed, you get several things for free:

• One fader for the whole group. Pull the drum bus down 1–2 dB for a verse and every drum track drops together, in proportion — the balance between kick and snare stays exactly as you set it.
• One EQ or compressor for glue. A light compressor across the whole drum bus (a slow attack, fast release, 2–4 dB of gain reduction) makes the kit feel like one cohesive instrument instead of several separate hits. This is a different job from compressing each drum individually — bus compression glues, track compression shapes.
• Bus-level automation. If the backing vocal bus should duck slightly under the lead vocal in a busy chorus, automate the bus fader once instead of automating every backing vocal track that feeds it. See how to use automation to make your mix move for the mechanics of drawing that curve.

Setting up a send

Step 1: Create a send channel for the effect

Add a reverb or delay channel and set it to 100% wet — no dry signal at all. This channel exists purely to hold the effect; nothing plays through it directly. Instead, tracks route a portion of their signal to it using a send knob.

Step 2: Send each track at its own level

On any track, turn up its send knob to route some of that track's signal into the shared reverb or delay. Because the reverb itself is 100% wet, only the amount you dial in on the send actually reaches it — the track's own fader and dry signal are untouched. A vocal might send at a moderate level, a pad at a higher level, and the kick and bass at none at all.

The advantage over giving every track its own individual reverb: every instrument that shares the send sounds like it is sitting in the same physical space, because they are all going through the exact same reverb tail. That cohesion is hard to fake by matching settings across several separate reverb instances by hand.

Step 3: Use more than one send for different effects

Most mixes benefit from at least two sends — a reverb send for space and a delay send for rhythmic echo. Route the lead vocal and lead synth to the delay send at a musical subdivision (an eighth or quarter note synced to your project tempo), and route pads, backing vocals, and atmospheric layers to the reverb send. Keep the kick, snare, and bass out of both, or nearly out — low-frequency reverb and delay tend to smear the low end and make a mix feel washed out.

Bus vs. send: which one do you need?

They are not competing tools — most mixes use both at once. Use this as a quick check for which one applies:

• If the question is "how do I control the volume or tone of a whole section together," you want a bus.
• If the question is "how do I get several tracks to share one reverb or delay," you want a send.
• A bus can also feed a send — for example, routing the entire backing vocal bus to the reverb send at once, instead of setting an individual send level on each backing vocal track.

Common mistakes

• Routing everything to one bus. A single "everything" bus defeats the purpose — you lose the ability to move drums independently of vocals. Split buses along the lines of what actually needs to move or be processed together.
• Setting the send channel to anything less than 100% wet. If the send channel itself has dry signal mixed in, you lose independent control over how much dry vs. wet each track carries, and levels get harder to reason about.
• Forgetting a track is routed to a bus. If a track sounds unexpectedly quiet or loud, check whether its output is going to a bus you have since turned down or muted, rather than assuming the track's own fader is wrong.
• Over-compressing the bus. A bus compressor is for gentle glue, not heavy dynamic control. If it is pumping or you can hear it working, back off the ratio or raise the threshold.

Frequently asked questions

Do I need buses and sends for a simple two-minute beat?

Not necessarily. If you only have five or six tracks, individual control is often fast enough on its own. Buses and sends start paying off once a project grows past ten or so tracks, or once you find yourself repeating the same fader move or effect setting across several tracks.

Can I automate a bus the same way I automate a single track?

Yes. A bus fader, its EQ, and its compressor all expose the same automation lanes a regular track does. See how to use automation to make your mix move for the step-by-step on drawing a curve.

Is a send the same thing as sidechain compression?

No. A send shares an effect like reverb or delay across tracks. Sidechain compression uses one track's signal to trigger volume ducking on another track, usually for the "pumping" effect heard in dance music. See sidechain compression explained for that separate technique.

Should the master bus be treated like any other group bus?

The master bus is the final stop before export, so treat it more carefully — light glue compression and gentle EQ are reasonable there, but heavy processing belongs on individual tracks or group buses upstream. See how to mix a track: EQ, compression, and reverb basics for the fundamentals that should already be in place before you start grouping.

Can I do this in the Tracks browser studio?

Yes. Tracks supports group buses, reverb and delay sends, per-track and per-bus EQ and compression, and automation on any of it, directly in the browser with no plugins and no download. Open the studio and route a few tracks to a bus or a shared send to try it. Nothing is uploaded — your project stays on your device.