Rescanning Sonnox Plug‑ins in Studio One

Modified on Wed, 30 Jul at 4:07 PM

If Sonnox plug‑ins don’t appear in Studio One, resetting the blacklist and forcing a full plugin rescan usually resolves the issue.
This guide is based on Studio One 6 and 7 behaviour and includes advanced options for stubborn cases.


Prerequisites

  • Studio One fully closed.

  • Administrative access (Windows) or proper file permissions (macOS).

  • Know your VST plugin installation location (default or custom).


Step‑by‑Step Solution

1. Reset the Blocklist & Enable Rescan

  • Open Studio One → Preferences (macOS) or Options (Windows).

  • Under Locations → VST Plug‑Ins, ensure your Sonnox plugin folder is listed (e.g., default VST3/VST2 paths).

  • Enable Scan at startup.

  • Click Reset Blocklist and confirm the prompt.

  • Close Preferences and restart Studio One.

    • This forces a full rescan and attempts to load any previously blocked plug‑ins.

2. Full Rebuild of Plug‑In Database (Advanced)

If the above doesn’t resolve the issue, rebuild the plugin database from scratch:

  • Windows:
    Navigate to your Studio One settings folder:
    C:\Users\<username>\AppData\Roaming\PreSonus\Studio One <version>\x64
    Delete or rename the x64 folder.

  • macOS:
    In Studio One, go to Help → Open Settings Folder.
    Locate and delete the corresponding x64 settings folder.

  • Relaunch Studio One — this forces a complete plugin scan and rebuild.


Troubleshooting / Alternative Fixes

  • Plugin still missing?

    • Confirm the insert path is correct and included in the VST locations list.

    • Make sure you're not adding 32-bit VSTs to Studio One Pro (which supports only 64-bit).

    • Reset the blocklist and scan again, or force rebuild as above.

  • Plugin stays listed but doesn’t load?

    • The plug‑in may still be disabled rather than skipped — resetting the blocklist helps.

    • Manually clearing plugin settings or cache may be needed if UI elements still conflict.


FAQ / Common Questions

Q: What’s the difference between “Skip” and “Disable” during plugin scans?
A: Skip prevents loading for that launch only — Studio One will try again next time.
Disable adds the plugin to the permanent blocklist until reset.

Q: Will resetting the blocklist remove my session data?
A: No, only internal plugin scan cache is cleared. Your projects and presets stay intact.

Q: Can Studio One crash during scans?
A: Yes, if a plugin is unstable or corrupted. Deleting cache or resetting settings may help.


Related Articles / Links

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article