Just bought the Waves Silver bundle on special offer from Cakewalk. Afraid it's not usable on my previously stable system: Windows 7 64-bit, 8 gig RAM, UA-101 interface.
 
Using any of the plugins brings down X2 (edit: or X1) very quickly:
 
1. Create a new project
2. Insert an audio track
3. Add any of the Waves plug-ins to the FX bin
4. Close the plug-in's pop-up window.
5. X2 (edit: or X1) crashes. 
  
EDIT: I was able to try a couple of the effects out in a pre-existing project, but it too would crash if I tried to delete the effect out of the FX bin.
 
I reset and rescanned my VSTs and still no luck.
 
Anyone else having this issue?
 

Hi jmedwid,
 
I had a similar issue when I first started using waves. I spent a month with Waves tech support with no luck, I spent 20 minutes with Cakewalks tech support and it was solved Thanks to Dean Capper.
 
My issue was caused by a mix of MS Visual C++ redistributables on my system. Many third-party applications will install these so sometimes the libraries can get skewed as multiple versions exist on the same computer. You could look in the Control Panel/Programs and Features panel/ to see if you have multiple versions of the same MS Visual C++ redistributable. There will be several instances from different years and possibly an x86 and x64 of each but the important thing is that the version number for each years release is the same.
 
The other possible problem could be due to any automap software such as that which comes with some of the Novation stuff.
 
In either case a quick call to Cakewalks support is probably in order. I would have never known what to do without their help. They know how to interpret the dump files Sonar sends to narrow down the cause.
 
Hope this helps a little bit.
 
Kind regards,
Rick

Thanks a lot, Rick.  I'm betting it is the C++ distributable. I have an email into Cakewalk support and will call them on Monday.

Cheers, 
Jason

please let us know what they say. i have a similar situation, where i get crashes with C++ errors when steven slate drums 4 is loaded. haven't had a chance to track it down...

There is something up with the compatibility between some Waves stuff and Sonar, shown by the problem I posted about recently with the SuperTap delay plug and the screwy behavior of the GUI when the track the plugin is on has a VSTi as an input. I contacted Waves and they were able to reproduce the behavior and told me they were looking at whether it was an issue with their code or with Cake's. 

It's not just the SuperTap plug that has problems, I've found that adjusting parameters on their Q-series EQ plugs is a little awkward as well. When you click a parameter and drag up or down to change the value, sometimes it will go in the reverse direction and sometimes it will get "stuck" and you find yourself having to move the mouse a freakin' mile just to adjust by a couple of dB's. 

Another issue is that the tempo based plugs (delays, H-comp compressor etc) don't register as tempo based plugs automatically with Sonar. You have to open the plugin manager on its own (without Sonar running) and register it manually. I really hope Waves get to the bottom of all this stuff when looking into the problem I reported, because they really are great plugs. 

I must admit I found it a bit odd when Cakewalk announced the deal on the Waves plugins given the problems you and others have mentioned.

The price may be a steal, but it's a lot of money for something that may not work. And Cakewalk is obviously aware of the problems.
I don't get it.

And I can't find anywhere that they're 64-bit, so that may be an additional problem.

Paul,

You get both the 32- and 64- bit versions of the VSTs when installing. You have to install both (apparently) so I directed the 32-bit plugs to be put in a folder on my desktop (i.e. well away from the rest of my VSTs). My system's definitely using the 64-bit versions.

Jason 

It's worth uninstalling the 32-bit version if you're only going to use the 64-bit (or vice-versa). There are a lot of plugs in a Waves bundle and you might get a shock when you look at your VST list when inserting a plug. You don't just get one Q compressor for example, you get separate ones for 1, 2, 3, 4, 6, 8 and 10 bands (mono and stereo versions of each). If you've got both 32 and 64 bit versions then it's a little overwhelming to say the least. I think to delete the 32 bit versions you just have to delete the 32 bit waves shell (wherever you've installed that - although it's worth checking to make sure). 

I installed the Gold bundle a while ago and it necessitated me finally biting the bullet and making a plugin layout divided into categories (EQ, dynamics, delay, distortion, modulation, analysis, amp sim, etc etc). It takes a bit of time but it's well worth it and you appreciate it every time you look for a plug 

I was able to resolve my issue.

I uninstalled the Microsoft C++ Redistributable libraries and downloaded them from Microsoft (the 2005 through 2012 versions).

I then updated the graphics driver on my Lenovo T500.

Doing both of these things were necessary to resolve the issue.


Jason

Per Waves Support, the WaveShell installs both in the 32-Bit and 64-Bit Program Files Folders. When you scan for your plug-ins, DO NOT let the 64-Bit Sonar scan the 32-Bit Program Files (x86) folder and find that version of Waveshell. That is a typical cause of the crashes.