Ok I am a little bit annoyed now. The Waves VST3 stuff is still not sorted completely I feel. Today I had a recording session with just acoustic guitar and vocals. I did a few takes so I did a very small amount of comping to fix one or two sentences and then the singer wanted to hear how it sounded from beginning to end. Hang on, I said, I'll slap on a little reverb and a compressor.
1. Create a new bus with BReverb2 Cakewalk, select a nice preset and kill the dry
2. Create a send from the vocal track
3. Load RVox mono
4. Crash "Sonar needs to close".
 
This happened four times in total during different versions of the same project (I resaved and reloaded with each new song after the guitar was done so I had to make the same basic vocal setup a few times). Only once did I get the error report thing and of course I sent it. If I closed the project, reopened it and inserted RVox it was usually fine although I did get one crash even that way. I got very CTRL+S happy but I'm not pleased.
I hope there is still some work being done on this for X3c.

Sander, I'm thinking this may be something specific to your system. There are many people using Waves without issues like what you're seeing from what I've read on the forum. I'd definitely try and contact Sonar support to see if they can help you on this.
 
Other than that, the only thing I can recommend would be to go into your preferences, VST and do a reset on the plugs. Then tick "rescan existing plugs", rescan and then see how it works. 90% of the time this fixes plug issues, but may not work for you. (remember to take the tick out of scan existing plugs after your done)
 
I just had a dealing with support today and let me tell you, I like to think I know what goes on with Sonar under the hood. As much as I know, I'm still clueless and found that my issue I reported was my own fault. Something that I completely missed was totally jacking my Waves plugs that would have been really hard to track down. But I was determined and found out it was totally on me. So you never know...I'm not at all dismissing that you have a problem, I'm just saying that quite a few times we can miss the obvious even when we are pretty sure we know we've done everything right. Then there's the other side....things that worked in X2 may appear to be broken in X3. This was part of my problem too.
 
"How did it work in 8.5, X1 and X2 yet it doesn't work in X3....it's X3's fault!!" Come to find out things are working BETTER in X3 so it caught the mistake that shouldn't have worked in previous versions. So it appeared broken in X3 when in reality, it was pilot error.
 
Just curious....do you happen to have any console emulation on any of your tracks or buses? If so, try removing them and see if it still happens. I wish I could be more helpful, but I'd definitely turn this one over to support by phone if you live in the USA.
 
-Danny

I also consider myself pretty tech savvy but of course that's exactly why it's easy to assume I did everything right, you're right about that.

However, I honestly don't believe a program crashing and not even giving you the chance of saving your work should ever be considered "pilot error". At best, assuming I actually did something really dumb and confusing for the software, it's crappy error handling.
As far as I'm aware the only caveat with Waves is to not mix VST2 with VST3 plugs, which I made very sure I'm not doing. I'm going to replace all my Waves VST3s with 2s in new projects and see how that goes for a while.

From what I've read on the forums it sounds to me like the Bakers are putting a lot of effort into fixing everything Waves related, so I would not be surprised if the next update improved things. For what it's worth I've had Waves crashes like you describe in X3b, but they were all related to mixing VST2 with VST3. Have you set Sonar to hide the VST2 plugs, just to be doubly sure?

As far as your plug-ins go - are you using the "Default All Plug-ins" menu or a custom menu to insert your Waves plug-in into your track?
 
If you are using a custom plug-in layout menu that you created before X3 then that might be part of the problem.
Currently as of X3b - even if you have the "Hide Related VST2 Plug-ins" option checked Sonar X3 does not replace the VST2 plug-ins listed in custom menus with their VST3 counterparts
 
If I recall correctly Noel mentioned that this was a feature that was going to appear in X3c.
 

Just updated to X3 from X2 (haven't installed it yet). I'm having pretty good luck stability wise with my Waves stuff right now. Kinda scared to mess things up. Is it mandatory to switch over to VST3 or, can I just stay with my VST2's with X3.

There is nothing forcing the switch to VST3, stay with VST2 versions if you wish.

Actually, I'd like to try the VST3's but, if I have a problem with them, can I switch back to the VST2's?

Sure, you  just need to be careful. You cannot mix Wave VST2 and VST3. SONAR still uses scan paths to locate plug-ins.

scook
Sure, you  just need to be careful. You cannot mix Wave VST2 and VST3. SONAR still uses scan paths to locate plug-ins.

Re >SONAR still uses scan paths to locate plug-ins.
Yes & no.
 
Most VST3 installers put a copy of the VST3 in C:\Program Files\Common Files\VST3
or if appropriate C:\Program Files (x86)\Common Files\VST3 
The X3 VST Scanner automatically scans these locations as well.
The scanner is smart enough to not list the 32 bit version if a 64 bit version exists.
 
If the VST Scanner finds a VST3 in both locations Sonar will list the copy found in your scan paths otherwise it will log that VST3 where it is found, regardless of if it's in your scan paths or the Program Files location.
So if you delete a VST3 plug-in from your scan path and a copy exists in Program Files that plug-in is still going to show up.
 
If you are using the "Default - All Plug-ins" menus then it should be pretty easy to identify what's what 'cause your plug-ins are already separated by type (VST2, VST3, etc.). 
If you are using custom plug-in layout menus then it depends on how you set up your menus and if they were initially created before X3.
 
As mentioned previously in this thread:

TheSteven
Currently as of X3b - even if you have the "Hide Related VST2 Plug-ins" option checked Sonar X3 does not replace the VST2 plug-ins listed in custom menus with their VST3 counterparts
If I recall correctly Noel mentioned that this was a feature that was going to appear in X3c.