
Use REAPER's Save all stats option to retain render statistics individually when a film-audio job produces several outputs. In the render analysis window, select the particular track, item, region or razor area whose result you are inspecting. A graph left on screen is not automatically the quality record for every file in the batch.
Key Takeaways
- REAPER can save statistics combined or individually.
- Multiple-output dry runs produce separate analyses that you select from a list.
- A dry run produces analysis without delivering the requested audio files.
Decide which result needs its own record
For a hypothetical film, narration, music and an approved full mix may be separate deliverables. Associate each report with the exact output role and revision. This association is a proposed editorial record, not a claim about REAPER's automatic report filenames.
The REAPER 7.81 rendering guide documents Save all stats with combined and individual choices. Select the individual approach when the receiving editor needs to inspect one output's measurements without confusing them with a batch summary.
Configure the analysis before relying on its values
Open File > Render and verify the source, bounds and intended outputs. In the render statistics controls, choose the measurements you require. Section 21.4 describes peak or true peak and RMS or LUFS statistics, as well as waveform displays and clipping indications.
Do not compare a value with a requirement for a different measurement. The loudness-versus-peak guide explains that distinction independently; its FFmpeg controls are not REAPER menu instructions. No universal loudness target is supplied here.
Select the output whose graph you mean to review
For multiple outputs, the manual describes a separate dry render for each selected unit. Use the list beneath the graph to select a track, media item, region or razor edit area. Check its identity before noting a peak or inspecting a suspect passage.
The Stats/Charts menu can open render statistic charts in a browser, where they can be saved or printed. Keep those saved charts with the relevant job record rather than assuming the closed render window is a durable archive.
Keep analysis and delivery separate
A Dry Run (no output) does not generate the deliverable audio files. Once the rendering configuration is approved, render the actual outputs and reconcile their identities with the retained records. Listen to the delivered beginning, ending and any flagged passage; a favorable statistic does not prove the correct language, edit or content.
If one output has an unexpected result, select that output's analysis and confirm its source and range before adjusting every track. A new render following a mix change needs a corresponding current record. This procedure proposes traceable review; it reports no completed render or listening test.
Related tasks
- FFmpeg ebur128: Which Loudness or Peak Reading Should You Use?
- Why Do Delivered Dialogue, Music, and Effects Stems No Longer Line Up?
Sources and scope
- REAPER User Guide 7.81, sections 21.3-21.5: Save all stats combined or individually; dry run has no output; analysis chart can be opened/saved; multiple-output dry runs have per-unit selection. Verified local text lines 22409-22528.
Based on REAPER User Guide 7.81, sections 21.3-21.5, read on October 23, 2026. Report association and listening checks are proposed editorial procedures; no render or measurement was performed.
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: William Liu / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.