Hey guys, first of all let me start by saying the I am not a software person, so maybe you guys who are a lot smarter than me can set me straight..
I am loving the monthly updates we are getting from the bakers, but at what point is it going to reach it's limit, meaning there is so much you can stuff into a program before it over flows and star creating bottle necks, am I right?
If you keep stuffing things into a bag eventually it's going to maybe stretch and pop, doesn't software programs work the same way...
 
 

With software there is no limit to "stuff." It just gets more complicated.  Take MS word.  I use it to make money, but I've never even used 1/10 of its capabilities since I don't prepare to publish with it.  Same with SONAR.  There is plenty of stuff I don't even know exists, tools to do things I never knew I needed, and ways to do jobs I don't do.  But they are all nice to have even tho I don't use them.
 
The biggest problem with the monthly updates (and a nice thing also!) is keeping up with every aspect of a complex DAW and consequently growing your own work load to take advantage of them.   Most people here are not professional users, so a lot of the capabilities aren't needed. But it is nice to have them when you do need them.  It is like owning a van or a truck - most of the time it is too much car, but when you need to move something bulky (or dirty), nothing else works.

Primetime
Hey guys, first of all let me start by saying the I am not a software person, so maybe you guys who are a lot smarter than me can set me straight..
I am loving the monthly updates we are getting from the bakers, but at what point is it going to reach it's limit, meaning there is so much you can stuff into a program before it over flows and star creating bottle necks, am I right?
If you keep stuffing things into a bag eventually it's going to maybe stretch and pop, doesn't software programs work the same way...
 
 

No, your bag is like an ever expanding universe

yea this isn't like some old play station game were you could only fit 4 GB max on the game disk.
With "Add on" possibility's, it's an infinite thing. Sure there are always tweaks that are going to be needed but I believe the monthly thing has ironed a lot of that out.
 

There may be no limit as to what can go into software. There is always a compaction or feature compression. Like a sequencer with a cludgy, manual pitch, velocity and after-touch interface that is replaced with a new artificially intelligent-neural-fractal sequencer.
 
Plus there are other examples. A tuner might seem like a great idea in a DAW but IMHO it is just a feature that should be somewhere else. Either as a piece of hardware in the studio or in a separate app. Kinda like building a George Foreman grill into the dash of your car. Handy and perhaps great for picnics but a bit out of place and likely to be removed.
 
So, in this sense, there is never really a bursting point. Cars are still the same basic shape and size as they always were. Plus they are getting more technical, smaller and more efficient and sometimes now without a gas cap...

A hover craft would not be too much.
 
A Cakewalk coffee mug seems to be too much (to offer) though.

well, the contrary example would be what's known as "bloatware"

The user interface stuff that just lays there waiting for you to click it in an event driven OS like windows consume little to no cpu cycles until you go click on them then they start executing their code. So don't worry about glossy ui stuff too much like the pretty PRV selector for instance. Memory consumption could raise it's head here though.
 
What's maybe more concerning is that while there are at least one pet issue for every user, Cakewalk is choosing to instead of hacking away at them, they are fixing issues that don't really exist yet. For example: We had a PRV track picker and we knew how to use it (and it showed all tracks too, for decades) But now we have a pretty picker with a learning curve. And we're now whining that it shows all the tracks! Now, I know it's hard to keep coders happy just bug fixing and they'll got somewhere else as it's much more gratifying to create. But the installed base by and large doesn't see it that way. There are things that worked in X1,2 & 3 for instance that don't in the New Sonar. Like I said, at least one issue for each user.
 
Now that many have lifetime updates it also takes away any leverage we may have had.
 
Suck it up, ButterCup!
 
Addendum: I can read and write C / C++ and would welcome the opportunity to fix some of my pet issues.
I'd do that for free. I have lifetime updates and a vested interest in at least one big ACT issue. I'd love to tackle that.

Thanks you guys are awesome!!

I see two issues at play. The first is adding more "stuff" that is for specific users, and which don't matter to others. For example suppose SONAR did a serious revamp of video support. That would involve a lot more "stuff," but it would add nothing for those who don't use SONAR with video.
 
But I also think there may be a tipping point where SONAR starts to consolidate features into an easier workflow. IOW there would be no less functionality, but it would be streamlined and easier to access.