For some reason, for the past week or so, Studio One has not been able to scan a single new plugin. I have no idea what could be happening - already reinstalled.

My copy of Studio One is legit - my plugins are not. So far, this has not caused problems, so I doubt it's the reason behind it.

 

Last edited: Dec 22, 2024 at 5:06 AM

Hmm.... .....Pc or Mac ? What Studio One version ? . Try reboot ?. Installed the right plugin-extenion (AU,Vst2 ,Vst3 ) ? Paths are correct?

Also found this, hope it helps:

and/or this:

https://obedia.freshdesk.com/suppor...-presonus-studio-one-s-preferences-on-windows

 

Windows 10, S1 7 Pro. Reboot does nothing. Yup, right extensions on right folders. It detects them, but fails to scan (gives a warning on startup).

Let's try the "Remove Plugin Settings"... It's going to take a while...

 

Last edited: Dec 22, 2024 at 8:20 PM

It's now failing to scan EVERY plugin, and it's doing it very slowly...

 

S1 started to behave like this with previous 6 version.
I updated to v7.0.1.103159 (sister site) and it work wonder.

So i advice you to uninstall S1 with BCU uninstaller, do a "deep clean" when asked.
https://www.bcuninstaller.com/
And resinstall last V7.

It worked wonder for me.
Tell us the EXACT version number.

 

Still not being able to scan anything.

 

Have you recently added any new and possibly sketchy plugins? Sometimes if I install an incompatible plugin, the first plugin crashes; and then my DAW (Logic) just shows it re-scanning all the installed plugins, way too quickly to be possible. Once the problem plugin is removed, everything works correctly again. I would check this manually moving plugins to "hide them" and then start manually putting them back. I wouldn't just assume your plugins are not causing your problem.

You probably remember the little timebomb in v6.x, and also the ip addresses people were blocking in those threads? You could look into those as things to check in your hosts file or firewall rules. You would probably already see more people commenting about an actual timebomb.
Make sure it has permissions set correctly to scan the drive/folder locations where your plugins live.

What is the "warning on startup"?

 

Last edited: Dec 23, 2024 at 2:31 AM

I can try that once I am back to my work PC.
"Warning on startup" is stuff like "plugin X failed to scan" or "plugin X was blocked".

 

If it is rejecting some plugins like this, you can lean on the side of s1 is scanning those locations, at least. You most likely have the correct permissions set on those locations. Did you already try cleaning up with Revo Uninstaller and then reinstalling S1? If not, it might be the more time efficient thing to do; as already suggested.

 

By the way, what do you mean by "timebomb"? It's the first time I hear about this.

 

Back in about April, PC users had their perfectly working v6.5 installations start showing up as blocked, de-authorized, etc.

A time bomb is usually a time or action-based de-authorization of an installed program or plugin. It generally does not need the computer to be online for it to happen and is similar result to a demo expiring.

 

it could be as well defender or anti virus not allowing it.. could be as well an indicator of disk drive has issue,, few weeks ago i had this issue in on mac.. but once i remove plugin setting.. it start fresh scan, take a while to complete.

 

I have solved this issue by always installing VST3 - infact I only install VST3. My experience is that Studio One always scan the VST3 folder correctly at start up so new plugins will be added.

 

Check with CrystalDisk if the health of your drives are okay. Might be soon enough to back up if that's the first sign. If it's all good, I would try moving all plugins to a different location and just try placing one there (that you know it worked before) to see if it scans. If it does, try placing the plugins back in batches until it goes wrong again, then you can narrow which plugin is messing it for everyone.