Multiband Compression on the Master: When It Helps

What Multiband Compression Does

A multiband compressor splits audio into frequency bands, compresses each, then sums them. Unlike a full-band compressor, a kick-driven gain reduction need not duck the whole vocal range if the low band alone is working.^[1]

On masters and mix buses, that selectivity is both power and danger. You can stabilize low-end notes or calm harshness, or you can reshape the mix into a lifeless, phasey pancake. Treat it as surgical dynamics, not a loudness button.

When to Use It on a Master

• Low-end inconsistency Some notes boom while others vanish—gentle low-band compression can even them.
• Harsh peaks Cymbals or bright synth spikes—control a high band instead of dulling the whole mix.
• Sticky midrange Occasional nasal build-ups—dynamic control beats static deep EQ cuts.
• Not for Fixing broken balances, replacing arrangement decisions, or crushing to “final loud.”

Starting Points and Guardrails

Start with two or three bands, not five. Solo bands only briefly to set thresholds, then decide in full context. Match output loudness when A/Bing—multiband often sounds “better” only because it is louder.

Linear-phase modes can reduce phase rotation at crossovers but add latency and pre-ringing risks; minimum-phase is often fine for gentle mastering GR. Choose consciously.

Chain Position

If you need more than a couple of dB GR on multiple bands, send the mix back. Mastering multiband should polish, not rebuild.

Tools and Free Options

Ozone’s Dynamics module, FabFilter Pro-MB, and various stock multibands can all work. Free dynamic EQs (for example TDR Nova) can solve many “multiband” problems with fewer crossovers. OTT-style presets are aggressive upward/downward designs meant for sound design more than transparent mastering—use with taste on electronic masters only.

Meter with LUFS and true peak after the chain. Streaming platforms still normalize; clean dynamics beat a crushed master that only looks loud pre-normalization.^[2]

Common Mistakes

Copying OTT presets onto acoustic masters, linking all bands so it behaves like a worse full-band compressor, ignoring crossover distortion, and never checking mono after band-limited imaging interactions. Another: multiband as a substitute for automation on a single loud synth—ride the synth instead.

Mini Walkthrough: Boom Without Harshness

Imagine a mix that feels good but the low end surges on a few root notes and the hi-hats spike in choruses. Instead of limiting harder, try a three-band approach: gentle low-band compression to even sub notes, untouched mids if vocals already sit, and a light high-band compressor with faster timing to catch hat peaks. Keep each band near 1 dB of gain reduction on average.

A/B against a full-band compressor at equal loudness. If full-band glue sounds more musical and the problems are mild, prefer simplicity. Multiband earns its complexity only when bands misbehave independently.

After multiband, reassess tonal balance. Compression changes perceived EQ; a small shelf after the multiband is normal. What is not normal is rebuilding the entire midrange with four multiband bands because the vocal was never ridden—go back to automation.

On electronic masters that already use OTT-style group processing, master-bus multiband should be subtler still. Cascading aggressive multibands stacks artifacts. One thoughtful stage beats three trendy presets.

Field Notes

Save mild multiband presets per genre as starting points, not laws. A preset that saved a hyperpop master may ruin a folk ballad. Always reset thresholds to the song’s actual peaks.

If you deliver to a mastering engineer, omit aggressive master multiband. Leave them headroom and dynamic truth; document any bus processing you cannot remove.

Practice Plan and Next Steps

To lock in the ideas in “Multiband Compression on the Master: When It Helps,” schedule three short practice blocks rather than one marathon. In block one, apply only the diagnostic checks from this guide on an old project so you can hear problems without deadline pressure. In block two, rebuild a single section (verse or chorus) using the step-by-step workflow until it translates on at least two playback systems. In block three, document your personal settings and mistakes in a note file you can reopen next month.

Create a before/after playlist. Export the original and the revised bounce at matched loudness, then listen the next day. Fresh ears catch whether you improved clarity or only added processing. If the after version is louder but not clearer, reset and try a smaller change set.

Share one revision with a trusted peer and ask a narrow question: “Is the lead clear on phone speaker?” or “Does the low end survive mono?” Narrow questions produce better feedback than “what do you think?” Incorporate one note, not ten, before shipping.

Finally, connect this skill to the rest of your chain. A fix you learn here should appear in your template: a mono utility, a named bus, a delivery checklist item, or a CRM field. Skills that never enter templates fade; skills that become defaults compound across every release.

Summary

Multiband on the master is a scalpel for uneven bands. Keep GR small, bands few, context checks honest, and loudness-matched. If the whole mix is wrong, fix the mix.