Jump to content
Jun Kwan

VST scan options are not working

Recommended Posts

1 hour ago, Nigel Mackay said:

For what it is worth my vstscan.exe is also version 6.0.3.0.  Dated 03/06/2020 15:00. And it works. Details are identical to Milton's.

 

2 minutes ago, HIBI said:

Same here and having no problem. (FYI: Running Japanese Windows 10)

Ok, maybe this isn't the issue then... I notice that I get the same version number too on my Windows 7 boot.

@Milton Sica - could this be your anti-virus software ?
 

Share this post


Link to post
Share on other sites

Ok, it looks like the problem @Milton Sica had was that his VST scan path included C:\Program Files\Cakewalk  - so it was trying to scan Cakewalk's program DLL's while the program was using them.

It's really important to:

1. Only include directories that hold only VST DLL's in your scan path
Unfortunately there's no way to tell if a DLL file is a VST2 DLL or not, except by Cakewalk loading it and attempting to bind to the VST2 methods.

DLL's that are not VST's do a variety of things when loaded: some expect other DLL's to be in memory at the time, or applications to be running and will crash if they're not there. There's absolutely nothing Cakewalk can do about this.

That is why it's important to only provide paths containing only VST DLL's.

2. Don't include a directory twice in your scan path 
Including a directory more than once could result in duplicate entries of a plugin.

3. Always use the Scan within Preferences/VST Settings and have the Sandbox Scan checked.  Do not use the Plugin Manager for scanning.
The plugin manager is no longer recommended for scanning, as it can only scan in a single thread. This causes the application to lock up should it find a plugin it can't scan. Its only purpose now is to facilitate enabling/disabling plugins and to configure plugin layouts.

The Sandbox Scan uses a separate thread for scanning each plugin, which means if one fails, the others will continue to scan.

  • Great Idea 1

Share this post


Link to post
Share on other sites
26 minutes ago, msmcleod said:

2. Don't include a directory twice in your scan path 
Including a directory more than once could result in duplicate entries of a plugin.

Couldn't duplicates be filtered out when writing the scan path to the registry?

Also remove children probably a bigger cause of duplicated scans.

26 minutes ago, msmcleod said:

3. Always use the Scan within Preferences/VST Settings and have the Sandbox Scan checked.  Do not use the Plugin Manager for scanning.
The plugin manager is no longer recommended for scanning, as it can only scan in a single thread. This causes the application to lock up should it find a plugin it can't scan. Its only purpose now is to facilitate enabling/disabling plugins and to configure plugin layouts.

I believe the only reason the scanner is still available in the PIM is for backward compatibility.

Maybe it is time to disabled the scanner when running the PIM from CbB.

Share this post


Link to post
Share on other sites

Some clarifications. 
There is nothing wrong with your VST scanner version. 6.0.3.0 is the correct one.
If you have the scan button grayed out its likely because something (antivirus, registry corruption, or personalization failing) has messed up the app install and the app doesnt have the path to the VST scanner anymore.

Look in HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Cakewalk VST X64 for a value of VSTScanPath. It should point to C:\Program Files\Cakewalk\Shared Utilities\VstScan.exe

If not, you can redo the personalization for Cakewalk. To do that, launch Cakewalk while holding down the CTRL key. This will show the personalization dialog. Click OK and let it finish. After that VST scan should be accessible again.

  • Like 1

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...