Scenario (Windows 11):
Live 11 (latest version) + SSL Native X-Saturator (VST3)

hi,
Live 11 doesn't detect SSL Native X-Saturator (VST3) even after X-Saturator has been uninstalled and re-installed a couple of time; weirdly FL Studio 25.2 and Live 12 detect it fine

Any idea/suggestion? TIA

P.S.
Legit softwares

 

Using VST plug-ins on Windows
https://help.ableton.com/hc/en-us/articles/209071729-Using-VST-plug-ins-on-Windows

3. Configure VST3 plug-ins
To use VST3 plug-ins, set Use VST3 Plug-in System Folder to On. In most cases, you can leave Use VST3 Plug-In Custom Folder turned off.


In rare cases, the installer may define a path other than the default VST3 System Folder. If needed, you can then select and enable a VST3 Plug-In Custom Folder. In this case, choose a dedicated folder. Do not select the same location as either the VST3 System folder (C:\Program Files\Common Files\VST3), or your VST2 Plug-In Custom Folder.

Important tips for plug-ins settings

• In the Plug-In Sources tab, do not set multiple folders to the same path.
• VST2 files (.dll) and VST3 files (.vst3) must be installed in separate folders.

Spoiler: Source: Grok KI

Hey, sorry to hear about the frustration with Live 11—super annoying when one DAW plays nice and another doesn't, especially with legit plugins like SSL Native X-Saturator. Since FL Studio 25.2 and Live 12 both detect the VST3 version without issues, this points to a Live 11-specific scanning or path quirk on Windows 11 (which is generally compatible with Live 11, but VST3 handling can be finicky). I've dug into common reports and Ableton's troubleshooting, and here's a step-by-step plan to try. Start from the top and work down; these fix it for most folks in similar spots.

Quick Checks First

1. Confirm the Install Path: SSL Native X-Saturator's VST3 should auto-install to the system folder: C:\Program Files\Common Files\VST3. Open File Explorer, navigate there, and verify you see X-Saturator.vst3 (it might be a folder ending in .vst3). If it's elsewhere (e.g., a custom spot or user folder), that's likely the culprit—reinstall via the SSL installer to force it to the system path.
2. Rescan Plugins (Basic and Deep):
   • In Live 11, go to Preferences > Plug-Ins tab.
   • Ensure Use VST3 Plug-In System Folders is checked (this is key for Windows—don't use a custom VST3 folder if possible, as it confuses Live 11's scanner).
   • If you have a custom VST2 folder set, uncheck Use VST2 Plug-In Custom Folder temporarily (Live 11 sometimes glitches if VST2 and VST3 paths overlap or conflict).
   • Click Rescan (wait for it to finish—can take a bit).
   • If no luck, hold Alt (Option on Mac, but you're on Win) and click Rescan for a "deep" scan. This forces Live to re-validate everything.
   • Restart Live after.
3. Run as Admin and Restart Everything:
   • Close Live, right-click the Ableton Live 11 shortcut > Run as administrator. Scan again.
   • Reboot your PC fully (not just sleep/hibernate). Windows 11 can lock plugin files oddly until a cold restart.
   • Also, quit any background audio apps (e.g., ASIO drivers, other DAWs) before launching Live.

If That Doesn't Work: Deeper Fixes

1. Reset Live's Plugin Cache:
   • In Preferences > Plug-Ins, click Manage Plug-Ins (if available in your build) or just delete the plugin cache file manually: Navigate to %APPDATA%\Ableton\Live 11.x\Preferences (paste into Explorer address bar), find PluginInfo.xml or similar cache files, and rename/delete them (back up first). Relaunch Live—it'll rebuild the list on rescan.
2. Check for Conflicts or Blacklisting:
   • In Preferences > Plug-Ins, look for a "Plug-in Blacklist" or error log—X-Saturator might be flagged from a prior install glitch.
   • Temporarily disable antivirus (e.g., Windows Defender real-time protection) during rescan, as it can block VST3 loading on Win 11.
   • Ensure your SSL license is activated via iLok (even if it's machine-based)—run iLok License Manager and refresh.
3. Reinstall with a Twist:
   • Uninstall X-Saturator completely (via SSL's uninstaller or Add/Remove Programs).
   • Download the latest installer from SSL's site (confirm it's the Dec 2025 version—should be 1.1.x or higher for best Win 11 compat).
   • Install as admin, explicitly choosing the system VST3 path if prompted.
   • Don't launch Live during install. After, deep-rescan as in step 2.
4. Test in a Clean Project:
   • Create a new Live set, add an audio track, and drag X-Saturator from the browser. If it loads but vanishes later, save the set as your default template to lock it in.

Why This Happens (and Why Other DAWs Are Fine)
Live 11's VST3 scanner is pickier than FL or Live 12's— it hates custom folders, partial installs, or even tiny path mismatches. Reports on Ableton forums and Reddit show this exact issue with SSL Native plugins (and others like Softube/Waves) on Win 11, often fixed by sticking to system folders and deep scans. No major bugs reported for X-Saturator specifically, so it's likely setup-related.

If none of this clicks, grab logs from Live (Help > Report a Bug, or check the crash reporter) and ping Ableton support—they're solid for version-specific stuff. Or hop on the Ableton forum/Reddit r/ableton with your exact Live build (Help > About). Let me know how it goes—TIA for the update!

 

hi @PulseWave
Issue fixed
Deep rescan (I never heard about it) detected it fast and nicely

Thanks mate

 

Last edited: Dec 4, 2025 at 12:31 PM

SSL Native should be compatible with any DAW that supports VST, AU, AAX or RTAS plug-ins. This includes most common DAW applications.

If you have compatibility issues with a particular DAW, please follow the DAW developer's guides before contacting SSL:

• Ableton VST/AU plug-in doesn't appear in Live
• Ableton scaling and size issues

Plug-in Compatibility - 24 November 2025
https://support.solidstatelogic.com/hc/en-gb/articles/8979522393245-Plug-in-Compatibility

1. On Windows, make sure Visual C++ 2010 SP1 is installed. This is required to run 64-bit applications that have been developed with Visual C++ 2010 SP1.