
REAPER's take-propagation command does not copy envelope points, even when it copies an envelope as part of the take's properties. Use propagation for the documented property transfer, then verify automation separately. Matching take names determine the command's target scope, so audit those names before applying it across a track or project.
Key Takeaways
- Propagating a take is not the same as duplicating its complete automation curve.
- The command targets similarly named active takes.
- Check copied processing, fades and envelope points as separate outcomes.
Define what needs to be copied
List the properties that should carry to other pieces of the recording. A tone correction may belong everywhere, while a local level dip or word-specific effect may belong only at one point.
For a fictional narration session, a long recording might have been split into several items. Applying a shared correction to those pieces is different from copying a timed reduction that protects one loud word.
Do not use the mere presence of an envelope lane as evidence that its detailed points were copied.
Inspect active take names and scope
The REAPER 7.81 manual, section 8.8, describes propagating to similarly named active takes on the current track or across tracks.
Check the actual take names and active alternatives before choosing the command. Names can identify more destinations than intended, especially when several recordings retain a default filename.
Use the narrower track scope when that matches the task. Avoid an all-tracks operation simply because it saves clicks; the destination set should follow the intended processing ownership.
Verify properties separately from automation
Apply the chosen propagation operation on a saved project copy. Inspect a target item's processing and fades, then inspect the envelope and its points.
The manual explicitly distinguishes copying the envelope from copying its points. If a timed curve is required, choose a separate supported envelope-editing operation and validate its temporal position. Do not invent a universal “copy everything” behavior for take propagation.
Check one intended target and one item that should remain unchanged. Matching names are operational identifiers here; a descriptive name is useful only when you have confirmed which recordings actually share it.
Listen through the target passages
Compare the source and target at similar listening levels. Check that the shared correction is present without duplicating a local movement that belongs to another sentence.
If a point-based adjustment is missing, treat that as a separate task rather than repeatedly running propagation. If an unexpected passage changed, inspect the matching names and command scope before making further global edits.
After completing the intended automation, check the combined voice and music for mix headroom. Accept the operation only when the intended target properties and the independent automation decisions both match the film brief.
Related tasks
- How to Check Headroom When Narration and Music Clip Together
- Where Did My Audacity Volume Envelope Points Go After Mix and Render?
Sources and scope
- REAPER User Guide 7.81 — page 165: propagate similarly named take envelope points
Based on the official REAPER 7.81 User Guide, retrieved October 23, 2026, with the relevant sections checked against the complete manual. The workflow and hypothetical review situations are documentation-based; no REAPER processing test 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: Pignatta / Pixabay, Pixabay Content License. This is an illustrative source photograph, not an application screenshot or a generated test result.