Renardo's REAPER backend controls instruments via OSC, enabling DAW-quality effects without SuperCollider

The REAPER backend lets Renardo send notes and automation to REAPER DAW via OSC (using reapy or a custom Rust extension called reaside). Instruments are REAPER FX chains — any VST/AU plugin chain becomes a Renardo instrument. Initialization (renardo --configure-reaper) sets up the OSC connection and installs the Renardo extension in REAPER. After setup, r1 >> ReaperInstrument('my_synth.RfxChain', notes=[0,4,7]) plays notes through REAPER plugins. This gives access to the full VST plugin ecosystem — something not possible with the SuperCollider backend alone. REAPER must remain open while Renardo runs; the backend manages the REAPER process lifecycle.

Examples

from renardo.reaper_backend import ReaperBackend
r1 >> ReaperInstrument("bass.RfxChain", notes=[0, 3, 7])

Initialize once: renardo --configure-reaper

Assessment

What is the main advantage of the REAPER backend over the SuperCollider backend for a producer who already has a VST plugin collection? What file format does REAPER use for effect chains?