Title: Building Reusable Automation Skeletons (Intermediate)

Alright, welcome back. Today we’re doing something that feels slightly unglamorous… but it’s one of those intermediate-level workflow upgrades that suddenly makes you finish more music.

We’re building reusable automation skeletons in Ableton Live, specifically for drum and bass. The goal is to stop redrawing the same filter opens, reverb throws, pre-drop suck-outs, and drop impacts in every single project.

Because here’s the truth: in DnB, automation is the difference between “cool 8-bar loop” and “this is a record.” And if you automate from scratch every time, two things happen. One, you lose time. Two, your arrangements start feeling random, because you’re reinventing the energy curve every project.

By the end of this lesson, you’ll have a template you can drop into rollers, jungle switches, even darker neuro-ish stuff. You’ll have a consistent 8, 16, 32-bar energy logic. You’ll have returns for throws that are always ready. And you’ll have group macros that you automate instead of a million device knobs that don’t translate when you swap sounds.

Let’s build it.

Step one: set up a DnB-ready session skeleton.

Set your tempo to something in the classic range, 172 to 176. I’d start at 174, because it’s a nice middle ground.

Now create three main groups: DRUMS, BASS, and MUSIC.

Inside DRUMS, put separate tracks for kick, snare, hats, break, and perc. Inside BASS, make sub, mid bass, and optionally a reese or neuro layer. Inside MUSIC, make pads or atmos, stabs, and FX.

This grouping is not just organization. It’s the core idea of reuse. When you automate groups, your automation still makes sense even if you completely replace the kick, the break, or the bass patch. You’re automating behaviors, not specific sounds.

Now add return tracks. Minimum: Return A for reverb throws, Return B for delay throws. And optionally Return C for parallel crush if you like that heavier, more aggressive control.

Cool. That’s the skeleton of the session.

Step two: build reusable return FX for throws, using stock devices.

Let’s start with Return A, your REV THROW. The vibe is clean but big.

First device is EQ Eight. High-pass it somewhere around 200 to 350 hertz with a steep slope, like 24 dB per octave. This is one of the most important habits in DnB: your reverb return does not need low end. Low end in throws is how drops turn into mud.

If the reverb ever feels sharp or painful, you can also do a gentle dip around 2 to 4 kHz. Don’t overthink it. Just keep it smooth.

Next add Hybrid Reverb. Pick an algorithmic hall. Set decay somewhere around 2.5 to 5.5 seconds. For throws, longer tails are actually useful because they read as “transition,” not “room.” Add pre-delay around 15 to 35 milliseconds so the dry hit stays punchy and the tail blooms after.

Set the return to 100% wet. Returns should be fully wet, almost always, because the dry signal lives on the source track.

Then add a compressor. For now, set it gently: ratio 2 to 1, attack 10 to 30 milliseconds, release 80 to 200. Later, we can sidechain it from snare or kick to keep throws huge but out of the way.

Then put Utility at the end. You can widen a bit, maybe 120 to 160%, but be careful. If your reverb disappears in mono, you’ve overdone it. If you need extra safety, turn on Bass Mono and set it around 120 Hz.

Now, think like an automation designer. What are the targets you want to automate here across every project? Usually it’s not the return’s dry/wet, since it’s already fully wet. Instead, you automate the send amount from key tracks. But you can also automate Hybrid Reverb decay for swell moments, or the Utility width for “widen the throw into the transition” moments.

Now Return B: DLY THROW. This is your sync’d, surgical movement maker.

Add Echo. Turn Sync on. Set time to one-eighth or one-quarter. If you want that jungle bounce, try dotted one-eighth. Set feedback around 25 to 45%. Then filter it: high-pass around 250 Hz, low-pass somewhere between 6 and 10 kHz. We’re keeping it controlled, not fizzy.

After Echo, put an EQ Eight to cut any resonant build-ups, and often a little cut around 300 to 600 if it’s getting boxy. Add a limiter if you want safety, because feedback automation can surprise you.

Automation targets here: feedback ramps for repeat builds, and very occasional time changes for stuttery fills. But be disciplined with time automation; it can sound cool, but it can also sound like the mix is glitching by accident if overused.

Step three: make macro automation racks on your groups.

This is the big workflow unlock. If you automate device parameters everywhere, your automation becomes non-transferable. But if you automate a set of macros, you can keep the same automation “performance” even when the sounds change.

On your DRUMS group, add an Audio Effect Rack and name it DRUMS MACRO.

Inside it, build a simple chain. EQ Eight first for tonal shaping. Then Drum Buss for drive and crunch. Then Saturator with Soft Clip on for controlled clipping moments. Then Glue Compressor for glue. Then Utility for width and gain.

Now map a few macros, and I want you to think in terms of “energy knobs.”

Macro one: Drum Tone. Map it to a filter frequency or a tilt-style move, basically controlling how dark or bright the drum group is. Macro two: Drum Crunch. Map it to Drum Buss drive and crunch together, but set min and max ranges so you can’t destroy the drums with one automation move. Macro three: Glue Amount. Map it to Glue threshold with a small range, because subtle is the point. Macro four: Drum Width. Map it to Utility width, maybe 100 to 140%.

And here’s a coach rule that will save you later: set macro polarity once and keep it consistent. Macro up equals more energy. Up is brighter, more drive, more width, more intensity. If you keep that consistent across every project, your hands learn the system, and your automation becomes fast and musical.

Now on the BASS group, add another Audio Effect Rack, name it BASS MOVEMENT.

Put EQ Eight for cleanup, then Auto Filter as the main motion control, then Saturator for edge, optionally Amp or Overdrive, and Utility for mono control and safety.

Map Macro one: Bass Filter, tied to Auto Filter frequency. Set a realistic range. Maybe minimum 80 to 150 Hz depending on how much you want to shut it down, and maximum somewhere like 2 to 6 kHz depending on the style. For neuro, you might open higher; for rollers, you might keep it more controlled.

Macro two: Bass Drive, tied to Saturator drive, something like 0 to 6 dB.

Macro three: Bass Width, but be careful. In DnB, width in bass is mostly a mids thing. You don’t want wide sub. If you’re not doing fancy multiband, keep width moves conservative and add safety like Bass Mono. Macro four can be Sub Safety: either Utility bass mono, or a gain control that protects the low end.

And another coach move: after any macro that changes tone, width, or distortion, consider a safety Utility or EQ after it to protect the low end from automation accidents. That’s how you keep the skeleton reusable even when the bass patch changes completely.

Step four: create reusable automation lanes in Arrangement View.

This is where we write the “skeleton.” And we’re going to write it in musical blocks that DnB listeners feel hard: 8 bars, 16 bars, 32 bars.

Pick a standard arrangement grid to work from. Here’s a great default:
Intro 16 bars, Build 8 bars, Drop 1 32 bars, Switch 16 bars, Drop 2 32 bars, Outro 16 bars.

Set locators for each section. This sounds like admin work, but it’s how you stay fast and consistent. You can even make a blank set that contains only these locators and empty groups and call it a locator skeleton.

Now choose automation targets that you will reuse constantly. Open lanes for the macros you mapped: Drum Tone, Drum Crunch, Bass Filter, Bass Drive. Then decide what you’ll automate for throws: usually send amounts from snare, vocal stabs, FX, maybe occasional return decay or delay feedback.

Keep master automation minimal. Maybe one Utility on the master for tiny gain dips or subtle width moves, but don’t turn your master into a rollercoaster. The movement should come from groups and returns.

Now let’s lay down the core automation curves you can copy and paste forever.

First, the build, 8 bars. Bass Filter gradually opens, like 25% to 70%. Drum Tone gets a little brighter, like 40% to 60%. Reverb throw send increases in the last two bars, usually on the snare or an FX stab. Delay throw send gets a tiny bump on the last bar, like a little “call forward” into the drop.

Then, the pre-drop suck, the last half bar. This is the moment where you create negative space so the drop feels bigger without needing more loudness.

Slightly tighten drum width. Do a tiny master gain dip, like minus 1 dB right before the drop. And cut the reverb. Either automate the send back to zero or automate the return down. The point is: the drop hits dry and punchy.

Then the drop impact, first bar. Bass Drive gets a quick bump and then settles. Same with Drum Crunch: quick bump and back. And keep reverb and delay sends near zero for the first beat so the punch lands clean.

Then your switch or fill patterns. One to two bars, usually every 16 bars. Pick a consistent pattern you can paste: maybe a delay throw on the snare on bar 16, or a quick bass filter dip that feels like a question mark, or a one-bar low-pass sweep on the drums for classic roller tension.

And here’s a big workflow tip: consistency equals pro. If you have a switch automation pattern you paste every 16 bars, your arrangement feels intentional even when your sound design is changing.

Now some extra coach notes that make this system actually usable at 3 a.m.

Name your automation like a system, not a vibe. Use a consistent prefix, like “AUTO – Build – Bass Open” or “AUTO – PreDrop – Suck” or “AUTO – Switch – Delay Ping.” It’s boring, and it’s incredible. Because later, when you’re copying from an older project, you can actually find what you need.

Another advanced idea: create a single Intensity lane and derive everything from it. Add a macro called INTENSITY, 0 to 100, on a top-level rack, maybe on a dedicated track or even on the master. Map it to multiple destinations with conservative ranges: a little drum saturation, a little transient tightening, bass filter opens slightly, return sends boost only near the top end. Then you automate one lane, and your whole energy arc becomes consistent by design.

And if you want to go even more portable, use dummy clips as an envelope library. Arrangement automation doesn’t always travel nicely unless you copy full tracks. So create a MIDI track called AUTO CLIPS, put an Audio Effect Rack with 8 macros on it, map those macros to key destinations across your set, then create Session View clips with clip envelopes for those macros. Now your build pattern is literally a clip you drag into any set.

Step five: store skeletons as reusable assets.

This is the payoff moment. You’ve done the work once, and now you stop repeating yourself.

Option A: save the whole thing as a template set. File, Save Live Set as Template. Name it something obvious, like DnB_AutoSkeleton_174_Template.

Option B: save modular bits. Save the DRUMS group with its rack as a group preset. Save returns by dragging them into your user library. This is great if you already have a favorite starting template but want to import your automation system.

Option C: if you built the AUTO CLIPS system, save those clips so your envelopes travel as a library.

Now, quick checklist of common mistakes to avoid.

First, automating too deep. If you automate 15 knobs on individual tracks, you cannot reuse it. Automate macros, not chaos.

Second, no macro min and max limits. Without ranges, one automation curve can ruin a mix: harsh highs, flabby low end, crushed drums. Make it hard to break.

Third, over-automating the master. Tiny, subtle moves are fine. But most movement should live on groups and returns.

Fourth, low end in reverb throws. High-pass first. Every time.

Fifth, ignoring 8, 16, 32-bar phrasing. DnB is structure-forward. If your automation isn’t anchored to that grid, it won’t feel like DnB, even if the sounds are right.

Now a few pro tips if you lean darker or heavier.

Use saturation automation as aggression control. A tiny one to two dB drive move on the bass group in the last two bars before a switch can feel massive.

Create a Dark Air noise riser channel. A noise source through a bandpass filter, saturator, and reverb, automated into builds. Save that as its own reusable track.

Sidechain your reverb return from snare or kick. That keeps tails huge but not swampy. And remember: widen the aftermath, not the drop. Drops often hit harder slightly narrower. Then after 8 bars, open it up for expansion.

And if you want “clipper moments” without third-party tools, automate Saturator drive with Soft Clip on, briefly, on the DRUMS group. Watch headroom, but it’s a clean way to add impact.

Let’s wrap with a quick practice exercise you can do in about 20 minutes.

Start a new set at 174 BPM. Load a basic drum loop plus a break. Add a sub with Operator sine, and a reese from Wavetable or a sample.

Build Return A and Return B exactly like we discussed. Build the DRUMS MACRO and BASS MOVEMENT racks.

Create an 8-bar build into a 16-bar drop. And automate only six things:
Bass Filter opening through the build.
Drum Crunch with a tiny bump pre-drop.
Snare send to the reverb throw only on the last two hits before the drop.
One delay throw on a fill.
A master gain dip of minus 1 dB for the last half bar pre-drop.
And a bass drive impact bump for the first bar of the drop.

Then save it as both a template set and as a DRUMS group preset.

Your deliverable goal is simple: you should be able to start a new project and get an arrangement energy arc going in under five minutes. Not a finished tune, but a real sense of build, drop, and movement without reinventing the wheel.

Recap.

We built returns for instant reverb and delay throws. We built group-level racks with macros so automation survives sound swaps. We wrote automation in 8, 16, 32-bar blocks so it feels like DnB. And we saved the whole system as templates and presets so every new session starts with momentum.

If you tell me what lane you’re aiming for, liquid, roller, jungle, neuro, jump-up, I can help you choose macro ranges and a curve pack that fits that vibe without wrecking your mix.