is rollback only possible if you actually install each release? or, once subscribed, could i choose any  (A-B-C-D...) version (since this new mechanism) to "rollback" to, assuming the chosen version was released within my subscription period?

Alex can we stop this tiresome argument and pointless back and forth please? Cakewalk has been developing software for 30 years. We know how to design and develop software in an effective way. We have thought through this system and despite what you or others might think we have had a solid industry standard engineering process in place for a long time. Its a ground truth of software development that there will be regressions and we have a system to deal with it. This is an app with multi-million lines of code and extremely complex dependencies - something that looks like a "sloppy testing" to end users is not always as black and white as it might seem as was the case with the drum maps issue.
Anyway the problem has been solved so please move on! That said, what is very helpful to is notifications of problems with clear reports - not discussions about how we should improve our internal process which nobody outside of cakewalk has any idea of.

pwalpwal
is rollback only possible if you actually install each release? or, once subscribed, could i choose any  (A-B-C-D...) version (since this new mechanism) to "rollback" to, assuming the chosen version was released within my subscription period?

It's only available for an update installed through the CCC. So if you've installed every update via CCC you can rollback to anyone of the previous versions. That is Alston, Braintree, Cambridge, Dorchester.

^^yup I agree with Noel^^

I've tried a rollback between Cambridge and back to Braintree. It worked very quickly and seamlessly.

I'm not sure whether it just reinstalled a previous download as stored in the CCC download folder or whether it caches the Sonarplt.exe file per version and reinstalls that. I don't remember seeing a specific discussion on what gets rolled back. Nor have I searched for a cached Sonar executable. Suppose I should do that. Then I'd know.

In the X1 days, rollback was tried a couple of times with a few of the quick fixes IIRC, and they were cached versions of the Sonar executable.

Noel, I still would like a Cakewalk or Sonar coffee mug.

FCCfirstclass
Noel, I still would like a Cakewalk or Sonar coffee mug.

I don't blame you.  The S-Plat mugs are awesome.  I can't believe how long they keep coffee hot. 

BobF

FCCfirstclass
Noel, I still would like a Cakewalk or Sonar coffee mug.

I don't blame you.  The S-Plat mugs are awesome.  I can't believe how long they keep coffee hot. 

 
I love your coffee smile, Bob.

Noel Borthwick [Cakewalk]
... not discussions about how we should improve our internal process which nobody outside of cakewalk has any idea of.

And yet there has been no such discussion, other than John trying to bait me into it which I duly ignored, the actual discussion has been about how it effects the end user. I guess the only thing you could point to is a single comment which speculated QA might have not had time to test, I'm sorry that I posted it but I think it's valid. Anyway I guess you have license now to state that's all I've been posting about in this thread.
 
Anyway aim for the jugular, I am now silenced once again.

Imagine the glorious day when Sonar development is, at long last, led by back-seat-drivers via forum posts. What an era of high stability and broad functionality that will be.