Installation

Two files, and nothing else. The artwork, the factory presets and the licensing component are compiled into the binaries, so there is no resource folder to install and no shared library to keep in step.

Both go to /Library rather than your home folder, so the plugins are available to every user on the machine and macOS will ask for an administrator password.

A standalone application is built for each plugin so we can look at the interface without a host in the way. It is not part of the product and the installer does not carry it.

Quit your host before you install, and open it again afterwards. Hosts scan for new plugins at launch, and one that was running through the install will not see them.

macOS validates every Audio Unit before a host is allowed to list it. If a plugin is missing from one host but present in another, that is the usual reason, and you can check it yourself in Terminal:

The manufacturer code is the same for everything we make. The plugin code is the four characters in the specification table on the plugin's own product page.

Check both plugin folders. macOS will load plugins from your home folder as well as the system one, and a copy left in ~/Library/Audio/Plug-Ins can shadow the one the installer put in /Library/Audio/Plug-Ins. If you find the same plugin in both, the one in your home folder is the older of the two.

Check for an older name. Several of these plugins were renamed before release, and a build installed under the previous name does not always make way for the new one — it appears in your host as a second, orphaned copy that no licence will activate. Removing the old bundle is safe; it holds nothing but the binary.

If neither is it, write to us with the plugin, the format, your host and your macOS version, and we will work it out from there.

This is almost always licensing rather than a fault. A plugin that is not authorised passes audio straight through instead of processing it. That is deliberate — a licence that lapses in the middle of a mix must never silence the session — but it does mean the symptom looks like broken processing rather than like a licence problem.

The interface is no help here: the meters and animation run off the parameters, so they keep moving whether or not any processing is happening. Open the plugin's licence panel and check that it says it is authorised.

Installing a new version replaces the two plugin bundles and touches nothing else. Your licences, your own presets and your saved sessions are left exactly where they are.

Early builds wrote both of those folders to ~/Library/Signature Algorithms/ instead. If you have that folder, leave it alone: the plugins read it, and move anything they find across the first time they run. Deleting it by hand can take a licence with it.