
REAPER's Separate process and Dedicated process are different bridge policies. Separate process places participating bridged plug-ins together in one external process; a failure there can interrupt the other bridged effects. Dedicated process gives a plug-in its own bridge, with a documented increase in overall CPU load.
Key Takeaways
- Separate does not mean a separate process for every plug-in.
- Dedicated changes the sharing boundary, not the effect's creative purpose.
- Bridge-window embedding is a different setting from process grouping.
Identify the effects sharing the bridge
For a hypothetical film narration project using an older authorized effect, note which plug-ins are bridged and their current Run as choices. Save the project and its dependency inventory before changing the hosting policy.
The REAPER 7.81 guide, section 16.18, explicitly describes shared and dedicated bridge processes. It also explains automatic bridging of older 32-bit plug-ins in 64-bit REAPER. This is not a promise that any obsolete effect will remain supported.
Compare the documented process choices
| Choice | Documented hosting relationship |
|---|---|
| Separate process | Participating bridged plug-ins share an external process |
| Dedicated process | A bridged plug-in gets its own bridge process |
| Native only | Plug-in runs in the main REAPER process |
Do not select a mode solely because its name sounds more isolated. Record the intended boundary and the actual plug-in affected.
Change the run policy deliberately
The manual documents Run as through the plug-in's FX-browser context menu. Inspect that policy for the intended effect rather than changing every plug-in at once. Dedicated hosting has a resource tradeoff; no numerical improvement is established for your computer.
Embed bridge UI determines where the interface appears. A conveniently embedded window is not evidence that the effect runs natively or has its own process.
Verify ordinary operation without inducing a failure
Reopen a preserved test project, inspect the intended effect's availability and settings, and play a representative passage. Do not deliberately crash a production session to test the explanation.
A 32-bit-float recording describes stored sample precision, a different meaning of bit depth from the plug-in process architecture discussed here. If the symptom is instead a doubled live voice, inspect monitoring routes.
Acceptance is a deliberate hosting policy with acceptable ordinary behavior. No containment experiment, recovered session or universal crash-prevention guarantee is claimed.
Related tasks
- Can a 32-Bit Float Recording Recover Every Distorted Shout?
- Why Do I Hear My Voice Twice in Headphones While Recording Narration?
Sources and scope
- REAPER User Guide 7.81: Section16.18: Separate process shared external bridge, failure affects others; Dedicated each own bridge CPU cost; Native insideREAPER; Embed bridge UI independent window choice. p117 RunAs via FX browser right-click.
Based on the official REAPER 7.81 user guide downloaded on October 23, 2026. Proposed checks have not been executed; no recording, crash-containment 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: William Liu / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.