mauryw
"there are some ways in which Waves does not play well with Sonar. But these are generally related to the functionality of the plugs (especially their GUI's) within the DAW."
 
When I add a Waves Plugin the GUI usually appears blank.  When I close SONAR and reopen, the full GUI appears as it should.  Still, even with X-Ray disabled, a new addition appears blank.  No crashes, however.  What is your work around for the Waves GUI interface appearing?

I don't have this problem with the GUI's, mine are related to certain Waves GUI controls being unresponsive and/or jumpy. The Super Taps delays are the worst. I actually contacted Waves and they were able to reproduce the problem and said that there does indeed appear to be issues with some Waves plugs and Sonar, and that they were going to contact Sonar to try to ascertain whose end the problem was on. 

I have Waves plug-ins that have jumpy controls, as well. Mainly when I'm trying to maximize or minimize, a slider, like the Compression control on a Waves CLA Drum Signature plug-in, the control requires multiple movement actions to finally get it to be set to the lowest or highest setting. This issue is only when using Sonar (X1d/X2a 32 or 64-Bit). Wavelab 7 doesn't have this issue. However, I've just learned to live with it. Maybe I shouldn't.
 
Another issue is that Sonar tends to hold hostage the exact Waves version. So, if Waves decides to upgrade the version from, for example, 9.1 to 9.2, will fail in Sonar.
 
I sincerely wish Waves would dump the WaveShell approach and go back to single dll's.

I use waves plugins all the time and they work just fine.
The only bug I have with waves plugins is when I place then in between 2 uad plugins.
good luck.
joni

Yes, I had the same errors on Waves Silver bundle that I just purchased. I worked with both Cakewalk and Waves. Neither could get me up and running on it. They had me do a whole lot of things, even to the point of reinstalling my windows 7 in my I7 PC. everything was a bust. I have countless hours in this and neither seems to take responsibility that it could be their own issues. I googled the error and there are many users with that error. It does not seem to be on anyones priority list to pay attention to this as far as I could tell with the 6 or 7 people that I worked with for weeks. The blame was on my side. Oh Well, as long as it works on 95% of the PCs it's not a bug right? NOT!

mauryw
"there are some ways in which Waves does not play well with Sonar. But these are generally related to the functionality of the plugs (especially their GUI's) within the DAW."
 
When I add a Waves Plugin the GUI usually appears blank.  When I close SONAR and reopen, the full GUI appears as it should.  Still, even with X-Ray disabled, a new addition appears blank.  No crashes, however.  What is your work around for the Waves GUI interface appearing?

When this happens just close the Waves GUI then reopen it from the FX Bin again.
No need to close Sonar. Sometimes every so often the GUI just doesn't respond but I found that a close and reopen brings it back.
I've never had to delete and reinsert the plug or close Sonar, just the blank window.
Once I do this all other Waves inserted to the project from that point on open correctly.
 
Mike 

If you want to send over the .dmp file I'll take a look at it and tell you if I can determine where the fault originated from. If it's on the Waves side though, best bet is to direct it to them. If it's on our side, I'll bug it up in our Fault Reporter system.
 
Your image suggests the file is located in your %appdata% folder.
 
Do this...
 
Open SONAR and then go to Help > About SONAR. From there, hold down the ALT key on your keyboard and click on the Legal... button. It will take you straight to your Minidumps folder. Grab the file named "test_06042013_225034.dmp".
 
As an aside, Waves has always been very upfront with us that a lot of crashing and graphical issues are a directing result of needing to update graphics card drivers because they use OpenGL. I'd always rule that out first.

Ryan Munnis [Cakewalk]

As an aside, Waves has always been very upfront with us that a lot of crashing and graphical issues are a directing result of needing to update graphics card drivers because they use OpenGL. I'd always rule that out first.

Ryan,
   For me, Waves focused on the 32 vs 64-bit versions of the plugins as seen by Sonar as the most frequent cause. During my last troubleshooting session with them, they never brought up my Graphics card drivers, not that I don't already have the very latest. I'm not arguing this isn't a cause, but the fix in my case was to "hide" the 32-bit plugins from Sonar. That didn't 100% eliminate the crashes, but very significantly reduced them. Could we be facing two causes, that when put together improve the chances for a crash?
 
Thanks!