I have been busy for 2 days now to find the problem for the vstscan in Sonar X3. I also contacted Cake support about the problem and was told to do a clean install. Everything out the register and all the other places which I have never been before and then installed Sonar X3 again.
I thought that all my problems were over , but that wasnt the case. After starting up X3 a couple of times my VST3 plugins were gone from the plugin Manager. This was also the problem the first time. I wasnt about to do another clean install so I started to check to see why this was happening.
I went into preferences/vst settings and tried a reset and then another scan. Still no VST3 plugins. I checked my computer as to where the vst folders were and found no problem with the vst paths.
I finally decided to delete all the vst paths in preferences except for the VST3 path. I did another reset and scanned again.
To my surprise the scan showed the VST3 plugins again. I didnt change the path names in the plugin manager and thought that they were connected with the preference settings, but now I only had my VST3 plugins and the internal plugins. 
I added the other vst plugin paths one by one in preferences and finally got the vstscan to find all my plugins.
As you can imagine I do not want to have to do this every time the plugins are not scanned right.
Can the bakers look into this to see if there is something wrong with the vst scan and the bigger question is if anyone has had the same problems with the scanning paths.
Thank You
 
 
Danny

I'm having an issue with scan not finding my Alchemy data bank. I have to manually direct it to where the data bank is installed - program data file, despite having the path listed.
 
Just an update...Camel Tech finally got back and gave me a process for sorting this particular issue out...all good now.

My problem is that it seems that the vstscan doesnt see the whole path when scanning. I have 4 paths in my drive to scan the plugins from.
 
They are: C:\program files\Vstplugins
              C:\program files\Steinberg\vstplugins
              C:\program files\cakewalk\vstfiles
              C:\program files\common files\vst3
 
I cant figure what the problem is that Sonar has problems scanning these directory's. How does this scan actually work in combination with the plugin manager?
 

Is there anyone at cakewalk that has an idea as to how this happens?
 

cowboydan
My problem is that it seems that the vstscan doesnt see the whole path when scanning. I have 4 paths in my drive to scan the plugins from.
 
They are: C:/program files/Vstplugins
              C:/program files/Steinberg/vstplugins
              C:/program files/cakewalk/vstfiles
              C:/program files/common files/vst3
 
I cant figure what the problem is that Sonar has problems scanning these directory's. How does this scan actually work in combination with the plugin manager?
 

I am not sure it matters but did you try using backslashes "\" instead of slashes "/" in windows path names. I have never used slashes in VST path names in SONAR.

2 things. There is no need to use Plugin manager at all to setup vst scan or to perform one. In fact there is a bug where potentially the 32 bit plugin manager was being launched (now fixed for X3C). Stick to setting up everything inside SONAR's VST preferences.
Also how did you get forward slashes in the paths?  Windows doesn't support that. To enter scan paths use the dialog provided in vst preferences.

Ooh, there's an X3c?

John T
Ooh, there's an X3c?

I believe it has been mentioned by CW staff in a few posts. It has not been released.

The forward slashes were my mistake. When you add a folder to scan a popup menu with your drive comes up and with mouse clicks you keep going until you get the folder you need and then it goes in the vstscan page

Noel Borthwick [Cakewalk]
2 things. There is no need to use Plugin manager at all to setup vst scan or to perform one. In fact there is a bug where potentially the 32 bit plugin manager was being launched (now fixed for X3C). Stick to setting up everything inside SONAR's VST preferences.
Also how did you get forward slashes in the paths?  Windows doesn't support that. To enter scan paths use the dialog provided in vst preferences.

Hi Noel
Would the bug mean that all of a sudden the scanner doesnt scan the paths that are in the preferences   window ? That is what happens. when I scanned the vst plugins All at once I didnt get the vst3 folder or plugins. That was the whole story.
 
Danny