Skip to main content
Help/Pressure/Research Notes

Research Notes: Pressure

Last updated: 2026-02-25 · Plugin v1.0.0 · BPTS v2.1.0

Current Test Status

  • Survived The Gauntlet™ (1,000,000 parameter mutations, 0 crashes)
  • Category 5 stress tests passing (25/25)
  • Zero audio artifacts detected in stress testing
  • Pluginval clean (strictness 10)
  • Zero memory leaks over 1 hour marathon test

Validation Depth

482

Total Tests

7

Adversarial Systems

6

Golden References

6

Security Vectors

3

Sanitizers

100K

Fuzz Iterations

Production latency: ~62 µs/block on M4 Pro at 48.0 kHz / 512 samples

Audio Quality Specs

Measured at −12 dBFS, 60% pressure

EngineTHD RangeCharacter
MIX (VCA)0.02–0.06%Clean, SSL-style
INST (FET)0.05–3.0%Natural 1176-style
VOCALS (Opto)0.4–0.7%Warm LA-2A character
DRUMS (VCA)0.01–0.08%Transparent dynamics
MASTER (VariMu)0.06–1.9%Classic tube compression

Framework Improvements

Issues identified through mutation testing and their resolutions.

  • DC offset detection added to buffer validation

    Mutation testing revealed that buffer validation did not yet cover DC offset. Detection was added with a −60 dBFS threshold, and all plugins were re-validated.

    Resolved in BPTS v2.2.0 · 2026-02-01

  • Sample-level discontinuity detection added

    Mutation testing identified that the framework lacked sample-by-sample gradient analysis. A discontinuity detector with a 6 dB inter-sample threshold is being integrated to extend coverage to transient-level anomalies.

    In progress

Why Public Research Notes?

Mutation testing is how we verify the test suite itself. By intentionally injecting faults into the plugin, we identify where the testing framework needs to improve—and then we improve it.

This page documents that cycle: what we found, what we fixed, and how the framework got stronger. Engineering rigor, documented in the open.

If you encounter unexpected behavior our tests haven't covered, we want to hear about it.

Learn more about our testing methodology: Testing Suite Documentation

Found a Bug?

If you crash it or hear artifacts our tests missed, email me:

keith@bellweatherstudios.com

Include: DAW + OS version, what you did before it crashed, crash log if available. Best bug reports get credited in release notes.

These are research notes, not marketing claims. We publish the engineering process because trust is built on evidence, not messaging.