What would cause X1...

...to scan VSTs every time it opens?
 
This is a new problem that has occurred since I installed some Waves plug-ins.
 
Sonor stalls during the scan, so I have to open the task manager and kill the scan, then Sonar opens.
 
The odd thing is, the new plugs seem to work just fine.
 
Any thoughts?

Go into your plug in manager,
under scan vst options there is a box that says scan vst's on start up.
Un check that.
Just remember that when you add a new vst that you will need to manually run the scan .

Mike

not sure why you would have the scan stalling
 
But the answer to you question is -  Preferences>VST settings>then uncheck "Scan for VST Plug-ins On Startup"

I believe there is also a way to do this from Options/Audio/Advanced but not sure because I'm on a different PC right now.

Mike

The stall could be because a dialog window has opened and is waiting for input but is covered by another window.

You can turn off scan on start in the preferences.

Wave


not sure why you would have the scan stalling
 
But the answer to you question is -  Preferences>VST settings>then uncheck "Scan for VST Plug-ins On Startup"

Yeah, that's the other way.
I'm still not used to the X1 lingo yet.


Thanks Wave.


Mike

Gary McCoy


...to scan VSTs every time it opens?
 
This is a new problem that has occurred since I installed some Waves plug-ins.
 
Sonor stalls during the scan, so I have to open the task manager and kill the scan, then Sonar opens.
 
The odd thing is, the new plugs seem to work just fine.
 
Any thoughts?

Are you using X1d?

The scan routine has been improved in the D update and scan on startup is now recommended.

Also IIRC the Waves plug-ins are accessed via a universal wrapper .dll which in turn accesses the individual plugs, I think if you have a large number of Waves plugs the specific Waves scan process, which has nothing to do with Sonar's scan routine, could take some time.  I'm pretty sure that's how the Waves setup works.

If Sonar's scan process is locking on the waves.dll scan contact Waves support.

Scan is definitely reccomended on start up,however on my much less powered laptop [i7 2630qm CPU] the scan takes much longer than my listed desktop,which compared to the Laptop-30+seconds,sometimes longer,only takes 5 seconds at MOST.

I don't have waves, but my DC V.I.P Bundle seems to be scanned first and it can take a while,but again only on the i7 Laptop

Both machines are set up identically,same plugs,everything.

Bob

Bob, does it take that long every time you launch Sonar, even if you don't have new plugins installed? If it does, you must have "Re-Scan Existing Plug-ins" checked. That should be unchecked. It really should only take about a second if you don't have any new plugs installed, even on my old computer.

StepD has got it nailed.

Setting it up this way means that when you start Sonar, it will only do a full scan when a new plug has been added.

This is exactly what you want.

Also make sure that the setting to Rescan Existing Plugins is NOT checked.

Cool,thanks I had no idea[surprise surprise], THANK YOU experienced ones!

Bob

This is odd but my desktop with "scan on at start up" takes less than a second,any harm leaving it ON?

Iv'e done as advised with the laptop,and it usually works,but occaisionally,I'll get the "This plugin/synth not found",that laptop[Dell XPS L502x i7 2630qm] is always odd[which is why I bought the desktop instead of an RME FF UC!!]

Thank's  
Bob

Bob according to Noel they drastically improved the scanning on start up so yes there is no harm. After learning that I set mine for scan on start and it works perfectly.

Thanks John

Bob