Sectional Loudness Budgeting: My 2026 Mix Prep to Hit -9 LUFS Without Crushing Dynamics

Horia Stan is a music producer and sound engineer at The One Records, Bucharest.

Why sectional loudness budgeting matters in 2026

I stop treating loudness as a single final number. Loudness is a resource you distribute across a song. Mixes that sound thin or crushed after mastering often handed the mastering engineer a single, inconsistent target: too loud in the verse, too soft in the chorus, no headroom left for glue. I set exact loudness and transient budgets per section. That forces arrangement, sound selection, and mix moves that survive mastering and modern streaming normalization.

I work in Logic Pro. I measure with Youlean Loudness Meter 2 and Logic's built-in loudness meter. I use FabFilter Pro-Q3 for surgical EQ, FabFilter Pro-MB for multiband sidechaining, and FabFilter Pro-L2 when I need a limiter for test renders. My interface is an Audient iD14 MkII. These are the tools I use while I follow a strict numerical plan.

The simple rules I follow

1. Leave -6 dBFS peak headroom on the stereo mix bus. I print with that ceiling. Do not chase peak-to-loudness by clipping.
2. Aim integrated mix loudness around -13 LUFS for the full mix print. This is not the master. It gives mastering 3-4 dB of loudness gain without needing to compress heavily.
3. Use sectional short-term LUFS targets: verse -17 to -16 ST, pre-chorus -15 ST, chorus -11 to -9 ST. I check these with Youlean or Logic's short-term display.
4. Keep true peaks under -1 dBTP on test renders. Mastering can add inter-sample peaks. I use FabFilter Pro-L2 to check true peak safety.

These numbers let me hit a commercial master loudness near -9 LUFS if required by the client, while still preserving my transient fingerprint. I choose -13 LUFS for the mix because platform normalization centers around -14 LUFS. If I hand over a mix at -13 LUFS, the mastering engineer can push to -9 for editorial use or keep it at -14 for streaming without damaging dynamics.

How I set the sectional budgets - step by step

I rarely reach target numbers by pushing one knob. I move elements around. I cut competing frequencies, reduce stereo width on mid-crowding elements, and add hits or plate tails to change perceived loudness without squashing dynamics.

Concrete plugin chains and exact settings I use

Chorus bus - presence and controlled loudness

• FabFilter Pro-Q3: surgical bell at 3.5 kHz -3 dB Q 2.0 if harshness exists. Use dynamic mode for vocal-led mixes.
• FabFilter Pro-MB: 2-band split. Band 1 20-250 Hz with -1.5 dB gain reduction using -6 dB threshold, attack 5 ms, release 80 ms to tame low energy that inflates perceived loudness. Band 2 2.5-6 kHz as a soft subtractor keyed to the lead - ratio 1.5:1.
• Optional Waves SSL G-Master Bus Compressor on mix bus for glued reference - aim for 0.5 to 1 dB gain reduction on choruses when printing a glued reference for the mastering engineer.

Those settings are starting points. The goal is to get chorus ST LUFS to -11 to -9 without a limiter shaving transients.

Verse bus - clarity without competing loudness

• FabFilter Pro-Q3: broad cut 200-400 Hz -1.5 dB to reduce mud. High shelf +1 dB at 8 kHz for air if needed.
• Transient control: Waves Trans-X or Logic's Enveloper. Reduce sustain by 1-2 dB to avoid verse energy masking the vocal.

Verse ST LUFS target is -17 to -16. If it sits louder, pull level, narrow stereo image, or shorten sustain on offending elements.

How I use multiband sidechain to keep sections clean

I key FabFilter Pro-MB or Pro-C2 on a bus to the lead vocal. That means low-mid content ducks under the vocal only when the vocal is present. It is surgical. It does not flatten the mix. I use a low ratio - 1.3:1 to 1.6:1 and set attack 4-6 ms, release 80-120 ms. Use look-ahead sparingly.

This move lets me raise chorus short-term LUFS without burying the vocal or resorting to heavy limiting. Keyed multiband subtraction changes perceived loudness far more efficiently than overall gain moves.

Stems, renders, and what I send to mastering

I export these files:

• Stereo mix print 24-bit 48 kHz, no final brickwall limiter, peak ceiling -6 dBFS, integrated LUFS -13 target.
• Sectional stems folder: drums, bass, guitars/keys, vocals, effects. Annotated names with section comments if a section deviates from the mix print targets.
• A one-page 'loudness map' with short-term LUFS per section and true-peak reading. I include the chorus ST LUFS and verse ST LUFS numbers.

I do not send a single over-limited file expecting mastering to reverse it. If a client wants a loud master for editorial plays, I discuss a second, mastering-directed route where I print a 'louder reference' limited only for rough reference.

Common failure modes and how I avoid them

• Failure mode: I push my mix bus limiter to reach chorus LUFS. Result: pumped transients and brittle highs after mastering. Fix: revert limiter, use sectional additions or keyed multiband moving energy without squashing.
• Failure mode: I hand an inconsistent mix with verse near -12 ST. Result: mastering flattens dynamics. Fix: enforce verse target -17 ST and use transient shaping.

Quick checklist before export

• Stereo mix peaks at or below -6 dBFS
• Integrated mix ~ -13 LUFS
• Chorus short-term -11 to -9 LUFS
• Verse short-term -17 to -16 LUFS
• True peak below -1 dBTP
• Stems labelled and section-annotated

Last words

This is not a trick or a plugin cheat. It is a planning discipline. Treat loudness as a budget to allocate per section. If you deliver a mix with the chorus sitting at -11 ST and the verse at -17 ST, mastering can add glue and reach aggressive loudness targets without crushing your transient fingerprint.

Takeaway: Render the mix with -6 dBFS peak headroom, integrated ~ -13 LUFS, and sectional short-term targets - verse -17 to -16, chorus -11 to -9. Include a loudness map with your stems. That single page saves revisions and preserves dynamics.