Hi Sonar friends,
 
Lately I have noticed that my Vst Scan is scanning ceaselessly! I think it happened after installing my new Electrax vsti, but I am not sure.
 
Any help?
 
Thank you

I had this happen while scanning a Vsti and it was due to the sample path not being set correctly. Fortunately, I was able to open the stand alone version, set the sample path, and all was well.
 
HTH
 
Kind regards,
Rick

Ok, but how did you find out which vsti was the responsible? I donnot think Electra X has any sample path. 
Thank you

Carlo Celuque
Ok, but how did you find out which vsti was the responsible?

I setup a manual scan, in preferences, and then watched the scan window to see which Vst was causing the issue. It continued to scan the offending Vst so it was very visible where the problem was.
 

The vstscanner can generate a log. To create a log, go to Preferences > File > VST Settings and hold the SHIFT key while clicking the Scan or Reset buttons. The log is written to %appdata%\Cakewalk\Logs

Ok, nothing wrong happened here within a new blank project. Maybe on the problematic project it may shows something.
 
I think the issue is with my Helix Vsti synth, since the that project had an 32 bits version at first which I changed for a new 64bits version. Every time I start the project it asks me to point to nearest Helix  vsti option and I have to redirect it to the new 64bits version. Why Sonar doesn`t memorize my decision and keep ask me everytime for this vsti? LOL
 
Thank you

You can exclude plug-ins from being scanned in the plug-in manager.
 
Also, it doesn't sound like the following is your issue, I mention it for others reading this thread because they've experienced the same problem: sometimes a plug-in will create a "splash" screen (like an update notice, authorization, etc.) that's behind SONAR so you don't see it. Check the taskbar icons to see if there's something unusual.

When the VST scanner hangs, it's always traceable to a specific plugin. What the scanner actually does is invoke a built-in function within each plugin that does whatever's needed to initialize that plugin. Only the plugin's author knows exactly what that entails.
 
The scanner itself does not know what actions are being taken within the plugin; all it can do is wait for a success or fail return code when the init function completes. If the function never returns, the scanner hangs. Of course, a well-written init function would not hang if something went wrong, but not all third-party plugins are well-written.
 
I have sometimes had to resort to a process monitor to identify where a VST init has gone wrong, but that's not a simple diagnostic procedure. Your best bet is to enable the scanner log as suggested by Steve, identify which DLL hung, and then ask yourself how important that product is to you. 

Bad actors do not always hang themselves. I have seen the scanner hang on known good plug-ins. In that case, I can usually get past the problem by moving the plug-in which hangs out of the scan path, rerun the scan, add the plug-in back and let the automatic background scan pick up the added plug-in.