Notes on how our plugins are built. What is inside the reverb and distortion engines, the decisions behind them, and what shipping each release actually involves.
A reverb has at least six parameters that genuinely change the sound. We put five of them behind a single control, and then spent a release working out how to give them back without breaking anything.
The core of EvoraVerb is a feedback delay network. Eight delay lines, each feeding all the others through a matrix. Here is what is actually inside it and why each choice is there.
Long tails are where artificial reverbs give themselves away, and the culprit is almost always the modulation. Not its presence, its regularity.
Most of the work in a long reverb is not in making it sound good. It is in stopping a feedback loop that runs for twelve seconds from quietly destroying itself.
Static saturation is honest about what it does: pick a transfer curve, run everything through it. ODD ENGINE started from asking what happens if the plugin is allowed to know what's coming in first.
One macro, one job: how much the drive stage listens to what's coming in. That simplicity turned out to hide a real design question about where zero and a hundred should actually sit.
Oversampling, denormal handling, real-time-safe allocation, true bypass: none of it is exclusive to paid plugins. It's just work most people never see, whether they paid for it or not.
ODDDIST tends to get reached for on vocals first, because that's where saturation usually lives in a mix. The same five controls and the ODD macro work just as well on almost anything else with a transient to grab onto.