How to Force Pro Tools to Scan New Plugins: A Comprehensive Guide

Pro Tools is known for its robust plugin management, typically scanning for new plugins automatically upon startup. However, sometimes a newly installed plugin might not appear in your plugin list, disrupting your workflow. Unlike some other DAWs, Pro Tools doesn’t offer a straightforward manual rescan option. But don’t worry, there’s a proven method to force Pro Tools to recognize and scan your new plugins, ensuring you can get back to creating music without interruption.

This guide will walk you through the necessary steps to effectively rescan your plugins in Pro Tools, covering everything from verifying plugin locations to clearing plugin preferences. Follow these instructions, and you’ll have your new plugins up and running in no time.

Step 1: Ensure Pro Tools is Completely Closed

Before attempting any plugin rescan, it’s crucial to completely close Pro Tools. Pro Tools scans for plugins during its launch sequence, so any changes or forced rescans require the application to be shut down first. Simply closing the main window might not be enough; background processes could still be running.

To guarantee a complete shutdown:

  • Windows: Open Task Manager (Ctrl+Shift+Esc) and check the Processes tab. Look for any Pro Tools processes and end them.
  • macOS: Open Activity Monitor (Applications > Utilities > Activity Monitor) and look for Pro Tools processes in the CPU or Memory tabs. Select any Pro Tools processes and click the “X” button in the toolbar to quit them.

Ensuring Pro Tools is fully closed prevents conflicts and ensures a clean rescan process.

Step 2: Verify Your Plugins Are in the Correct Plugin Folders

Pro Tools is specific about where it looks for plugins. It primarily recognizes plugins located in its designated plugin folders. Pro Tools 11 and later versions exclusively use plugins residing in these specific directories. If your new plugin isn’t showing up, the first thing to check is whether it’s installed in the right location.

Here are the standard plugin folder locations for Pro Tools on both Windows and macOS:

Standard Pro Tools Plugin Locations:

Windows 10:

  • C:Program FilesCommon FilesAvidAudioPlug-Ins
  • C:Program FilesCommon FilesDigidesignDAEPlug-Ins
  • C:Program Files (x86)Common FilesAvidAudioPlug-Ins (Less common for 64-bit Pro Tools, but worth checking)
  • C:Program Files (x86)Common FilesDigidesignDAEPlug-Ins (Less common for 64-bit Pro Tools)

macOS:

  • Macintosh HD/Library/Application Support/Avid/Audio/Plug-Ins
  • Macintosh HD/Library/Application Support/Digidesign/Plug-Ins

Checking Other Potential Plugin Locations (Less Likely for Pro Tools):

While Pro Tools prefers the directories above, some installers might place plugins in more general VST or VST3 folders. While Pro Tools primarily uses AAX format plugins, it might be worth checking these locations if you’re unsure about your plugin’s installation path:

Windows:

  • C:Program FilesVSTPlugins
  • C:Program FilesSteinbergVSTPlugins
  • C:Program FilesCommon FilesVST3
  • C:Program Files (x86)Common FilesVST3
  • C:Program FilesCommon FilesVST2
  • C:Program FilesCommon FilesSteinbergVST2
  • C:Program Files (x86)SteinbergVstPlugins

macOS:

  • Library/Audio/Plug-ins/VST
  • Library/Audio/Plug-ins/VST3
  • Users/*YourUsername*/Library/Audio/Plug-ins/VST
  • Users/*YourUsername*/Library/Audio/Plug-ins/VST3

Important Note: Pro Tools 11 and later are designed for 64-bit AAX plugins. Older VST plugins, especially 32-bit versions, are unlikely to be compatible with modern Pro Tools versions. Ensure your new plugin is AAX and 64-bit compatible for proper functionality.

If you find your plugin in a different location, move or copy it to one of the standard Pro Tools plugin folders listed under “Standard Pro Tools Plugin Locations” above.

Step 3: Relaunch Pro Tools and Check Your Plugin List

After verifying or moving your plugin to the correct folder, relaunch Pro Tools. During startup, Pro Tools should automatically scan the plugin folders. Once Pro Tools is open, check your plugin menus to see if the new plugin now appears.

If the plugin is still not visible, proceed to the next step, which involves forcing a more thorough rescan by deleting plugin preferences.

Step 4: Delete Your Pro Tools Plugin Preferences to Force a Rescan

When a plugin is initially scanned, Pro Tools creates preference files to manage and remember its settings. Sometimes, these preference files can become corrupted or prevent new plugins from being recognized. Deleting these preference files forces Pro Tools to rebuild them, triggering a fresh rescan of all plugins upon the next launch.

Caution: Deleting plugin preferences will reset all your plugin settings to their defaults. If you have custom presets or settings you want to keep, back them up before proceeding.

Deleting Plugin Preferences:

Windows 10:

  1. Open File Explorer.

  2. Enable Hidden Items: Click on the “View” tab and check the “Hidden items” box. Plugin preference folders are often hidden by default.

  3. Navigate to one of the following locations (check both):

    • C:Users*YourUsername*AppDataRoamingAvidPro Tools
    • C:Program Files (x86)Common FilesDigidesignDAEDAE Prefs
  4. Within these folders, you can either:

    • Delete the Entire Pro Tools Folder: This is a more drastic approach but ensures all preferences are reset.
    • Delete the InstalledAAXPlugIns File: This file specifically stores information about installed AAX plugins and deleting it can be sufficient to force a rescan.

macOS:

  1. Open Finder.

  2. Go to the following location: Macintosh HD/Library/Preferences/Avid

  3. In the Avid folder, you can either:

    • Delete the Entire “Pro Tools” Folder: Resets all Pro Tools preferences.
    • Delete Specific Preference Files: For a plugin rescan, deleting these files is usually enough:
      • com.digidesign.ProTools.plist
      • com.digidesign.ProTools.plist.lockfile
      • DAE Prefs
      • DigiSetup.OSX
      • Pro Tools Prefs
  4. Empty Trash: After deleting the folders or files, remember to empty your trash bin to permanently remove them from your system.

Step 5: Relaunch Pro Tools Again

With your plugin preferences deleted, relaunch Pro Tools. The application will now be forced to rescan all available plugins and create new preference files. After Pro Tools has fully loaded, check your plugin lists. Your missing plugin should now be recognized and available for use.

Step 6: Customize Your Plugin Menus for Easier Navigation

Sometimes, even after a successful rescan, a new plugin might be placed in an unexpected category or manufacturer folder within Pro Tools’ plugin menus. Pro Tools allows you to customize how your plugin menus are organized, making it easier to locate your plugins.

To customize plugin menu organization:

  1. In Pro Tools, go to the “Setup” menu and select “Preferences”.
  2. In the Preferences window, navigate to the “Display” tab.
  3. Look for the section titled “Organize Plug-In Menus By”.
  4. Experiment with different organization options, such as “Category/Manufacturer”. This is often the most helpful for finding plugins, as it groups them by type and developer.

By organizing your plugin menus, you can quickly browse through categories and manufacturers to pinpoint your newly scanned plugin if it’s not immediately obvious in your default plugin lists.

Conclusion

Forcing a plugin rescan in Pro Tools involves deleting plugin preference files to trigger a fresh scan upon relaunch. By following these steps – ensuring Pro Tools is closed, verifying plugin locations, deleting preferences, and then relaunching – you should successfully resolve issues with Pro Tools not recognizing new plugins. Remember to always ensure your plugins are compatible with your version of Pro Tools, particularly regarding AAX and 64-bit compatibility. With these troubleshooting steps, you can maintain a smooth and productive workflow within Pro Tools, keeping your focus on music creation.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *