install

Installing, and the one odd step.

Nothing here is unusual except that the installer isn't notarised yet. That means macOS blocks the first double-click. Here's the way round it.

Not currently suitable for Pro Tools

These are AU and VST3 plugins. Pro Tools only loads AAX, which these aren't built as - so none of the suite will appear in it. Please check your DAW before you buy - once you download, the sale is final.

system requirements

What you need.

Formats
Audio Unit (AU) and VST3 on macOS, VST3 on Windows. VST2 isn't built - the SDK is discontinued.
macOS
10.15 Catalina or later. Confirmed on Intel Macs from Catalina up, and on Apple Silicon (M4, Logic Pro). The installers are universal binaries, so they run natively on both - Rosetta is not needed.
Windows
Windows 10 or 11, VST3. There is no Audio Unit format on Windows - that is a macOS thing, not something missing here. Confirmed working in Studio One.
Installer
macOS: a standard .pkg. Windows: a standard .exe installer.
Host
Any host that loads AU or VST3. See the confirmed list below.

Where it's confirmed to work

Honest version: this is a one-person operation, so it has been properly tested in the DAWs below and not yet in the others. Not tested yet means exactly that - not that it fails.

DAW compatibility
DAWSystem Plugins load They share with each other
Logic PromacOSYesYes
GarageBandmacOSNot tested yetNot tested yet
Ableton LiveMac/WinNot tested yetNot tested yet
Cubase / NuendoMac/WinNot tested yetNot tested yet
Studio One
Confirmed on Windows (VST3). The sharing side is still to be checked.
Mac/WinYesNot tested yet
Reaper
Confirmed on Intel Mac - both AU and VST3, and the plugins share with each other. Not yet tested on Windows.
Mac/WinYesYes
FL StudioMac/WinNot tested yetNot tested yet
Bitwig StudioMac/WinNot tested yetNot tested yet
Digital PerformerMac/WinNot tested yetNot tested yet
Pro Tools
Pro Tools only loads AAX plugins. These are AU and VST3.
Mac/WinNoNo
Operating system compatibility
SystemConfirmed
macOS on IntelYes
Confirmed working from 10.15 Catalina upwards.
macOS on Apple SiliconYes
Confirmed on an M4 Mac in Logic Pro. The installers are universal binaries, so they run natively - no Rosetta needed.
Windows 10 / 11Yes
VST3 only - there is no AU on Windows. Confirmed in Studio One.

"They share with each other" is the ANALYSE pass, the clash matrix and the AUTO settings. Where a DAW keeps plugins apart, every plugin still works perfectly on its own - they just can't pass measurements between them, and nothing breaks. Ten-second check in any DAW: put Analyser on two tracks, turn one to master, and see whether the second track appears in its overview. Tell me what you find and this list gets updated.

macOS

Installing the .pkg

  1. Download the .pkg from the link in your email.
  2. It isn't notarised yet, so a normal double-click gets blocked. Control-click (right-click) the .pkg → Open → Open. (Or try to open it normally, then go to System Settings → Privacy & Security and click Open Anyway.)
  3. Run the installer. It puts the AU in /Library/Audio/Plug-Ins/Components and the VST3 in /Library/Audio/Plug-Ins/VST3.
  4. Rescan plugins in your DAW. Logic validates new AUs on its next launch.

To be upfront about it: notarisation means paying for an Apple Developer ID, and at launch that money is better spent on the plugins. It's a known trade-off, not an oversight, and signing is coming in a later drop. Until then you get one scary-looking dialog and then never again.

Something not showing up?

Nine times in ten it's the DAW's plugin cache. Rescan, or in Logic run auval -a in Terminal to see whether macOS registered the AU at all. If it's still missing, email me at {mailto()}.