Using Comments and Notes Inside Sessions, intermediate Ableton Live workflow for drum and bass. Let’s go.

If you make drum and bass, you already know the problem: your session starts as a clean little loop, and then suddenly it’s 20 drum channels, three bass resamples, five versions of the drop, and a bunch of “I’ll remember what this is” clips… which you absolutely will not remember next week.

So in this lesson, we’re building a simple, repeatable notes system inside Ableton Live. Not a separate document. Not a phone note. Inside the set, right where you need it, so you can finish faster without killing the vibe.

By the end, you’ll have a DnB Session Notes System: a dedicated notes track, section locators that actually tell you what to do, consistent naming and colors, and a resample log that stops version chaos.

Alright. Open a Live set. Existing project is perfect, or start something new at 174 BPM if you want the full DnB feeling.

Step one: create a dedicated NOTES track.

Create a new MIDI track and drag it to the very top of the set. Rename it 00_NOTES. The double zero is on purpose: it stays at the top forever.

Color it something loud. Bright yellow or white works great. The goal is that your eyes always find it instantly.

And this track should never output sound. Easiest way: don’t put an instrument on it. Just leave it empty. If you’re the type who worries you’ll accidentally route something to it, you can drop an empty Instrument Rack in there and keep the volume all the way down, but honestly, empty is fine.

Teacher tip: This one move changes everything. Because now you’ve got a home base for your brain. When you’re in flow and you notice a problem, you don’t stop producing to “be organized later.” You just capture it here, fast.

And for structure, keep 00_NOTES at the top, then your main groups underneath: DRUMS, BASS, MUSIC, FX, VOCALS, PRINT or RESAMPLE. Even if your groups are different, the point is: notes first, sound second.

Step two: use MIDI clips as sticky notes in Session View.

Go to Session View and in your 00_NOTES track, create a few empty MIDI clips by double-clicking in empty clip slots. You’re not putting notes into MIDI. You’re using the clips as labeled sticky notes.

Name a few like: TODO, Mix Notes, Resample Log, Break Chops Map, Arrangement Checklist, Mastering Checklist. Whatever matches how you actually work.

Now, the key habit: write short notes in clip names so you can scan them in half a second.

Examples that actually help in DnB:
Kick feels late versus snare in Drop 2.
Ghost snares too loud around 200 Hz.
Bass reese v4 is best movement, print it.
Break edit: keep Amen ride in bar 7.

If you need longer notes, don’t write an essay. Stack across multiple clips: Mix Notes 1, Mix Notes 2, Mix Notes 3. The point is speed. Notes should be written at the speed you hear the problem.

Now add a simple color system. Pick a palette and reuse it every project. For example:
Red means urgent fix.
Blue means arrangement.
Purple means bass design.
Orange means drums.

Your colors don’t have to match mine, but they must be consistent. Random colors are basically visual noise.

Expansion tip: make notes “queryable,” not just readable. Use prefixes so your brain can search quickly:
TODO: something you can execute.
DECISION: an A/B choice you must commit on.
WHY: the reason you did something.
REF: reference track info.
RISK: something that might break later, like mono issues or headroom.

So instead of “Drop 2,” try something like:
DECISION: Drop 2 equals Reese_v7 or NeuroStab_v3, pick today.
WHY: sub muted in intro for DJ blend plus tension.
RISK: widener on tops, check mono.

That prefix system is small, but it’s powerful. It stops endless tweaking because you’re naming the type of thought, not just the topic.

Step three: use Arrangement Locators as section labels plus action notes.

Switch to Arrangement View. Up at the top timeline, right-click and add a locator. Do that at your key sections: intro, build, drop, breakdown, second drop, outro.

But here’s the important part: don’t name locators only as “DROP 1” or “BREAK.” Add the intention.

For example:
INTRO, DJ-friendly, no sub until bar 17.
BUILD, automate high-pass filter on break.
DROP 1, bass v3, drums tight.
16 bar switch, add ride and crash tails.
BREAKDOWN, cut kick, keep hats.
DROP 2, heavier snare, darker reese.

This matters in drum and bass because structure is often 16 and 32 bar phrasing, and the energy is all about controlled variation. Locators make it easy to jump and A/B different versions, verify fills land correctly, and keep transitions consistent.

Extra arrangement upgrade: try adding “energy” locators too. Not just section names, but intensity ratings:
ENERGY 2 out of 10, DJ intro.
ENERGY 6 out of 10, build pressure.
ENERGY 9 out of 10, main drop.

That helps you diagnose why a drop doesn’t feel huge. Sometimes it’s not the sound. It’s that your energy curve is flat.

Step four: clip naming discipline for drums.

This is where sessions usually fall apart. If you’ve got Audio 12, Audio 27, and “copy of copy,” you’re basically producing in the dark.

Adopt a naming system. For breaks:
BRK_Amen_170_Edit1.
BRK_Think_170_HP.
BRK_ShuffleLayer.

For kicks:
KICK_Punch_01.
KICK_SubTick.
KICK_TopClick.

For snares:
SN_Main_200Hz.
SN_ClapLayer.
SN_NoiseTail.

For hats:
HAT_Shuffle_16.
HAT_Offbeat_Open.

Do it fast: select a clip, hit rename, type. And when you resample or print a break edit, name it immediately. Not later. Immediately. For example:
BRK_PRINT_Drop1_8bars_Tight.

If you’re using Drum Rack, rename pads too. Kick Tight, Snare Crack, Hat Swing, Ride Jungle. When you come back weeks later, it’s the difference between “what is pad 14?” and “oh yeah, that ride layer.”

Step five: create a resample log track for bass.

DnB bass design gets version-heavy fast. v1, v2, v3… and if you don’t label, you lose hours.

Create an audio track called PRINT_BASS_LOG.

Put a simple, safe chain on it:
Utility for gain staging.
Saturator for gentle glue if you want it.
Limiter as safety only. Not smashing, just catching.

Now every time you resample a bass phrase, name the printed clip like a deliverable:
Reese_v5, 1/8 LFO, best movement, print it.
NeuroStab_v2, shorter release, heavier mid.

And include the chain references in the name when it matters:
Reese_v5, Wavetable plus OTT style multiband plus Erosion.

Expansion move, super useful: parameter journaling. You don’t need every setting. Just the 2 to 4 parameters you always forget. Like:
Reese_v8, WT position 32 percent, FM 15 percent, Sat soft clip, high-pass at 28 Hz.

Now future-you can recreate the vibe without guessing.

Also consider resample checkpoints to avoid infinite chains. Put reminders in your notes like:
PRINT after tone stage, pre-OTT.
PRINT after distortion stage, pre-limiter.

That keeps your sound design reversible and saves CPU.

Step six: add mix notes directly into the mix with marker clips.

This is one of the best “don’t forget” hacks in Ableton.

Wherever the problem happens in time, create a blank MIDI clip right there. On the DRUMS group, or BASS group, or even a dedicated track called MIX_FIX_MARKERS.

Name the clip with an action note:
FIX: snare rings at 220 Hz.
CHECK: hats harsh at 9 to 10k.
SIDECHAIN: bass too static versus kick.

Color these marker clips bright red so they jump out.

The magic is that the note lives exactly where your ears heard the issue. Not in a random list. It’s anchored in time. When you play through the drop, you literally see the work coming.

Coach tip: make your notes “definition of done.” Add a pass/fail condition. For example:
TODO: snare tune and layer. DONE when snare peak sits around minus 6 dB and tail doesn’t ring at 200 to 250 Hz.

That stops you from endlessly tweaking because you’ve defined what success sounds like.

Step seven: build an arrangement checklist that prevents the “great loop, messy track” trap.

Back on 00_NOTES, create a clip called ARRANGEMENT CHECKLIST.

Then create a series of short checklist-style notes like:
Intro: 16 bars no sub, plus 16 bars tease bass.
Drop 1: 32 bars, 16 bar switch.
Break: 16 bars with tension automation.
Drop 2: 32 bars heavier variant.
Outro: DJ-friendly 16 to 32 bars.

Then align your locators to match. Even if you break the rules later, having a default prevents you from wandering.

And for transitions, create a clip called TRANSITION RECIPES. Write a few go-to moves you can copy mentally when a transition is boring:
Recipe A: remove sub for two beats, vocal stab, impact tail.
Recipe B: one-bar drum mute, snare fill, reverse crash.
Recipe C: automate reverb send on snare last hit, hard cut.

This keeps you producing instead of sample browsing for an hour.

Step eight: collaboration-ready notes.

Even if you never collaborate, this is for future-you. Create a clip called SOURCES AND INTENT.

Write things like:
Break: Amen from pack X, chopped plus transient shaped.
Snare: layered body 200 Hz plus crack 3k plus noise tail.
Bass: Wavetable reese plus resampled distortion plus notch automation.

And add the basics:
Tempo 174.
Key or root: for example F, sub follows F.
Reference tracks: list two or three.

If you do handoffs, make a clip called HANDOFF: DO, DON’T, QUESTIONS.
DO: tighten Drop 2 drums, print bass stems.
DON’T: change tempo, don’t re-warp breaks.
QUESTIONS: snare tone, more crack or more body?

This prevents chaos when someone else opens the set.

Common mistakes to avoid, quick fire.

One: writing notes but not placing them where they matter. Use locators and marker clips anchored to bars.

Two: vague notes. “Fix bass” is useless. “Bass masks kick at 50 to 60 Hz, carve or sidechain” is actionable.

Three: not versioning resamples. In DnB you’ll resample a lot. Label versions or you will lose the plot.

Four: color chaos. Pick a palette and stick to it.

Five: leaving Audio 1, Audio 2. Silent killer of finishing tracks.

Now a two-minute session startup ritual. This is how you turn notes into results.

Create one clip in 00_NOTES called OPENING MOVE.

Every time you open the set:
First, fix the most obvious red marker.
Second, bounce or resample one thing to commit.
Third, do a 30-second arrangement pass: add or remove one element.

This keeps momentum and stops you from endlessly looping the drop for the hundredth time.

Mini practice exercise, 10 to 15 minutes.

Open a DnB project.
Create 00_NOTES with clips: TODO, Mix Notes, Resample Log, Arrangement Checklist.
In Arrangement, add locators: Intro, Drop 1, Break, Drop 2, Outro.
Add three marker clips at real problem points: one drum issue, one bass issue, one transition issue.
Then print one bass idea to PRINT_BASS_LOG and name it like a pro:
Reese_v1, Wavetable to Saturator to Multiband, good groove.

Your goal is simple: close the set, reopen it tomorrow, and know exactly what to do in under 60 seconds.

Before we wrap, one last advanced push: archive decisions so you stop second-guessing.

Make a clip called CHOSEN VERSION LIST.
Write:
Drop 1 drums equals BRK_Amen_Edit3 plus SN_Main_200Hz v2.
Bass lead equals Reese_v5, keep. v6 delete later.

That’s how you stop the “why is v4 still here?” syndrome.

Recap.

You’re using a dedicated 00_NOTES track to centralize your thinking.
Session clips become sticky notes and checklists.
Arrangement locators map structure plus intent.
Marker clips placed in time tag real issues.
Resamples get versioned and labeled, especially bass.
And naming plus color stays consistent so big sessions stay fast.

If you tell me your style, break-based jungle, rollers, or neuro and heavy, and whether you work Session-first or Arrangement-first, I can tailor a tight prefix system and a color palette you can reuse every project.