Title: Automation lane cleanup with clean routing (Beginner)

Alright, let’s clean up automation in Ableton Live the way drum and bass projects actually need it: punchy, fast to navigate, and not a jungle of tiny lanes that you’re scared to touch later.

Because in DnB you’re constantly automating things like filter sweeps, bass movement, reverb throws, drum intensity, little pre-drop moments… and if you automate every plug-in on every track, your Arrangement view turns into automation spaghetti. Today we’re going to do the opposite: clean routing, smart control points, and just a few automation lanes that tell the story of your track.

By the end, you’ll have a small 16 to 32 bar section that feels production-ready, with a drum bus that has one or two macros for intensity, a bass setup that moves with just a couple macros, and a reverb throw on a return track that you automate using a send. Minimal lanes, maximum impact.

Before we touch any automation, we do the thing that saves hours later: we organize.

Step zero: prep and naming.

Create a DRUMS group. Inside it put Kick, Snare, Hats, and optionally a Break track if you like layering breaks. Then create a BASS group, with a Sub track and a Mid Bass track. And finally an FX audio track for impacts, risers, downlifters, fills, whatever.

Now color code. Drums in warm colors like orange or red. Bass in cool colors like blue or purple. FX in green or grey. And rename like you mean it: DRUMS BUS, BASS BUS, REV THROW, things that make sense instantly when you open Automation mode.

The goal is simple: when you hit A and automation shows up, you never have that moment of “Wait… what is this lane even controlling?”

Now we build the core concept of the lesson.

Here’s the mindset: groups are “where,” racks and macros are “what.”

Groups and buses are your routing and mix structure. That’s where audio goes, and where section-level changes should live.

Audio Effect Racks and macros are your control surface. That’s what changes over time, in a simplified, musical way.

So instead of automating six different parameters across four devices, we create two or three performance controls, and automate those.

Let’s start on the DRUMS BUS.

On the DRUMS BUS group track, drop an Audio Effect Rack. Inside it, add EQ Eight, Saturator, Drum Buss, and optionally Glue Compressor if you want some cohesion. This is a really classic, stock Ableton DnB-friendly chain.

Now we map key parameters to macros.

Macro one is your intensity control. Name it something clear like DRM: Bite. Map Drum Buss Drive to it, and Saturator Drive to it. Keep the ranges tight. Teacher tip here: macro ranges are your safety rails. You don’t want a macro that can destroy your mix if you draw one steep automation ramp. So set Drum Buss Drive maybe from plus 2 to plus 8, and Saturator Drive from 0 to plus 6 as a starting point. You can adjust later, but keep it musical.

Macro two is your tighten control. Name it DRM: Tight. Map EQ Eight’s low cut frequency, something like 20 hertz up to 60 hertz. And if you added Glue Compressor, map the threshold very gently so it tightens when you need it, not slams.

And right there, you’ve done something big: you just turned a whole pile of device automation into two lanes that make sense. Bite and Tight. That’s readable. That’s mixable. That’s DnB.

Now let’s build the reverb throw properly, because this is where beginners often create a mess.

Step two: the clean reverb throw with a return track.

Instead of putting a reverb on the snare channel and automating wet level and decay and EQ inside that insert… we’re going to make a return.

Insert a return track and name it REV THROW. On REV THROW, load Hybrid Reverb or the standard Reverb. Then put EQ Eight after it. That “after it” matters, because we want to shape the reverb tail, not the dry signal.

Set the return reverb wet to 100 percent, because returns are supposed to be fully wet. For a good starting vibe, set decay around 2.5 to 5 seconds, and pre-delay around 10 to 25 milliseconds so the snare stays punchy before the tail blooms.

Then in EQ Eight after the reverb, high-pass around 200 to 400 hertz to remove mud, and low-pass around 8 to 12k to darken the tail. In darker DnB you can go even lower, like 6 to 10k, to keep it ominous and not fighting your hats.

Now the magic: go back to your snare track, and automate the send to that return. In most default sets, that’ll be Send A. You only automate that send when you want the throw.

This is one of the cleanest automation habits you can build: automate sends, not insert wet knobs, for throws. It keeps your snare track simple, it keeps your CPU lighter, and it keeps your automation lanes obvious.

Arrangement idea: in bar 16, last snare before the drop, push the send up for a big blooming throw. Later, maybe bars 31 to 32, do an even bigger one going into a breakdown. It’s classic, and it reads clearly: “Snare Send A rises here.” No mystery.

Quick coach note: decide automation ownership early. If it’s a one-off musical gesture, like a quick filter flick on a single synth hit, that’s fine on the source track. If it’s a section-level vibe change, like “the whole drum kit gets more aggressive,” put it on the bus. If it’s space and ear-candy, that belongs on returns.

Now step three: bass movement without lane chaos.

We’ll do this on the Mid Bass track, because the sub needs to stay solid.

On MID BASS, add an Audio Effect Rack. Inside, add Auto Filter, Saturator, optionally Redux for grit, and Utility for width control.

Now map a few macros.

Macro one: BASS: Sweep. Map Auto Filter frequency to something like 120 hertz up to 2.5k. Map resonance slightly too, like 0.8 to 1.4, just enough to speak without whistling. This becomes your build energy, your “opening up” control.

Macro two: BASS: Grind. Map Saturator Drive from 0 up to plus 10, and if you used Redux, map downsample subtly. Again, subtle range. You want “more teeth,” not “broken radio,” unless that’s your style.

Macro three if you want it: BASS: Width. Map Utility width, but keep it conservative. Like 0 to 30 percent. And here’s the important DnB rule: keep the sub mono. So on your SUB track, put a Utility and set width to 0 percent. If you want to go further, you can also make sure everything below roughly 120 hertz stays mono using EQ and layering choices. The point is: movement happens in the mids, stability stays in the sub.

Now you can automate one or two macros and get a bass that evolves like a pro track, without twenty automation lanes.

Step four: automation lane hygiene. This is where the cleanup really happens.

Press A to toggle Automation mode.

Now, keep lanes minimal. A lot of people create “Show Automation in New Lane” for everything, and suddenly the track is five lanes tall. Instead, aim for one lane per track whenever possible. That’s why we made macros.

If you ever can’t find what’s controlling something, build this habit: click the device or parameter, look at the Info View in the bottom left, then press A and see what lane is active. That’s the fastest beginner troubleshooting loop. No guessing, no hunting.

Also, rename macros like you’re handing the project to someone else tomorrow. Use prefixes so the automation chooser list stays readable: DRM: Bite, DRM: Tight, BASS: Sweep, BASS: Grind, FX: Space. When you look at your automation lanes, it should read like a storyboard of the track.

Now step five: keep routing clean so automation stays clean.

The common beginner trap is duplicating reverbs and delays on every track, then automating all of them. It’s CPU heavy, and it’s impossible to keep consistent.

Instead, route like this:
Individual drum tracks go into DRUMS BUS. Individual bass tracks go into BASS BUS. Space effects live on returns. Master stays minimal. No heavy automation on the master chain. If you need the drop to feel bigger, do it at the source or bus level, not by cooking the whole track on the master.

At this point, you’ve got the core workflow. Now let’s do a mini practice build, and I want you to really stick to the constraint because it forces good habits.

We’re going to build a 16-bar loop.

Bars 1 through 8: steady rolling beat and bass.
Bars 9 through 16: a build into a drop.

Your tasks:
First, on DRUMS BUS, you already created the rack. Make sure Macro 1 is DRM: Bite, mapped to Drum Buss Drive and Saturator Drive.

Second, create the REV THROW return and automate Snare Send A on bar 16’s last snare hit. Big throw. Let it bloom.

Third, on MID BASS, use BASS: Sweep to open the filter through bars 9 to 16, so it feels like tension is rising.

Now here’s the challenge: automate only three lanes total.
Lane one: DRM: Bite on the drum bus.
Lane two: BASS: Sweep on the mid bass.
Lane three: Snare Send A for the reverb throw.

If you can make that feel like DnB with only three automation lanes, you’re doing it right. That’s not a limitation. That’s control.

A couple extra teacher-style upgrades you can try once that’s working:

One, use section blocks. Instead of drawing scribbly curves everywhere, make three plateaus: intro, build, drop. Then add two accents: a last-bar ramp and a first-hit snap. That keeps automation readable and musical.

Two, try call and response automation. For example, bars 1 to 4, let the bass move while drums stay stable. Bars 5 to 8, let drums tighten and bite while bass stays stable. Alternating attention makes the track feel active without stacking automation everywhere.

Three, a drop impact trick that sounds way more professional than adding more stuff: reduce space before impact. In the last half bar before the drop, pull down the reverb send, or shorten the return decay if you’re controlling the return. Then at the drop, put it back. Contrast equals impact.

And finally, a slightly more advanced idea for later: one macro, two behaviors. In a rack, make two chains, one clean and one heavy, and map the chain selector to a macro. Now you can morph from clean to heavy across sections with one lane. That’s huge for DnB transitions.

Let’s recap the main system.

Use groups and buses for clean routing and section-level control.
Use Audio Effect Racks and macros to reduce automation lanes dramatically.
Use return tracks for reverbs and delays, and automate sends for throws.
Name everything clearly, use macro ranges as safety rails, and keep a lane budget so your arrangement stays readable.
And remember the DnB fundamentals: sub stays mono, movement lives in the mids, and automation should be meaningful, especially going into drops and fills.

If you tell me what substyle you’re aiming for, like liquid, jump-up, neuro, or jungle, I can suggest a specific beginner macro set with exact parameter ranges and a five-lane automation plan for a full 32 to 64 bar arrangement.