Doktor Avalanche
To say that there is no demand for stability releases (as has been stated only recently) is a ridiculous statement.
Of course that's ridiculous. Everyone wants stable software, and it's clear some months have concentrated more on fixes or more on features. But it's also unwise not to satisfy those clamoring for more features. Cakewalk learned that the hard way when SONAR 2015 was introduced.
I think no one would dispute that out of the gate, SONAR 2015 was much more stable than X3 because so much emphasis was placed on "under the hood" work between versions. However, there were people who felt the new features in 2015 were "underwhelming." If they can't see that fixes were made, or if the fixes relate to issues that didn't impact them, as far as they're concerned there's no perceived value to the update. And if X3 worked for them, they wouldn't update unless they saw new features, or took it on faith that when people in the forums said 2015 was more stable, those stability fixes would create a better experience. They wouldn't know it was a better experience unless they updated, which they wouldn't do
sans new features.
To me the biggest advantage of the monthly releases in terms of fixes is that they're ongoing, they don't stop after 5-6 months or whatever it took for X3 to stop doing fixes. Yes, of course bugs will be introduced with new features...but again, unlike the big yearly update where all features hit at once and it can take months to squash everything, it really does seem that if there's a bug introduced in a release it's fixed in the next one, sometimes even with a hotfix that occurs within weeks. This to me is
far preferable to the old model, which also of course didn't have the option to roll back...so whatever bugs you had were there until Cakewalk could fix them.
What would make the system better is more resources for QC but that's a chicken and egg situation. The more people who sign up for membership, the more resources become available. Paradoxically, those who harp publicly and repeatedly on what's lacking in SONAR drive potential users away from the program, thus making it more difficult to fix the issues about which they complain, so then they complain more. As in other aspects of life, negativity begets negativity.
Of course negative issues should not be ignored, and obviously, a lot of the fixes have been driven by forum comments. But ongoing repetition of the same laundry list of issues is counter-productive. Fixes are prioritized based on multiple factors, including perceived good for the greatest percentage of active users, timing (there's no point in fixing a bug if the functionality is going to be changed in the near future), feasibility, whether or not a workaround exists for an issue (it makes more sense to prioritize issues that don't have a workaround), and impact on time that would preclude developing new features in order to remain competitive and satisfy those who don't have stability problems and want more features.
Now, for some comments on features as a SONAR user who depends on it for my livelihood. What I like most about the monthly updates is being able to absorb a limited number of features at a time, and choose whether or not to include them in my workflow. I find it
far less disruptive to learn a little bit every month than a whole lot every year.
I've also noticed that few of the new features are "global" features I use all the time in every project. Instead, they are more targeted...there are some projects where VocalSync is essential, some where Mix Recall is essential, sometimes I'm on a laptop and need the virtual controller, Drum Replacer I haven't used all that much but when I have, it's been
essential and made a huge improvement...some plug-ins need upsampling, some don't...etc. So I see the new features more like new tools in the toolset than fundamental reworkings of the program.