Waves minor version changes invalidates previous Sonar .cwp projects' Waves plug-ins

Wow that really sucks beyond words. I've been suffering ongoing problems on and off with Waves plugins losing their settings even without any version changes. Not to mention the GUI problems. I like to think that a major DAW manufacturer like Cakewalk would be working together with a major VST manufacturer like Waves in order to make sure the two play nicely, however given how long these problems have existed I don't hold out much hope. 

That's Waves' doing, not Cakewalk's. Plugins are identified internally not by version numbers but by unique identifiers called class IDs, abbreviated CLSIDs. The developer decides if a new version of a DLL will inherit its predecessor's CSLID or get a new one. If it gets a new one, then SONAR has no choice but to consider it as a brand-new object just as if you'd added some unrelated plugin. There are legitimate reasons for giving a new version a new CLSID, but sometimes it's just an oversight/mistake on the part of the programmer.

I opened a ticket online with Cakewalk Saturday morning, but didn't hear back yet. They're probably busy with the Labor Day catching up. I'm genuinely questioning what the best procedure is to update Waves plug-ins in Sonar without a lot of trouble. Surely someone has run into this and found a good way? Thanks!

One would think that waves would maintain backwards compatibility as far as CLSIDS - you really need a good reason to drop previous interfaces - who knows? Most simply keep the existing ones, and create a new ones for new features and updates. This way, old stuff continues to work as before while new features are there for those who want them.
 
Anyway, I really don't like the idea of a master VST shell hosting some pseudo-vst plugins - it's just more stuff to go boom-boom and doesn't add value.

Can't go backwards, only forward ...

Something to add here. I don't have this problem with Wavelab 7. Does that bring this issue back a little closer to Cakewalk? FWIW, I did also submit a ticket to Waves about this. 

brconflict
The only fix I found was to re-install the older release version, re-scan/reset all plug-ins, manually save each and every Waves plug-in settings for each project in my Sonar history, uninstall the old version of Waves, install the new, re-scan, replace each Waves plug-in in each Sonar .cwp. then, manually and individually re-import the previously saved settings for each Waves plug-in.

Yep! That was/is basically my work-around. :-( However, my old DAW is still around so I do not need to uninstall/reinstall ...

Cakewalk Support hasn't responded yet to my email support request from Friday, but Waves said they'll work with me. They claim it should not have this issue, but I've not had one update that went without this problem. Perhaps they have the correct procedure/fix/workaround for this. I'll report back here what we find.

brconflict
Did you ever solve this issue? I am hopeful you did as I have this same issue after Installing X3.
 
Thanks

Meno, it seems Waves may have misguided you. VST2 doesn't mean 32-bit, because you can have VST2 64-Bit plug-ins, I believe. Anyway, here is a procedure I posted that should take care of 99% of your Waves woes (it still won't renew your WUP, unfortunately, but hey...)
 
http://forum.cakewalk.com...Try-this-m2944841.aspx
 
This procedure starts fresh. Sonar's Plug-In Manager should be able to correctly separate VST2 from VST3, making that much easier. Or, you can simply "hide" VST2 plug-ins in Edit Preferences=>File=>VST Settings.

brconflict
Meno, it seems Waves may have misguided you. VST2 doesn't mean 32-bit, because you can have VST2 64-Bit plug-ins, I believe. Anyway, here is a procedure I posted that should take care of 99% of your Waves woes (it still won't renew your WUP, unfortunately, but hey...)
 
http://forum.cakewalk.com...Try-this-m2944841.aspx
 
This procedure starts fresh. Sonar's Plug-In Manager should be able to correctly separate VST2 from VST3, making that much easier. Or, you can simply "hide" VST2 plug-ins in Edit Preferences=>File=>VST Settings.

brconflict
I don't think I said anything about VST2 being 32bit only. All I did was describe how to correct for 32bit Version of X3. I use both Sonar 32bit and 64bit. I did follow the directions that X3 gives on how to hide/replace but this did not work and I kept getting the Waves CLSID errors.
 
Waves did good by me. The latest versions of my Waves plug-ins are all VST3. The conflict is having both versions showing in Sonar plug-in manager. I had VST2 plugs showing in Sonar's "VST Audio Effect Category" and the "VST3 Audio Effects Category". Having both is what was causing the issue. So the work around removes all of the VST2 plugins and keeps all the VST3 in the Plug-IN Manager.
 
I was going to take a look at your advice "procedure" but I can't get that link to work.

I've seen issues with 64-Bit Sonar, but never with 32-bit. So that's interesting you ran into the case of the CLSID errors there.
 
Meno, I just wanted to point that out since Waves may have told you to create "VST2" folders, instead of "32-bit" folders in Program Files(x86), which is the 32-bit Program Files folder, and your header for these steps said, X3 32-bit.. just wanted to make sure you and others who read your instructions knew those weren't hand-in-hand the same (VST2 and 32-bit). I'm sure you knew that, Waves should have known that, but possibly other may not. Sorry for not assuming you knew that.   And yes, Waves support helped me work this out early on as well, even at 9PM at night on a call-back! WUP costs money, but IMO it can be worth it in a pinch.
 
So, there were three separate issues overall that caused problems for me with Waves plug-ins:
1) Mixing 32-bit and 64-Bit plug-ins in Sonar X1/X2. Crashes (maybe fixed in X3). The procedure I have fixes this in particular.
2) Mixing VST2 and VST3 in X3. GUI Glitches and possible crashes (avoid mixing these Waves plugins).
3) CLSID issues from sub-versions (i.e. 9r7 to 9r13, etc.) in Waves plug-ins (seems to be fixed in X3).
 
Hope this helps!!