Skip to content

Require VST3 double-precision validation - #150

Closed
satoshi-assistant wants to merge 2 commits into
novonotes:novonotes-internalfrom
satoshi-assistant:codex/vst3-f64-validation
Closed

Require VST3 double-precision validation#150
satoshi-assistant wants to merge 2 commits into
novonotes:novonotes-internalfrom
satoshi-assistant:codex/vst3-f64-validation

Conversation

@satoshi-assistant

Copy link
Copy Markdown
Contributor

Summary

  • Treat Steinberg validator's skipped 64-bit audio processing as a validation failure
  • Require evidence that the double-precision test suite ran
  • Keep the existing validator as the source of VST3 format behavior instead of adding another host implementation

Why

Steinberg's validator exits successfully when a plugin reports that 64-bit audio processing is unsupported. WRAC needs a stricter contract: VST3 wrappers must preserve the host's sample precision.

Verification

  • cargo test -p wrac_build_ops
  • cargo xtask quality
  • Confirmed that a VST3 bundle without double-precision support now fails after Steinberg's validator completes

Steinberg's validator treats unsupported 64-bit audio processing as a successful skip, so enforce WRAC's sample-precision contract from the validator output.
Integrate the extracted validator configuration and MIDI output changes while preserving the explicit double-precision validation gate.
@satoshi-szk satoshi-szk closed this Aug 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants