IN
Input Trim before the chain
Input Trim defaults to 0.0 dB, is applied before the serial VST3 chain and uses bounded smoothed gain changes. The input L/R meters observe the post-trim signal.
Compatibility · latest stable
Broad VST3 effect support, with explicit boundaries.
The project targets conventional Windows x64 VST3 audio effects. Compatibility is evidence-based, not implemented as a hard-coded vendor whitelist, and no responsible host can guarantee every VST3 implementation.
Stable support matrix
What the current stable product is designed to support
Windows
x64 supported
OBS Studio
29.1+ compatibility floor; release qualification builds against pinned current OBS/libobs.
VST3 audio effects
Supported in the current mono/stereo Float32 scope.
Single VST3 Host
Stable
Serial VST3 Rack
Stable
Compact graphical Rack Editor
Supported in the isolated Rack helper.
Input Trim / Output Fader
Supported as real pre-chain/post-chain DSP controls.
Stereo input/output peak meters
Supported around the Rack master signal path.
LUFS-I integrated loudness
Supported on the final post-output-fader signal.
dBTP reconstructed true peak
Supported on the final post-output-fader signal.
Automatic working-Rack recall
Supported
Native vendor editors
Supported where the plug-in exposes a compatible native editor.
Named Rack presets
Supported independently from the automatic working session.
VST3 instruments / MIDI
Not currently supported
Sidechain / free-form routing
Not currently supported
Arbitrary multichannel / Float64 fallback
Not currently supported
macOS / Linux packages
Not currently shipped
Rack master signal path
The meters and faders describe the actual shipping Rack path.
The master console is not decorative UI. Input Trim, Output Fader and broadcast telemetry are attached to the generated shipping Rack helper while preserving the isolated-helper architecture.
OUT
Output Fader after the chain
Output Fader defaults to 0.0 dB and remains authoritative after the chain, including fail-dry output, so deliberate attenuation does not jump back to full level when a wet result is unavailable.
METER
Final-output loudness
Output L/R peaks, LUFS-I and dBTP observe the final post-output-fader audio delivered to OBS.
Metering contract
Broadcast metrics are bounded telemetry, not a claim of universal loudness compliance.
The implementation follows a deterministic broadcast-oriented measurement contract: integrated loudness uses K-weighting and gated ITU-R BS.1770 / EBU R128-style structure; true peak uses reconstructed inter-sample estimation. Final platform delivery targets and compliance remain the user's responsibility.
✓
LUFS-I structure. 400 ms windows with 75% overlap, -70 LUFS absolute gating and -10 LU relative gating.
✓
dBTP reconstruction. 4× quarter-sample reconstruction with a 33-tap windowed-sinc polyphase interpolator and session-max hold.
✓
Realtime boundary. Telemetry publication is atomic/lock-free and avoids UI calls, mutex waits and dynamic audio-path allocation.
✓
Reference coverage. Deterministic tests cover loudness gating and inter-sample true-peak behavior.
Real-machine evidence
Representative commercial VST3 effects have been part of project qualification.
Across the stable Single Host line and Rack development, real-machine qualification has included effects from vendors such as:
iZotope Ozone / RXFabFilterWavesKlevgrandNeuro AudioProcess Audio
These names are qualification examples, not an allowlist or guarantee. A different plug-in version, licensing layer, editor implementation or VST3 lifecycle behavior can still expose a vendor-specific compatibility issue.
Persistence evidence
Recall testing covers the actual working Rack, not only reusable presets.
Real OBS validation changed settings in commercial split controller/processor VST3 effects across successive OBS sessions. The latest working Rack and full DSP state restored on restart, including cases where controller metadata alone would not have been sufficient.
✓
DSP-safe capture frontier. State capture is coordinated away from concurrent vendor processing.
✓
Dry-first restore. Slow chains can remain safely available as dry/pass-through while materializing.
✓
Split-component synchronization. Native GUI edits and preset-wide parameter resyncs reach processor state before capture.
✓
Explicit storage failure. The product does not present a writable Rack as normally persistent when durable session storage is unavailable.
Download current stable
Install directly from the public site.
The installer button resolves the latest public release automatically and downloads the release asset directly.