Noel Borthwick [Cakewalk]
not in X2 though but when I was working on some stuff in X3.

Your's faithfully (now sacked for leaking info)
Noel "leaky" Borthwick

:P

Peski moose.

Youre suprised that I'm working on the next version of SONAR?  We start work on the next version immediately after the release of a new version - been that way for about 15 years :)
Sometimes even prior to the release of a new version. Its very common for software companies to work that way. For example Microsoft was working on Windows 9 even before Win8 was released - thats a more extreme case of course due to the scale of microsoft.
Anyway please lets not hijack this thread. Were talking about a specific compatibility issue here.

Noel's right. Just because they are working on X3 doesn't mean they don't have a team working on X2b. Dropping X3 in the forum only shows that X3 is in the works--albeit, that could also be re-titled, or re-packaged, released, or simply dropped. There's not as much of a hint as one would infer.
 
I'm still begging and pleading for X2b, but if X3 has a massive overhaul of Take Lanes, and a way I can remove features of X3 I'm not ready for or don't use, or don't have the horsepower for, I'll gladly take X3 at $99.
 
I was working in X2a last night, and had no issues. I was quite happy that this is the first session I didn't have a crash (not one in 4 hours!). I was avoiding some things that, in the past have crashed it, but learning how to hack the way I do things has helped, as well as patience with Waves plug-ins. Maybe X3 will make this easier, with higher tolerance of 3rd-party plug-ins, improved performance, and more stability perhaps! (fingers crossed!)

Noel Borthwick [Cakewalk]
Youre suprised that I'm working on the next version of SONAR?  We start work on the next version immediately after the release of a new version - been that way for about 15 years :)
Sometimes even prior to the release of a new version. Its very common for software companies to work that way. For example Microsoft was working on Windows 9 even before Win8 was released - thats a more extreme case of course due to the scale of microsoft.
Anyway please lets not hijack this thread. Were talking about a specific compatibility issue here.

Good comeback! lol...But after Ryans very strict and professional "WE WILL NOT DIVULDGE INFORMATION" routine, you have really dropped a penny here! :D

So Sharke, so much going on in this thread not directly related to your original post but ... did I get this right, that all is now working ok for you with GR, or was it just Waves?

ULTRABRA
So Sharke, so much going on in this thread not directly related to your original post but ... did I get this right, that all is now working ok for you with GR, or was it just Waves?

As of now everything's still up in the air. My main Waves plug reset issue was with the Q-series EQ's. I have replaced all instances with the Renaissance EQ's instead and we'll see how that goes. So far I haven't had any resets, but then again the reset issue is one that comes and goes and in the past there were times I thought I was rid of it but then it started happening again. As for Guitar Rig, well I've been in contact with Native Instruments about this and they suggested that it's something to do with me having both the 32-bit and 64-bit versions installed, but I don't - I only have the 64 bit version installed. So now they are asking me to remove all traces of the program and install it again. We'll see how that goes too. 
 
And yesterday I thought I was rid of the Waves GUI problems after updating my Radeon drivers. I swear, the problem completely disappeared at first and ALL of my Waves plugs were as smooth as butter. Then today, I fire up some projects and the problem is back. It now feels like I dreamed the smooth as butter part. 

Oh and to add re: Native instruments tech support, they told me that the problem is "not a known issue," but I did find a post on this forum from 2011 in which someone describes the same problem and said that NI tech support had told them it's a Sonar Issue.
 
http://forum.cakewalk.com/Guitar-Rig-Solid-Mix-Series-problem-settings-go-zero-m2430766.aspx

Noel Borthwick [Cakewalk]
Sharke I'm sorry to hear about your problems. Issues with compatibility are always frustrating.
I wanted to let you know that we have a great relationship with Waves and have been working very closely with them over the past months.

Many issues with plugins are not what they may seem on the surface so be careful about jumping to conclusions that the primary fault lies in the DAW without analysis. A subtle change in behavior in a plugin can cause very drastic results from one DAW to another. A good example is supertap - this is actually a quirk in the plugin implementation that causes a feedback loop of parameter changes. This is why simply rolling the transport when a parameter is armed causes automation to start writing. I managed to address this by putting in  parameter feedback detection logic. The general sluggish UI issue with Waves plugins has also been resolved by reworking some of the core logic dealing with parameter notifications in SONAR.
 
I have not seen a case with complete loss of parameter state with Waves plugins. If you have a project that exhibits this you should definitely bug this up both with Waves and Cakewalk. If you have already done so please list the CWBRN number here. I have however seen the loss of parameter state with Guitar Rig - not in X2 though but when I was working on some stuff in X3. Based on what I saw I'm pretty sure that this is actually a GR bug. If the plugin is started before we load its persistence for some reason when audio streaming starts the plugin will reset itself! I was able to work around this in what I was doing. If you are seeing this in X2 there is probably some special situation where this same condition occurs in the project. If you do have the project file that exhibits this please send it to me and I can take a look at the specific case.
 
Anyway regarding the alleged lack of communication from Cakewalk its not due to some conspiracy to not communicate with users. Keep in mind that we have very few people that are public facing these days. Its a hard decision that many companies have to make to be profitable in these crazy economic times. Brandon Robin and Seth were(are) great guys and their role allowed them to interact more with users here. Its hard for us in other departments to get actively involved here but we try.

Thanks for the reply Noel. Can I take it then that a Waves GUI fix is on the cards for a future release? As I mentioned before, a graphics driver update yesterday fixed the problem temporarily and I had perfectly working Waves plugs for a few hours before they screwed up again! So understandably, I'm frustrated. 

Depends on which GUI problem you are referring to. The one where moving knobs on waves plugins wouldn't set the parameters properly and be inaccurate is fixed. That was a feedback loop. 
BTW if you have someone at NI who claims that the GR lost params problem is a host problem please have them contact me. I would like a chance to dispute that claim :) If its our issue of course I will try and fix it.
We have been spending a lot of time addressing compatibility problems so we always welcome contact with plugin vendors.