← All posts ·

10 to 20 Minute Fix and DSP Verification for AAX Plugins in Pro Tools

10 to 20 Minute Fix and DSP Verification for AAX Plugins in Pro Tools

Engineer verifying AAX plugin in Pro Tools

Most missing AAX plugins come down to three causes: the plugin files are not in Avid's standard plug-ins folder, Pro Tools is working from a stale plugin cache, or you're on Apple silicon running an Intel-only build. Start by confirming the file location, then clear the cache and restart. If you're on an M-series Mac, check whether the plugin has a native build before you do anything else.

TL;DR:

  • Confirm that the plugin files are located in the correct Avid plug-ins folder and not in a subfolder or leftover installer directory.
  • Clear the AAXPluginCache and delete the InstalledAAXPlugins preference files to force a fresh plugin scan.
  • Enable Rosetta for Pro Tools when using Intel-only plugins on Apple silicon Macs and verify plugin binary compatibility.
  • On Windows, ensure plugins are in the correct Avid path, run Pro Tools as administrator after installation, and remove the preference file if needed.
  • Perform a quick functional test on loaded plugins to verify audio processing and check CPU utilization before using them in critical mixes.

Table of Contents

Quick diagnostic checklist you can run in 10 to 20 minutes

Work through these checks in order. Each one eliminates a likely cause before you move to something more time-consuming.

  1. Open the Avid plug-ins folder and confirm the .aaxplugin file actually sits there, not in a vendor-created subfolder or a leftover installer directory.
  2. Check the Plug-Ins (Unused) folder. Pro Tools moves plugins there automatically in some cases, and anything inside is invisible to your session until you move it back into Plug-Ins.
  3. Look inside the Pro Tools application bundle itself for a stray Plug-Ins folder. Some installers mistakenly write files there instead of the system-wide Avid location, and Pro Tools won't scan that path.
  4. Restart Pro Tools after each change, and restart the machine once you've made several changes, since some scan states only clear on a full reboot.
  5. Open your session notes or the plugin list in the Session Setup window for warnings about missing or offline plugins. This often points you straight to the plugin name and format causing the gap.
  6. If you're on an Apple silicon Mac, check whether the plugin ships as a universal binary or Intel-only. An Intel-only plugin needs Rosetta to load at all.

None of these steps require deleting anything permanently, so you can run through all six without risking your existing setup.

Pro Tip: Keep a plain text note of every path you check and what you find. If you end up contacting support, that log cuts the back-and-forth in half.

macOS-specific fixes: exact paths, Rosetta, permissions, and when to clear caches

On macOS, AAX plugins live at /Library/Application Support/Avid/Audio/Plug-Ins. That's a system-wide path, not a user folder, so check it even if you installed the plugin under your own account. The matching Plug-Ins (Unused) folder sits right next to it, and a plugin parked there won't appear in Pro Tools no matter how many times you rescan.

Avid's own troubleshooting guidance for cases where only default AAX plugins load points to exactly this fix: check both plugin folders, then delete the InstalledAAXPlugins preference to trigger a fresh scan. That single step resolves a large share of "missing plugin" tickets without touching the plugin install itself.

The Rosetta setting is per user account, not system-wide. On a shared studio Mac with multiple logins, enabling Rosetta for one account leaves it disabled for every other account on the same machine, which is a common reason a plugin loads for one engineer but not another.

Rosetta setting separated by user accounts

Windows-specific fixes: correct AAX paths, installer issues, and privilege tips

On Windows, the standard AAX path is C:\Program Files\Common Files\Avid\Audio\Plug-Ins. Some installers, especially older ones or ones ported from other DAW formats, drop files into a different Common Files subfolder or into the plugin's own Program Files directory instead.

Reinstalling should be a last step, not a first one. Most Windows cases trace back to a plugin sitting one folder level off from where Pro Tools expects it.

Exactly which cache and preference files to remove

Clearing the right cache files forces Pro Tools to treat every AAX plugin as new and rescan it from disk. This fixes cases where a plugin is correctly installed but Pro Tools still refuses to show it, usually because a corrupted scan record is overriding the real file.

  1. Close Pro Tools completely before touching any files.
  2. Back up the InstalledAAXPlugins preference file and the AAXPluginCache folder, in case you need to restore them.
  3. Delete the contents of the AAXPluginCache folder. The exact path varies by OS version, but it sits alongside the other Avid preference files on both macOS and Windows.
  4. Remove the InstalledAAXPlugins preference file itself (~/Library/Preferences/Avid/Pro Tools on macOS, the equivalent AppData path on Windows) when Avid's own troubleshooting steps call for it.
  5. Restart the computer, not just Pro Tools, to clear any lingering scan state held in memory.
  6. Launch Pro Tools and let it complete a full rescan. This can take longer than a normal launch, which is expected.
  7. Confirm the plugin appears, then check that it's authorized. A plugin that shows up but refuses to instantiate often has a separate licensing problem, not a detection one.

This sequence mirrors Avid's own guidance for cases where only default plugins load: the preference deletion and cache clear are the two actions that actually change Pro Tools's behavior, everything else is verification.

How Apple Silicon affects AAX loading and the Rosetta workaround

Universal AAX plugins load natively on Apple silicon without any extra setup. Intel-only plugins are a different story: they won't load at all when Pro Tools runs natively on an M-series chip, and Pro Tools does not reliably warn you when it silently skips one.

Avid confirms this behavior directly: universal binaries load under both native Apple silicon and Rosetta, while Intel-only plugins simply don't appear when Pro Tools runs natively, with no on-screen warning when they're skipped.

How to prevent missing-plugin problems and keep Pro Tools scanning lean

A few habits can reduce how often this happens again, saving you troubleshooting time later.

Pro Tip: Rename your Unused folder to include the date you moved each plugin out. Six months later, you'll know at a glance whether it's safe to remove for good.

Vector DSP verification checks: functional and performance tests

Once a plugin shows up in Pro Tools, showing up isn't the same as working correctly. We recommend a short functional pass before you trust it in a mix. Insert the plugin on a track and run a quick dry and wet comparison to confirm it's actually processing audio and that the GUI opens without delay.

Watch your CPU meter during that test. A plugin that's bypassed internally or failing silently sometimes still shows normal latency but produces no audible change, while a genuine processing failure often spikes CPU without changing the signal. If the GUI opens but the audio stays untouched, check the plugin's authorization state before assuming it's a routing mistake.

AAX plugin functional verification workflow

For side-by-side checks against your existing plugin chain, a demo license lets you insert ToneLab's lane-based EQ alongside what you already use and compare behavior directly, rather than guessing from memory.

Author perspective: recurring root causes and a five-step rhythm

Nearly every missing-plugin ticket I've seen traces back to one of four things: wrong folder, stale cache, a Rosetta mismatch, or an installer that wrote files somewhere unexpected. My rhythm is always the same: verify the folder, check Unused, clear the cache, restart, then run a functional test. If the plugin still won't load after that, it's time to contact Avid or the plugin vendor directly.

— Kai

FAQ

Which DAW uses AAX plugins?

Pro Tools is the primary DAW that uses the AAX plugin format, developed by Avid specifically for its own software. Other DAWs typically rely on VST3 or AU formats instead, so a plugin needs a dedicated AAX build to run in Pro Tools.

Why won't my plugins show up in Pro Tools?

The most common reasons are files sitting outside the standard Avid plug-ins folder, a stale plugin cache, or an Intel-only plugin running on Apple silicon without Rosetta enabled. Checking the Plug-Ins and Plug-Ins (Unused) folders and clearing the InstalledAAXPlugins preference resolves most cases.

Why is the plugin not working?

A plugin that loads but doesn't process audio usually has a licensing or authorization problem rather than a detection issue. Check the plugin's activation status first, since a missing or expired license can leave the GUI functional while the actual processing stays inactive.

Why are my plugins not showing up in GarageBand?

GarageBand uses the Audio Unit (AU) format, not AAX, so an AAX-only plugin will never appear there regardless of installation. You need a plugin with a dedicated AU build, or a plugin that ships with both AAX and AU versions, to use it inside GarageBand.

What does the AAE -7058 error mean?

AAE -7058 means Pro Tools found a plugin file that isn't a valid 64-bit AAX build, often because of an outdated plugin version or a corrupted install. Avid's guidance for this specific error points to updating the plugin or reinstalling it with a current build.

Authoritative links used for troubleshooting steps and compatibility lists

For deeper reference, these are the official sources behind the steps above, covering folder locations, Apple silicon compatibility, and the PT-321737 crash workaround documented in the current Pro Tools release notes.