Welcome back. This lesson is all about the least glamorous, most powerful skill in releasing drum and bass: the pre-release review.

Because if you’re at the point where the track basically slaps, the thing that separates “ready” from “almost” is not one more synth layer. It’s systematically catching the problems you’re currently too used to hearing.

Today you’re going to build a repeatable pre-release checklist inside Ableton Live. Think of it like a quality control mode. You’ll run it in about 20 to 45 minutes per track, and it’ll cover arrangement flow, bass and sub translation, drum impact, loudness prep, real-world translation, and export sanity checks.

First rule. Step zero. Non-negotiable.
Duplicate the project.

Go to File, Save Live Set As, and name it something like TrackName PRE-RELEASE AUDIT v1.
This is your safe sandbox. You’re going to be making judgement calls, toggling things, maybe freezing stuff, maybe printing tests. Do not do that on your beloved main set.

If the project is heavy, this is the moment to freeze any wild sound design tracks so your computer isn’t gasping while you’re trying to make decisions. Flatten only if you’re totally confident. The goal is: audit without breaking.

Now, before we touch any devices, I want you in a different listening mode.
This is coach mode, not creator mode.

If you’re on Live 12, open the Notes view. If not, create a little text file next to your project called REVIEW_NOTES.
And I want you to use a tiny template:
Biggest win to protect.
Top three problems to fix.
Two things to ignore for now.

That last line is huge. Two things to ignore. Because the biggest risk in a review session is spiraling into infinite tweaks. The track doesn’t need to become perfect today. It needs to become releasable.

Next, do a timeboxed triage pass.
Set a timer for six to eight minutes.

During this pass, you do only two actions.
One: drop locators where you hear an issue.
Two: write a three to five word diagnosis at that moment.

Examples: “snare buried by bass stab.”
Or “hats painful, 8k.”
Or “drop energy flat, too similar.”
No EQ moves. No compressor moves. No plugin browsing. Just identify problems like a doctor. We treat after the diagnosis.

Alright. Step one: arrangement markers and the DJ reality check.

In Arrangement View, right-click the timeline and add locators for your major sections.
Intro, DJ-friendly.
Build.
Drop one.
Break or atmos.
Drop two, with variation.
Outro, mix-out.

For drum and bass, a DJ-friendly intro and outro usually means 16 or 32 bars that are actually blendable. Not just “cool,” but functional. The question is: if someone is mixing into this in a club, do they have clear rhythmic material to lock onto? Hats, rides, ghost snares, a steady pulse. Something that behaves like mix material.

Then check your drops. Are they distinct?
If drop two is literally a copy-paste, the energy flatlines. You don’t need a whole new sound palette. You need one meaningful change: a different call-and-response, a drum fill, a bass rhythm switch for four bars, a stop, a one-bar kick removal before a hit. Small structural edits read huge in drum and bass.

And while you’re in this arrangement mindset, make a quick pass on automation lanes. Four categories that make a track feel finished are:
Drum density.
Bass call-and-response.
FX intensity.
Ambience width.

If you only automate those, the track usually starts feeling intentional instead of looped.

Step two: reference track A/B. Real A/B.

Make a new audio track called REF and drop in two or three references that match your vibe and era. Similar tempo, similar density. Not “the biggest mastered anthem ever” if your track is a deep roller. Keep it fair.

Important: for references, you generally want Warp off, because you’re not trying to time-stretch a master for fun. You’re trying to compare tone, balance, and impact. If you must warp, be careful with modes.

Now put Utility on the REF track and turn it down. Start around minus six to minus ten dB. The whole point is level matching by perceived loudness, not peak meters. If the reference is louder, it will always seem better. That’s just human hearing.

Here’s the A/B method.
Loop eight bars of your Drop 1. Then loop eight bars of the reference at a similar section.
Match the level by ear.
Then ask three questions:
Is my sub as controlled?
Are my drums as forward?
Does my mix feel foggy compared to theirs?

Foggy usually means too much low-mid or too much wash from reverb and delay, or a mid-bass that’s eating everything. We’ll address that in a minute.

Step three: build a Master Audit Rack using stock devices.

This is not your master chain. It’s a flashlight.
And it should be off by default.

On your Master, add Utility first. That’s your mono and width sanity checker. Map a macro or just get used to toggling mono quickly.

Then EQ Eight. Turn the analyzer on. This is for problem finding.
Set up a gentle high-pass around 20 to 30 Hz just to reveal rumble. You’re not “removing bass,” you’re identifying unnecessary subsonic garbage.
Then make a narrow bell that you can sweep when something feels harsh. In DnB, hat and snare pain often lives around 2 to 6k, and sometimes the fatigue zone is more like 6 to 10k.

Then Spectrum. Set the block size to 8192 so the low end reads more steadily. You’re looking for obvious spikes and weirdness, not trying to mix with your eyes. But Spectrum can confirm if one sub note is exploding or if there’s random low-end energy that shouldn’t be there.

Then, a Limiter. Audit only.
Ceiling at minus 1.0 dB.
Turn it on briefly and see how it reacts if pushed. If it’s instantly doing a ton of gain reduction, you’re not “not loud enough,” you’re usually too peaky, too uncontrolled in transients, or too dense in the wrong band.

Again: keep this rack off by default. We use it to reveal, not to fix.

Now we hit the number one release killer: sub and bass.

Step four: sub and bass checklist.

First: your sub must be mono and stable.
If you have Live’s Utility with Bass Mono, set it around 120 Hz. That’s a solid starting point.
If you don’t have that feature, do it the smart way: separate sub layer, then set Utility width to 0% on that sub track.

Now do the real test: in the drop, toggle your Master mono.
If the sub drops in level, or gets weird and hollow, you’ve got stereo low end, phase issues, or a layered bass that’s fighting itself.

And here’s a super common roller problem: sub notes that overlap and smear.
The bass line feels like it’s dragging. The kick loses definition. The groove turns to soup.

Fix number one is musical: shorten the MIDI notes so they stop just before the next kick or snare impact. That space is punch.
Fix number two is control: put a Compressor on the sub, ratio two to one up to four to one, attack around 15 to 30 milliseconds, release around 60 to 120 milliseconds depending on tempo and feel.
Then add sidechain from the kick, or better, from a ghost kick so the pumping is consistent without changing your audible kick choice.
Aim for about two to five dB of gain reduction on hits. Enough to create room, not enough to turn your bass into a breathing effect unless that’s the vibe.

Step five: drum impact audit. Kick, snare, hats.

Solo kick and snare for thirty seconds.
In drum and bass, the snare is often the emotional anchor. It needs to read clearly on two and four, especially in the midrange. Ask yourself: is the snare the loudest midrange event? And does the kick support it rather than fight it?

If you need a quick, clean Ableton stock chain idea on a drum group:
Drum Buss with drive around five to fifteen percent, crunch maybe five to twenty for edge, boom usually off or very subtle for DnB.
Then Saturator with soft clip on, one to four dB drive, careful not to add harshness.
Then Glue Compressor, light settings, ratio two to one, attack three to ten milliseconds, release auto or around 0.1 to 0.3 seconds. You’re looking for one to three dB of gain reduction on peaks. Just enough to feel like it’s one drum kit.

Now hats. Hat harshness is sneaky because it feels exciting at first and painful later.
Loop 16 bars of your busiest section, often Drop 2.
If your ears get tired fast, check 6 to 10k.
A gentle EQ dip of one to three dB around seven to nine kHz can help. Or you can use Multiband Dynamics lightly to control the harsh band without dulling everything.

And here’s a pro move: sometimes it’s not an EQ problem. It’s a sample choice problem.
Swap the brightest hat for a darker one, then push it slightly louder. That often keeps energy without the razor blade.

Step six: midrange bass clarity. Reese and neuro management.

This is where a lot of intermediate mixes collapse. The mid-bass is sick by itself, but in the mix it’s eating the entire record.

Do this quick workflow:
Toggle master mono.
Turn the sub down by about three dB temporarily.
Now listen to the bass character, roughly 200 Hz to 2 kHz.

If the bass vibe vanishes when you do that, your bass is relying too much on stereo width, phasey layers, or sub dominance. You want the bass to still speak in mono, especially in the low mids.

Use EQ Eight on the bass group.
If the snare body disappears, check 200 to 400 Hz. That zone can turn into cardboard real fast.
If the snare crack or vocals fight, check 1 to 3 kHz.

If you want a clean structure, build a little audio effect rack on the bass group with three bands:
Sub, 0 to 120, forced mono.
Low-mid, 120 to 500, lightly saturated for presence.
Mid-top, 500 and above, where you can add controlled width if desired.
That gives you “dark width” that doesn’t wreck the club.

Step seven: space, FX, and the “too wet” detector.

DnB needs atmosphere. But the drop has to hit clean.
So in your drop, ask: can I clearly hear the snare transient, the bass rhythm, and the main hook? If any of those are blurry, check your returns.

A great standard is reverbs on return tracks, not inserts, so you can control them like an environment.
Inside the reverb, high-pass around 200 to 400 Hz and low-pass around 6 to 10k. That keeps the reverb from filling your low mids and sizzling your top end.

Then, sidechain your reverb return with a compressor keyed from the snare or the full drum bus. Fast attack, medium release, ratio two to one up to four to one.
That gives you space that moves out of the way when the drums hit, which is basically the modern “clean but atmospheric” sound.

Step eight: headroom and pre-master prep.

Before release, you want a clean premaster, even if you’re self-mastering.
A practical target is peaks around minus six dB on the master, and no accidental clipping anywhere.

And here’s an advanced reality check: don’t only watch the master.
A lot of mystery distortion happens inside groups and returns.
During review, look at the drum group meter, bass group meter, and your FX returns. You might find one return is insanely hot and smearing the entire drop.

If you need quick control, use Utility to trim groups: drums, bass, music, FX.
If the mix feels good but peaks are wild, lightly glue the drum group, and consider soft clipping on drums or bass groups rather than slamming a master limiter.

Step nine: translation tests, the real-world pass.

First, mono test. Toggle mono on the master. Snare should stay strong. Sub should remain stable.
Second, low volume test. Turn your monitors way down. Can you still follow the groove? If the track falls apart, your balance might be relying on loudness instead of clarity.
Third, bad speaker test: phone or laptop. You won’t hear sub, but you should hear bass presence through harmonics. If you can’t follow the bass line at all, create a sub translation layer.

Quick method: duplicate your sub MIDI to a new track called SUB_HARM. Use Operator sine or your sub source, add a touch of saturation or overdrive, then high-pass that layer around 120 to 180 Hz so it’s only harmonics. Blend until it’s readable, then back it off ten percent. Translator, not second bass.

If possible, do a car test or earbuds test. Listen for boomy notes, harsh hats, sibilant vocals, weak snare. Write down what you hear. Don’t fix in the car. Just diagnose.

Now step ten: export checklist.

For a premaster to send to mastering:
Export from the master.
Sample rate: match your project, commonly 44.1 or 48k.
Bit depth: 24-bit.
Dither off.
Normalize off.
Convert to mono off.

And a key detail: if you have that master audit rack on, make sure you’re not accidentally exporting with it. Either disable it, or set “include master effects” appropriately. The goal is a clean premaster, not your flashlight chain printed into the file.

For a release-ready master, if you’re self-mastering:
Many distributors accept 24-bit WAV. If you need 16-bit, dither on with a standard TPDF style dither, and keep your ceiling safe, aiming around minus 1.0 dB to avoid ugly true peak overs.

Name files like a professional:
Artist dash TrackName, Master v3, 24bit.
And also keep a premaster file labeled clearly.

Now let’s lock in a versioning rule that prevents regret.
When you finish the audit and start implementing fixes, save a new version: TrackName AUDIT v1 becomes TrackName FIX v1.
That way you can A/B entire versions, not just wonder which device change ruined the vibe.

Optional advanced move: print a DJ mix test inside the project.
Create an audio track called PRINT_DJ_TEST and set it to resampling.
Print 64 to 128 bars that include the last 32 bars of a reference track outro into your intro and first drop, with a crossfade.
This reveals if your intro and outro actually behave like mix material in real life, not just “sounds cool alone.”

And one more advanced check: two loudness checks.
Do one pass quiet, for groove and snare readability.
Do one pass loud, for hat fatigue and sub control.
A lot of DnB mixes pass one and fail the other.

Alright, mini practice exercise. Twenty minutes.

Pick one current project.
Add locators: intro, drop one, break, drop two, outro.
Add a reference track on a REF lane and level match with Utility.
Build your master audit chain: Utility for mono, EQ Eight, Spectrum, Limiter for audit.
Then loop three sections: eight bars of drop one, eight bars of the busiest section, and eight bars of intro or outro.

Now the golden rule: write down three fixes max.
One sub fix.
One drum fix.
One arrangement or FX fix.

Implement only those, then re-check the exact same loops.
You’re training consistency, not perfection.

Before we wrap, common mistakes to watch for:
Stereo sub, especially from chorus or unison patches, which collapses in mono and dies in clubs.
Over-layered drums without phase checking, which makes the snare thin and the kick weak.
Too much 200 to 400, which creates that cardboard fog.
Over-wet drops that wash transients and make the groove feel late.
Using a limiter as a mix fix, which tricks you into hearing “loud” instead of “good.”
And copy-pasting drop two, which kills forward motion.

Final recap.
Before release, your job is to prove the track works everywhere.
Structure is DJ-friendly, energy moves logically.
Sub is mono, stable, and not fighting the kick.
Drums are punchy and readable, especially the snare.
Mid-bass is aggressive without masking the mix.
FX add vibe without washing the drop.
Exports are intentional and clean.

Run this checklist every time. Same monitoring chain, same process, same mindset. And you’ll notice something: your releases start sounding more consistent, more professional, and way more club-ready, without guessing and without endless tinkering.