Waves plugins not recognized by Sonar

I am getting frustrated! I am having a huge difficulty with Sonar recognizing Waves plugins. It started right after the previous update to Platinum. Upon startup there was a popup that stated that several plugins that I used in the project I was loading into Sonar were not available and may not have been installed properly. These were plugins I have used successfully for some time without a problem and all were from Waves. On the phone to Waves support and we eventually got them back, but only after reinstalling Sonar. The issue recurred several days later. I tried all the probable fixes attempted during the session with Waves to no avail. In the meantime I attempted to contact Cakewalk support. It took 9 days for Daniel A. to respond for which he did apologize, but only offered the usual fixes which I thought I made clear had been tried. Back on the phone to Waves and after some remote poking around he said I guess I would have to try and reinstall Sonar again, which I did. Twice. I have the latest updates for all products concerned. I had already replied to Cakewalk twice and it has now been five days. I have been a happy Cakewalk customer since Pro Audio 6 in 1998, but now not so happy. Any help would be appreciated.
 
Michael (Studio Vheissu)

Sounds like the automatic scanning might be problematic for some reason in your case. Do you keep your Waves license on an iLok or is the machine authorized?
 
You should be able to switch the scanning mode to manual, do a full reset, and then a full scan and be able to use them again.

1. Go to Preferences | VST Settings and set the scan to Manual Scan
2. Turn ON Rescan Failed Plug-ins
3. Turn ON Rescan Existing Plug-in
4. Click Reset
5. Click Scan
6. Wait for the scan to complete
7. Check for Waves plug-ins

If all is good you'll want to turn OFF Rescan Failed Plug-ins and Rescan Existing Plug-in. That way your scan time isn't longer than it has to be the next time you add a new plug-in.
 
Hope that helps,

I had the same issue... Waves Central was the problem in my case, coupled with what I think was a Windows Security update. Update Waves Central and reactivate the licenses. I THINK that's how I fixed it - there was a lot of clicking, downloading and cussing.

Could be that sonar is excluding them. Try rescanning failed plug-ins. I gather you went to the %appdata% and wiped the cache and also the waves central directories.

One other thing check your license cloud and where the licenses are being stored.

Not sure if it is related to your problem, but here's what I ran into with my Waves plugins. On my laptop, I have to disable my Ethernet network connection in order to make LatencyMon happy. The Ethernet port has to be enabled in order to install Waves plugins properly with Waves Central, so after installing Waves, then disabling the Ethernet port and going back to just my WiFi connection, Sonar would not recognize my Waves licences. I had to re-enable the Ethernet, transfer the Waves licences back to their cloud, disable my Ethernet, go back to Waves Central while on WiFi and transfer the licences back to my computer, then rescan plugins in Sonar... now every Waves plugin runs nicely in Sonar. I have to do this process every time I buy a new Waves plugin. I use Sound Forge as well, but I've never tested the situation with it. -Mark.

If you have more than one Waveshell then perhaps. Even though the later versions supercede it might be worth checking.
 
I only install VST3 to my directory (C:\Program Files (x86)\Common Files\VST3)
 
VST 2.4 externally in it's on directory called C:\VST.
 
Another thing only 64-bit VST3 gets installed and Sonar is set to use VST3 where possible. I could be barking up the wrong tree but I hope it give some insight.
 

I would advise against adding all the 32bit paths to 64bit SONAR. You would be better off reducing the number of 32bit plug-ins being scanned. Most of them likely have a 64bit version later in the scan path which should be used in 64bit SONAR. You would be better off, copying the few 32bit plug-ins that have no 64bit option to a separate folder and remove the rest of the 32bit paths from the 64bit scan path.
 
Redundant scan paths should be avoided ALWAYS. This is a bad idea:

Studio Vheissu
C:\Program Files (x86)\Cakewalk\vstplugins
C:\Program Files (x86)\Cakewalk\vstplugins\cakewalk sound center

The scanner will go into "cakewalk sound center" folder because the parent folder is already in the scan path. Having both in the scan path causes the scanner to look in "cakewalk sound center" twice. In the past scanning a plug-in multiple times has been know to cause problems.
 
Are there any 32bit only VST3 plug-ins? If not, this

Studio Vheissu
C:\Program Files (x86)\Common Files\VST3

should not be in the 64bit SONAR scan path.
 

Sound Forge is a 32 bit application so it needs the 32 bit VSTs but as Scook said you shouldn't have all those redundant scan paths in Sonar. For all of Waves you only need the 64 bit VST 3 versions scanned. Obviously you'll have some other 64 VST2 plugins but with some good housekeeping they can all be placed in one folder.

Before you do all that, try a clean rescan. Go to Preferences -> File -> VST Settings, click the "Reset" button followed by the "Scan" button. It may not solve your problem, but it's an easy step.
 
Do you have this issue when you attempt to insert a plugin into a new project, or only when you're opening previous projects that have Waves plugins in them?
 
FWIW, Waves plugins are working fine here. I have had them fail on three previous occasions (which is why I don't buy Waves products anymore), but each time it was a Waves licensing issue, not a SONAR problem.

Well after a frustrating week or so, it seems like some sort of miracle occurred and available instrument and FX plugins are playing nice with Sonar Platinum. Like Mike V said above a couple posts a little housekeeping can't hurt and I managed to get my list of vst paths down to three:
C:\Program Files (x86)\vstplugins
C:\Program Files\Common Files\VST3
C:\Program Files\vstplugins
 
For those of you with Native Instrument software, they have a neat little program used to put all of their 32 and 64 bit vsts in any folder you want. So with all the flotsam and jetsam left behind by the Department of Redundancy Department (old Firesign Theater fans may remember this little joke), it seems that every thing is running smoothly again. Waves AAS, NI, Izotope and the rest are all making nice-nice with Cakewalk. A huge thanks to those who took the time to try to help.

I just bought the Puigchild compressor and after I installed it (new waves installer as well) it broke my Grand Rhapsody and some other waves plugins.  Also pooched my Slate stuff on Ilok2 which I don't have my waves on at all.  Updated the Ilok2 stuff but there's still a Slate problem.  I did the reset and rescan with Sonar Platinum and it fixed most of the waves stuff, now I have duplicate Grand Rhapsody vstis so I'll have to sort that out manually I guess.