Compression Signal Flow Explained Simply

Compression Signal Flow Explained Simply

By James Hartley ·

Compression Signal Flow Explained Simply

Compression gets taught as a handful of knobs—threshold, ratio, attack, release—but the real skill is understanding the signal flow: what the compressor “listens to,” what it changes, and what happens before and after gain reduction. Once you can picture the internal path, you’ll set compressors faster, avoid common artifacts (pumping, dull transients, distortion), and make deliberate choices like sidechain filtering, parallel compression, and serial compression.

This tutorial walks you through a practical workflow you can use on vocals, bass, drums, and bus compression. You’ll learn how audio enters the compressor, how the detector makes decisions, how gain reduction is applied, and how to verify that you’re improving the sound rather than just making it louder.

Prerequisites / Setup


Step-by-step: Building Compression Understanding Through Signal Flow

  1. 1) Confirm what’s feeding the compressor (insert position and gain staging)

    Action: Place a compressor as an insert on your chosen track. Put a meter before the compressor and another after it if possible (or use the compressor’s input/output meters).

    Why it matters: Compression behavior is level-dependent. A 6 dB hotter signal can turn gentle control into heavy squashing because the detector sees more level above threshold.

    Specific targets:

    • For digital mixing, aim for typical track peaks around -12 to -6 dBFS before compression. Vocals often peak around -10 dBFS in a well-gained session.
    • Don’t chase a single number—consistency and headroom matter more than “hot” levels.

    Common pitfalls:

    • Clipping before compression: If the track or a plugin before the compressor is clipping, compression won’t fix it; it may make it worse.
    • Pre-FX EQ changes the detector: An EQ before the compressor changes what the detector hears, which can be good or bad depending on intent.

    Troubleshooting: If you can’t get consistent behavior, trim the clip gain or use a gain plugin before the compressor to hit it at a predictable level.

  2. 2) Identify the two paths inside a compressor: audio path vs. detector path

    Action: Open the compressor and locate (if available) sidechain controls, high-pass filter for the detector, and any external key input options.

    Why it matters: A compressor is essentially two systems:

    • Audio path: The actual sound being turned up/down.
    • Detector (sidechain) path: The “measurement” circuit that decides how much gain reduction to apply.

    Many mix problems happen because the detector is reacting to the “wrong” thing—usually too much low end, plosives, kick bleed, or harsh consonants.

    Common pitfalls:

    • Assuming the compressor reacts to what you hear: It reacts to what the detector hears, which may be different if sidechain filtering is engaged or if you’re using an external key.
    • Not noticing RMS vs Peak detection: “Peak” tends to grab transients; “RMS/Avg” tends to level overall loudness. Different compressors label this differently (Peak/Avg, Feed-forward/Feed-back, etc.).
  3. 3) Set a controlled baseline: ratio, attack, release, and knee

    Action: Choose starting settings that make the compressor’s behavior obvious but not extreme.

    Suggested starting points:

    • Vocals: Ratio 3:1, Attack 10–20 ms, Release 80–150 ms, Soft knee if available.
    • Bass: Ratio 4:1, Attack 15–30 ms, Release 100–200 ms.
    • Drum bus: Ratio 2:1, Attack 20–30 ms (let transients through), Release 50–120 ms (tempo-dependent).

    Why these values:

    • Attack decides whether transients pass before compression clamps down. Slower attack preserves punch; faster attack smooths spikes but can dull the sound.
    • Release decides how quickly the compressor lets go. Too fast can cause distortion or “chatter”; too slow can cause the track to sink after loud moments.
    • Knee controls how gradually compression begins around the threshold. Soft knee is more transparent for vocals; hard knee can be punchier.

    Common pitfalls:

    • Attack too fast on drums: You lose impact and wonder why the kit feels small.
    • Release too slow on vocals: Loud phrases push the whole vocal down for too long, making the next words disappear.
  4. 4) Drive the detector on purpose: set threshold to hit a specific GR target

    Action: Lower the threshold until you see consistent gain reduction on loud moments.

    Specific GR targets (practical ranges):

    • Vocals (leveling): Average 3–6 dB GR on peaks; occasional 7–10 dB on shouty lines is okay if it stays natural.
    • Bass (control): 4–8 dB GR on plucks/notes that jump out.
    • Drum bus (glue): 1–3 dB GR most of the time; more if you want an obvious pump.

    Why it matters: The threshold is effectively the “when” of compression. If you don’t aim for a GR range, you’ll either compress so little nothing changes, or compress so much that you start solving one problem by creating three new ones.

    Common pitfalls:

    • Watching meters instead of listening: Use GR as a guide, not a scoreboard.
    • Threshold set by quiet sections: Then loud sections get destroyed. Set threshold while looping a representative loud section.

    Troubleshooting: If compression sounds “grabby” even at modest GR, your attack may be too fast or your detector may be reacting to low-end hits (fix in Step 6).

  5. 5) Match output level (makeup gain) for an honest A/B

    Action: Toggle bypass while adjusting makeup gain so the bypassed and engaged levels match closely.

    How to do it:

    • Use the compressor’s output gain to match integrated loudness (LUFS) if available, or match RMS/average level by meter and ear.
    • As a quick method: if you’re averaging 5 dB GR, start by adding about +3 to +5 dB makeup gain, then fine-tune.

    Why it matters: Louder almost always sounds “better” on first impression. Level matching is how you decide if you improved tone, consistency, and clarity—not just volume.

    Common pitfalls:

    • Auto makeup gain surprises: Some compressors add gain aggressively. If you hear a big level jump, disable auto makeup and set it manually.
    • Comparing different peaks: Compression may reduce peaks; don’t only match peak level. Match perceived loudness.

    Troubleshooting: If the compressed version feels smaller even when loudness-matched, your attack may be too fast, or you’re compressing the life out of transients.

  6. 6) Control what the compressor “hears” using sidechain filtering (HPF)

    Action: Engage a sidechain high-pass filter (detector HPF) if the compressor offers it. If it doesn’t, you can simulate it by duplicating the track: send to a sidechain input with an EQ inserted, or use a compressor that supports SC EQ.

    Recommended detector HPF settings:

    • Vocals: HPF at 80–120 Hz to reduce plosive-triggered compression.
    • Mix bus: HPF at 60–90 Hz to prevent kick and sub from dragging the whole mix down.
    • Bass: Use cautiously; HPF at 40–60 Hz if low-end rumble causes over-compression, but don’t remove the fundamental from the detector if you want consistent bass level.

    Why it matters: Low frequencies carry lots of energy and can dominate the detector. The result is “pumping” or dullness—especially when kick, plosives, or proximity effect hits.

    Common pitfalls:

    • Over-filtering the detector: If you HPF too high (e.g., 200 Hz on vocals), the compressor may ignore the body of the sound and respond weirdly to midrange, making the vocal edgy.
    • Confusing audio EQ with sidechain EQ: Sidechain filtering changes the compressor’s behavior; it does not change the tonal balance directly.

    Troubleshooting: If the track still pumps, lengthen release slightly (e.g., from 80 ms to 140 ms) or reduce ratio (e.g., 4:1 to 2.5:1). If it gets dull, slow the attack (e.g., 5 ms to 15 ms).

  7. 7) Choose serial vs. parallel compression based on the signal flow goal

    Action (Serial): Use two gentle compressors in a row instead of one doing everything. Example for vocals:

    • Compressor 1 (fast peak control): Ratio 2:1, Attack 1–5 ms, Release 30–60 ms, aim for 1–3 dB GR on peaks.
    • Compressor 2 (leveling): Ratio 3:1, Attack 10–20 ms, Release 80–150 ms, aim for 2–5 dB GR.

    Action (Parallel): Create an aux track with a compressor set aggressively, then blend it under the dry signal.

    • Parallel drum crush starting point: Ratio 8:1, Attack 10–30 ms, Release 50–120 ms, aim for 10–20 dB GR, then blend the return at -20 to -10 dB below the dry bus.

    Why it matters: Serial compression splits the job across stages (cleaner, more controllable). Parallel compression keeps transients from the dry path while adding density from the compressed path.

    Common pitfalls:

    • Parallel phase/latency issues: Some plugin chains introduce delay. Use DAW delay compensation and avoid zero-latency mismatches. If it sounds hollow, check latency and polarity.
    • Overdoing parallel returns: Too much crush brings up cymbal hash, room tone, mouth noise, and bleed.

    Troubleshooting: If parallel sounds bright and splashy, add an EQ after the parallel compressor: low-pass around 8–12 kHz and/or dip 3–6 kHz by 2–4 dB.

  8. 8) Verify the result using real listening tests, not just meters

    Action: Do three checks:

    • Consistency check: Can you hear every word/ghost note without riding faders?
    • Transient check: Did the punch stay (kick/snare consonants/plucks), or did it flatten?
    • Noise/room check: Did compression bring up headphone bleed, breaths, or hum between phrases?

    Why it matters: Compression is a trade: you exchange dynamic range for stability and tone. The win is clarity and control; the cost can be artifacts and raised noise floor.

    Common pitfalls:

    • “Set and forget” compression: A setting that works in a chorus may not work in a verse. Consider automation or multiple stages.
    • Ignoring context: A vocal that sounds slightly over-compressed solo might sit perfectly in a dense mix, and vice versa.

Before and After: What You Should Expect

Before: Peaks jump out (a loud word, bass pluck, snare hit), quieter details get lost, and you keep reaching for the fader. On buses, the mix may feel spiky—loud hits feel too loud, then the rest feels too quiet.

After (with level-matched A/B):


Pro Tips to Take It Further


Wrap-up

If you can describe compression as “audio path plus detector path,” you’re already ahead. Set a baseline, aim for a GR target, match levels for honest comparisons, then shape what the detector hears with sidechain filtering. Practice on three sources—vocal, bass, drum bus—and keep notes on what attack/release ranges consistently work for you. The speed comes from repetition, and the confidence comes from knowing exactly where in the signal flow the change is happening.