Mixing and mastering
Kick and bass clashing? Find the octave and the bars where it happens
Find the octaves and bars where kick and bass clash, then try EQ, ducking, arrangement or tuning changes. Check each move in the full mix.
The short answer. Kick and bass clash when both are loud in the same octave at the same time. Find the octave (usually 40–80 or 80–160 Hz), find the bars where both play there, then fix only that spot: give one of them the octave, carve a little EQ room in the other, or duck the bass when the kick hits. A fix that runs everywhere solves a problem that only exists in some places.
Most "how to mix kick and bass" advice is the same five tips: EQ, sidechain, dynamic EQ, mono, layer. They're all real tools. What the tips skip is the diagnosis: where is the clash, and when? Answer those first and the right tool is usually obvious.
What masking is
Masking is when one sound makes another harder to hear because both have energy in the same frequency range at the same moment. In the low end it's worse than anywhere else:
- Kick and bass both put most of their energy below 200 Hz, often in the same octave.
- Low frequencies are long. A 50 Hz cycle takes 20 ms, so a bass note and a kick decay overlap for a while even when they don't start together.
- Club systems and headphones show the low end very differently, so a clash that's polite on laptop speakers can turn into a wall on a big system.
The result: the low end gets louder without getting clearer. You push the kick up to hear it, the bass disappears, you push the bass up, and the meter fills with mud.
Step 1: find the octave
Think in octaves, not single frequencies:
| Octave | Range | What usually lives there |
|---|---|---|
| Sub-bass | 20–40 Hz | Felt more than heard; a lot of sub bass, long kick tails |
| Sub | 40–80 Hz | Kick body, sub bass fundamentals |
| Bass | 80–160 Hz | Kick punch, bass fundamentals and first harmonics |
| Upper bass | 160–315 Hz | Bass harmonics, kick "box", low synths |
Solo the kick and bass together. Sweep a narrow EQ boost slowly through 40–200 Hz on the mix bus (listen only, don't keep it) and note where the pair suddenly sounds thick or flappy. Or put an analyzer on each track and see where each puts its peak energy. If both have their biggest bump in the same octave, that's your clash.
Step 2: find the bars
A clash only matters where both parts are loud there at once. That depends on the arrangement:
- A bass that plays between kicks (offbeat bass in house, rolling bass in techno) may barely overlap the kick.
- A sustained sub under a four-on-the-floor kick overlaps on every beat.
- A bass that only comes in for the drop clashes in the drop, not the intro.
Loop each section and listen to the two tracks alone. Write down the bars where it gets thick. That list decides the fix: a clash in 8 bars of a 128-bar track doesn't need a fix that runs for all 128.
Step 3: fix it there, and only there
Give the octave to one of them
The cleanest fix is a decision. One part owns the sub octave, the other steps up:
- Sub-heavy bass, tighter kick: high-pass or shelve the kick's lowest octave a little and let its punch (around 60–100 Hz) and click do the work.
- Big kick, higher bass: high-pass the bass so its fundamentals start above the kick's body, and let the bass's harmonics carry the line.
Carve a little EQ room
If both need to stay full, cut a few dB in the shared octave on the part that matters less there, and leave the other one's body alone. A moderate bell (around Q 1.4) of 2–4 dB is usually enough. Big, narrow cuts tend to sound like a hole.
Duck the bass when the kick hits
When the clash is about timing (both hit together, every beat), ducking is the classic fix: the bass dips for a few milliseconds each time the kick hits, then comes back. Usually that's a compressor on the bass keyed from the kick (sidechain compression), or a volume envelope locked to the beat. For a smaller, frequency-limited version, a dynamic EQ on the bass can dip only the shared octave when the kick plays.
Change the arrangement
Sometimes the fix is notes, not processing:
- Move the bass off the kick: offbeat bass, or let the kick's decay finish before the bass note starts.
- Shorten long bass notes in the busiest bars.
- Drop the bass out for a bar before the drop, so the drop has somewhere to land.
Tune the kick
If the kick has a pitched tail (808-style kicks especially), tune it to the song's root or fifth. A kick a semitone off the bass note beats against it, and no EQ fixes a pitch clash.
Checking the fix
Listen at a moderate level, then in mono, then on a second system. Check the busy bars you wrote down. Compare against a finished track in your genre, matched in loudness so the louder one doesn't win by being louder. If the low end got clearer and the kick still hits, you're done. If it got clearer but weaker, you cut too much.
A reproducible example: one change, measured and heard
Measurement and listening answer different questions. A number tells you whether two parts collide at a moment you chose to measure. Only your ears tell you whether the result is better. This example keeps them apart, and the steps are ones you can repeat with your own tracks.
What the files are. A kick and a bassline, rendered by monody's offline renderer on 4 October 2026 from recorded notes, with no assistant request and no external DAW. The kick is a synthesized exercise with a 180 ms pitch envelope, 32 hits on the beat at 124 BPM, not a recorded drum. The bass is the 32-note line from AI basslines you can edit. The two files differ in one thing: the timing of the bass.
- Before. The same 32 notes moved half a beat earlier, so each lands on a kick. This clash was built on purpose, it isn't one found in a real mix.
- After. The notes as they were recorded, half a beat later, on the off-beats between the kicks.
Same notes, same bass sound, same kick and the same gain in both files. We measured their overall levels within about 0.1 dB of each other.
What was measured. The bass on its own, in the first 180 ms after each of the 32 kick attacks, as RMS. On-beat: about −30.4 dBFS. Off-beat: about −96.5 dBFS, which is effectively silence. That is a measure of timing at the attack. It is not an octave analysis and not a score.
To repeat it with your own kick and bass:
- Pick eight bars where the low end feels cloudy, and write down the bar numbers.
- Render them as they are. That is your before. Don't touch the gain.
- Decide what to measure. In the example it was the bass level in the window after each kick. For a frequency clash, measure the octave where both are loud at the same moments, with an analyzer that shows both tracks over time, or monody's Finish view.
- Change one thing. One EQ cut, one duck, or one note moved, not three. If you change several you won't know which one worked.
- Keep the level the same. Leave the gain alone, or turn the louder render down until they match. Louder sounds better, and that is the usual way to fool yourself.
- Measure again on the same bars with the same tool.
- Listen in order. Before, after, before, then after again. Do it at a moderate level, in mono, and on a second system if you can.
- Decide separately. The numbers say whether the collision dropped. Your ears say whether the kick still hits and the bass still has weight.
What the example does and doesn't show:
- It shows a controlled change. Same notes and sound, one difference, equal gain, and a number before and after.
- It doesn't prove musical quality. A bass that avoids the kick can still be the wrong bass. A cleaner measurement is a technical result, and a track can measure cleaner and sound weaker, which is the "you cut too much" case above.
- It isn't a benchmark. It is one pair of files with a synthetic kick, not a test of how often a fix works.
- It isn't your mix. Your kick, bass and room are different, so repeat it with your own.
How monody finds it
monody's Finish view renders the song and checks every pair of tracks (not buses) octave by octave. It flags a pair when:
- each track carries at least 15% of its own energy in that octave;
- both are loud there (at least 15% of that octave's total) at the same moments, in at least 35% of the moments either one plays there;
- and that adds up to at least four seconds.
The finding names both tracks, the octave, the bars where it happens and how often they overlap. It also suggests which track gives way: the one for which that octave matters less. "Carve room" hands it to the assistant, which makes the EQ edit in your session. Its edits are marked. Hear the result with Before/After, then measure again in Finish to check whether the overlap dropped.
Sidechain keys. monody's source (the committed build we checked on 4 October 2026) lets a device take its key from another track or bus: a compressor on the bass can listen to the kick. The master can't be a key source, a track can't key its own devices, and a key that would loop back through the mix is refused. The compressor, bus compressor, gate, auto-filter and vocoder accept a key. Whether the build you have installed includes this depends on its version, so check Settings, About. The kick and bass example above is a timing edit, not a sidechain test.
Checked on 1 October 2026. The sidechain paragraph and the example were added on 4 October 2026.
Questions
- Why do my kick and bass clash?
- Both put most of their energy into the same low octaves, usually somewhere between 40 and 160 Hz, and they often hit at the same moments. When two sounds are loud in the same octave at the same time, the ear can't separate them, so the low end turns into one blurred thump and gets louder without getting clearer.
- Should the kick or the bass take the sub?
- Pick one owner per octave. A common split is a sub-heavy bass with a kick that lives a little higher (its punch around 60–100 Hz and its click above), or a big sub kick with a bass that sits higher. Either works; trying to have both full in the same octave is what clashes.
- Do I need sidechain compression to fix kick and bass?
- Not always. Sidechain ducking fixes the moments where both hit together, which is the classic case in four-on-the-floor music. If they clash only in some bars, or only because both are too full in the same octave, EQ carving or an arrangement change can be cleaner.
- How do I know which bars the clash happens in?
- Masking only matters where both parts play loudly in the same octave at once. Solo the two tracks and loop the sections one by one, or use an analyzer that compares the tracks over time. monody's Finish view lists the bars for each clash it finds.
- Should I tune my kick to the key of the song?
- It helps when the kick has a clear pitched tail, as long 808-style kicks do. A kick tuned to the root (or the fifth) sits with the bassline instead of beating against it. Short, clicky kicks matter less.