Skip to content

Signs of over-compression and how to fix them

Send feedback

Last updated 6 min readTags:MixingCompressionDynamics

Hear the signs of over-compression, find the compressor or limiter responsible, and restore punch and movement with a level-matched comparison.

Over-compression happens when compression or limiting removes more of a sound's dynamics than you want. Drums may lose their attack, the mix may dip after each kick, or a vocal may lose its emphasis. It can affect one instrument, a group of tracks or the whole mix.

These symptoms are reasons to check the processing. The useful test is whether a change improves the sound when you compare both versions at the same loudness.

Five signs of over-compression

1. The mix dips and swells after each kick

Listen to the cymbals, pads or reverb while the kick plays. If they dip with each hit and rise afterwards, a bus compressor or limiter may be turning down the whole mix in response to the kick.

This is called pumping. It can be deliberate, especially in dance music. It becomes a problem when the level changes distract from the rhythm or make sustained sounds unsteady.

Reduce the gain reduction first. Then adjust release while listening to the rhythm: a short release can make the recovery abrupt; a long release can keep the mix turned down into the next hit. There is no release setting that suits every track or processor.[1][2]

If low frequencies dominate a bus compressor's response, try its sidechain high-pass filter. This reduces bass in the detector signal, so the kick has less influence over gain reduction. It does not remove bass from the audio itself.[3]

2. Drums have lost their attack

A kick still has bass and a snare still has body, but the start of each hit sounds weaker. The drums may seem farther back even though their average level has increased.

A fast attack can reduce the brief initial peak, or transient, that gives the hit its definition.[1] Compare the drum compressor, drum bus and master processing separately to find where the attack disappears.

At the responsible compressor, try a slower attack or less gain reduction. For a conventional drum compressor, 10–30 ms is a reasonable range to audition, rather than a target. Keep the setting that restores definition without making the peaks excessive. Limiters use different timing designs, so their controls need a separate check.[2]

3. The chorus has lost its lift

If the chorus becomes less distinct from the verse after processing, a bus compressor or limiter may be reducing the louder section much more heavily. Compare the transition with and without that processing.

Reduce compression or the level driven into the limiter, then listen across the transition again. If the chorus still lacks impact with the processing bypassed, check the arrangement, instrument balance and automation. A chorus can gain impact through rhythm, texture or width as well as a rise in level.

4. Bass notes or loud hits sound rough

Listen for a buzz on bass notes, crackle on kicks or crunch on loud snare hits that appears only after processing.

Compression can distort without clipping: very fast gain changes can alter the waveform, particularly at low frequencies.[3] Heavy limiting, a clipper or an overloaded later stage can also introduce roughness. The sound alone does not identify which one is responsible.

Reduce the drive into the suspect processor and compare again. On a compressor, try a longer release if very short timings cause the roughness. On a limiter, audition its cleaner modes and timing options. More lookahead may reduce distortion in some designs, but can also soften transients.[2] Check downstream levels too; lowering the final output cannot undo distortion introduced earlier.

5. Breaths and room noise compete with the vocal

After compression and make-up gain, breaths, mouth noises and room sound may seem much louder relative to the words. Heavy compression can also reduce the contrast between an intimate line and an emphatic one.

Try less gain reduction and compare the whole phrase. If only a few words are much too loud, use clip gain or volume automation to lower those words before compression. You can then use the compressor for smaller level changes.[4]

A prominent breath may suit the performance. Change it when it distracts from the words or produces an unintended shift in level.

How to find the processor responsible

Save a version of the session before making changes. Choose a passage where the problem is obvious; include a verse-to-chorus transition if section contrast is the concern.

  1. Start at the output. Compare with and without the master limiter or clipper. Then check the mix bus compressor, group buses and individual tracks as needed.
  2. Match the listening level. Turn down the louder version with output compensation or a gain control. Similar peak readings do not mean similar loudness. Use your ears, with a loudness meter as a guide.
  3. Change one processor at a time. If bypass restores the missing attack or stops the level swings, reduce that processor's gain reduction and compare again.
  4. Recheck the full chain. A change upstream can alter how hard later compressors and limiters work. Listen with the complete chain active before deciding the fix is finished.

Several stages can contribute to the problem, but one badly set compressor can also be enough.[4] Keep the compression that serves a clear purpose. There is no need to reduce every stage by the same amount.

For a limiter, reduce input gain or drive to ease the limiting. On designs where threshold controls the amount, raise the threshold. Simply lowering a post-limiting output control makes the result quieter without restoring the lost dynamics.

What the meters can tell you

A gain-reduction meter shows when a processor turns the signal down and by how much. Watch it during the troublesome passage. Does each kick trigger a large reduction? Does the chorus cause much more reduction than the verse? Use those observations to choose what to compare by ear.

There is no universal safe amount of gain reduction. A sustained reduction that suits a vocal may be excessive on a mix bus; even a small reduction can change a drum's attack.

Whole-file measurements describe different aspects of the result:

Measurement What it tells you What it cannot establish by itself
Integrated LUFS Average perceived loudness across the measured programme Whether compression improved the mix
Crest factor The difference between peak and RMS level Which processor changed the transients
Loudness range Variation in loudness over time Whether individual drum hits retain their attack
True peak An estimate of the reconstructed signal's highest peak Whether distortion is already present in the recording

A loud, dense mix can suit the music. Equally, a quieter file may contain heavily compressed recordings. Use the measurements in your Sonalix report to guide checks in the session; compare the sound before and after processing to judge the result.

Listening fatigue is also an unreliable diagnosis on its own. If a mix becomes tiring, take a break and return at a comfortable level. Check brightness, distortion and balance as well as compression.

Can you fix an over-compressed audio file?

The best fix is in the session, before the processing is committed to an export. Reduce or remove the responsible stage and export again.

If you have only the processed file, expansion or transient shaping may change its apparent punch, but cannot reliably reconstruct the original dynamics or remove baked-in distortion. Ask for an earlier mix or the unprocessed tracks where possible.

Sources

  1. FabFilter: Basic compressor controls
  2. FabFilter Pro-L 2 manual: Advanced settings
  3. FabFilter: Side chain compression
  4. iZotope: 5 signs of over-processing in a mix

Was this page helpful?

    Type to search titles, headings and summaries.