mike_mccue


Susan G said:
"I frequent the REAPER forums, and I have to say I haven't seen even one post from a SONARite bashing REAPER."

As a reminder, this thread is actually about Cakewalk's choice to not fix a big problem with SONAR.

A problem that has existed for 5 years and 5 paid upgrade versions. ( = $900 U.S.D. )

A problem that is so bad that it makes Cakewalk users seek alternatives because, if they are like me, they feel that Cakewalk as a company has abandoned it's existing customers while searching for an emerging customer.

There may be a very good reason you don't see Reaper users bashing Reaper by pointing out where SONAR is better.

Perhaps Reaper users feel secure and satisfied that the program is developing in a manner that will compliment their needs?

I wouldn't know. I helped my Nephew set up a Reaper install, but I've never used it myself.

What I do know is that after buying 13 versions of Pro Audio/SONAR and sending a couple thousand dollars to Cakewalk they choose to ignore my needs. Cakewalk chooses to pursue emerging customers rather than fix glaring problems with their product.

Cakewalk routinely delivers a broken product and then they refuse to focus on fixing what they have  not done properly in the first place.

It appears to me that this is why Cakewalk's existing customers are not as attractive to Cakewalk as what Cakewalk describes as "emerging" customers. Presumably emerging customers do not know that Cakewalk has demonstrated a pattern of delivering a product with broken features nor do emerging customers know that the broken features are unlikely to be fixed in a timely manner.

That is what this thread is about; Cakewalk's existing customers are angry that Cakewalk will not fix broken features in it's SONAR program.

best regards,
mike

Sonar once had such support... For many years one of it's beautiful elements was that the Bakers were in tune with their' customers' needs and answered them well and quickly...

I'm sad to say that since just prior to becoming "Cakewalk by Roland", this was beginning to wane.

It's now becoming such an item that instead of the non-stop praise for them and their raport with their' user base, they are now beginning to receive the opposite... I truly hope this is a passing phase but..............

I have been a stolid Cakewalk user since Cakewalk For Windows first appeared and have no plans to change... but if this continues much longer I will be forced to look elsewhere. It was the relationship between developer and user that first brought me here and it may be what carries me away.

That would be very sad as I enjoy the program overall.... but the bugs that are important are now being overlooked in favor of the eye-candy which is useless to the majority... I'm sure there are many users who want Sonar to be more like Ableton or such.... but in that case they should GO with the change as each is designed for a different kind of user...

Nice when Cakewalk adds extra features to fill some of those needs, but NOT at the cost of it's primary toolset.

I was (and am) more than willing to pay for all the useless glitz that has been given to me with the program, but I want and expect that these primary tools (ENVELOPES!!!) to be working correctly and with a complete toolset...

So, PLEASE... Bakers..... Here all this noise being made and surprise us all  with a quick update-fix devoted to these issues....

I still stand behind you.... but for how much more?

Love Ya'
Keni

Glennbo

Marah

the idea that the only reason to discuss product B in product A's forum is on the marching orders of product B's developers is simply idiotic.

You got that right.  I came here because I began to get email after email from Cakewalk about the new version of Sonar, and I wanted to see what they had done in the way of improvements and fixes to the core DAW software.  I posted a link to a freeking text file, that contained no links or promotional stuff whatsoever, as an illustration of something I think Cake needs to have.  A simple text only changelog, that was mostly about bug fixes.  Something that I believe that Cakewalk should have posted somewhere on their web site.  A simple text only list of what's been fixed in the newest version. A changelog.  It's no wonder that people get bent when they buy the latest version, hoping that a bug that's been bugging them will have been fixed, only to find out that it's still present.  That's what this thread is about.  Bugs that go from version to version and don't get fixed, while the resources that could have been spent fixing them, are used on revamping plugins to v2.0

I'm with you Glennbo!

dontletmedrown

Robin Kelly [Cakewalk
]

Guys you are on a peer to peer forum, expecting responses form Cakewalk is setting yourself up for disappointment. Thinking that if you get the page count up higher then you will force a response/action on the issue is another wrong way to go about it.

Just because we have not posted does not mean your issue has not been reported. Definitely report problems using the lines of communication we created for you to do so. There is something in SONAR called the Problem reporter, refusing to use it and posting here instead is essentially you going out of your way not to have your problem addressed.

If you want to discuss a problem here, no problem. If you want to use it as an official line of reporting an issue I am afraid you should reread the TOS and understand what this forum is all about. I strongly encourage you to use the tools (like the Problem Reporter) we provide to report problems in the official capacity, that is the fastest way to get issues into the system. Then come here and start a thread if you need/want too.

Robin

Robin, with all due respect, this is a perfect example of what some of us consider a "corporate disaster".  You work for the company, and you're here reading about a bug that a decent amount of user are unhappy about.  Maybe it might be in your company's best interst for YOU to send this info through the appropriate channels.  It's actually quite typical for an overgrown corporation to "pass the buck" and tell the customer to use the "appropriate channels" rather than taking charge and just making it happen yourself.  Most people will simply opt out when they become frustrated.  It's probably not realistic to expect a frustrated user to fill and forms and bug reports.

Hi Dave...

I agree with you and hopefully Robin is doing so even tho it wasn't mentioned in the message... In "the old days" this was laways the case as the few people running/developing Cakewalk products was small and close.... I'm wondering if that's still the case?

We're not beta testers... Please don't treat us as such. I'm sure we'd all like to help out, but our interests aside, we're not developers...  Simply users expecting the gas we buy to allow our cars to go... I'm not in the habit of logging into a Chevron site to help them make their' fuel better... ;-)

Keni

Keni

Glennbo

Marah

the idea that the only reason to discuss product B in product A's forum is on the marching orders of product B's developers is simply idiotic.

You got that right.  I came here because I began to get email after email from Cakewalk about the new version of Sonar, and I wanted to see what they had done in the way of improvements and fixes to the core DAW software.  I posted a link to a freeking text file, that contained no links or promotional stuff whatsoever, as an illustration of something I think Cake needs to have.  A simple text only changelog, that was mostly about bug fixes.  Something that I believe that Cakewalk should have posted somewhere on their web site.  A simple text only list of what's been fixed in the newest version. A changelog.  It's no wonder that people get bent when they buy the latest version, hoping that a bug that's been bugging them will have been fixed, only to find out that it's still present.  That's what this thread is about.  Bugs that go from version to version and don't get fixed, while the resources that could have been spent fixing them, are used on revamping plugins to v2.0

I'm with you Glennbo!

Thanks Keni.

I had no idea that anyone (like Richard) would blow a fuse when I suggested that Cake needs to focus on the core DAW and post a changelog like the one I posted a link to (which was a text only list of fixes), that clearly spells out what has been addressed (not marketing hype) in the update, so end users will know if particular issues they may be experiencing have been addressed.

All I can say is that I'm amazed about Cakewalk's generosity in providing a place where people can openly bash their company. This thread has posters writing about Cakewalk being all about profit, that they lost their way, they don't care about the users anymore, blah, blah, blah.

I understand that people get frustrated when their issues are not addressed, but damn, it goes to far when posters use Cakewalk's forum to influence users to quit Sonar and switch to a competing product. It's plain uncouth.

Some of you should create your web site for that purpose (and take advantage of your freedom of speech). But constantly doing it on Cakewalk's dime, that's just lame.