My concern is that we will now have frequent, but half baked, updates that used to be free. I think it's 100% for the benefit of Cakewalk and not for the user base. Nothing  will ever have to be working well and we'll all be hoping the current build, or next months' build will fix the problem. A feature could be announced and then take 2 years before it's actually ready for prime time.
 
I'm buying and trying the new paradigm. Time will tell if I was a visionary or simply paranoid. 

ampfixer
My concern is that we will now have frequent, but half baked, updates that used to be free. I think it's 100% for the benefit of Cakewalk and not for the user base. Nothing  will ever have to be working well and we'll all be hoping the current build, or next months' build will fix the problem. A feature could be announced and then take 2 years before it's actually ready for prime time.
 
I'm buying and trying the new paradigm. Time will tell if I was a visionary or simply paranoid. 

I believe it was quoted by a Baker (Noel?) that you could roll back via the Command Center thingy.
 
So build 913 is good (and your membership allows the install). 914 is wonky. They say you can go back to 913.
 
I'll assume that if 914 915 and 916 are also wonky you can still go back to 913.

bapu

ampfixer
My concern is that we will now have frequent, but half baked, updates that used to be free. I think it's 100% for the benefit of Cakewalk and not for the user base. Nothing  will ever have to be working well and we'll all be hoping the current build, or next months' build will fix the problem. A feature could be announced and then take 2 years before it's actually ready for prime time.
 
I'm buying and trying the new paradigm. Time will tell if I was a visionary or simply paranoid. 

I believe it was quoted by a Baker (Noel?) that you could roll back via the Command Center thingy.
 
So build 913 is good (and your membership allows the install). 914 is wonky. They say you can go back to 913.
 
I'll assume that if 914 915 and 916 are also wonky you can still go back to 913.

But wait,, they wont be wonky because now, with the new model, CW is not pressured to put out the updates,
they will be tested, rock solid and debugged.
 
Also whats the benefit of having up to the minute  updates if they are terrible and you have to roll back?

And there's the rub. It's a trust issue. If you don't trust Cake then this won't work for ya. On the flipside they know this so they'll likely hustle to earn that trust.
 
We've also been asked to trust them with the old yearly versions too. I bought X2 thinking it would be fully patched before the next release cycle and got burned. I was not amused and nearly bailed. X3 has been a dream though so... well here I am...
 
rock you like a hurricaaaane!!

MM100,
 
My example was not meant to mean that things are wonky and will be wonky, just IF they got wonky.
 
The IF is the nature (sometimes) of software development. Bug do get through even after testing.
 
Here's a more real world example. 
 
You install 913. 914 changes audiosnap. But you have problems in PRV. Maybe you want to roll back to see if 913 worked OK. if it did you can now do due diligence to report to CW that 914 "appears" to have broken PRV. And you can go back to 913 (assuming you're not already dying on the vine from audiosnap in 913)
 
Any Beeps said it best: It's a trust issue. If you don't trust Cake then this won't work for ya.
 

More than a trust issue I think. I like the version roll back feature Bapu described, but..., some things have never been fixed. There are going to be numerous people finding things wrong because of their computer build and work habits, that are going to trash the new Sonar to death to get that one thing "fixed" to their liking. It's liable to create problems with support because now they can say, hey!, I paid for this fix! Where is it! So now you roll back for a year, and it still isn't fixed. Do you feel cheated and slam Sonar and influence sales and loyalty to the product? Thereby influencing revenue and development. 

IDK but it seems that there might only be .0002% of the users that may actually roll back for more than a day or two.
 
And only then to verify that what they see today was not "what was" sometime prior to today.
 
To day, I've never uninstalled a patch/update. I wonder how many have on purpose.

 Roll backs are no big deal, I can do it now. My concern is that build 214 will introduce a new module that doesn't work right until build 300. "We decided to put it back into the oven for a few months", wasn't completely baked.
 
Now we are buying a package and promises. They can keep showing new features that they are working on and claim that they coming soon, even if they're not. I'm also really confused when Craig says that development time will be enhanced by the new billing scheme. Makes no sense.

ampfixer
 
 I'm also really confused when Craig says that development time will be enhanced by the new billing scheme. Makes no sense.

THIS

musicman100

bapu
I also imagine it won't be on sale before then.
(I've been wrong before though)
 

the article upstairs mentions January 15

What year though?