Loudness, Dynamics, and Translation in Mastering

Loudness is a tool. Dynamics are the material you are working with. Translation is how you know whether the decisions you made actually worked. Here is how all three fit together in mastering.

Loudness

When most people talk about loudness in mastering, they mean how loud a track feels relative to other music. That is a perceptual question, not a technical one, and it is worth treating it that way.

Modern mastering uses LUFS (Loudness Units relative to Full Scale) as the primary loudness measurement because it correlates more closely with how the ear actually integrates sound over time. RMS measures average signal energy. LUFS accounts for frequency weighting and time integration in a way that better predicts how loud something feels to a listener. Two tracks can share the same RMS and feel very different. LUFS is usually the more reliable predictor.

Streaming platforms normalize loudness to a target. What this means in practice is that pushing a master louder than a platform's target does not make it play louder. It gets turned down to match. What gets lost in that process is dynamic nuance, the quiet details, the space between elements, the expressive contrast that makes a record feel alive. Loudness decisions made without accounting for normalization can quietly undo a lot of careful work.

The level should feel right for the music and hold up through encoding without losing what matters. That's the whole brief.

Dynamic Limited -14.0 LUFS
Streaming platforms normalize to approximately -14 LUFS at playback
Integrated loudness
-14.0 LUFS
Dynamic range
10 LU
True peak
-1.0 dBTP

Dynamics

Dynamics are the distance between the softest and loudest moments in a recording. That distance is where expression lives. Managing it in mastering is not about eliminating it. It is about preserving musical intent while ensuring the record holds together.

Compression and limiting can increase perceived loudness and control peaks without flattening the record. Used too heavily, they compress the expressive arc of the music into something uniform and fatiguing. I hear this constantly on mixes that come in hot off a streaming reference. When everything is loud all the time, nothing actually feels loud. The chorus stops feeling like a chorus. The drop stops feeling like a drop. The record just… sits there.

At the same time, a record with no dynamic control can feel disconnected or lose forward momentum in ways that work against it on real playback systems. Some mixes benefit from a degree of cohesion that careful compression provides. Some do not. The question is always what the music needs, not what the meter is reading.

Some records are built to be loud. Density, energy, and intensity are part of the intention. Mastering should support that when it is genuinely what the music calls for. The point is to arrive at loudness honestly, not to treat it as a universal destination.

Translation

Translation is the test. A master that translates well sounds coherent and intentional whether it is heard on headphones, a car stereo, a laptop, a club system, or a phone speaker in a noisy room. The emotional content survives the trip.

Getting there requires understanding how audio behaves across different playback systems, codecs, and listening environments. A decision that sounds right in the mastering room may reveal a problem on a consumer earbuds. A low end that feels controlled on a calibrated monitor may accumulate on a system with a bass boost. Translation is why mastering engineers listen in multiple contexts and check their work on more than one system before delivery.

When loudness and dynamics are handled correctly, the listener does not think about either of them. The music just feels right wherever it lands. That is the only measure that matters to me. Not the meter. Not the number. Whether it holds up in the car on the way home.

When Translation Isn't the Goal

Translation is the right test almost everywhere, but there's an exception worth naming directly.

Sometimes a mix comes in already slammed. Already clipped. Distorted past where I'd normally step in. Sometimes that's an error nobody caught. Sometimes it's exactly what the artist wants, hip-hop, industrial, EDM, noise, anything built on distortion as texture rather than accident. The first job is finding out which one I'm looking at, so I ask before I touch anything.

Once I know it's intentional, the job changes. I'm not mastering toward translation anymore. I'm mastering to protect a decision that's already been made. The loudness was decided in the mix, not on my end, and a track can sit at a LUFS value most mastering advice would call too hot and still be doing exactly what it's supposed to do. My limiter isn't pushing for more in that case. It's doing safety work on the way out the door.

The true peak ceiling still depends on how the mix behaves, and the direction can surprise you. A dense, evenly clipped file is exactly the material where lossy encoding pushes reconstructed peaks the highest, so hot-and-even earns the more conservative ceiling, not the looser one. A pokey file, with sharp transient spikes sitting above the general density, needs that same ceiling doing real catching work on those specific peaks. Same source, different behavior, depending on what the peaks are actually doing.

None of that means nothing is happening. QC still runs. Anything actually broken, rather than intentionally aggressive, still gets caught. Deliverables still get assembled correctly. A record built to survive a phone speaker and a record built to sound destroyed aren't failing the same test. They're not even taking the same one.

Previous
Previous

From Single to Album: What to Expect at Mastering

Next
Next

Mastering Loudness Targets for Streaming: Spotify, Tidal, Apple Music, and Bandcamp