artturner
jpetersen
Scook, Beepster - After what Craig and Noel revealed sunk in, I began to understand where the priorities really lie. And must do. I tried replying 3 times and that was all I could say.
Puts our diligently assembled lists of bugs and feature requests properly in their place.
It's left me shattered.
This. I can't speak for others, but this describes my reaction to the LANDRing.
Out of all the bugs and features passionately requested and discussed on the forum, I don't remember any that were looking for an "add track" button or the ability to export to LANDR. We pay for rolling updates and look forward to what will be fixed next, then discover that the bakers have used their time to produce updates that few people seemed to need. They then spend time explaining why this is what we should have wanted all along.
Ever since the new rolling update model began, it seems to me that the primary focus is to reduce beginning user support calls first and serve pro users coincidentally.
For the record, I won't be leaving Sonar over this. But the "sigh...denied again" feeling is all too familiar.
With all due respect...I think there are some
extremely short memories around here...
The
M release had a bunch of optimizations, and responded directly to user feedback about improved solo logic for patch points and aux tracks, as well as the request to include patch points and aux tracks in track templates. Trust me, Patch Points and Aux Tracks were not introduced to "reduce beginning user support calls," and along with synth recording, this kind of functionality was one of
THE most-requested features of the past few years.
The
L release included optimizations that related to projects with large numbers of clips (as required by pro users), loading times, file imports, and more. Fixes related to Staff View, the PRV, clip splitting, the Start Screen, Matrix View, Event List data, drag drop and drag copy, control surface persistence, and others.
The
K release was also super-heavy on optimizations, with a focus on speed increases and VST3 enhancements. If pros don't want faster and more stable operation, especially with large projects, I would be shocked. There were also 31 bug fixes (and of course, the wonderful Monitorizer FX chain

). And the Start Screen had the list view people had wanted.
The
J release brought Patch Points and Aux Tracks but also lots of optimizations regarding load times, virtual instrument streaming, VST scanning, and CPU power savings...more pro-oriented features...and again, 31 bug fixes including the end of the long-standing denormalization problem that produced pops with some plug-ins. There was also upsample on playback...an extension to upsampling, another pro-oriented feature because it makes SONAR sound better. To me, sound quality is sorta important.
All the people who don't think this was all that big deal of a release should have a discussion with all the people who've said they don't care if Cakewalk misses a monthly release if it's too difficult to come up with big features and improvements every month (like the ones listed above).
And think logically for a second. What's more important, general optimizations of the core program, or attending to subsets of the core program which might be made obsolete by core optimizations?
Some of the bug fixes people want are issues with awkward functionality, not stability. But I think those who realize you can't have everything fixed all at once would place a higher priority on stability. Sure, it's not as glamorous to fix things that people forget were fixed
because they're not causing problems any more. But they're important fixes. Plenty of people posted threads about "Hey, my ProChannel effects make loud pops at unpredictable times, when are you going to fix this?" No one ever posts a thread that says ""Hey, I just noticed none of the ProChannel effects pop any more at unpredictable times." They'll move on to the next thing they want fixed, and forget about what was fixed.
Fortunately, some people look over the
continuum of the past year and realize that taken as a whole, Cakewalk's
priority has been on providing a
balance of features, enhancements, fixes, and optimizations for all types of users, from first-timers to veterans. The result has been increased stability, speed, and functionality.
I'm surprised more people don't take a longer view. IMHO that's the best argument for having yearly updates - people won't have to remember all the cool stuff that happened just a few weeks or months ago, everything will hit at the same time, so they can't avoid seeing the balance.