Welcome back. This is an advanced Ableton Live lesson, drum and bass edition, and we’re doing something that separates “I can make a loop” from “I can finish a record.”

Automation lane cleanup from scratch, using only stock Ableton devices.

Because in DnB, automation is the lift. It’s the tension, the drop control, the bass movement, the throws, the micro-phrasing. But the reality is, once a project gets serious, your automation view turns into a crime scene. Thirty, fifty, sometimes a hundred lanes. Conflicting moves. Hidden clip envelopes. And that classic moment where you’re like: why is this not hitting… and the answer is buried in some lane you forgot existed.

So today we’re building a clean, readable automation architecture. The goal is simple: fewer lanes, more impact, and you can understand your whole song’s movement in seconds.

Before we touch anything, set the scene.

Set your tempo in the classic DnB pocket, 172 to 176. I’ll use 174. Go to Arrangement View. Turn on Automation Mode with the A key. Then set your grid to Fixed Grid, usually one-eighth or one-sixteenth is perfect for DnB moves.

Now do something that feels boring but changes everything: locators.

Put locators for a clean structure. Intro, 16 bars. Build, 16. Drop, 32. Break, 16. Drop two, 32. Name them clearly. You’re not just labeling the song. You’re creating audit checkpoints, so when the automation gets heavy, you always know where you are and what the section is supposed to feel like.

Now, quick mindset shift. We’re going to work with an automation budget.

Pick a number of lanes you’re allowed per 32-bar drop. Seriously. This is how you stop automation from turning into clutter.

For drums: one to two lanes, bus-level only.
For bass: two to four lanes, preferably macros rather than raw device parameters.
For FX and atmos: one to two lanes, ideally on returns or a group.

If a section needs more than that, it’s not a sign you should draw more. It’s a sign you should re-architect. Rack it. Resample it. Or move motion into modulation.

Alright. Step one: find and eliminate hidden conflicts. This is the number one cause of “broken automation.”

DnB projects are notorious for automation fighting between clip envelopes, arrangement automation, modulation, duplicate lanes, and automation inside racks.

So here’s your conflict checklist.

First, click clips and look in Clip View under Envelopes. If you see automation there, ask yourself: do I want this to be visible globally in the arrangement? If yes, move that idea into Arrangement automation and clear the clip envelope. Clip envelopes are great for experiments, but they’re also where automation goes to hide.

Second, watch the top of the screen for that “Re-Enable Automation” warning. If something sounds wrong, it’s often because you tweaked a knob manually and now Live is ignoring the automation. Click Re-Enable Automation and you’re back to reality.

Third, duplicates. Click the parameter you think you’re automating, like Auto Filter frequency, then choose “Show Automation in New Lane.” If you see multiple lanes for the same parameter, that’s a red flag. You might have overlapping edits, or you wrote automation in two places and now you’re hearing a weird average of decisions.

Cleanup action: choose one source of truth per parameter.

My recommendation for DnB is this. Big arrangement moves live in arrangement automation. Internal motion, the stuff that makes a sound feel alive inside the bar, can live in modulation style tools or in a rack macro that you automate cleanly. One clear driver.

Now step two is the biggest upgrade: convert messy parameter automation into a small number of macro lanes. This is the rack strategy.

If your bass track has separate lanes for filter frequency, resonance, saturator drive, utility gain, compressor threshold, and more… you’re basically writing a novel with ten pens at once.

Instead, we’re going to put a control panel on the sound.

Go to your bass channel. This could be Wavetable, Operator, Sampler, or even a resampled audio bass. Add an Audio Effect Rack. Group it, Command or Control G.

Inside the rack, build a stock chain. Start with Auto Filter. For DnB, LP24 is solid, or MS2 if you want that nasty resonant character. Then add Saturator. Set it to Analog Clip, drive somewhere like three to eight dB, and turn Soft Clip on. Optionally add Redux for a little grit, but keep it subtle. Then Utility at the end. Turn Bass Mono on so the sub stays locked.

Now map it to macros.

Macro one: Bass LP Sweep. Map it to Auto Filter frequency, but do the safe engineering with min and max ranges. Set the minimum around 80 to 120 hertz, unless you very intentionally want to choke the sub. And set the max in the six to twelve kilohertz range.

Macro two: Bite. Map it to Saturator drive, maybe three to nine dB.

Macro three: Air Kill. This could be a utility gain that tucks the top in builds, or it could be a secondary filter range trick depending on your sound. The point is: one macro that reduces brightness or energy when you need control.

Macro four: Crunch, if you’re using Redux. Map downsample in a small range so it never destroys the tone by accident.

Now instead of five plus messy lanes, you automate Macro one and two for most of the song’s movement. It’s cleaner, it’s faster, and it’s easier to understand.

Here’s a classic DnB arrangement move with this setup.

In the build, slowly raise Bass LP Sweep from around 200 hertz up to maybe eight kilohertz. Then at the drop, snap it back down to around one to three kilohertz so it’s heavy and controlled, not just white-noise loud. And then inside the drop, add little ramps every two bars. That’s the rolling phrasing. Micro-gestures that keep the groove alive without adding new sounds.

Now step three: clean the automation shapes themselves. Reduce points, keep intention.

If your lane looks like scribbles, you’re not hearing all of that. You’re seeing anxiety.

Click the lane, box select clusters of points, delete them. Then rebuild with fewer anchors. For most DnB phrases, you want two to six points per phrase unless you’re doing intentional glitch work.

And don’t sleep on curves. Hold Option on Mac or Alt on Windows and curve the segment. Curves are perfect for risers, tension ramps, and making your automation feel human instead of robotic.

A good DnB rule: builds often want an exponential curve. Slow at first, then fast. Drops often want fast then settle. A quick snap, then a little glide into the groove.

Now here’s a readability hack that makes your projects instantly scannable: phrase markers inside the automation lane.

Put anchor points exactly on phrase boundaries. For a 32-bar drop, think bar 1, 9, 17, 25. Even if the lane is doing something complex, those anchors let your eye understand the shape immediately. And it prevents accidental drift where a curve slowly ends up in a different place over time.

Step four: replace “too many lanes” with shared movement via return tracks.

This is where a lot of DnB projects go wrong. Every track has its own reverb automation, its own delay automation, its own little throw. It’s chaos.

Instead, we make two strong returns and automate sends. It’s cleaner and it sounds cohesive.

Return A, call it Dark Verb. Put Reverb on it. Set size around 35 to 60 percent, decay around two and a half to five and a half seconds, pre-delay ten to twenty-five milliseconds. Then low cut the reverb, somewhere around 200 to 400 hertz. Keep the low end clean. Put EQ Three or EQ Eight after to control mud. If you want, a light saturator after the reverb can thicken it.

Return B, call it Ping Throw. Put Echo on it. Time could be one-eighth dotted or one-quarter. Feedback 25 to 45 percent. Filter it. High-pass around 250 to 500, low-pass around five to eight k. Then a Utility after Echo to manage return level.

Now the cleanup strategy: stop automating reverb dry-wet on twelve tracks. Automate sends instead. Even better: automate one group send. Drum group send, FX group send, vocal group send if you have it.

Classic move: last snare before the drop. On that snare, automate Send B up from minus infinity to around minus six dB just for that hit, then immediately back down. One lane, huge impact.

And if your throws start washing out the mix, there’s a clean stock fix: make the return self-ducking.

On the Echo return, add a Compressor after Echo. Turn on sidechain. Sidechain it from the dry drum group or the lead source group. Duck one to four dB. Now you can throw harder without drowning the drop, and you don’t need a bunch of micro-corrective automation later.

Step five: group tracks and automate at the bus level. Drum bus discipline.

In DnB you might have breaks, tops, rides, ghost snares, layers on layers. If you automate each one, you’ll never finish.

Put them in a Drum Group. On the group, build a simple stock chain.

Drum Buss first. Drive somewhere like five to twenty percent. Crunch 0 to 20, but don’t overdo it. Boom is optional; if you use it, keep it subtle and tuned around 50 to 60 hertz, and only if it actually helps the groove.

Then Glue Compressor. Attack around ten milliseconds, release auto or 0.1 to 0.3 seconds, ratio 2:1. Aim for one to three dB gain reduction in the loudest sections.

Then EQ Eight with a high pass at 25 to 35 hertz. Maybe a little dip around 200 to 400 if it’s boxy. Then Utility for final trim.

Now, keep your drum automation lanes minimal but powerful.

One lane could be Drum Buss Drive or Amount. Another optional lane could be Glue threshold. And if you need overall impact control, Utility gain.

A great DnB move is this: in the build, slightly increase compression by lowering Glue threshold a bit. Then when the drop hits, release it, less compression, so the drums punch harder. That sounds like “the drop got bigger” without you turning the whole mix up.

Step six: tidy mutes and dropouts.

A lot of automation mess comes from using volume curves as mutes. And then you’re stuck later because you can’t tell what’s a creative mute and what’s a mix correction.

Best practice: if you want a hard silence, do it with clip editing. Split the clip, delete the piece. If you want a controlled fade, automate Utility gain with a short ramp.

And avoid automating track volume constantly unless it’s a deliberate mix move. Track volume is your mix balance. If you automate it everywhere, you’ll have no reference point later.

Here’s a clean DnB fill trick: one beat drum mute right before the drop, like bar 31 into 32. Cut the drum clips for one beat, and let only the reverb tail or an impact remain. It’s dramatic, it’s clean, and it doesn’t add any automation scribbles.

Also, quick safety note: don’t rapidly automate device on and off. That’s where clicks and pops happen. If you’re tempted, put a Utility after the chain and automate the gain with a five to thirty millisecond ramp. No clicks, and visually it’s obvious what you’re doing.

Step seven: standardize naming and visibility so future-you wins.

Color-code groups. Drums in a warm color. Bass in darker green or blue. FX and atmos in purple or grey. Rename the important macro lanes so your automation view reads like a story.

BASS Sweep. BASS Bite. DRUM BUS Drive. FX Throw.

And keep lanes collapsed unless you’re actively editing them. The goal is that when you open automation view, your eye lands on the few lanes that matter.

Here’s a teacher rule that helps a lot: one featured automation per section.

For example, the build is mainly Bass Sweep plus FX Throw. The drop is mainly Drum Bus Drive plus small Bite pulses. You can still do detail, but the big identity moves should be obvious.

Now step eight: resample to commit and reduce automation overload.

If a bass has fifteen lanes of motion, consider printing it.

Make a new audio track called BASS PRINT. Set input to Resampling. Solo the bass group and record eight to sixteen bars. Then you can disable the heavy synth chain and keep the project light and readable. And now your automation becomes simple audio-level moves: a filter, a send, a couple of edits. Plus you can do clean stutters and reverse tails without reopening a monster rack.

Now a few advanced coaching ideas to level this up.

First, build a control surface. Make a dedicated MIDI track called CTRL. Put an Instrument Rack on it, even with no instrument. Name the eight macros something like Drop Intensity, Build Lift, Bass Edge, Drum Clamp, Throw Amount.

Then map those CTRL macros to other track macros, to utility gains, and even to return-related moves where possible. This gives you one place to read the whole song’s movement, like a master automation dashboard.

Second, learn to detect automation that doesn’t matter.

Bypass the device you’re automating. If the section still feels ninety percent the same, that automation lane is high effort, low impact. Either delete it, or move the idea into a macro with a bigger, safer range, or commit it via resampling.

Third, prefer range mapping over detailed drawing.

Advanced cleanup is often not about drawing better. It’s about constraining the macro min and max so your automation lane can be simple and still sound controlled. Like: the filter never fully closes. The resonance never whistles. The distortion never nukes your headroom. That’s engineering done once, so you can write musical automation quickly.

Now a big DnB sound design extra, because it affects automation cleanup massively: keep the sub stable, and put movement in the mids.

If your bass is doing everything on one chain, split it inside an Audio Effect Rack.

Make a SUB chain. EQ Eight low-pass around 120 to 180. Utility width at zero percent, mono. Minimal distortion.

Make a MID chain. This is where Auto Filter, Saturator, Amp, Redux live. This is where you automate width. This is where Motion happens.

Map one macro called Motion to the MID chain movement only. Now you can go wild and your low end stays solid. That alone reduces the need for “fix automation” later.

Also, if you want perceived loudness automation without level jumps, automate tone density instead of gain. Tiny saturator drive moves, tiny amp gain, a small EQ bell around one to three k. Map it to a Presence macro. That translates on small speakers and keeps headroom sane.

Let’s do a mini exercise to lock this in.

Take a 16-bar drop section in one of your projects where automation is messy. Your goal is to reduce it to five automation lanes total while keeping the same musical impact.

Set up a drum group bus chain. Set up a bass rack with two macros: Sweep and Bite. Set up two returns: Dark Verb and Ping Throw.

Now delete or disable all automation except: Drum Bus Drive, optional Glue threshold, Bass Sweep macro, Bass Bite macro, and one send automation lane, either a group send or a key track send.

Then rebuild the section using clean curves. Build into the drop with Sweep rising and one throw on the last snare. In the drop, make Bite pulse every two bars, and bump Drum Drive on bar one and bar nine.

Pass condition: you can understand the entire movement of that drop by looking at the lanes for ten seconds.

And to finish, here’s the bigger homework challenge if you want to really master this.

Reduce a full song to a ten-lane master plan. Not counting clip cuts or audio edits. Ten automation lanes or fewer.

Rules: create a CTRL track with eight macros. Create at least one split bass rack with a Motion macro. And make one return self-ducking with sidechain compression.

Then hide all lanes except your chosen ten. If you can still describe the entire track’s energy story just by looking at those lanes, you pass.

That’s the whole philosophy: automation that reads like a story. Clear control schemes. Fewer lanes. Bigger impact.

If you want, describe your current groups—like drums group, bass group with two layers, atmos, leads, FX—and I’ll propose a ten-lane map with macro names, what they control, and safe min and max ranges so your automation stays clean and powerful.