Native VST3 meter-forwarding harness¶
prepare.py also writes a public-fixture marker. In a new empty isolated REAPER
project, native-meters.lua requires that marker before making any host change.
It loads only the public RAVET gain VST3, mutes project hardware destinations,
plays the generated input and compares all twelve normalized peak/RMS/diagnostic
parameters. A floating-window handle is logged separately; it cannot prove
visual/assistive-technology behavior. It stops playback and closes its test FX
window, leaving the disposable project. It writes native-meter-host.log under
this resource directory's ravet-validation folder.
The first local attempt stalled in a startup modal while native UI automation returned cgWindowNotFound. After owner readiness, the isolated REAPER 7.82/macOS arm64 main window became inspectable. Loading/running the guarded script through its action list passed all twelve normalized meter comparisons and the native floating-window handle. Playback stopped and the editor closed afterward. This is actual DAW forwarding evidence; no visual/assistive-tech/deadline claim. See work status for the retained historical attempts. Guard fixtures execute with an optional installed Lua interpreter to verify missing/incorrect marker and nonempty project rejection before host mutation. See decision 0101.
The native meter harness logs its enumerated FX count and public Gain candidate
names before the discovery assertion, making disposable-cache/path problems
visible without logging unrelated plug-in names. On macOS arm64, the native
REAPER VST path setting is vstpath_arm64; vstpath64 alone does not configure
that host. Prefer its VST preferences for a committed path and scan.