Frequently asked questions

Drag the whole EvoraVerb.vst3 folder into C:\Program Files\Common Files\VST3\, then restart your DAW.

Windows shows it as an ordinary folder, but it is the plugin itself. Copy it as one unit and never move its contents separately, or your DAW will not recognise it.

There is no installer and no command line involved.

Double-click each .tar.gz file. macOS extracts them on its own, leaving the plugins next to the archives.

Then move EvoraVerb.vst3 to /Library/Audio/Plug-Ins/VST3/ and EvoraVerb.component to /Library/Audio/Plug-Ins/Components/.

If you would rather not type an administrator password, the same folders inside your home Library work just as well. Restart your DAW afterwards; Logic rescans Audio Units on launch and the first scan takes a little longer.

EvoraVerb is not yet signed with an Apple Developer ID or notarised. The binaries carry only the ad-hoc signature the compiler generates, which does not satisfy Gatekeeper, so macOS blocks them the first time.

Open System Settings, go to Privacy & Security, and allow EvoraVerb using the notice near the bottom of the page. You only have to do this once, and no Terminal commands are needed.

Proper signing and notarisation are on the list for the stable release.

Delete the plugin file from the folder you installed it into. That is all.

There is no installer and no background service.

If you saved your own presets, those files stay behind on purpose, so reinstalling does not lose them. On macOS they live in your home Library under Audio/Presets, in an ODDSIGNAL AUDIO folder; on Windows, in the ODDSIGNAL AUDIO folder inside your user application data. Delete that folder if you want them gone too.

On Windows, VST3 and a standalone application. On macOS, VST3, Audio Unit and standalone.

There is no VST2 and no AAX, so EvoraVerb does not load in Pro Tools. AAX requires the Avid SDK and a PACE signature, neither of which we have yet.

Windows 10 or later, 64-bit, and macOS 11 Big Sur or later.

The macOS build is a universal binary: it runs natively on Apple Silicon and on Intel Macs, with no Rosetta involved.

Any host that loads VST3 or Audio Units will run it: Ableton Live, Logic Pro, Cubase, Studio One, Reaper, Bitwig, FL Studio and the rest.

The only exception is Pro Tools, which needs AAX.

Not natively. EvoraVerb is not available in AAX yet, and Pro Tools only loads AAX plugins.

You can still run it through a wrapper such as Blue Cat's PatchWork or DDMF Metaplugin, which host the VST3 inside an AAX shell.

Not directly. EvoraVerb is stereo in, stereo out, which is what lets it keep left and right on separate paths all the way through the reverb.

For a mono source, put it on a stereo bus or a stereo send. That is how reverb is usually set up anyway.

Whatever your project runs at. Every delay length and filter coefficient is recalculated when the sample rate changes, so the reverb sounds the same at 44.1 kHz and at 96 kHz.

Twenty factory presets, from tight rooms to infinite spaces, with starting points for vocals, drums and piano. Since version 1.2 you can also save your own.

They set Amount and Mix. The low and high cut filters stay out of presets on purpose, since where you cut frequencies depends on your material rather than on the type of room.

That is the simple mode. Amount moves six internal parameters at once along a path where every position is a usable space, so you can find a sound quickly instead of hunting for a good combination.

Open the advanced panel and you get those six directly, plus a low cut and a high cut for the reverb. The technical page covers all of it.

No. It reports zero samples, so nothing in your session shifts and you can leave it on while tracking.

No. Nothing is allocated while audio is running, everything is reserved when the plugin loads, and the engine is eight delay lines rather than a convolution.

You can run several instances on a modern machine without trouble.

Yes. Everything is stored in your session, so reopening the project restores exactly what you left.

No. There is no serial number, no activation and no copy protection of any kind.

The plugin never connects to the internet and works fine on a machine that has never been online.

Yes. Anything you record with EvoraVerb is yours, with no restrictions and no royalties.

EvoraVerb is sold through KVR Audio, where you can see the current price. One purchase covers Windows and macOS, and all three formats.

New versions are announced on our KVR Audio page, and buyers get the updated download there. You can also follow us on Instagram.

Four things, in this order:

First, that the plugin sits in the right folder. Second, that you copied the whole .vst3 unit rather than the files inside it, which is the most common mistake on Windows. Third, that your DAW is 64-bit. Fourth, that you are looking under VST3 or Audio Units and not VST2.

If everything checks out, force a plugin rescan. Some hosts only pick up new plugins after you clear their cache in preferences.

Logic only shows Audio Units, so make sure EvoraVerb.component is installed and not just the VST3.

Logic also caches the result of its validation: if the plugin failed the first scan because of the Gatekeeper warning, allow it in Privacy & Security first, then reopen Logic so it validates again.

You should not. Every parameter is ramped internally, from 20 ms on Mix to 250 ms on Decay, precisely so that automation stays clean.

If you run into it, tell us which parameter and which DAW, because that would be a bug worth fixing.

Write to oddsignalaudio@gmail.com with your operating system, your DAW and its version, and what you were doing when the problem appeared.

That is the fastest route to a fix, and the reports we get shape what we work on next.