Sonar is stable when tracking here and now, with midi and recording audio at once,onto many tracks at once...bravo!....I would not change a thing in that...
 
Hope the little buggy things get ironed out, that people found...and continue to find.
 
As for score...?..
A feature that can be found in score software of differing parties....
All that work and efforts to get a product so finely coded....cannot merge into sonar?....Must be a way soon?...or...imagination and methods to solve for X...by the user...
 
Well, I hope Tom keeps his Sonar prog, and adds more DAWs, and scoring software, to his tool belt, and a second laptop, to slave sync to the other...might help, in more ways than one, for the time being?.
 
Cheers!

Anderton
The reason Cakewalk structured updates the way they did is you can update quarterly if you like. Or if you want to be on the bleeding edge, you can update every month...or update one month if there's a feature you really like, then not do anything for another six months. Or jump off for a year and come back in again later.

The problem is, each time there's a release you don't know whether it's stable or not. So you can wait, check the forums, and see whether it's safe to upgrade, but that's time-consuming, and you're basically doing extra work just to keep your DAW in the sweet spot between being free of bugs and having all the features and content you paid for.
 
One alternative would be for Cakewalk to have 2 parallel branches, a Stable and Experimental. This works well for some software and gives customers a better expectation of what they're getting.

is it possible to not upgrade for say 6 months, and then pick a release from those 6 months to upgrade to? i.e., say i currently have release "B" installed, can I upgrade to "E" or would i have to upgrade to the latest (H?) and then "rollback" to E?

pwalpwal
is it possible to not upgrade for say 6 months, and then pick a release from those 6 months to upgrade to? i.e., say i currently have release "B" installed, can I upgrade to "E" or would i have to upgrade to the latest (H?) and then "rollback" to E?

Check your store account and see which versions are available for download.

Kylotan

Anderton
The reason Cakewalk structured updates the way they did is you can update quarterly if you like. Or if you want to be on the bleeding edge, you can update every month...or update one month if there's a feature you really like, then not do anything for another six months. Or jump off for a year and come back in again later.

The problem is, each time there's a release you don't know whether it's stable or not.

 
I'm not sure "stable" is the correct term. I think it's more a question of a new feature having a bug, which is typically fixed the next month. I don't recall any update which resulted in crashing or freezing for a large number of users. The one bug I do remember that really mattered to some people was when the control bar's custom module was stuck to the far right, which was a new bug to an existing feature. But I wouldn't consider that as affecting stability, it was fixed the next month, and if you found it really problematic, you could roll back to the previous update for 30 days. Bugs are never welcome, but if there's one that's introduced with a new feature, you can pretty much just wait a month and ignore whatever new feature was added. 
 
As you can imagine I have to keep up to date, but have not encountered a situation where updating caused the program to become less stable. In fact with the various bug fixes in each version, SONAR has generally become more stable with each update. I'm willing to trade off a whole bunch of bug fixes for the possibility that a few were introduced in a new feature, although I recognize not everyone will agree.
 

to be fair, there have been two (?) mid-release hotfix patches so far, implying that those particular scheduled monthly updates weren't "quite right"...

pwalpwal
to be fair, there have been two (?) mid-release hotfix patches so far, implying that those particular scheduled monthly updates weren't "quite right"...

Yes, no question about it, bugs have been introduced with new features. But that's the case whether all the updates are batched up and released in a year, or released one at a time. The difference here is that, as you've noted, they can be fixed more quickly. (Compare the progression of bug fixes and their timing with X3 to those since SONAR 2015 was introduced.) Probably the most severe example was when upsampling caused issues if tempo changes were present. It was addressed with a hotfix within a couple weeks, so if you just stayed on the previous release, or didn't use upsampling, you didn't have problems. 

sure, but if they'd been "batched up" for a yearly release, the bugs showing up monthly surely would have been found "in house" before users got/discovered them? characters like "ö" in the new start screen for example (goodness, that one's a classic "schoolboy error"!)

pwalpwal
sure, but if they'd been "batched up" for a yearly release, the bugs showing up monthly surely would have been found "in house" before users got/discovered them?

Not necessarily - check out the bug fixes for X3. I agree if the start screen had been developed early in a dev cycle and sitting around for six months, the error you mention probably would have been caught. But if it had been developed in the month before the release, you could have the same situation you have here.

pwalpwal
is it possible to not upgrade for say 6 months, and then pick a release from those 6 months to upgrade to? i.e., say i currently have release "B" installed, can I upgrade to "E" or would i have to upgrade to the latest (H?) and then "rollback" to E?

Yes. This was something that was really bugging me being the laggard I am (I was perpetually missing the cut off before the new releases came out). Previous if you had not downloaded (or installed) a version and a new version came out in the meantime you were out of luck. I posted a thread asking this be corrected and apparently it had been bugging one of the Bakers as well (I forget which one actually came into the thread... Ryan maybe?). He announced they were fixing it and I think within a few days we had a new area that provides download links for ALL releases that have come out during a paid subscription period.
 
It's awesome and has made me an extremely happy Beep.
 
I think you click on the main Sonar download links thingie then there is an extra button that exposes previous releases by version/date. Something like that (I've only used it once but it was immediately useful to me).