Synth Berry on the Test Bench

Method

• The installed native Windows VST3 binary is pinned by SHA-256 and matched to its installation receipt. Actual loaded processor name and module path are checked in a separate REAPER process.
• REAPER runs on an isolated non-input Windows desktop, using its own resource folder. No FX editor, audio-device playback or existing REAPER process is used.
• Parameters below are the actual defaults read back after loading. Reported latency and host-program count are read directly through the REAPER API.

Limits of this report

• Instrument audio, eight-note CPU load, three named factory-preset renders and polyphony are still to be measured. No dry/processed comparison is invented.
• The host-exposed program count may be zero even when the instrument has its own factory library. This report does not count that library.
• Real-time CPU at a 128-sample buffer has not been measured. The isolated offline route uses a 512-sample device configuration and does not start playback; render speed is not reported as CPU usage.
• Windows VST3 only. This report does not measure the macOS build or imply analogue-hardware equivalence or an endorsement.
• Signal measurements are not subjective listening. The remaining measurements are listed here rather than represented as completed.