if i never had the issues reported by others do i need these updates? are they still playing well in other hosts? tia

Well, I can't update through CCC, no luck, even after "Checking For Updates" manually.
 
Off to download froom the store.
 
Cheres,
Jerry
 
Edit : in the store still showing v43 for Z3ta 2
 
C2A on v112 so here we go.
 
A.N. Other Edit : Z3ta now showing v 47 in the store (wtf ? ) so we're good to go.

pwalpwal
if i never had the issues reported by others do i need these updates? are they still playing well in other hosts? tia

I haven't had the issues either, everything is working fine. However I'd still recommend downloading the updates when they become official. The fact that some people have experienced the problem and some haven't might indicate that a situation could arise in the future that exposes any limitations in the current plug-ins.
 
In any event...thanks, Lance!

Rob[atSound-Rehab]

John
For some reason unknown to me after the full release of Sonar Platinum I have not run across any problems with CA2A or Z3TA+2. 

same here.
 
no more issues after installing official 2016.12 on the test system plus full VST scan (with process monitor open just for safety) - crashes which were reproducible especially after reboot no longer are ...

Likewise.
 
I'm able to open up all the projects which were causing problems without error.

Anderton

pwalpwal
if i never had the issues reported by others do i need these updates? are they still playing well in other hosts? tia

I haven't had the issues either, everything is working fine. However I'd still recommend downloading the updates when they become official. The fact that some people have experienced the problem and some haven't might indicate that a situation could arise in the future that exposes any limitations in the current plug-ins.
 
In any event...thanks, Lance!

I think I will wait for the official release, as I too haven't had any problems with crashes with CA-2A inside of Platinum.
 

Rob[atSound-Rehab]

John
For some reason unknown to me after the full release of Sonar Platinum I have not run across any problems with CA2A or Z3TA+2. 

same here.
 
no more issues after installing official 2016.12 on the test system plus full VST scan (with process monitor open just for safety) - crashes which were reproducible especially after reboot no longer are ...

The problem was definitely not in SONAR since the bug also manifested in other hosts. The crazy thing about crashes like this in Windows is that depending on the memory state at the time of the problem, it may actually crash or not!
Also since this was timing related, any subtle change in the app can change the timing enough to mask the problem.
 
Irrespective of whether you see the problem or not its highly recommended to get the fix. You can wait till the final release but its unlikely anything will change.

[link=mailto:CA-@A]CA-[/link]2A is working for me again, with that rollback fix. Thanks Lance

Noel Borthwick [Cakewalk]

Rob[atSound-Rehab]

John
For some reason unknown to me after the full release of Sonar Platinum I have not run across any problems with CA2A or Z3TA+2. 

same here.
 
no more issues after installing official 2016.12 on the test system plus full VST scan (with process monitor open just for safety) - crashes which were reproducible especially after reboot no longer are ...

The problem was definitely not in SONAR since the bug also manifested in other hosts. The crazy thing about crashes like this in Windows is that depending on the memory state at the time of the problem, it may actually crash or not!
Also since this was timing related, any subtle change in the app can change the timing enough to mask the problem.
 
Irrespective of whether you see the problem or not its highly recommended to get the fix. You can wait till the final release but its unlikely anything will change.

Hey Noel do you have an explanation of why I was having this runtime error crash related to CA-2A and LP64-EQ while using 2016.09? When this problem started about 3 weeks ago, even reverting back to earlier image files didn't' solve the problem.
 I have auto-updates disabled, so I'm puzzled why something from the internet was causing some changes on my computer. I did not get this crash if I reverted to my 10/23 image and stayed disconnected to the internet. Once I connect to the internet it takes a few minutes to a few hours to develop the runtime errors and then it keeps up even if I disconnect from the internet. I’ve never tried 2016.11 or any MS updates after 10/9
Last week on Tuesday 12/20, without me making any changes, all runtime errors stopped suddenly.
on 12/5 I filed a bug report  -

CWBRN-61469   No response from Cakewalk

 
Any clues would be appreciated,

I did the install when it came out of the early release for those plugins. I have not had a single problem with them. This is an update to say nothing to report. A very good thing. Happy New Year everybody.

Thank you for the updates.
 
But I would be much happier, if these apps would use their existing App Installation path. It is almost the same as some months ago with sonar. the current AppDataPath is ignored and overwritten with "c:\program files\cakewalk".
No Chance to Change this in the Setup Dialog. So either the current path should be read from registry or the app path should be choosable.
 
I hate this behaviour, because I always have to move these files then by hand and hack the registry again.....