Title: Chord pacing at 170 BPM: using Session View (Advanced)

Alright, welcome back. This is an advanced Ableton Live lesson for drum and bass, and we’re going straight into a problem that hits hard at 170 BPM: chord changes.

Because at this tempo, harmony can either feel like it’s doing nothing… or it can feel like it’s stepping all over the groove. And in DnB, the groove is king. The drums and the bass are the headline, and chords are there to support weight, mood, and forward motion without stealing the focus.

So today, we’re using Session View as a rapid composition lab. Not “I’ll write a whole progression and hope it works.” More like: we’re going to A/B different chord pacing ideas in seconds, against real drums and bass, and let the music tell us what’s correct.

By the end, you’ll have a Session View harmonic performance set: multiple chord clips that use the same harmonic idea, but with different pacing strategies. Then you’ll build scenes like a DJ, perform them, and record straight into Arrangement when you find the magic.

Let’s set it up.

Step zero: project timing and Session layout.

Set your tempo to 170 BPM.

Now look up at the top bar and set Global Launch Quantization to 1 Bar. That’s your starting point, because it keeps everything tight while you test.

Create tracks in this order, top to bottom:
DRUMS
BASS SUB
BASS REESE or MID
CHORDS PAD
CHORDS STAB
ATMOS or FX

Teacher tip: color-code them. It sounds trivial, but Session View gets dense fast, and color is speed.

Cool. Now we build a truth source: drums.

Step one: establish a reliable DnB groove reference.

Your chords are only going to feel “right” if the groove you’re judging them against is consistent. So either drop in a two-bar loop you trust, or build a tight two-bar MIDI groove.

If you build it, keep it classic: kick on one, snare on two and four, hats with 16th motion, maybe a touch of swing but don’t get cute yet. We’re not trying to win a drum programming contest here. We’re building a stable grid to test harmony.

If you want a quick stock chain on the drum track: Drum Rack into Glue Compressor with gentle settings, like a couple dB of gain reduction, then a Saturator with soft clip for a little density. The point is: make the drums feel “real enough” so you can judge whether chord timing makes the snare hit harder or softer.

Now bass.

Step two: lock bass fundamentals so chords don’t lie.

This is huge. If your bass phrase is unstable, you’ll blame the chords for problems that are actually coming from a wandering low end.

On your SUB track, use Operator with a sine wave. Decide whether you want short sub notes or sustained ones, but keep the phrase simple and loopable across two bars or four bars. Add Utility and make sure the bass is mono.

Then your REESE or MID bass: Wavetable is fine. Add unison lightly, then filter, some saturation, maybe a little chorus width but only on the mids, and EQ it so it’s not fighting the sub. High-pass it somewhere in the 120 to 200 range, depending on the sound.

Key rule: the bass phrase needs to loop cleanly. No weird tail clicks, no timing slop. Once bass is stable, chord pacing decisions become real.

Now the chord sound design: we separate pad and stab. This is one of the biggest “advanced” moves at 170, because one chord sound trying to do everything usually smears.

Step three: build chord sounds that work at 170 BPM.

On the PAD track, think sustained, filtered, background glue. Something that can sit behind rolling drums. Analog or Wavetable works. Slight detune, low-pass filter, then reverb with a low cut so the reverb doesn’t dump mud into your low mids. Then EQ Eight to high-pass the pad somewhere around 200 to 350, maybe a small dip if it’s boxy. Utility for width is optional, but only after you’ve cleaned the low end.

On the STAB track, we want punctuation. Short envelope, transient-forward, and tempo-aware effects. You can use Simpler with a stab sample, or a plucky Wavetable patch. Then Drum Buss is a great trick here: turn up transients so the stab has bite without just turning up volume. Add Echo with dotted eighths or quarter timing, filter out the lows, and use a shorter reverb than the pad.

Here’s the mindset: pad equals atmosphere and glue. Stab equals rhythm and conversation with the snare.

Now the core of the lesson.

Step four: create multiple chord pacing test clips in Session View.

We’re not writing “a progression.” We’re building variants. Same harmonic cell, different pacing.

First, choose a harmonic cell. Two bars or four bars. Keep it DnB-friendly: minor key, maybe suspended tones, maybe a 7th or 9th if it’s not getting jazzy in the low mids. Also, avoid big root movement if your bass is already active. In rollers especially, sometimes one chord plus moving bass is the whole sauce.

Now on the PAD track, create four MIDI clips. Make them two bars long to start so they all compare fairly.

Clip A is your control version: two-bar hold. One chord, held for two bars. And I want you to automate something subtle inside the clip, like filter cutoff rising slightly, so it has life without changing harmony.

Clip B: one-bar changes. Chord one in bar one, chord two in bar two. Classic. Often this is enough to feel like motion without clutter.

Clip C: half-bar changes. Chords flip every two beats. At 170, this reads as urgent and techy fast, so keep your voicings tight. Don’t jump octaves, don’t stack thick low-mid clusters.

Clip D: anticipation. This one is spicy. Change the chord one eighth note early before a snare, like just before beat two or beat four. You’re not increasing overall complexity, you’re creating forward pull. This is one of the best ways to make harmony feel like it’s pushing the groove without adding more notes.

Very important workflow note: rename the clips. Seriously. Put “2-bar hold,” “1-bar,” “half-bar,” “anticipation” in the clip name or the Notes box. Session View gets messy fast.

Now stabs.

On the STAB track, make one-bar clips, because stabs are rhythm events.

Stab clip one: hit on beat one only. Anchor.

Stab clip two: hit on beat one and the “and” of two. That’s classic syncopation that locks into the snare pattern.

Stab clip three: call and response around the snare. Place stabs so they feel like they’re answering the snare, not competing with it.

Stab clip four: a jungle-ish pickup, like a stab just before the snare. That creates urgency.

And keep stabs high-passed. If your stab is fighting the bass, it’s not a stab anymore, it’s a problem.

Now we make Session View feel like a performance instrument.

Step five: use scenes to audition pacing like a DJ.

Make scenes that combine drums, bass, and specific chord clips.

Scene one: minimal drop. Drums full, sub on, reese on, pad is the two-bar hold, and either no stabs or just the beat-one stab.

Scene two: one-bar harmonic roll. Pad goes to the one-bar change clip, stabs go to the syncopated clip.

Scene three: busy, techy. Pad goes to half-bar changes, stabs go to the call-and-response clip, but use it sparingly because this can get loud fast.

Scene four: anticipation and tension. Pad goes to the anticipation clip, stabs go to the pickup stab.

Now launch scenes and listen like a producer, not like a theorist.

Ask: does the groove feel bigger or smaller?
Did the snare lose impact when chords change?
Is the chord movement complementing the bass, or is it fighting for attention?

And here’s an extra coach note that changes everything: think in harmonic hitpoints, not chord names.

At 170, the question isn’t “what chord is it?” The question is “where does the harmony assert itself on the grid?” Pick two to four hitpoints per two bars. For example: bar one beat one, bar one beat three, bar two beat one, bar two beat three. Then decide which hitpoints are allowed to carry a chord change. This prevents over-writing and keeps the groove clean.

Now we tighten how Session behaves.

Step six: launch quantization and legato.

Keep Global Launch Quantization at one bar while you do clean comparisons.

Then experiment. Set it to half a bar. Now your harmonic flips can happen faster, which is great for testing urgency. Set it to quarter bar for stabs if you want to perform them, but be careful because it can get chaotic fast.

Then Legato launch: for PAD clips, enable Legato so when you launch a new pad clip it doesn’t restart the whole phrase or modulation. It feels seamless, like you’re morphing harmony rather than re-triggering it.

For STAB clips, keep Legato off. You want clean triggers, not weird “continuations.”

Now the fun part: controlled chaos.

Step seven: Follow Actions for automatic pacing permutations.

Select your four PAD clips, go to the Launch box, and enable Follow Actions.

Set follow time to two bars. Then set it so most of the time it goes to Next, and sometimes it jumps to Other. A ratio like three to one works great: mostly predictable, occasionally surprising.

Let it run while drums and bass loop. This is where you discover combinations you would not have written manually.

And when something hits and you get that “oh, that’s it” moment, duplicate that clip or rename it “KEEP” immediately. Because you will forget which one it was. Session View moves fast.

Also, record this. Either record into Arrangement by hitting global record and performing, or record resampling audio if you want to capture the vibe as sound.

Now we commit without losing the Session magic.

Step eight: record to Arrangement.

Hit record on the transport and perform your scene launches for a few minutes. Don’t overthink it. Treat it like a DJ set where you’re managing energy using chord pacing.

Then jump to Arrangement View and edit. Find your best 16, 32, or 64 bars. Consolidate. Duplicate sections. And build variation intelligently.

A great DnB pacing idea: keep drops heavy by reducing harmonic change. Use your busier pacing as turnarounds. Like: 14 bars minimal, last 2 bars go anticipation or half-bar flips, then reset hard back to minimal. That contrast is what makes the next section feel intentional.

Let’s hit common mistakes before you go.

Mistake one: changing chords too often while the bass is busy. At 170, bass movement plus chord movement equals clutter. If your bass line is chatty, slow your chord pacing.

Mistake two: full-spectrum chords masking the snare. High-pass pads, control low mids, and remember the snare body and crack need space.

Mistake three: reverb washing the groove. If the pad reverb is smearing rhythm, low cut it harder, shorten decay, or gate the reverb on a return.

Mistake four: voicings too wide in the low mids. The 200 to 600 range stacks up fast. Keep chords tighter, and move extensions up an octave.

Mistake five: not keeping a control version. Always keep that two-bar hold clip as your baseline so you can tell if complexity is actually better, or just different.

Now a few pro-level upgrades you can layer in.

One: separate “change” from “re-voicing.” Make extra clips where the chord root doesn’t change, but the inversion changes, or the top note changes, or you swap one extension. In DnB, that reads as momentum without stepping on the bass.

Two: micro-timing isn’t just about starts. Place chord ends deliberately. Shorten some notes so they lift right before the snare, or hold them through the snare on purpose. You’ll feel the snare weight change instantly.

Three: dummy clips for automation. Create an empty audio track, drop a clip, and automate chord bus filter cutoff, reverb send, width, or a small volume trim. Now you can audition “more urgent” versus “more spacious” without rewriting MIDI. This is one of the most powerful Session View composition tricks.

Four: A/B at matched loudness. Faster harmonic movement often sounds better because it’s denser and effectively louder. Put Utility on the chord group and level-match before you decide.

And if you want a deeper advanced move: polymetric clip lengths. Keep drums and bass at two bars, but make a pad clip that’s three bars or five bars, and launch with Legato. The phase relationship drifts over time, giving you evolution without writing new chords. That’s how you make a roller run for minutes without feeling like a two-bar loop.

Now a quick practice run you can do in 15 to 20 minutes.

Build a two-bar drum and bass loop at 170.

Make one chord that fits.

Create three PAD clips: two-bar hold, one-bar change, and anticipation.

Create two STAB clips: beat one only, and beat one plus the “and” of two.

Make three scenes that combine them. Perform launching for two minutes and record into Arrangement.

Then listen back and decide: which pacing made the drop feel heaviest? Which felt most driving? And where did the snare lose impact?

Final recap.

At 170 BPM, chord pacing is a groove decision, not just a harmony decision.

Session View is perfect because you can A/B instantly with scenes.

Build multiple pacing variants: two-bar holds, one-bar changes, half-bar flips, and anticipation changes.

Use Launch Quantization, Legato, and Follow Actions to explore quickly, then record a performance into Arrangement.

And for darker, heavier DnB: fewer chord changes, more automation, cleaner low mids, and stabs that interact with the snare like call and response.

If you tell me your sub pattern and key, I can suggest three clean chord pacing sets that will sit over it at 170 without muddying your drop.