ORIGINAL: creynolds
I don't want your money. I don't really wan't mine back to be totally honest. I want people to hear my greivance and create a movement that makes Cakewalk think about what they have done and maybe reconsider the direction they have taken. We are the customer.
As I've already written in other threads, I think Cakewalk made a gutsy move when deciding to focus on fixes, not features, in the Sonar 8 upgrade. I too felt this way last week when I learned the details of this release, and I too expressed my frustration and disappointment with negative comments here on the forum.
But after more thought, I've come to the conclusion that a) the philosophy behind the Sonar 8 release creates a win/win situation for Cakewalk and its users, and b) Cakewalk showed great strength of character in its decision not to focus on features.
I've been a weekly visitor to this forum since I started using Sonar 4 3 years ago, and therefore it's been clear that Sonar's 64-bit audio engine has had serious problems since its release two years ago. The product has been way too sensitive to variations in drivers and platforms, and has been much more vulnerable to plugin-caused crashes than competing hosts and daw platforms.
So, I disagree with your initial statement that Sonar 8 is a shambles. I would counter with: Sonar 6 and Sonar 7 had severe problems. Call it a "shambles" if you like, but I don't see it that way. Sonar 8 is an attempt to address the problems in Sonar 6 and Sonar 7.
Don't misunderstand -- I'm not telling you to shut up. We all have to blow off some steam now and then, and you have plenty of empathy here.
Cakewalk could have continued the status quo, piling more features on a questionable undercarriage. For two years they've managed by dealing with major problems in real time, while a handful of users here on the forum have served as an unpaid volunteer support group, helping noobs through configuration issues -- (great job, forums users.) But other DAWs just don't display this kind of eccentricity. Sure, noobs will have problems, but those problems are much more common in Sonar.
But Cakewalk chose to do the right thing -- find out what's wrong, get in there and fix it. That took guts, because they knew they'd get reactions just like yours (and mine, last week).
Now, I too was incensed over having to pay for these bug fixes.
10 to 20 years ago in the software publishing industry, software took longer to manufacture. Subsequently, releases came intervals of every 1.5 to 3 years, instead of today's practice of a release every year. Those major releases were not discounted as steeply as today's upgrade, and were priced within 25% of the retail price. If you do the math, and stretch the $170 of today's Sonar upgrade over a longer time period, you'll find that today's price is consistent with yester years, and maybe even a few percentage points less.
What I concluded was that we pay the same as we always did, whether we call it a new feature upgrade, or a maintenance release, whether we get a free update or have to pay for a major release. If you add it up, and divide by the number of years over the lifetime of the product, we pay what we always paid, because one way or another, a company has to maintain a revenue stream. That's the bottom line. Nobody is getting ripped off here, and nobody is getting rich -- it's business as usual, and in this case, that's not a bad thing.
Listen, I felt the same way, but when I calmed down and thought, it all made sense and I'm not mad anymore. We needed these fixes -- sounds like they didn't get them all yet. And, we also need some new features -- if I don't get a compositional interface to score my music pretty soon, I'm gonna stomp my feet and hold my breath til I turn blue -- and won't Cakewalk be in trouble them!
Hang in there -- the future does look brighter, but it requires patience, and that's how we support Cakewalk at this stage. Keep using Sonar and keep reporting back with your problems until they get addressed. We do have their attention.
-- Kurt Matthies