• SONAR
  • [RESOLVED] The Neverending VST Scan
2013/10/02 10:40:52
MIDIMINDS
Can anyone duplicate this "bug"? -
 
Even after several minutes (10 or more), if I try to select Options or Scan VST Plug-ins in the Cakewalk Plug-in Manager, an error message pops up stating that a VST Scan is already running.  Makes adding/changing plugs a total PAIN!  
 
This "background process" is also unaffected by trying to end the process in Task Manager.   FRUSTRATING!!!
 
What's up, Cake?
JG
2013/10/02 10:57:24
Dan Gonzalez [Cakewalk]
MIDIMINDS
Can anyone duplicate this "bug"? -
 
Even after several minutes (10 or more), if I try to select Options or Scan VST Plug-ins in the Cakewalk Plug-in Manager, an error message pops up stating that a VST Scan is already running.  Makes adding/changing plugs a total PAIN!  
 
This "background process" is also unaffected by trying to end the process in Task Manager.   FRUSTRATING!!!
 
What's up, Cake?
JG




It sounds like your background VST scanner isn't finishing it's actual background scan. Do you get a SONAR Notification stating how many plugins were found when you open up SONAR X3?
 
I have been in and out of the Cakewalk Plugin Manager multiple times and haven't received this message.

Also, how many plugins do you have?
2013/10/02 11:23:54
smallstonefan
After all the cajoling on another thread, I picked up X3 Producer and I'm having the same problem. It says it finished and gives a count (something close to 600) but then starts back up again. I let it run overnight - I'll go home at lunch and see if it finshed or ground my hard drive to a nub. :)
2013/10/02 11:37:52
MIDIMINDS
It does give notification.  Approx. 535 plugs (mostly Waves).  However, like James stated, it seems to re-start itself and I can't break the cycle. 
 
BTW - This problem started AFTER I installed the XLN Addictive Drums.  Connection, maybe?
 
Thanks for checking, Dan!
JG
2013/10/02 11:45:57
rloseven
I had a problem like this also.  Don't know if its the same problem you're having, but to solve mine, I went into Preferences/ VST settings and unchecked Rescan Existing Plugins.  That solved it for me, but I had checked that options earlier trying to solve another problem.  Hope this helps.
 
Ron
 
2013/10/02 11:50:42
djwayne
I found that the automatic vst scan when opening X3 was a bit much so I went into "preferences" and changed the vst setting to "manual."  No more vst scan on opening !!
2013/10/02 11:51:44
Dan Gonzalez [Cakewalk]
Hrmm, I'm going to field this post to some of the other guys on the team and see if I can come to something conclusive. 
 
MIDIMINDS
BTW - This problem started AFTER I installed the XLN Addictive Drums.  Connection, maybe?
 


I would be more than willingly to bet that there is no connection to XLN Audio other than it being a plugin within SONAR X3 Producer. It may be related to the number of plugins that are present.  
 
Is it safe to say that everyone in this post has 400+plugins? Don't be shy to tell me your number. :)
 
 
2013/10/02 11:57:33
backwoods
I think the OP is onto something here. Since installing AD the toast notification has been very slow to tell me how many plugs on my system. Before AD it was very quick. I don't know if it is restarting as I just shut the toast thing now. I have more than 400 also.
 
edit: actually I don't know. It is only very slow for the first scan upon boot up. may just be number of plugins.
2013/10/02 12:30:49
Noel Borthwick [Cakewalk]
There is absolutely no need to go into plugin manager and manually launch the scan if you have automatic background scan on. That workflow is no longer needed in X3. As long as you have the VST scan paths set up to point to the right scan folders, SONAR will automatically detect when new plugins are added and scan them in the background. In fact if you launch it from plugin manager while an automatic scan is already running from X3 that might explain the multiple launches. 
 
Also its a pretty rare case that you need rescan existing plugins enabled. Why are you leaving that on permanently?
Doing that will make the scan run really slow since it does *every* plugin each time the scan is launched. If you have > 500 plugins of course that will take time since its loading every one of them.
 
Now regarding the automatic background scan, the only time that runs is once on startup and then subsequently *only* if something changes externally to the vst scan path folders. Is it possible that something you have is adding or updating files within those folders? If so that will retrigger the background scan. From the symptoms described it looks like that's whats happening.
 
In general the default values in the VST settings should handle 99% of the use cases so you should only change them if you need to. If you don't wish the automatic background scanning set the scan option to "Scan On Startup". Then SONAR will only trigger the scan once when SONAR is launched (it will still be done in the background)
2013/10/02 14:05:34
timp410
I was having the same issue. I decided to change my scan settings to manual because it was happening just about everytime a launched Sonar. Sometimes it would occur when I closed one project and open another exiting project.
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account