
An open REAPER plug-in window does not necessarily receive every keyboard command. A floated FX window has Send all keyboard input to plug-in, while the FX chain has a separate shortcut policy that can pass commands to the main window. Inspect input routing before diagnosing an unexpected timeline movement as damaged media.
Key Takeaways
- Identify which interface should receive the key.
- The floated-window control and chain shortcut policy have different scope.
- Test a harmless input before using a command that could alter the arrangement.
Describe the intended recipient
Suppose a narration editor wants arrow keys to change a plug-in control while the film arrangement stays still. That is a different requirement from using the keyboard to navigate the arrangement while an FX window remains visible.
Record the plug-in instance and whether its interface is floated. Save the working project before investigating shortcuts that could move or modify timeline content. This is a proposed diagnostic, not an observed keyboard failure.
Inspect the floated-window control
The REAPER 7.81 manual, section 6.11, places Send all keyboard input to plug-in in the floated FX window's title-bar context menu. It specifically uses arrow keys as an example of input intended for the FX instead of arrange view.
Enable it when that is the desired policy. Do not treat the mere presence of a visible plug-in as evidence that the policy is already active.
Check the chain's separate shortcut choice
The same guide's FX-chain options, on page 338, document Ignore FX keyboard shortcuts, which passes shortcuts through to the main window; its example is Space starting or stopping playback. Inspect that choice when the observed recipient conflicts with the intended job.
This is not an automation-mode issue. A fader following a stored envelope can move for a different reason even when keyboard routing is correct.
Verify the receiving interface deliberately
Use one harmless key or navigation action whose expected effect is identifiable. Observe both the plug-in and arrange view, then confirm that no timeline edit occurred unexpectedly. Restore the intended routing after the diagnostic.
If the control you need is absent, first identify the actual window and instance. The selected-property guide discusses the broader importance of identifying the control target; its video controls are not REAPER commands.
Acceptance is an intentional input recipient, not a promise that every third-party plug-in implements every key identically. No keyboard test or successful correction is reported here.
Related tasks
- Why Does My Premiere Audio Fader Snap Back During Playback?
- Why Can’t I Find Keyframe Controls for the Clip I Selected?
Sources and scope
- REAPER User Guide 7.81: Section 6.11: floated FX title-bar context Send all keyboard input to plug-in. Page338 FX chain Ignore FX keyboard shortcuts passes shortcuts to main window.
Based on the official REAPER 7.81 user guide downloaded on October 23, 2026. Examples are proposed checks, not executed application tests or measured production results.
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.