Plugin missing from the browser

A plugin that can’t be used isn’t silently hidden. It stays visible in the browser and inspector, labeled with the reason it was excluded: Crashed, Intel-only, or Not loadable. Neutral Tracks scans plugins automatically at launch (only new or changed files, so it’s fast), and you can rescan at any time from the Plugin Browser. Find your symptom below.

Labeled “Crashed”

Cause: the plugin crashed or timed out during scanning.

Fix: install the vendor’s updated build. Exclusion follows the file, not the name. When the vendor ships a crash fix, the updated file is rescanned automatically at the next launch, with no manual cleanup. To pick it up right away, rescan from the Plugin Browser.

Labeled “Intel-only”

Cause: the binary has no Apple Silicon slice, so it can’t load in Neutral Tracks.

Fix: install the vendor’s universal binary. As with any updated build, the new file is rescanned automatically at the next launch, or immediately with a manual rescan.

Labeled “Not loadable”

Cause: the file scanned cleanly but exposed no usable plugin.

Fix: same path as the other labels: an updated file from the vendor is rescanned automatically, and a manual rescan from the Plugin Browser picks it up without waiting for the next launch.

Not in the browser at all

Cause: the plugin isn’t installed where the scan looks, or it ships a format Neutral Tracks doesn’t host.

Fix: confirm both of these:

• It’s installed in a standard location: ~/Library/Audio/Plug-Ins/VST3 or Components, or the system-wide /Library equivalents.
• It ships VST3 or Audio Unit (AUv2). Neutral Tracks does not host AUv3.

Once the plugin is in a standard location, the automatic scan finds the new file at the next launch, or rescan from the Plugin Browser to load it immediately.