SteveStrummerUK
This is how I thought it was going to happen, with new stuff and updates being released when they were ready, rather than saving them all up for the end of the year.
Totally disagree. Consider that many features previously released as part of a big yearly update continued to evolve, but with a much slower pace of evolution...introduce feature, spend months fixing bugs, collect feedback, make changes for next big update...compare the original ProChannel to what it is now. Imagine if that development had been compressed into months (like it is now) instead of years (like it used to be).
These days "new feature bugs" get fixed pretty much within a month, and feedback is implemented much faster as well. The evolution of the program has sped up considerably. I believe the only reason people don't see this is they have short memories about the arc of progress/updates with SONAR prior to 2015. Here, this will jog your memory: X2
There really is no need for an update of sorts each and every month. As long as we get some tidy stuff every now and again I think most of us would be happy with that modus operandi.
It doesn't matter if Cakewalk was working on a new feature every month and having it sit on the shelf until the big yearly update, or whether they're working on a few feature every month and then release it. The only difference is the program evolves much faster, and becomes more stable, under the new model.
The biggest problem with the monthly update is it puts things under the microscope that were hidden before. If new feature "X" has a bug, the forum explodes -
"New Update Buggy!" Rolling back!!" Then pretty consistently, it's fixed in the next release or several times, with a hotfix a week or two later (like the arpeggiator data bouncing issue, or the tempo change issue with upsampling). Before, if feature "X" introduced in a yearly update had a bug, it might take a while to discover because it was mixed in with a whole bunch of new features, and it would take even longer to fix it.