Research Notes: Pressure
Current public release: v1.8.3
These results cover v1.7.0, tested on 2026-06-08. They do not cover the current release, v1.8.3.
Test results and methodology
Results for v1.7.0
- ✓Survived The Gauntlet™ (1,000,000 parameter mutations, 0 crashes)
- ✓Category 5 stress tests passing
- ✓Zero audio artifacts detected in stress testing
- ✓Pluginval clean in this snapshot (strictness 10)
- ✓Zero memory leaks over 1 hour marathon test
Validation Depth
Production latency: ~85 µs/block on M4 Pro at 48.0 kHz / 512 samples
Distortion Character
How each engine colors the signal, from clean to richly saturated.
Engine Response Characterization
Measured 2026-05-31. Controlled lower-layer characterization at approximately 6 dB raw gain reduction.
These measurements are response fingerprints, not universal quality rankings or release thresholds. They do not claim preset, AUTO-mode, lookahead, oversampling, or full-plugin behavior.
VOCALS: The final 1% recovery crossing remained above the measurement floor after the 20 s observation window.
What AUTO Does
AUTO is an engine-aware compression system. PRESSURE drives a tailored curve for the selected voice rather than applying one generic compressor setting.
- •Coordinates threshold, ratio, attack, release, and knee through per-voice curves.
- •Adds an input-aware threshold adjustment while preserving the selected voice's identity.
- •Uses TONE to shape engine-specific detector emphasis.
- •Keeps DRUMS-specific program-dependent release distinct from the shared AUTO curve system.
Internal characterization confirms that AUTO produces materially different behavior by voice and event duration. The published response table above remains the cleaner controlled comparison because it measures all five voices at approximately 6 dB raw gain reduction.
AUTO is not a universal material-adaptive attack/release algorithm, and these observations are not a five-engine AUTO timing table.
Why Public Research Notes?
These notes record measurements and testing methods for the versions identified above. They describe what was tested and the limits of those results.
Learn more about our testing methodology: Testing Suite Documentation