
REAPER automation items can share envelope points while retaining some instance-specific properties. Point edits affect the pool, but Automation Item Properties separates settings applied to All pooled copies and offers a specific Baseline/amplitude sharing option. Inspect it before changing the intensity of only one repeated gesture.
Key Takeaways
- Shared points and instance properties are different parts of an automation item.
- Baseline shifts the reference level; amplitude changes modulation depth.
- Unpool only when independent editing is actually needed.
Decide whether the pattern or its application should differ
For a hypothetical film transition, several filter gestures might use one point pattern while a particular occurrence needs a subtler effect. Changing the pattern and changing its applied depth are different requests.
Identify the items and their actual pool relationship. Similar names or curves alone are insufficient evidence that data is shared. Preserve the project before revising the repeated gesture.
The REAPER 7.81 manual explains these properties on pages 381–383. This differs from an audio fader following an existing envelope; the issue here is which copies receive an edit.
Inspect the Properties sharing controls
Double-click the item's title bar to open Automation Item Properties. The manual describes baseline as raising or lowering the envelope baseline and amplitude as controlling modulation depth.
Inspect the settings grouped under All pooled copies and the option allowing Baseline/amplitude changes to affect pooled copies. Establish the intended sharing state before adjusting either control.
Other changes in this Properties dialog are documented as applying to the individual item. Do not extend that statement to point editing: changing shared point data still changes the pool.
Compare an edited occurrence with a protected copy
On a disposable project, make a small reversible property adjustment. Compare the intended occurrence with another pooled copy that should stay unchanged. Inspect the displayed shapes and the affected effect control during playback.
If every occurrence should receive the new intensity, enable the appropriate shared-property behavior deliberately instead. Identical numeric values are not guaranteed to sound identical on different source material.
Unpool when the point sequence needs independence
The title-bar context command Remove from pool separates the item for independent editing. Use it when a genuinely different sequence is required, then confirm the remaining pool is unaffected.
The shared-source guide describes a related ownership principle, but it does not supply these automation-property controls. No automation experiment has been executed here. Accept the revision only after its intended local or pooled effect is demonstrated.
Related tasks
- Why Does My Premiere Audio Fader Snap Back During Playback?
- Editing One Nested Intro Changes Every Copy: Is the Source Sequence Shared?
Sources and scope
- REAPER User Guide 7.81: Automation items pages381–383: title-bar Properties; baseline raises/lowers envelope baseline and amplitude changes modulation depth; pooled point edits affect pool; All pooled copies properties shared; Baseline/amplitude sharing optional; other Properties edits local; Remove from pool.
Based on the verified official REAPER 7.81 manual read on October 23, 2026. These proposed procedures and fictional sound-design examples have not been executed; no measured result or completed 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: William Liu / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.