Sends & Buses: How Pros Route Their Mixes (And Why You Should Too)

Walk into any professional recording studio, look at the mixing desk, and you'll see a routing setup that would make a beginner's head spin. Sends here, buses there, groups nested inside groups — and that's before they've even started mixing. But here's the thing: there's a logic to it all, and once you understand it, you'll never look at a flat list of tracks in Ableton the same way again.

Most bedroom producers default to stacking all their effects directly on individual channels. One reverb here, another one there, a different delay on each synth. It feels intuitive but it's actually making your life harder in almost every way — more CPU usage, less cohesive sound, harder to automate, impossible to change your mind later. Proper routing using sends and buses fixes all of this.

Sends and Returns vs Buses and Groups: What's the Difference?

These terms get used interchangeably sometimes, which causes confusion. Let's be precise:

Sends and Returns: A "send" is a signal path that takes a copy of your audio and routes it to a shared effects unit (the "return" track). The original signal continues on its way unchanged — you're adding a copy of it to the effects chain, not replacing it. This is fundamentally a parallel signal path. You're blending wet and dry.

Buses and Groups: A "bus" or "group" collects multiple signals together and processes them as one. When you route your kick, snare and hi-hats all into a "Drum Bus" group, everything that happens on that bus channel happens to all three simultaneously. Unlike sends, this is a serial path — the combined signal goes through whatever is on the bus, and that's what you hear.

In Ableton's terminology: Return Tracks are your sends/returns. Audio Tracks with other tracks routed into them function as buses/groups (though Ableton also has dedicated Group Tracks, created by selecting tracks and pressing Cmd/Ctrl+G).

Ableton's Return Tracks Explained

In Ableton's Session and Arrangement view, Return Tracks appear to the right of the main track area (in Session) or at the bottom of the track list (in Arrangement). By default you'll have Return A and Return B — typically assigned to reverb and delay respectively, though you can delete these and set them up however you like.

Each regular track has Send knobs (the small rotary controls visible when you look at a track) — one for each Return Track. Turn up Send A and you're routing a proportion of that track's signal to Return A. The Return Track's fader then controls the overall level of the effects that come back into the mix.

Key points to understand:

• Return tracks always output to the Master track
• You can have up to 12 Return Tracks in Ableton
• Each Return Track can have its own chain of effects
• Return tracks can send to other Return tracks (useful for chaining effects)

Why You Never Put Reverb Directly on a Channel

This is one of the most important things any mixing engineer will tell you. When you put a reverb plugin directly on an instrument channel, a few bad things happen:

1. CPU waste. Each instance of a CPU-hungry reverb like Valhalla Room or FabFilter Pro-R costs processing power. If you have reverb on 12 different channels, you're running 12 separate reverb engines. If you use one Return Track with reverb, you're running one engine — and routing any number of channels to it for free.

2. Incoherent sound. If every instrument in your mix is in its own unique reverb space, the mix sounds like it was recorded in twelve different rooms. When multiple instruments share the same reverb return, they all sound like they exist in the same acoustic environment. This is what creates the "glue" in a professional mix.

3. Loss of flexibility. With reverb directly on a channel, changing the reverb character means modifying that one instance. With a Return Track, changing the reverb affects everything routed to it simultaneously. Want to change from a small room to a large hall? One adjustment.

4. Can't automate cleanly. Automating the reverb send level on a Return Track is clean and easy. Automating the dry/wet on multiple individual instances is a nightmare.

Pre-Fader vs Post-Fader Sends

In Ableton, you can right-click any Send knob to toggle between "Pre" and "Post" fader modes. The difference is significant:

Post-fader (default): The send amount is proportional to the channel fader level. Pull the fader down and the send to the reverb also reduces proportionally. This is what you want in most mixing situations — as you lower an instrument in the mix, its reverb tail also gets quieter. The overall effect level stays consistent relative to the dry signal.

Pre-fader: The send is taken before the fader, so the send level is independent of the channel fader. You can fade a channel to silence while its reverb tail continues at full level. This is extremely useful for creative effects — fade out a synth completely while a huge reverb trail continues washing through the mix. Also used in live sound for monitoring (you want the monitor mix to stay consistent regardless of the front-of-house fader position).

For standard music production, post-fader is almost always what you want. Use pre-fader intentionally as an effect.

Building a Reverb and Delay Send Setup

Here's how I typically set up sends in a new Ableton project:

Return A — Short Reverb: A small room or plate reverb. Something bright and tight with a short decay (0.5-1.5s). This is for snares, percussion, adding presence to synths. Keep the reverb's pre-delay at 10-25ms to separate the transient from the wash.

Return B — Long Reverb: A larger hall or room. 2-4 second decay. This is for pads, long synth tails, creating depth and space. Often used more subtly — just a touch on pads to make them feel three-dimensional.

Return C — Delay: A tempo-synced delay, usually 1/8 or 1/4 note. Ping-pong or stereo. This adds width and movement to leads and melodic elements. Set the feedback to around 30-40% and make sure there's a high-pass filter on the delay output to prevent bass buildup.

Return D — Parallel Compression: A heavily set compressor for parallel drum processing (see our parallel compression guide). No reverb or delay here — just compression for density and glue.

This four-return setup covers 80% of what you need in a typical EDM mix. Add more returns for specific effects as the track demands.

Drum Bus, Vocal Bus and Mix Bus Routing

Beyond sends and returns, grouping tracks into buses is essential for efficient mixing. Here's a typical EDM mix routing structure:

Drum Bus

Route all drum elements (kick, snare, claps, hats, percussion) into a group. On the group bus, you might have: a gentle compressor for glue (2:1, slow attack, catching maybe 3dB of reduction), a transient shaper to add or reduce the punch, and a subtle saturation device to add harmonics. Automation on this one fader controls all your drums simultaneously during drops and builds.

Synth/Melodic Bus

All your melodic synths, leads, and chords routed together. This makes it easy to drop all melodic elements simultaneously in a breakdown or ride the level as a group.

Bass Bus

Sub bass, mid bass, and any bass layers grouped together. Useful for controlling overall bass level and applying multiband limiting to keep the low end in check.

Mix Bus (Master)

The master fader in Ableton is your mix bus. This is where mastering-style processing lives — a very gentle compressor (2:1, maybe 1-2dB gain reduction), a linear phase EQ for broad tonal shaping, a limiter at the end to prevent clipping. Keep processing on the master very light during mixing — save the heavier stuff for mastering.

Parallel Processing via Sends

Because sends copy your signal to a Return Track while leaving the original intact, they're perfect for parallel processing of any kind — not just reverb and delay. Here are some creative uses:

Parallel Saturation: Route your entire drum bus to a Return Track with a heavily saturated chain (Saturator → Compressor → high-pass filter). Blend in just a touch of this for harmonic excitement on your drums without touching the original signal.

Parallel EQ: Route a bass track to a Return with a mid-range boost EQ. This adds frequency content to the parallel path that you blend in for more presence, without changing the character of the original dry signal.

Width Send: Create a Return Track with a Haas effect (a very short delay on one side) and a stereo imager. Route mono elements to this return to add controlled width while keeping the original centred and mono-compatible.

CPU Savings: Why Routing Matters for Performance

On a modern computer, a single instance of a CPU-hungry reverb like Convolution Reverb Pro might cost 10-15% of your CPU budget. Run it twelve times and you're in trouble — buffer dropouts, clicks, and pops. Run it once as a Return Track and route twelve channels to it — same sound, fraction of the CPU cost.

The same logic applies to any processor that multiple tracks share. One master EQ, one master compressor, one master limiter — not dozens of individual instances doing the same job.

Proper routing is also essential for recall. If you need to revisit a project three months later, a well-organised routing structure makes it immediately obvious what everything is doing. A flat list of tracks with effects everywhere is an archaeological dig. A neat bus structure with labelled groups is self-documenting.

Take the time to set up your routing properly at the start of each project. It's one of those things that feels like overhead but saves you hours further down the line — and produces a genuinely better-sounding mix.