Muddy trance low end is almost never a bad sound — it’s a scheduling problem. Your kick and bass are trying to occupy the same frequencies, the same phase relationship, and the same milliseconds in time, and no mastering EQ will unpick that after the fact. Treat the two as one instrument that gets split across time by sidechain and across frequency by EQ, and the mud dissolves on its own.
TL;DR
- The 40–120 Hz zone is where kick sub and bass sub collide — pick one to own it.
- Sidechain release shape matters more than depth; a lazy release keeps the bass permanently ducked.
- The kick has a pitch. Tune your bass and key to it, or pick a different kick.
- Everything below roughly 120 Hz should be mono and phase-friendly with the kick.
- The “blanket over the speakers” feeling lives at 200–400 Hz, not in the sub.
Diagnose before you touch a plugin
Solo the kick and bass together, loop four bars, and listen once on headphones and once on a small speaker. You are looking for a specific symptom, not a general “it sounds bad” feeling. Match what you hear to one of the rows below and start there.
| Symptom | Likely cause | First move |
|---|---|---|
| Kick disappears the moment the bass enters | Bass sub masking kick fundamental | High-pass the bass around 80–100 Hz |
| Boomy, one-note “wooooo” underneath | Kick pitch and bass root are close but not locked | Retune the bass in cents until beating stops |
| Woolly, blanket-over-the-mix feel | 200–400 Hz build-up in the bass mid layer | Narrow 3–5 dB cut on the offending resonance |
| Pumping but still muddy | Sidechain release too slow — bass never fully recovers | Shorten release so the bass returns before the next kick |
| Great in headphones, sludge on speakers | Stereo content below 120 Hz | Force mono under 120 Hz, check correlation meter |
| Kick clicks but has no weight | Kick and bass sub partially cancelling | Flip kick polarity or nudge it a few ms |
Split the sub: one instrument owns it
The single biggest source of trance mud is two sub-heavy sounds fighting for 40–120 Hz. In most trance styles, the kick has a long pitched sub tail — the “boom” after the click — and the rolling bass is also sitting on a sub layer. Both cannot be full-range at once. One has to move.
My default: the kick keeps the sub, the bass gets high-passed. A rolling trance bass rarely needs anything below ~90 Hz to feel powerful, because the kick is playing every quarter note and doing all the sub lifting. On the bass bus:
- Steep high-pass (24 dB/oct) around 30 Hz to kill DC and rumble.
- A gentler high-pass (12 dB/oct) somewhere between 80 and 100 Hz, tuned by ear until the bass still has body but no longer thumps.
- Narrow bell cut of 2–4 dB somewhere in 200–350 Hz to clear the mid-mud (find it by sweeping — see below).
- A small 1–2 dB bell around 900 Hz–1.5 kHz for definition on small speakers.
A/B the second high-pass in and out while soloing kick+bass. When it’s engaged, the kick’s fundamental should snap into focus on every beat. If the solo’d bass now sounds thin, that’s correct — it’s not meant to sound huge on its own. It’s meant to sound huge with the kick.
For big-sub styles (uplifting rollers, psy-adjacent) where the bass genuinely needs sub weight, invert this: let the bass own the sub, and shorten the kick’s sub tail with a fast decay envelope. But pick one — never both.
Tune the bass to the kick
A surprising amount of “mud” is actually detuning. Trance kicks are strongly tonal thanks to that pitch-down tail, and if the bass root is even 20 cents off, you get slow amplitude beating that reads as an unstable, murky low end.
Drop the kick into your DAW’s sampler and figure out its pitch. Most commercial trance kicks land somewhere between F1 and A1 by the time the tail settles. Once you know that note, one of two things has to be true: the kick is the same pitch class as your track’s root, or it sits a consonant interval away (fifth or octave). If your key is F minor and the kick reads as F#1, either retune the kick down a semitone or find a different kick.
Then listen for the beating. If the kick hits and you hear a slow “wow-wow-wow” underneath, kick and bass are close but not locked. Nudge the bass in single-cent increments until the wobble slows to zero. This is genuinely audible on a sub or good headphones — don’t skip it because it feels fussy.
Sidechain: fix the release before you touch the depth
Most producers set sidechain by watching gain reduction hit −12 dB and calling it done. Depth is rarely the problem. Release is. If the release is too long, the bass never fully recovers before the next kick and lives in a permanently half-ducked, mushy state. Too short, and you get an audible click at the release point that reads as noise, not groove.
At 138 BPM, a quarter note is 435 ms and an eighth is 217 ms. You want the bass fully back up a few tens of milliseconds before the next kick lands, with a smooth curve, not a hard corner. Starting points for a compressor doing the ducking:
- Attack: fastest available (0.01–0.1 ms).
- Release: 150–220 ms at 138 BPM, then tune by ear.
- Ratio: 4:1 to 8:1.
- Threshold: set for around 8–12 dB of gain reduction on the kick.
If you’re using a volume shaper (LFOTool, Kickstart, ShaperBox, Volumeshaper), the curve shape matters more than the depth knob. A curve that dips fast and rises smoothly across roughly 60–70% of the beat feels tight. A curve that stays low across the full beat and then snaps back up feels pumpy and — counter-intuitively — muddier, because the bass rushes back in exactly when the next kick is trying to punch.
Zoom in on the bass waveform after the sidechain is applied. The amplitude envelope should visibly return to full height before the next kick’s transient, not at the same moment.
The 200–400 Hz mud belt
Everyone blames 60 Hz for mud. It’s usually 250. The “blanket over the speakers” feel almost always sits between 200 and 400 Hz — and it’s rarely the kick. It’s the bass mid layer, sometimes the pad, and occasionally the kick’s body harmonic piling on top.
Solo the bass mid layer (the saw or square above the sub) and sweep a narrow +6 dB bell through 150–500 Hz with a Q around 4–6. You’ll hit one or two obvious ugly resonances — often near 250 Hz and 350 Hz. Invert to a cut of 3–5 dB at the same frequency and Q. Repeat on any pad sitting under the bass, but more gently (1–2 dB).
Then check the kick. Most trance kicks have a punch hump around 100–150 Hz, which is fine. But if the kick also has energy at 250–350 Hz and the bass mid also has energy at 250–350 Hz, they stack. A broad 1–2 dB shelf-ish cut on the kick around 300 Hz (Q around 1) often clears the whole mix in one move.
Browse Trance packs at Myloops →
Phase-align at the sample level
This one is invisible on a spectrum analyser and obvious on a sub. When the kick’s pitched sub tail overlaps with the bass sub, their waveforms interact — and depending on where they line up in phase, they either reinforce or partially cancel. A cancelling relationship is why a great kick can suddenly feel gutless the moment the bass enters.
Zoom to sample level at the point the kick hits. Ideally the bass is fully ducked there, so nothing interacts. If it isn’t, you want the bass’s waveform moving in the same direction as the kick’s first cycle. Two practical fixes:
- Nudge the kick 1–5 ms earlier or later and listen for the sub to snap into focus.
- Flip the kick’s polarity (the ø switch) and A/B — one polarity almost always sounds noticeably fuller against your specific bass.
Neither is “correct” in an absolute sense. You’re just finding the alignment that constructively adds for this kick against this bass. Do it once, commit, and move on — don’t rabbit-hole.
Mono below 120 Hz. No exceptions.
Wide stereo bass sounds enormous on headphones and turns to sludge on a club rig, because mono playback sums left and right — and if they’re out of phase, the sum is smaller than either channel alone. A supersaw bass with heavy unison detune running full-range is literally cancelling itself before it ever meets the kick.
Use Ableton Utility, FL’s Fruity Stereo Shaper, Ozone Imager 2, bx_solo — anything with a bass-mono or width-per-band control — to force everything under 120 Hz to mono on the bass bus. Then watch the correlation meter on your master during the drop. It should hover between 0 and +1, never dipping negative when the bass hits.
For the sub layer itself, start with a pure mono sine or a barely-detuned saw low-passed at 120 Hz. All the width should come from the mid and high layers above that. This is the mechanical reason layered basses beat one full-range patch: you can set width per layer.
Layer the bass so each layer has one job
A bass patch trying to be sub, body, and bite simultaneously is almost impossible to mix against a four-on-the-floor kick. Split it into three layers, each with a job:
- Sub layer: sine or triangle, mono, low-passed around 120 Hz. No detune, no chorus, no width. This is the fuel.
- Mid layer: saw or square, mild detune, high-passed at 100 Hz and low-passed around 1 kHz. This carries the note.
- High layer: distorted saw or reese, wide stereo, high-passed at 400–500 Hz. This carries movement and grit.
Now sidechain each layer separately. Hardest duck on the sub, medium on the mid, light or none on the high. That’s why commercial trance basses feel simultaneously tight and rolling — the layers aren’t ducking in lockstep. The kick punches cleanly through a fully-ducked sub, while the high layer keeps the sixteenth-note groove alive between kicks.
Shorten the kick’s tail — don’t lengthen it
When a kick feels weak, the first instinct is to reach for a sub boost or a plugin that “adds low end”. Nine times out of ten the fix is the opposite: shorten the tail so it stops smearing into the next bass note.
Load the kick in a sampler and put a volume envelope on it. Attack at 0, decay tuned so the audible tail lands around 200–350 ms depending on tempo, with a fast release. At 138 BPM, a kick tail longer than about half a beat (~215 ms) starts colliding with the sidechain recovery of the bass — that’s your mud, right there.
If it still needs weight after that, add it in the mids, not the sub:
- Layer a short transient sample (a snap, a click) with energy around 2–4 kHz for attack.
- 1–2 dB bell around 100 Hz on the kick body for chest impact.
- A saturator — tape, tube, or a soft-clip — at 5–10% drive to generate harmonics.
Saturation is doing something specific here: it pushes kick information into the 200 Hz–2 kHz range that laptops, earbuds and phone speakers actually reproduce. Your kick then reads as powerful even on systems that can’t play the sub at all.
Reference on three systems in this order
Every low-end decision needs checking on at least three playback systems:
- Headphones: for phase, stereo width and slow beating between kick and bass.
- Phone or laptop speaker: the “does the kick still exist” test. If it vanishes on a phone, you have no midrange body — go back to saturation and click layering.
- Monitors or a car: for sub balance and room interaction.
Load a reference from an artist whose low end you trust — pick one that matches your subgenre, not a generic “big trance record” — and A/B at matched loudness. The Fletcher-Munson curve will lie to you the moment your track is even 1 dB louder than the reference, so match perceived loudness with a LUFS meter (integrated within about 1 LU) before you compare. If your kick and bass sit at a similar balance to the reference on all three systems, you’re done. Mud announces itself immediately on a phone speaker — if it survives that test, it’s clean.
Browse Trance packs at Myloops →
The bottom line
Muddy trance low end is a conflict problem, not a sound-design problem. Two elements are trying to do the same job in the same frequency range at the same moment, and until you stop them, no plugin will save the mix. Treat kick and bass as one instrument, split across time by the sidechain and across frequency by EQ.
Do it in this order: tune the kick and bass to each other first, then decide which one owns the sub, then dial in sidechain shape and timing, then clean 200–400 Hz, then check phase and mono compatibility. Those five moves in that order will get you 90% of the way to a punchy low end before you ever open a mastering plugin.
When in doubt, subtract. A clean low end is almost always a smaller low end than you think it should be — the kick and bass hit harder when they have room to breathe, not when they’re stuffed with sub.





Leave a reply