
FFmpeg loudnorm can upsample audio to 192 kHz in dynamic mode for true-peak detection. If the deliverable requires another sample rate, set the output sample rate explicitly with -ar or aresample and probe the completed file. Do not assume the source rate automatically defines the normalized output.
Key Takeaways
- Dynamic loudnorm processing can change sample-rate behavior.
- The required output rate belongs in the delivery specification.
- Loudness, true peak and sample rate require separate final checks.
Identify which rate changed
Record the source audio rate, the filter chain and the completed output's rate. A changed rate after normalization is different from incorrect playback caused by interpreting samples at the wrong rate. Establish what the file actually contains before changing the voice's speed or pitch.
The official loudnorm documentation explains the dynamic-mode upsampling and explicitly recommends -ar or aresample to set the output rate. Its loudness and peak targets describe separate quantities.
- Read the receiver's required sample rate and loudness measurements.
- Inspect the source rate and normalization configuration.
- Specify the required output rate using the documented output option or resampling filter.
- Encode a separately named candidate with the intended stream mapping.
- Probe the completed audio stream and measure the required loudness and true peak.
For an illustrative 48 kHz delivery requirement, -ar 48000 states that rate in an output configuration. It is not a complete command or a universal recommended delivery rate.
Do not infer the normalization mode from one flag
The documentation says linear normalization requires measured values and additional conditions; if those conditions are not met, it reverts to dynamic mode. Therefore, merely requesting linear behavior is insufficient evidence that dynamic processing was avoided.
A hypothetical producer might plan a linear normalization pass but omit required measured fields. The next investigation should inspect the actual normalization setup and final stream rather than asserting that the sample-rate change is impossible.
Keep measurement labels precise
Use the loudness measurement guide when interpreting integrated loudness, range or peak values. Passing a peak check does not establish the correct sample rate, and selecting a sample rate does not establish compliant loudness.
Accept only when the final stream has the specified rate, expected channels and complete duration, and its measured soundtrack meets the actual brief. Listen for unintended artifacts and synchronization changes as well.
If the file still has the wrong rate, inspect the output to which the option applies and any later resampling or re-encoding stage. Keep the original audio and record the full processing chain. This explanation is documentation-based and does not claim a performed normalization test.
Related tasks
- FFmpeg ebur128: Which Loudness or Peak Reading Should You Use?
- Why Did My Narration Become Faster and Higher-Pitched After Import?
- Why Can an AAC Export Distort When the Sample Peak Meter Stays Below Full Scale?
Sources and scope
- FFmpeg loudnorm: Dynamic-mode upsampling to 192 kHz for true-peak detection; -ar or aresample for explicit output rate; conditions for linear-mode fallback.
Documentation-based guidance. Scenarios and acceptance checks are proposed or hypothetical; no hands-on test, search-volume measurement or AI-citation ranking is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.