Do the Sonar Platinum users feel overwhelmed with all of the updates?

Sanderxpander
My main concern is that so far every new release has come with SOME bugs. They're usually not big but it becomes pretty hard to judge whether or not one will be a problem for me and I don't like rolling the dice every month.

This is something I don't quite understand. It takes only a few minutes to update, and even less time to roll back. Any bugs usually affect only a limited number of people, so there's really nothing to be lost by updating, then if you encounter a bug that actually affects your work, rolling back to a previous version.
 
As to the general topic of being overwhelmed, I have yet to see a serious DAW that didn't have an overwhelming feature set. But, just because you own a car doesn't mean you have to drive every road...you drive on the roads that take you someplace you need to go. 

I kind of did at first but that was simply due to my need to "KNOW ALL THE THINGS!!!"
 
Throughout the year though it's become apparent that the Baker's aren't really changing much of anything. The core of the program is X3 (an undoubtably popular and stable incarnation) and all this new stuff is exactly that... new stuff that doesn't screw with the main X3 foundation. You can use the new stuff or not use it but it's there when and if you decide you want/need to.
 
The only exceptions to the "it's just X3" premise would be the new Control Bar (which is super easy to figure out and WAY better) and the new PRV stuff which has seemingly remained the same since it was initially implemented (with necessary fixes). Everything else can be safely ignored unless you go out of your way to use it.
 
I've only updated SPlat I think 2 (maybe 3) times and am about to do so again to get at the track to track stuff. I've mostly been doing things as I have been since X3 but occasionally reach out to the new tools because they were useful for what I'm working on (for example I'm about to use Drum Replacer for the first time).
 
Also I find it BETTER with these monthly releases of new stuff because, due to my personal laid back update method, I get a chance to really let the possibilities sink in and see how everyone is using/liking new stuff. The monthly eZines was a great idea. I read through them (and download/store them with my manuals) to get an idea of what's up and how things apply to my work. This all makes it much easier to use these things once I actually DO something with them.
 
Before when it all got dumped in our laps once a year (AND with massive changes to how the core program worked) it took at least a couple months to catch up. Now once I do get around to installing the updates/using the new stuff I already know what's going on and my work isn't disrupted really at all. I just have some cool extra options.
 
I haven't really been nailed by any of the "bugs" or problems either because if I see a ton of people complaining about stuff here I just write off that version and wait to see what the next one brings. Looks like JP is probably a good version to snag and squat on. The only complaints I've seen were in regards to specific third party plugins that I don't use and over the top routing issues that can be avoided (and the Bakers said they're working on).
 
Much more protection and choice IMO with the new model I think and really no reason to be overwhelmed because nothing new seems to get in the way of old workflows (if you are already used to X3 or Sonar 2015 anyway).
 
There were some stumbles at first but this does all seem to have been thought out rather well and humming along quite nicely now.
 
Cheers.

Anderton

Sanderxpander
[That's easy to say, Craig, but you don't always notice bugs right away, sometimes they mess with your save files

 
Just curious, have there been incidents where some bug caused problems with saved files? I don't recall seeing anything about saves in the forums other than people having issues trying to open old Bundles. If you open a SONAR project with an older version of SONAR it ignores new features, so that might be a simple solution if this indeed happens to someone. 
 

sometimes they are seemingly small things where you don't understand right away what is going wrong.

 
I can definitely see that ("Is it me or is it SONAR?") but you don't have to try and troubleshoot the problem. If doing the same thing worked before, just roll back.

I don't mean to belittle Cake's intent or efforts with this new system. But the question was posed and for ME new updates all the time can be perhaps not overwhelming but at least disruptive to my workflow. Even though I love some of the new features. I'd just rather not have my DAW be like my phone or iPad like that.

Anderton
Well, you're preaching to the converted on one level because I haven't upgraded my MacBook Pro to El Capitan, or my phone to iOS 9 yet , so I know where you're coming from...but I have upgraded my iPad, because I don't use it for business. It's very convenient to be able to "test" an upgrade on the non-mission critical stuff before applying it to something that really matters to my work, but that's basically what rolling back/forward lets me do.
 
I'm also in the camp of finding it easier overall to have my workflow disrupted a little bit once a month compared to a major disruption every year. I think the main argument in favor of a yearly big disruption was that you could have the old and new versions installed side-by-side. 
 

I recall an issue where some plugin states weren't recalled correctly. I can't say for sure that it was in the way Sonar saved things. But my point was that I'd only notice it after hours of work and upon RETURNING to a project.

I really just don't like the whole jiggamarole monthly instead of yearly (or three times a year with patch fixes). X2 wasn't as unstable for me as for some and X3 was on the whole very good. Every patch fixed a number of small known issues and for the most part didn't introduce new issues. Sorry if I don't feel the installing and rolling back is more comfortable. It makes me feel like a beta tester and I want to be making music. No matter what you say, it disrupts the process and it's not just the rolling back but also the time spent figuring out what's up, possibly cleaning up the mess etc.
I just find it uncomfortable. YMMV.