
REAPER render postprocessing offers different normalization groupings: each file separately, to the loudest file, or as if files play together. Files intended to be simultaneous soundtrack components should not automatically be treated as independent finished programs. Separate normalization can change the relationships you established in the mix.
Key Takeaways
- Decide whether files are alternatives or simultaneous contributions.
- The normalization grouping is separate from choosing LUFS, RMS or peak measurement.
- Verify the recombined delivery instead of assuming every normalized file retains its original role.
Define the files' relationship
For a hypothetical film handoff, dialogue, music and effects stems may be intended to play together. Three alternate complete mixes are instead intended to play one at a time. Both packages contain multiple audio files, but they pose different normalization questions.
Write that relationship before choosing a common target. The common-start stem guide establishes timing and shared-range requirements. Correct alignment alone does not preserve relative levels after later per-file processing.
Inspect the postprocessing grouping explicitly
In File > Render, open Postprocess and inspect the normalization setting for the actual multi-file output. The REAPER 7.81 render documentation lists the three grouping choices alongside the available measurement targets.
Do not read each-file normalization as merely writing the same setting into each filename. It treats the files separately. Likewise, a label referring to files playing together is relevant only when those files really are intended to be simultaneous components.
Keep the chosen grouping in the delivery record, with the actual metric and target. The loudness-versus-peak explanation addresses that separate measurement choice.
Compare the reconstructed result
Preserve an unmodified stem set and the approved reference mix. In a proposed test, render the candidate package, place every component at the agreed common start and play it at the documented reconstruction gains.
Listen to a narration phrase with music, an effects-only event and a quieter transition. Do not immediately compensate by ear for each file: first identify whether postprocessing changed the relationships the receiving editor expected.
A file can meet its own loudness target while being unsuitable as one component of the intended sum. Conversely, a quiet component is not necessarily defective when it represents deliberately quiet ambience.
Avoid promising an exact master reconstruction
The grouping option does not establish that independently processed stems will exactly reproduce a nonlinear master-bus processor. Retain the agreed routing and the approved complete mix as a reference.
Acceptance requires the intended multi-file relationship, appropriate measured targets and an approved combined result. No render, normalization measurement or reconstruction comparison has been performed here.
Related tasks
- Why Do Delivered Dialogue, Music, and Effects Stems No Longer Line Up?
- Why Is My Film Quiet Even Though the Audio Peaks Near the Maximum?
Sources and scope
- REAPER User Guide 7.81: Render Postprocess options include normalize each file separately, to loudest file, or as if files play together, with metric choices distinct. Does not guarantee separately processed nonlinear stems reconstruct master or prescribe a universal target.
Based on the verified official REAPER 7.81 manual read on October 23, 2026. Proposed rendering comparisons have not been performed; no measured output or software test 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: 85 LENS (Ngô Hoàng Auth) / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.