
An effect parameter can move in REAPER because parameter modulation is active, even when no automation envelope is drawing that movement. Audio control, an LFO or a MIDI/FX-parameter link can supply a separate driver. Inspect modulation for the exact parameter before deleting more automation or replacing the plug-in.
Key Takeaways
- An absent envelope does not prove a parameter has no controller.
- Bypassing modulation is different from bypassing the whole effect.
- If an envelope is enabled for a modulated parameter, that envelope supplies the baseline instead of the modulation window's baseline slider.
Open the moving parameter's modulation controls
In a saved project copy, open the intended track or take effect and touch the control that moves. Choose Param > Parameter modulation/MIDI link. The manual also documents opening its settings through the Mod column in the Envelopes/Automation window.
Confirm the parameter name before changing anything. A chorus wet control and an output gain control can produce different audible changes even when both knobs move during the same sentence.
The REAPER 7.81 modulation chapter describes these drivers for track and take/item effects. This is separate from the ordinary Read-mode fader behavior described in the Premiere guide.
Identify the controller that remains
| Enabled driver | What to inspect |
|---|---|
| Audio control signal | Which track audio channels feed the controller |
| LFO | Whether an oscillator, rather than speech timing, is generating the variation |
| MIDI or FX-parameter link | Which event or other parameter controls this target |
For audio control, channels 1/2 can use the track's own signal; other available channels can support a different routed source. Do not assume that the loudest audible voice is the controller. The Audacity Auto Duck guide illustrates why controller identity matters, although its selection rules are different.
Isolate modulation without removing the effect
Disable the modulation enable checkbox for this parameter and replay the same passage. REAPER documents this as bypassing modulation. Leave the effect itself active so the comparison isolates its controller rather than removing its entire sound treatment.
If the motion stops, decide which driver the scene actually requires. Re-enable only the intended relationship. If it continues, investigate other control ownership instead of claiming modulation explains every moving control.
Check the baseline before restoring automation
With an enabled envelope on the same parameter, REAPER uses that envelope as the modulation baseline. Moving the baseline slider alone will therefore not establish a fixed starting value.
Review a quiet interval and a louder phrase with hands off the controls. Acceptance is a known controller and baseline producing the intended variation. This proposed diagnosis does not report an executed listening test or guarantee a universal modulation preset.
Related tasks
- Why Does My Premiere Audio Fader Snap Back During Playback?
- Why Is Audacity Auto Duck Following the Wrong Voice Track?
Sources and scope
- REAPER User Guide 7.81: Parameter Modulation: Sections19.1–19.10: audio, LFO and MIDI/FX links; selecting last-touched parameter via Param or Mod column; modulation can bypass independently; an enabled envelope determines baseline instead of the PM baseline slider.
Based on official documentation read on October 23, 2026. REAPER references use the verified 7.81 manual. The proposed checks have not been executed; no completed software test or measured result 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: Mak Cézar / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.