
Click Analyse to Apply Effect when Kdenlive Normalize (2 Pass) has not yet processed the voiceover. The manual says its first pass analyzes the intended audio and stores results; the second applies those results to reach the chosen loudness over the filter's range. Merely adding the effect does not complete both steps.
Key Takeaways
- Target Program Loudness is a requirement to choose deliberately.
- The analysis pass must cover the intended material.
- Loudness normalization does not restore missing words or clipped detail.
Identify the program being normalized
The Normalize (2 Pass) reference describes analysis of an entire audio file or track and a Target Program Loudness parameter in LUFS.
Decide what the delivery's program actually contains: one narration file, a track or an agreed mixed passage. Record its intended range and target. Do not adopt a number simply because it appears in a default field or another platform's example.
The loudness-versus-peak measurement guide explains why a peak value is not interchangeable with integrated loudness.
Run the documented first pass
- Preserve the working audio and identify the effect's intended range.
- Add or inspect Normalize (2 Pass).
- Set Target Program Loudness from the actual brief.
- Click Analyse to Apply Effect and observe completion.
- Review the processed result and its actual output.
The documentation says the first pass stores its result in the results property. Keep the analysis scope tied to the current material. A result from a different interval should not be assumed to describe a revised voiceover.
For a live stream, the manual points to a different Normalize effect rather than promising this two-pass workflow for live analysis.
Use a narration-review example
Suppose a hypothetical client explanation includes a quiet introduction and a louder product demonstration. Analyzing only an easy phrase does not establish the desired whole-program behavior.
Listen through the actual beginning, louder section and ending after processing. Record intelligibility and level behavior. A suitable loudness target cannot make a clipped consonant undamaged or recreate a word omitted during capture.
If the mix is quiet despite high peaks, the loudness-versus-peak normalization guide helps separate that requirement from simple maximum-level adjustment.
Verify the delivered file
Export a representative approved candidate and assess the required loudness measurement over the stated scope. Listen to the complete voiceover as well as checking the numerical requirement.
Keep the chosen target, analyzed range and output identity with the project. Do not claim compliance based only on the effect's presence. This is a documentation-based procedure and proposed acceptance plan, not a reported normalization measurement.
Related tasks
- FFmpeg ebur128: Which Loudness or Peak Reading Should You Use?
- Why Is My Film Quiet Even Though the Audio Peaks Near the Maximum?
- I requested 10 seconds in 16:9. How do I check the actual AI video file?
Sources and scope
- Kdenlive Manual: Normalize (2 Pass): The effect first needs Analyse to Apply Effect; second pass uses stored results.
Documentation-based guidance. No account access, hands-on test, measured speed gain, search volume or AI citation rate 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.