How to EQ Bass: Clear Mud and Make Room for the Kick

A bass can sound great on its own and still fight everything around it. Turning up the highs will not necessarily fix the muddy frequency that is causing the problem.

Zen’s approach is to find what the bass is competing with, reduce what gets in the way, and judge the result in the song. The aim is a balanced combination of sounds, not an impressive soloed bass.

This tutorial follows HOW TO EQ YOUR BASS PROPERLY, Zen’s August 2017 lesson. He starts by making one thing clear: this is his way of reaching the result, and other approaches can work. The example frequencies below belong to those projects.

What You’ll Learn

• Decide which frequency role each bass layer should fill.

• Use the kick’s frequency content to guide a bass cut.

• Find muddy areas with an EQ audition, then reduce them.

• Check the bass again after saturation and in the full mix.

• Use selective boosts without copying another track’s EQ curve.

How to EQ Bass Around Its Role in the Mix

Before moving an EQ band, identify what else is playing with the bass. In the first example, Zen listens to the other central, mono elements and notices that they already occupy some of the mid and high-frequency space.

That gives his bass EQ a purpose. He uses a high cut, also called a low-pass filter, to reduce the bass’s upper-frequency contribution where it competes with those sounds. A low-pass filter lets the lower range through while reducing the range above its cutoff.

The lesson is not that every bass needs its highs removed. Later in the same video, Zen likes a bass’s high end and decides to keep it, then checks whether it interferes with the track. The role of the sound determines the decision.

Listen for the conflict before choosing the cut

The first bass sounds good in isolation, but Zen hears fighting when he plays the elements together. He identifies the sounds sharing that space, changes the bass, and returns to the combination. Follow that order: hear the problem, identify the overlap, then decide what the bass can give up.

Make Room for the Kick Where It Actually Hits

Zen checks the kick rather than choosing a familiar bass-cut frequency from memory. In the first project, he identifies the kick around 54 Hz, enters 54.1 Hz on the bass EQ, and makes a small reduction there because the kick and bass play together.

A bell EQ band targets a region around its center frequency. Here, that region is chosen from the kick in the actual song. The transcript does not give an exact cut depth or bandwidth, so there is no fixed decibel or Q setting to copy.

He plays the kick and bass together after the cut. Listen for the two sounds working together rather than one trying to occupy the same space as the other. The useful move is identifying the conflict in your track, not automatically cutting every bass at 54.1 Hz.

Why does he add a boost around 110 Hz afterward?

Zen follows the cut with a small bell boost at 110 Hz. He describes this as moving roughly an octave above the area he reduced, using the spectrum and note reference to find the new location.

In his workflow, the boost restores some weight in a more suitable part of the sound. He credits John Christian for this approach. Keep the demonstrated numbers intact: the cut is 54.1 Hz and the boost is 110 Hz. They are the settings he names, not an exact mathematical doubling.

Zen presents cutting first and adding selectively afterward as his preference. Treat the boost as something to listen for in this example, rather than a requirement to compensate for every cut with another EQ band.

Give Layered Bass Sounds Separate Jobs

In the future-bounce example, Zen divides the bass into low, mid, and top roles. The sub handles the low part, so the other bass layers do not all need to carry that same range.

He first restricts the sub to the portion he wants it to occupy. Then he removes the lows from the other bass sounds. One layer supplies the lower and middle character, while another contributes the higher part that is still needed

The important question is what each layer adds to the combination. Once one bass is covering a region, Zen does not keep the same content in another layer just because it sounds good alone.

How to apply the layer-role approach

1. Listen to the sub and identify the low-frequency role it will handle.

2. Remove unnecessary low content from the other bass layers.

3. Decide which layer supplies the middle and which supplies the top.

4. Listen to the layers together and address any remaining muddiness.

The video demonstrates this division with filters, but the spoken transcript does not supply crossover frequencies. Choose the boundaries by listening to the actual layers instead of inventing a universal split point.

Find the Mud Instead of Boosting Around It

Zen’s opening preference is subtractive EQ: reduce the part that sounds muddy rather than trying to overpower it with extra highs. He describes his usual balance as about 95% reducing and 5% adding. That is how he characterizes his approach, not a quota for your next mix.

In the layered example, he hears a muddy area, uses the EQ’s audition function to isolate what he dislikes, and reduces that region. He then moderates the cut, explaining that it does not need to be excessively harsh.

The final example uses the same idea twice. Zen searches with a raised bell band and audition mode, finds a problematic area, and turns the emphasis into a reduction. He already knows one of the problem areas in that project and openly says so.

What should you listen for after the cut?

Listen to whether the bass fits the other sounds more clearly. Zen explicitly says the bass should sound good with everything else, not only by itself. After each correction, return to the arrangement to hear whether the imbalance has improved.

He also warns against copying his locations. Your unwanted region may be somewhere else. The process of finding it is transferable; the exact curve is not.

Check the Bass Again After Saturation

After shaping the individual layers, Zen EQs the combined bass after saturation. His reason is that saturation can introduce frequency content he no longer wants in the result. The final EQ lets him address that combined signal.

Saturation is a processing stage that adds or changes harmonic content. In this example, the important consequence is that the earlier layer EQs are not the final word on what comes out of the chain.

He enables oversampling on the EQ shown during the demonstration, but does not give a broader explanation or prescribe a setting for every processor. The supported lesson is to listen after the saturation stage and make the cleanup the resulting sound needs. For a wider view of that chain, see how to process a bassline.

Pro Tips and Advanced Techniques

Keep useful highs when the arrangement allows them

In the final example, Zen tests removing some upper content, decides he likes that high end, and leaves it while checking the full track. That is a useful counterpoint to the earlier high cut: the same instructor makes a different decision when the sound and its role change.

Keep the 30 Hz cut attached to the example

Zen removes content below 30 Hz in the last project, explaining that he cannot hear that range in his situation. This is his stated reason for that cut. It should not become a claim that nobody can hear anything below 30 Hz or that every bass needs the same filter.

Compare the correction without a loudness distraction

Pro Tip: Compare the processed and bypassed bass at a similar listening level when assessing the EQ. This helps you judge the change in balance rather than prefer whichever version happens to be louder.

Frequently Asked Questions

Should I cut or boost when a bass sounds muddy?

Zen starts by finding and reducing the frequency region causing the muddiness. He prefers that to adding highs in an attempt to hide the problem, then uses selective boosts where they help the result.

What frequency should I cut from bass to make room for a kick?

Check the kick in your own track. Zen’s first example uses a bass cut at 54.1 Hz after identifying the kick around 54 Hz, but he explicitly warns against copying example frequencies into unrelated songs.

Should every bass layer contain sub frequencies?

Not in Zen’s layered example. A dedicated sub supplies the low role, so he removes unnecessary lows from the other layers and assigns them middle or upper-frequency jobs.

Do I always need to low-pass my bass?

No. Zen reduces upper content when other sounds need that space, but keeps a different bass’s highs when he likes them and they work with the track. The arrangement determines the choice.

Why use an EQ after saturation on a bass group?

Zen uses it to remove unwanted content introduced by the saturation stage. He listens to the bass as a combined sound after the individual layers have been shaped.

Should I always remove everything below 30 Hz?

The video does not establish that as a universal rule. Zen uses that cut in the final example and ties the decision to what he can hear in his situation.

Related Tutorials

Article: How to Process a Bassline: Simple to Advanced TechniquesWhy it’s relevant: Expands corrective EQ into a broader bass-processing chain.Suggested anchor text: how to process a bassline

Article: Suggested future article: How to Assign Frequency Roles to Bass LayersWhy it’s relevant: Develops the sub, mid and top division demonstrated in this lesson.Suggested anchor text: assign frequency roles to bass layers

Article: Suggested future article: Finding Mud With an EQ AuditionWhy it’s relevant: Focuses on identifying an unwanted region before making a cut.Suggested anchor text: find muddy frequencies by ear

Next Step

Open a project where the bass fights the kick or another layer. Identify what each sound needs to contribute, make one targeted reduction, and compare the result with the full arrangement playing. Keep the change only if the combination works better.

If you would rather start from a designed bass sound and focus on fitting it into your track, explore the presets and sample packs in the Evo Sounds store.

Conclusion

Good bass EQ is about the relationship between sounds. Find the conflict, give each layer a useful role, and check the result after processing and in the song. Zen’s examples offer a way to make those decisions, not a curve to paste onto every bass.