Hey — welcome. This is an intermediate Ableton lesson all about send and return workflow for drum and bass, focused on keeping the low end tight while making the top end feel huge. I’m going to walk you through a practical setup you can build in Live 10 or 11, give you concrete device chains and starting parameters, explain routing and automation strategies for drops and fills, and share pro tips and common mistakes so you don’t waste time troubleshooting later. Let’s get into it.

First, the big picture. Use multiple dedicated returns for different roles: long ambience for pads, a short snare reverb, a rhythmic echo for groove and fills, a parallel distortion bus for grit, and a parallel compressor to glue drums. Always set the effects on the returns to 100 percent wet and control the amount with the send knobs on the source tracks. That keeps one place responsible for the wet/dry mix and prevents accidental double-dipping.

Start by setting your project tempo to 174 BPM. Open the Return Tracks and create five returns. I’ll refer to them as Return A through E. Rename and color them so they’re instantly recognizable — for example, Return A Long Reverb, Return B Short Snare Reverb, Return C Rhythmic Echo, Return D Parallel Distortion, and Return E Parallel Compression.

Return A is Long Ambient Reverb for pads and atmos. If you have Live 11, use Hybrid Reverb. In Live 10 use Reverb and push decay. Set decay around 2.4 seconds to start, pre-delay about 12 milliseconds, diffusion moderate, and damp the highs to taste. Put an EQ Eight after the reverb and high-pass around 120 to 200 Hz, and consider using EQ Eight in M/S mode to cut the sides under ~350 Hz so your reverb doesn’t smear the low end. Add a Utility at the end with width around 40 to 60 percent. Set the return fader around minus six dB as a starting point.

Return B is the Short Snare Reverb — tight and snappy. Chain Reverb or Hybrid’s short algorithm, set decay between 0.4 and 0.9 seconds, pre-delay 8 to 15 ms, and Wet at 100 percent. After the reverb put a Gate if you want gated tails, then EQ Eight with a high-pass around 200 to 300 Hz, and a light Compressor last that you’ll use for ducking. Start this return around minus nine dB. Send snares and rims here at moderate levels — think around minus ten to minus seven dB on the send knob — and increase for big breaks.

Return C is your Rhythmic Echo. In Live 11 use Echo, in Live 10 use Delay. Sync on. For 174 BPM try 1/16 or 1/8 triplet for rolling grooves. Feedback is a useful parameter: 20 to 45 percent for subtle repeats, up to 60 percent for more looped rhythms. Put a filter after the delay — Auto Filter or EQ Eight — high-pass around 200 to 300 Hz and low-pass around 6 to 10 kHz so the repeats live in the mid/high band. Return fader start around minus eight dB. Automate sends to this for fills and rolling percussion movement.

Return D is Parallel Distortion for midrange bite. Chain Saturator or Overdrive, then EQ Eight to cut below around 120 Hz and boost presence around 800 Hz to 2 kHz by a couple of dB if needed. Optionally add Redux for subtle bit reduction. Drive around plus six to plus ten dB with soft clip on and trim output to unity. Set the return fader around minus ten dB. This is where you route drum bus or percussion to add aggression — but avoid sending subs. Send only the mids and harmonic content.

Return E is Parallel Compression for glue. Use Compressor or Glue with a high ratio like eight to ten to one, very fast attack around one to five milliseconds and release around 50 to 150 ms. Push it to get six to twelve dB of gain reduction and use make-up gain to bring level back. Keep this return Wet at 100 percent and blend under your dry drums — typical send amounts are subtle: think minus twelve to minus six dB, or visually 20 to 40 percent on the send knob.

Routing and bass considerations are critical in DnB. Never send sub below roughly 100 or 120 Hz to long reverb or echo. Two practical approaches: duplicate your bass track and high-pass the duplicate around 120 to 150 Hz, then send the duplicate to returns while keeping the original dry for sub energy. Or split frequencies inside a return using EQ Eight in M/S or an effect rack to keep subs out of the wet signal. Always make low end mono on returns — use Utility width or EQ Eight in M/S to collapse sides under 300 to 350 Hz.

Sidechaining returns keeps the low end punchy. Put a compressor on the return and sidechain it to your kick and snare bus. Fast attack like one to five ms and release around 80 to 200 ms usually sounds natural and lets tails breathe between hits. This is especially helpful on long reverb and echo returns so the transients cut through.

A quick word on pre-fader versus post-fader sends: leave sends post-fader most of the time so send levels follow track fader automation. Switch a send to pre only when you need the effect level independent of the track fader — for example, a live loop you want a constant echo on while you control dry level separately.

Now a few automation and arrangement strategies. For drops, kill or drastically reduce reverb sends for drums and bass on the first hit to make the drop hit harder. For fills, spike the snare send to the rhythmic echo or crank the distortion return for one-bar aggression. During builds, slowly raise long reverb on pads and open echo feedback; automate reverb decay or echo feedback on returns for tension rather than automating every source — it’s simpler and more CPU friendly. Treat returns as arrangement elements: create 1 to 2 bar automation lanes on return faders and trigger them like instruments.

Common mistakes to avoid: sending pure sub to long reverb, leaving return effects at less than 100 percent wet, overusing pre-fader sends, and forgetting to mono the low end. Also group tracks before sending where it makes sense — send from a drum bus rather than individually routing every drum unless you truly need that granularity.

Pro tips for darker, heavier DnB: use parallel distortion on midbass harmonics and percussion, employ extreme sidechain on returns for claustrophobic drops, and use Beat Repeat or Grain Delay on dedicated returns to create chaotic fills. If CPU becomes an issue, freeze and flatten a return or resample a stacked effect to audio.

A short practice exercise to put this into action: build three returns — Long Reverb, Echo, and Parallel Comp. Set Long Reverb decay around 2.4 seconds, pre-delay 12 ms, with HP at 120 Hz. Set Echo to 1/16 synced with 35 percent feedback and HP at 200 Hz. Make the parallel comp heavy enough for 6 to 10 dB GR. On your drum bus send roughly 25 to 35 percent to the parallel comp, 10 to 20 percent to echo, and small amount to the long reverb. Duplicate your bass, HP the copy at 130 Hz and send that copy to the reverb and echo while keeping the original dry. Automate a 1-bar spike to the echo send on a fill and raise the long reverb fader in a breakdown. Add a sidechain compressor to the long reverb keyed to the drum bus.

Some extra coach notes: solo-test returns by soloing the return track while the source plays and using Solo-In-Place to hear how the effect sits against the dry. Keep return faders near unity during setup and control gain with device outputs. Map Utility width to a macro for quick mono-checks and use Freeze/Flatten or resampling to manage CPU if chains get heavy. Organize returns with clear names and small text hints so collaborators know recommended send levels.

For homework, build a 32-bar section with an intro, build, drop, and breakdown, using at least three returns and resample one transition tail into a playable sample. Make sure no significant reverb energy sits under 100 Hz, transients stay punchy, and your resampled tail triggers cleanly at the drop.

Recap: use multiple focused returns, set wet to 100 percent, filter and mono low end, sidechain and automate returns for musical transitions, split bass frequencies to protect the subs, and save your return templates so you can recall them instantly. If you want, I can generate a concise checklist you can paste into your project or provide a .als outline with the exact device chains and starting parameters to drop into a template. Want that template?