AUDIO
Source snapshot · 12 October 2026

REAPER host validation

Prepare a disposable session

Build the bundle with python3 scripts/bundle-clap.py. Use an official REAPER installation or evaluation build. Give the test copy its own resource directory via REAPER's -cfgfile /absolute/path/reaper.ini option. Configure its CLAP path to the absolute target/clap/release directory. Keep test settings and files in target/reaper-validation; do not use an existing production project or licence fixtures. REAPER may automatically append system VST3 paths and perform a startup scan even when explicit test paths are provided.

Generate the synthetic four-second stereo PCM source:

python3 tools/reaper-validation/prepare.py target/reaper-validation/config

In an empty disposable REAPER project, use Actions → Show action list → ReaScript Load to select tools/reaper-validation/validate.lua, then run it. The script asserts the project has no tracks before mutation. It mutes master volume for hardware output, instantiates RAVET Gain, checks parameters and window creation, plays automation, saves wet/dry/automation projects and reopens saved sessions. The generated files and host-validation.log go into <REAPER resource directory>/ravet-validation. The script uses REAPER's public ReaScript API and does not change the normal user resource directory.

The script identifies actual plug-in parameters separately from REAPER's index-prefixed wrapper identifiers, such as 2:bypass, 3:wet and 4:delta. Host window handle existence verifies creation/reopening, not visual layout, GUI gesture recording or live meter rendering. If the host prompts about audio configuration or evaluation, complete its normal startup before running the script.