TheSteven

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 
 
 

Those are scan paths too, just not shown in SONAR Preferences. SONAR has not displayed all scan paths starting with X1 Producer. With VST3 Cakewalk just added two more.

rodreb
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?

I think the easiest is to just hide VST3's in plugin manager - not fiddle with folders.
I did the same, but opposite, hiding all VST2 Waves not to make mistakes.
 
Noel shared that it's easy to see if a VST3 or VST2 is loaded - the bypass up on the left is grayed for VST2 but works for VST3.
 
I would also uncheck replacing VST2's thingy setting - so that does not interfere inserting VST2's somehow. One never knows how that is implemented.

Hi guys,
 
There are lots of enhancements coming up in X3C that address many plugin management issues. Layouts will also auto upgrade to VST3 if you choose to upgrade VST2's. Also several fixes were made to bulletproof the upgrade process. Most problems are being caused by inadvertently mixing Waves VST2 and VST3.
You can also now tell easily if a plugin is a VST3 by looking at the VST menu - it will say VST3 or VST2.

Ok to clarify, over the past few weeks I've made sure like four times now that I'm not mixing VST2 and 3. I'm using a custom plugin layout that I created in X3 and the VST2 versions of Waves are not in there at all. I've verified this numerous times now. So unless the VST background scanner is randomly opening plugins in the background or something, there is no way at all I'm mixing the two. Especially not since in the situation I described, RVox VST3 was only the second plugin I opened, the first being BReverb2 Cakewalk. I wish I could uninstall the VST2 versions completely as an extra safeguard, but I'm also running Ableton and need them for that. I may uninstall the VST3 versions but I was happy to use the side chaining.

Again, I'm not ruling out I'm doing something strange on my end, but it's not mixing Waves VST2/3. And I still don't believe an abrupt force close is acceptable, no matter what I did.

In my case, there are also problems with Waves VST3.
When I close a project and open another, Sonar X3b crashes every time.
But it works fine, when I close the project, close Sonar, and restart Sonar and then load the other project. This is an easy workaround for this problem.
Something from Waves seems to linger in the RAM Memory by closing the project. All projects are saved in X3b and it ist ONLY up to the VST3 waves plugins.
I have thes problem identical on three Computer.
Some crash reports were sendet a few days ago.

I also sent a message to Waves support and they got back to me saying they're aware there are still issues with Waves and X3, they're working with the Cake people, and it's the reason X3 is not on the list of "supported products" yet.

So maybe the odd crash I get when opening one particular project is not due to Kontakt 5 after all? Maybe I'm after the wrong suspect here and it's also due to WAVES VST3??? Need to wait to here back from Cakewalk, I did submit to the problem reporter ...
 
My particular project loads a bunch of K5 samples and when done, it crashes. When shutting the Octa-Capture off, it loads, then prompts for a missing interface and then crashes ... so maybe the crashes are not related to the K5 sample loading, but due to the audio engine and Waves VST3 because it was mostly recorded and mixed in X2a (never showing the current problems) ... now with X3b, I ensured that WAVES is all VST3 ... I wonder if that was such a great idea ...

X3c should be out in a week or so, I am sure there are bunch of improvements in the VST handling.. if you have submitted bug reports, probably best to wait until then...?

Sanderxpander
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 dry2. Create a send from the vocal track3. Load RVox mono4. 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.

Send Support or myself a bundle file and we can load it up on our Waves machine to see what's up. Crash issues are hard to track down so send us a .dmp file too if you can get this to crash repeatedly.

One crash report was sent automatically. I'm mixing the projects now and they have been fine.
Each time the crash happened after I had been recording for a while, doing a few takes, made a very basic comp and then inserted RVox or RComp. If this happens during a next a recording (or mixing) session I will definitely send you the project, however, saving/closing the project and then reopening it always made it work again, so I don't know how easy it would be to reproduce the crash.
 
Waves support told me they'd likely be making a new installer too, and also that there is no reason VST2 should work any better since it is also not officially supported for X3 yet. So yay. At least I don't have to bother uninstalling the VST3s. I'll just not use them. Nice virtual gold paperweights.