se7en beatlab

Levels & dynamics

Normalization is not compression; leveling is not normalization

Normalization changes gain toward a target; leveling changes level relationships over time; compression shapes dynamics through a detector and curve.

Go to the exercise ↓

The starting point

Normalization applies gain to a programme; leveling changes relationships over time. If one phrase disappears while another is correct, raising the entire file preserves that difference.

A practice case

The interview has one quiet phrase, not one quiet file

Practice case: a speaker moves away from the microphone for a sentence. Normalizing raises that sentence and everything else. If the gap between sections was the problem, it remains.

Try clip gain or automation on the quiet sentence before compressing the entire voice. Once relationships are stable, decide the overall level. In music a softer verse may be intentional: leveling should not erase expressive differences.

Try the calculation

Before you add gain, check the peak

Uniform-gain estimate only. Gain = target − current loudness; predicted peak = current peak + gain. Compression, gating changes and encoding require a new measurement.

Example: +4.0 dB gain → +2.0 dBTP predicted peak. This exceeds 0 dBTP.

Choose a test from what you hear

Observation and next test
You noticeTry this
Everything needs the same changeUniform gain or normalization.
Only some phrases differClip gain, automation or leveling.
Attacks or sustain need shapingCompression with a defined purpose.

Bring it into your session

One pass, with a clear objective

0 / 4

Checks stay on this page and are not sent anywhere.

When to stop

Phrases have a useful relationship without losing intended expressive differences.

Quick diagnosis and decision protocol

Check first

  1. Ask whether the problem is absolute level, moment-to-moment level or dynamic shape.
  2. Level-match before judging processors.
  3. Inspect what changes when bypassing.

Then decide

  1. Use gain for absolute offsets.
  2. Use automation or leveling for phrase balance.
  3. Use compression when the dynamic behavior itself needs shaping.

Measurement boundary

Correct terminology makes troubleshooting faster because each control solves a different class of problem.

Watch out for this: A louder processed signal can win an A/B even when the processing is worse.

Technical references

Documentation for the methods and product behaviour discussed. Practice cases are illustrative examples, not client case studies.

References reviewed:

Try it with your own audio

Choose the free tool that fits your task. You do not need to buy a plugin to use the guide.

Open the free tools →