• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

VSTs scanning taking 1 minute each for 300 minutes total?

NoTimeForThoughts

New member
Weirdest thing I have seen in a while when I tried to get studio one to simply open up (and I had forgotten to turn off the plugin scanner last time)
All my plugins have scanned before, and so they should go past in about 1 second.

Instead it took the last almost an hour to scan. It's going thru each one as if it were activating a plugin license on every one. Even the free ones.

WTF?

I would say it's been about an hour and it's thru 210 of 300. I did a comlete restart of the computer because the first time I just hit skip because it was thru 50 after 5 or 10 minutes. So basically an hour, at a minute each for many of the plugins, then it will skip 3 or 4.
So the cmputer basically crashed after the first time don't know why, looked in event viewer and no red flags except the same one that happens every day with AMD Graphics driver. No explanation as to why Studio One suddenlly won't scan the plugins normally at all. Even scanned them just last week in under 20 seconds no problem. Nothing new as far as I know on the computer, it just won't scan these plugins.

Now it's thru 246 'marimbaphonic'. All these plugins were my short list of plugins that never gave me any trouble before. Pretty sure Studio One 6 version that is running this plugin scanner is completely wrong minded.
 
Last edited:
Weirdest thing I have seen in a while when I tried to get studio one to simply open up (and I had forgotten to turn off the plugin scanner last time)
All my plugins have scanned before, and so they should go past in about 1 second.

Instead it took the last almost an hour to scan. It's going thru each one as if it were activating a plugin license on every one. Even the free ones.

WTF?

I would say it's been about an hour and it's thru 210 of 300. I did a comlete restart of the computer because the first time I just hit skip because it was thru 50 after 5 or 10 minutes. So basically an hour, at a minute each for many of the plugins, then it will skip 3 or 4.
So the cmputer basically crashed after the first time don't know why, looked in event viewer and no red flags except the same one that happens every day with AMD Graphics driver. No explanation as to why Studio One suddenlly won't scan the plugins normally at all. Even scanned them just last week in under 20 seconds no problem. Nothing new as far as I know on the computer, it just won't scan these plugins.

Now it's thru 246 'marimbaphonic'. All these plugins were my short list of plugins that never gave me any trouble before. Pretty sure Studio One 6 version that is running this plugin scanner is completely wrong minded.
now it's thru 273...very very very slow going. I was just looking thru the drive with my VSTs on it, and I can cruise around there looking with no problems at all. It's not a shared drive, so it's not a network thing with the VST folders. It's super fast to look thru with Windows Explorer as you would expect. But just scanning 300 plugins has taken over 20 minutes!
 
Do you always get the 5 warnings against those Vsts ?
 
iZotope plugins (like RX) are part of NI Komplete now. NI plugins take more time to "scan" than most. I think that they call NI's server in France. I have a bunch of Black Rooster plugins and have ZERO problems scanning them. I'm wondering if you might have a problem with your anti-virus/anti-malware/Defender app(s) where Internet access is being blocked for certain URLs.
 
iZotope plugins (like RX) are part of NI Komplete now. NI plugins take more time to "scan" than most. I think that they call NI's server in France.
Apart from most likely being nonsense, I can't see what this possibly could have to do with every plugin scanning for minutes.

There's clearly something wrong with the OP's Studio One installation, or, (more likely) with his computer.
 
For windows, if you use Windows Defender and not some third party virus scanner, you can use these reg files to turn off (and on) Realtime Scanning. That reduces the duration of the first scan after (re-) booting significantly.
Change .pdf to .zip
 

Attachments

I don't konw it was really unusual I could have sworn I never'd a saw Studio One do anything of the sort, on any windows ever. And I never change windows defender settings, and I also scanned these same plugins a couple of times in the last month and never had any issues with any of them. I was wondering why this would happen but I don't think there is anyone who knows. I should try and start it doing the same again and look at recording the process monitor. Only way to identify problems is the Process Monitor.
 
Windows Defender slowing down first S1 Plugin scan is a thing. Happens on every Win10 and Win11 I ever tried.
 
iZotope plugins (like RX) are part of NI Komplete now. NI plugins take more time to "scan" than most. I think that they call NI's server in France.

I have 14 iZotope plugs installed (in my stash of 406 currently) and startup takes 9 secs from double click on the desktop to the S1 Start Page.

There is no "phoning home" going on here. Something else major is holding up the parade for the OP.

VP

PS: I do have Windows Defender majorly tamed and it is set to ignore the entire S1 structure and ALL plugins that I use.
 
I have 14 iZotope plugs installed (in my stash of 406 currently) and startup takes 9 secs from double click on the desktop to the S1 Start Page.

There is no "phoning home" going on here. Something else major is holding up the parade for the OP.

VP

PS: I do have Windows Defender majorly tamed and it is set to ignore the entire S1 structure and ALL plugins that I use.
No, those all went by very quickly. You can even see from their time stamps they went flitting by. It was just these many other plugins that seemed to instantiate which is new. I have also used the program previously on the computer here and this is not the first time to scan things all into here.

I am sort of imagining it instantiating sample libraries for VSTi or something. Which is a thing because I did add many VSTi in here. However I had scanned them all previously. This made no sense because I have never seen Studio One instantiate plugins and load libraries during the scan.
 
I'm assuming this is a windows machine?

From what's been reported so far it looks like a one off and could have been caused by any number of things from thermal throttling to processor scheduling or a boot process missing a beat and failing to load some windows index service, et al.
It could be something like a failing SSD. That could be tested by running chkdsk or some other diagnostic Disk checking app. If it were me I might do that just to be sure that it's not a failing disc. Nothing worse than a load of data getting fried.

Out of curiosity did the fans on the computer spin up or any other change to the normal boot up process take place?

Anyway IMHO.
If it was a regular thing that would be of concern. The OP has said he had never seen it before and most probably will not see it again. Put it down to a gremlin in the machine. If it happens again and becomes a regular issue it may be time to get your wallet out.
On the other hand if this is a mission critical machine for live performance it might be time to get it looked into in detail.

Regards
 
Windows Defender was the culprit here for me when this used to happen.

Virus & Threat Protection > Manage Settings > Turn off Realtime Protection would normally solve it

If it's not Windows Defender it 100% sounds like an antivirus or other system app actively scanning each file before S1 can handle it.
 
  • Like
Reactions: AAV
Back
Top