Hi guys, anyone else having issues with the Automatic Plug-In Scan popping up all the time while working with lots of VSTs and some older DXIs in a project? I could just switch it off, but that's not really ideal.
 
Ludwig

The only time it should pop up is if something is updating the folder in which the plugins live. That is the trigger for the scan. Are you by any chance copying files to that folder or doing a background install?
Or perhaps you an AV program or something writing to that folder. One of the plugins in the project might also be writing there (illegally) triggering the scan!
Also when you say the scanner is popping up, are you seeing toast notifications - if so which plugins are being scanned if at all?

Hi Noel,
 
thanks for the reply. Nothing unusual running in the background, but an incorrect install is very possible.. But, with 934 plugins, where does one start looking?!?!
 
How about a "Scan in the background only ONCE till I tell you to scan again" option? :O)
 
Thanks for the new build - very nice work!

LJB
But, with 934 plugins, where does one start looking?!?!

Start with a project which exhibits the behavior, run it safe mode and try to isolate the the plug-in(s) which cause the problem. I would pick a project which does not use all 934 plug-ins. you may get lucky and find that it is one or two plug-ins used in most if not all of your projects.

LJB
 
How about a "Scan in the background only ONCE till I tell you to scan again" option? :O)
 

Hi
Did you try setting it to "Scan On Startup" ... that should only be done once.
 
However, I never really got the point why I should have it set to "automatic background scan" at all. I decide when I update plugins. I follow each update by a scan. Afterwards I don't want to have any changes to the system, especially not in the background while I'm working with the DAW ... but that's just me ...
 
 

LJB
Hi Noel,
 
thanks for the reply. Nothing unusual running in the background, but an incorrect install is very possible.. But, with 934 plugins, where does one start looking?!?!
 

 
Please list what folders are listed in the VST scan path. You shouldn't include folders that are modified or it will trigger a scan. Plugins should never write data to their executable folders since that violates UAC.
If it is indeed a plugin writing to the scan folder you should be able to isolate it to one that is being used by the project. i.e. plugins can't do damage unless they are loaded :) 
If it is NOT a plugin causing it then you should see the behavior by simply opening SONAR and letting it sit idle with an empty project with no plugins. In that case it would be something else on your system modifying the scan folders somehow.
 
FWIW I have never seen this behavior.