DNB COLLEGE

Drum & Bass Ableton Live 12 Tutorials

LESSON DETAIL

Sequence a call-and-response riff from scratch in Ableton Live 12 for jungle oldskool DnB vibes (Intermediate)

An AI-generated intermediate Ableton lesson focused on Sequence a call-and-response riff from scratch in Ableton Live 12 for jungle oldskool DnB vibes in the Atmospheres area of drum and bass production.

Back to lessons
Sequence a call-and-response riff from scratch in Ableton Live 12 for jungle oldskool DnB vibes (Intermediate) cover image

Narrated lesson audio

The voice track includes the tutorial plus extra teacher commentary.

Open audio file

Main tutorial

```markdown

Sequence a Call-and-Response Riff in Ableton Live 12 (Oldskool Jungle / DnB Atmospheres) 🥁🌌

1. Lesson overview

In jungle and oldskool DnB, call-and-response riffs are a huge part of the vibe: one phrase “calls” (often brighter/forward), the next phrase “responds” (often darker/filtered/spacey). You’ll use this technique to create movement and narrative without overcrowding your mix—perfect for atmospheric rollers.

This lesson focuses on Ableton Live 12 workflow and stock devices to build a call-and-response riff from scratch, then arrange it like a proper jungle tune.

---

2. What you will build

You’ll create:

  • A 2-bar call phrase (higher, clearer, attention-grabbing)
  • A 2-bar response phrase (lower, filtered, moodier)
  • Both phrases routed into a simple atmospheric bus with reverb/delay and sidechain movement
  • A clean arrangement concept that drops in and out over breaks/bass
  • End result: a 4-bar repeating riff (call+response) that feels authentic in oldskool jungle / atmospheric DnB, ready to sit over breaks and a rolling sub.

    ---

    3. Step-by-step walkthrough

    Step 0 — Session setup (tempo, groove, palette)

    1. Set tempo: `165–170 BPM` (try 168 BPM for classic jungle pace).

    2. Warp mode: keep audio (breaks) in Complex Pro later, but for this lesson we’re mainly MIDI.

    3. Create these tracks:

    - MIDI Track 1: `CALL - Riff`

    - MIDI Track 2: `RESPONSE - Riff`

    - Return Track A: `Space Verb`

    - Return Track B: `Dub Delay`

    - Optional: Audio Track: `Break` (if you want to test in context)

    🎛️ DnB mindset: riffs should complement break transients and bass weight. Leave room.

    ---

    Step 1 — Build a “call” instrument (bright, present) ✨

    On `CALL - Riff`, load Wavetable (stock).

    Wavetable settings (quick, effective jungle lead):

  • Osc 1: Basic Shapes → Saw (or “Bright Saw”)
  • Osc 2: Basic Shapes → Square (low level for bite)
  • Unison: `2 voices`, Amount `20–35%` (don’t go trance)
  • Filter: MS2 (or LP24)
  • - Cutoff: ~`2.5–5 kHz`

    - Resonance: `10–20%`

  • Amp Env: fast and plucky
  • - Attack `0–5 ms`

    - Decay `250–450 ms`

    - Sustain `0–15%`

    - Release `80–160 ms`

    Add a simple chain after Wavetable:

    1. Saturator

    - Drive: `2–6 dB`

    - Soft Clip: On

    2. EQ Eight

    - High-pass around `120–200 Hz` (keep it out of sub space)

    - Small dip `2–4 kHz` if it gets harsh later

    ✅ This call patch should cut through without needing tons of volume.

    ---

    Step 2 — Write the call phrase (2 bars, hooky but sparse)

    Set your loop to 2 bars first (we’ll expand to 4 after).

    Key choice: try F minor or G minor (classic dark tone).

    In the MIDI clip:

  • Grid: 1/16 with occasional 1/32 nudges for energy.
  • Keep it syncopated and “question-like.”
  • Example call pattern idea (2 bars):

  • Use notes around: `F3, Ab3, C4, Eb4` (if in F minor)
  • Rhythm approach:
  • - Bar 1: short stabs on 1, 1.2, 1.3.4

    - Bar 2: answer the rhythm with a slightly longer note on 2.3 then a quick two-hit pickup into the loop

    Human feel (important):

  • In the clip, vary Velocity:
  • - Accents: `95–120`

    - Ghosts: `50–80`

  • Nudge one or two notes slightly late (`+5 to +12 ms`) to get that lurchy jungle swagger.
  • 🎚️ If it feels stiff: add Groove Pool swing:

  • Try MPC 16 Swing 57–62 (subtle, don’t overdo).
  • Commit only if you’re happy.
  • ---

    Step 3 — Build a “response” instrument (darker, filtered, more atmospheric) 🌑

    On `RESPONSE - Riff`, load Analog (stock) or another Wavetable. Let’s use Analog for oldschool flavor.

    Analog settings (moody response):

  • Osc 1: Saw
  • Osc 2: Sine or Square very low (adds body)
  • Filter: LP24
  • - Cutoff: `300–1,200 Hz` (start low!)

    - Resonance: `15–30%`

    - Envelope Amount: `20–40%` (so it “wahs” subtly)

  • Amp Env:
  • - Attack `5–20 ms` (slightly softer than call)

    - Decay `400–700 ms`

    - Sustain `0–20%`

    - Release `150–300 ms`

    Response chain (for texture + space control):

    1. Auto Filter

    - LP mode, Cutoff around `600–2k` (map macro later)

    - Add a tiny bit of Drive (`2–5`)

    2. Redux (optional, very light)

    - Downsample: `1.2–2.5`

    - Dry/Wet: `5–15%` (just grit)

    3. EQ Eight

    - High-pass `80–120 Hz`

    - Small notch if it rings

    ---

    Step 4 — Write the response phrase (2 bars, “answer” the call)

    Now extend your loop to 4 bars total:

  • Bars 1–2 = CALL plays
  • Bars 3–4 = RESPONSE plays
  • Arrangement approach:

  • In the CALL clip: write notes for bars 1–2, leave bars 3–4 empty.
  • In the RESPONSE clip: leave bars 1–2 empty, write bars 3–4.
  • How to make the response feel like a response:

  • Use a lower register (e.g., `F2–C3`) or the same notes but down an octave.
  • Use longer notes and fewer hits.
  • End with a “lead-in” note that points back to bar 1.
  • Concrete tip: If your call ends on an “open” note (like C), make the response end on the root (F) so it resolves and cycles nicely.

    ---

    Step 5 — Create an atmosphere bus (returns + sidechain movement) 🌫️

    Atmosphere in jungle is often reverb/delay that ducks out of the way of drums.

    #### Return A: “Space Verb”

    Add Hybrid Reverb on Return A:

  • Mode: Convolution + Algorithm
  • Convolution: choose a Hall / Warehouse / Large Space
  • Reverb Time: `3.0–6.5s`
  • Pre-delay: `20–45 ms` (keeps clarity)
  • Low Cut: `200–400 Hz`
  • High Cut: `6–10 kHz` (optional darker vibe)
  • Dry/Wet: `100%` (since it’s a return)
  • Then add Compressor after it for ducking:

  • Enable Sidechain
  • Input: your Break track (or Kick/Snare group)
  • Ratio: `3:1–6:1`
  • Attack: `1–10 ms`
  • Release: `80–180 ms`
  • Threshold: adjust until the verb ducks noticeably on hits
  • #### Return B: “Dub Delay”

    Add Echo on Return B:

  • Time: 1/8 dotted or 1/4
  • Feedback: `25–45%`
  • Filter: HP `250–450 Hz`, LP `4–8 kHz`
  • Modulation: small (`5–15%`) for movement
  • Add Limiter after Echo if it runs away
  • ✅ Now send:

  • CALL: small sends (A: `-18 to -12 dB`, B: `-20 to -14 dB`)
  • RESPONSE: more sends (A: `-14 to -8 dB`, B: `-18 to -10 dB`)
  • This keeps the call upfront and the response deeper in the mist.

    ---

    Step 6 — Glue them with macro control (performance-ready) 🎛️

    Group each riff track’s device chain (`Cmd/Ctrl+G`) and map key parameters to Macros:

    CALL Macros:

  • Macro 1: Filter Cutoff (open/close hook)
  • Macro 2: Saturator Drive
  • Macro 3: Reverb Send amount
  • RESPONSE Macros:

  • Macro 1: Auto Filter Cutoff
  • Macro 2: Redux Dry/Wet (grit on demand)
  • Macro 3: Delay Send amount
  • Then automate these in Arrangement:

  • Open CALL cutoff slightly in the 8 bars before the drop
  • Increase RESPONSE reverb/delay during breakdown or transition fills
  • ---

    Step 7 — Place it in a jungle arrangement (quick blueprint)

    Try this 32-bar structure:

  • Bars 1–8: Break + pads, RESPONSE only (filtered, lots of space)
  • Bars 9–16: Introduce CALL quietly (high-pass it), tease the hook
  • Bars 17–24 (Drop): Full CALL/RESPONSE alternating clearly
  • Bars 25–32: Remove CALL, let RESPONSE trail with dub delay; add a break edit/fill
  • 🧠 Jungle trick: mute the call for 1 bar every 8 bars so the listener “misses” it.

    ---

    4. Common mistakes

  • Both phrases too busy: If call and response both have rapid hits, the groove collapses. Keep response simpler.
  • No register contrast: If both live in the same octave, it doesn’t read as a conversation.
  • Too much low end in the riff: Leads fighting sub/bass is the fastest way to ruin a rolling mix. High-pass and keep it intentional.
  • Reverb not ducked: Big atmosphere + no ducking = washed-out breaks.
  • Identical processing: If call and response share the same tone/space, the “A/B” effect disappears.
  • ---

    5. Pro tips for darker/heavier DnB 🖤

  • Minor 2nd tension: Add a quick passing note (e.g., in F minor, use Gb briefly) to make it nastier—just don’t overuse it.
  • Resample for character: Freeze + Flatten the response, then chop it like audio. Add tiny fades and reverse tails for spooky jungle edits.
  • Multiband dynamics on the return: Put Multiband Dynamics after Hybrid Reverb (Return A) and tame the low-mid bloom (around `200–500 Hz`).
  • Distortion in parallel: Create a return with Roar (or Saturator) + EQ, send only the response to it lightly for gritty depth.
  • Call clarity with transient space: Sidechain the CALL slightly from the snare only (light settings) so it “speaks” between hits.
  • ---

    6. Mini practice exercise (15–20 minutes) ⏱️

    1. Build your call phrase in 2 bars, using only 4 notes max.

    2. Duplicate it to response, then:

    - Drop it down an octave

    - Delete 50% of the notes

    - Increase reverb send by ~`4–6 dB`

    3. Add one automation:

    - RESPONSE filter cutoff slowly opens across bars 3–4, then snaps shut at bar 1.

    Goal: the loop should feel like it’s asking a question, then answering from the shadows.

    ---

    7. Recap ✅

  • You built two contrasting instruments: CALL (bright, present) and RESPONSE (dark, filtered).
  • You sequenced a clean 4-bar call-and-response by leaving space in each clip.
  • You used Hybrid Reverb + Echo returns with sidechain ducking to get that classic atmospheric jungle depth.
  • You mapped macros and planned arrangement moves so the riff evolves like a real DnB track.

If you want, tell me your target sub/bass style (Reese? sine + harmonics? 4x4 jungle techno crossover?) and I’ll suggest note ranges and riff rhythms that avoid clashing with it.

```

Ask GPT about this lesson

Chat with the lesson tutor, get follow-up help, or use quick actions.

Bigup 👽 Ask me anything about this lesson and I’ll answer in context.

Narration script

Show spoken script
Title: Sequence a call-and-response riff from scratch in Ableton Live 12 for jungle oldskool DnB vibes (Intermediate)

Alright, let’s build a proper oldskool jungle call-and-response riff from absolute scratch in Ableton Live 12. The goal here is that classic conversation vibe: a bright, upfront phrase that “speaks,” then a darker, misty phrase that “answers.” And we’re going to make it sit correctly in the Atmospheres lane of drum and bass production, meaning it brings movement and emotion without stealing the transients from the break or the weight from the sub.

By the end, you’ll have a four-bar loop where bars one and two are the call, bars three and four are the response, both feeding a space bus with reverb and delay that ducks out of the way of the drums. It’s going to feel like a real jungle record quickly, even with stock devices only.

First, the setup.

Set your tempo to somewhere between 165 and 170 BPM. I’m going to pick 168 because it’s a sweet spot for that classic jungle pace: fast, but still roomy. We’re mostly doing MIDI today, so don’t stress warp settings yet.

Now create four tracks:
One MIDI track called CALL – Riff.
A second MIDI track called RESPONSE – Riff.
Then create two return tracks. Name Return A “Space Verb” and Return B “Dub Delay.”
Optional, but recommended: add an audio track called Break, so you can throw any loop on it and check the riff in context. Even a basic break will immediately tell you if your notes are stepping on the snare.

And quick mindset check before we touch any synths: in jungle, your drums own the transients. The riff is there to create narrative and glue the vibe together. If you get tempted to fill every gap with notes, resist it. Space is the whole point.

Cool. Let’s build the call instrument.

Go to the CALL – Riff track and load Wavetable. We’re going for bright and present, but not trancey, not supersaw festival. Think: slightly rude, slightly glossy, but still lean.

In Wavetable, set Oscillator 1 to a saw. Basic Shapes Saw is perfect. For Oscillator 2, add a square, but keep its level low. That square is just there for a little bite in the midrange so it speaks on small speakers.

Turn on unison, but keep it controlled: two voices, and set the amount around 20 to 35 percent. If you go too wide, you’ll lose the mono punch and your break will start feeling less aggressive by comparison.

Now the filter. Try MS2 or a 24dB low-pass. Set cutoff somewhere around 2.5k to 5k. Jungle leads are often bright, but you don’t need “ice pick.” Add a touch of resonance, like 10 to 20 percent, just to give the filter edge when you automate it later.

Now the amp envelope: make it plucky. Attack basically instant, like 0 to 5 milliseconds. Decay around 250 to 450 milliseconds. Sustain very low, like 0 to 15 percent. Release around 80 to 160 milliseconds. We want it to stab and get out of the way.

After Wavetable, add Saturator. Drive around 2 to 6 dB, and turn Soft Clip on. This is one of those jungle cheats: you get perceived loudness and attitude without just pushing the fader.

Then add EQ Eight. High-pass it somewhere around 120 to 200 Hz so you’re not fighting the bass and sub. And just remember: if later it gets harsh, a tiny dip somewhere around 2 to 4k can calm the bite without killing presence.

At this point, play a few notes. You want it to cut through at a reasonable volume. If you need it insanely loud to be heard, the patch is probably too dull or too wide.

Now let’s sequence the call phrase.

Set your loop brace to two bars for now. We’ll expand to four after we’ve got the “question” working.

Pick a key. F minor is a classic dark jungle vibe, G minor too. I’ll talk in F minor for reference. Keep your note choices tight: you don’t need a full melody; you need a motif.

Create a MIDI clip on the call track. Set grid to 1/16, and feel free to use occasional 1/32 nudges later for little flicks of energy, but don’t start there. Start simple.

Here’s a practical approach: use F3, Ab3, C4, and Eb4 as your little note family. Now write something syncopated and “question-like.” Think short stabs with gaps.

Try this vibe: in bar one, you hit a stab right on beat one, then another on the “and” of one, then something late in the bar like around beat 1.3.4 if you’re thinking in 16ths. In bar two, answer your own rhythm: maybe a slightly longer note around beat 2.3, then two quick pickups right before the loop comes back to bar one.

Now, the part a lot of people skip: make it feel human.

Open the velocity lane and give it dynamics. Accents can live around 95 to 120. Ghosts around 50 to 80. That alone gives you the oldskool “played” feeling.

Then do one more thing: pick one or two notes and nudge them slightly late, like 5 to 12 milliseconds. Not everything. Just a couple. Jungle has that lurch, that swagger. Perfect timing is the enemy here.

If it still feels stiff, use the Groove Pool. Try MPC 16 Swing around 57 to 62. Subtle. The aim is to make the riff lean into the break, not stumble. And only commit the groove if you’re sure, because once you commit, you’re basically printing that feel.

Alright. Now let’s create the response instrument: darker, filtered, moodier, and more atmospheric.

Go to the RESPONSE – Riff track and load Analog. This is a nice way to get a slightly oldschool flavor without doing anything complicated.

Osc 1: Saw. Osc 2: add a sine or square very low, just for body. Don’t make it a bass; it’s a response voice.

Filter: LP24. Start with cutoff low, somewhere in the 300 to 1200 Hz range. Start lower than you think. Add resonance around 15 to 30 percent. Then give the filter envelope a bit of influence, like 20 to 40 percent, so it has a subtle “wah” when notes hit.

Amp envelope: slightly softer than the call. Attack around 5 to 20 milliseconds. Decay 400 to 700 milliseconds. Sustain low, 0 to 20 percent. Release 150 to 300 milliseconds. The response can hang a little longer because it’s meant to smear into the atmosphere, but we still don’t want it washing over snares.

Now add a response chain.

First, Auto Filter. Set it to low-pass. Start cutoff around 600 Hz to 2k, and add just a touch of drive, like 2 to 5. We’re using this because it’s an easy parameter to automate later, and it adds character.

Optional: add Redux, but be gentle. Downsample around 1.2 to 2.5, and Dry/Wet only 5 to 15 percent. We’re not doing full “bitcrush”; we’re doing “early sampler bandwidth” vibes.

Then EQ Eight: high-pass around 80 to 120 Hz. If it rings, notch the annoying frequency instead of just low-passing everything.

Now we write the response phrase.

Extend the loop to four bars total.

The arrangement trick is important: we’re going to make the call and response extremely obvious by literally leaving space in each clip.

On the CALL clip: put your notes only in bars one and two. Leave bars three and four completely empty.
On the RESPONSE clip: leave bars one and two empty. Write notes only in bars three and four.

This is one of the cleanest ways to get “conversation” without getting tangled in automation or muting.

Now, how do you make the response read as an answer?

Three main moves:
One: go lower. If the call was hanging around F3 to C4, bring the response down around F2 to C3, or just drop the same motif down an octave.
Two: use fewer hits and longer notes. The response is the shadow. Let it breathe.
Three: make the end of the response point back into bar one. That’s the loop magic.

A super practical tip: if your call ends on something that feels open, like C, then end the response on the root, F, so the loop resolves and restarts cleanly. You’re basically telling the listener, “we’re home, now the next question starts.”

Now let’s build the atmosphere bus. This is where it stops sounding like a dry MIDI exercise and starts sounding like jungle.

Go to Return A, Space Verb. Drop Hybrid Reverb on it.

Set it up as a big space: Convolution plus Algorithm mode is great. Choose a hall or warehouse type impulse. Set reverb time somewhere around 3 to 6.5 seconds. Pre-delay around 20 to 45 milliseconds so the initial stab stays clear before the cloud arrives.

Then filter the reverb. Low cut around 200 to 400 Hz so you’re not building mud. Optionally high cut around 6 to 10k if you want it darker and more “tape-era.”

Set Dry/Wet to 100 percent, because it’s a return.

Now the crucial jungle part: duck the reverb with sidechain so the drums stay crisp.

After Hybrid Reverb, add a Compressor. Turn on Sidechain. Choose your Break track as the input, or if you’ve got drums grouped, use the kick/snare group. Ratio 3:1 up to 6:1. Attack 1 to 10 milliseconds, release 80 to 180 milliseconds. Then bring the threshold down until you can clearly hear the reverb tuck down on snare and kick hits, then swell back up in the gaps.

That swelling is the atmospheric breathing sound. That is the oldskool magic.

Return B, Dub Delay. Add Echo.

Set time to 1/8 dotted or 1/4. Feedback 25 to 45 percent. Filter it: high-pass 250 to 450 Hz, low-pass 4 to 8k. Add a small amount of modulation, 5 to 15 percent, so repeats drift a little. And put a Limiter after Echo because delays can get excited and you don’t want surprise peaks.

Now set your sends.
On the CALL track, keep the sends relatively small. Think Space Verb around minus 18 to minus 12 dB, and Dub Delay around minus 20 to minus 14 dB. The call needs to be readable and direct.
On the RESPONSE track, push more send. Space Verb around minus 14 to minus 8 dB, and Delay around minus 18 to minus 10 dB. The response lives in the fog.

Now, quick coach move: check the conversation on a spectrum and in mono.

Drop Spectrum on both riff tracks, or just use Channel EQ. In general, your call will have strong energy in that 1 to 5k zone, and your response will live more around 250 Hz to 2k. Doesn’t have to be exact, but if both are blasting the same range, your ear won’t separate them.

Then do a mono check. Put Utility on the master temporarily and hit Mono. If the two-part conversation collapses, it usually means the call is too wide, or the response is too similar in rhythm and register. Reduce unison width on the call, or go lower and simpler on the response.

Now let’s make this playable and arrangable with macros.

Select the device chain on the CALL track and group it, Control or Command G. Map Macro 1 to the Wavetable filter cutoff. Macro 2 to Saturator drive. Macro 3 to the reverb send amount. The reason we map sends is because it’s an arrangement superpower: you can throw a single note into the void for a transition without rewriting MIDI.

Do the same on the RESPONSE track: group it. Macro 1 to Auto Filter cutoff. Macro 2 to Redux Dry/Wet if you used Redux, so you can add grit on demand. Macro 3 to the delay send amount.

Now you can automate like a producer instead of like a programmer.
Before a drop, open the call filter slightly over eight bars. During a breakdown, swell the response reverb and delay. Then snap things back tight for the drop.

Let’s place it into a quick jungle arrangement blueprint.

Try a 32-bar idea:
Bars 1 to 8: break plus pads, response only, filtered, lots of space. This sets the mood.
Bars 9 to 16: introduce the call quietly, maybe high-pass it a bit so it teases without taking over.
Bars 17 to 24: the drop. Full call and response alternating clearly. This is where the loop earns its keep.
Bars 25 to 32: remove the call, let the response trail with dub delay, and add a break edit or fill.

And here’s a classic jungle trick: mute the call for one bar every eight bars. Just one bar. The listener suddenly misses it, then you bring it back and it feels like an event without doing anything complicated.

Now, a few phrasing markers so it doesn’t sound like a static four-bar loop.

Add one micro-event, maybe two.
You can add a single pickup note in the last 16th before bar one. Or delete one stab that normally lands on a strong offbeat, so there’s a “hole” that feels intentional. Or do a tail throw: on the last note of bar two or four, automate a quick spike into Echo so the delay blooms and then gets ducked by the drums. That one move screams jungle.

If your riff fights the break, do not just turn it down. Reshape it.
If it’s too clicky and masking snare attack, tame the initial transient with a little compression, no sidechain, just a touch. Or use Shaper if you like. If it’s too sustained and washing into the break ambience, shorten the decay in the amp envelope so it becomes more percussive.

Quick groove checklist: solo break plus riff.
Is the call landing between snare hits more than on top of them?
Does the response feel slightly later, more laid-back?
Do you have at least one full eighth-note gap somewhere every two bars?
If yes, you’re in the pocket.

Now, two advanced variation ideas to level it up if you want.

One: cross-rhythm. Keep the response straight, like eighth notes or quarters. Then make the call accent every three sixteenths for one bar, and resolve back to the grid in bar two. That creates busy-but-controlled tension without adding a ton of extra notes.

Two: answer with harmony instead of melody. For the response, hold a pedal note, like the root or fifth, through most of bars three and four. Then add two short dyad hits right before bar one returns. That reads as a response even if it’s barely melodic.

Alright, common mistakes to avoid as you finish this.

Don’t make both phrases busy. If call and response both have rapid hits, your groove collapses.
Don’t keep them in the same register. If they’re both living around the same octave, it stops sounding like a conversation.
Don’t leave low end in your riff. High-pass it and let the sub own the bottom.
Don’t run huge reverb without ducking. You’ll wash out the break instantly.
And don’t process both phrases identically. If they share the same tone and space, you lose the A versus B effect.

Now a quick 15 to 20 minute practice exercise you can do right after this lesson.

Build your call phrase in two bars using four notes maximum. Strict limit.
Duplicate the MIDI idea into the response, drop it down an octave, delete half the notes, and increase the reverb send by about 4 to 6 dB.
Then automate one thing: the response filter cutoff slowly opens across bars three to four, and snaps shut when bar one returns.

Your goal is simple: the loop should feel like it’s asking a question, then answering from the shadows.

Let’s recap.

You built two contrasting instruments: call is bright and present, response is dark and filtered.
You sequenced a clean four-bar call-and-response by leaving space in each clip instead of overcomplicating it.
You created atmosphere using Hybrid Reverb and Echo returns, with sidechain ducking so the breaks stay crisp.
And you mapped macros so the riff evolves across an arrangement like a real jungle tune, not a static loop.

If you tell me what your sub or bass is doing in the track, like a Reese, a pure sine with harmonics, or something more modern, I can suggest safe note ranges for the call and response so they never clash with the low end, and I can suggest placements that dodge the snare in a really classic way.

mickeybeam

Go to drumbasscd.com for +100 drum and bass YouTube channels all in one place - tune in!

Generating PDF preview…