"It's simple really. If you don't like Sonar, how they run their business, how they patch, how they release their products, their tech support, how long they make us wait, how they keep all these secrets, the list goes on and on, right? If a person doesn't like all that and feels the need to vent or complain here or in front of clients, isn't it time to change your weapon of choice?"

So, it's like "pay, like it or not, but shut up"? Or "It's software, of course it's buggy!"? What is wrong with you guys?! If someone is having problems with the software they have paid for, you say it's not ok to "complain"?! No emphaty? I understand completely those who use DAW daily to make their living and are frustrated of annoying bugs or crashes they're reporting.

I've had no big issues with X1d. Ok, maybe some, but not very big ones... Example everytime I've exported audio (or bounced track), I have to close and reopen the project or otherwise there will be loud cracks and pops with level meters hitting at 100 during playback. I guess it has something to do with those tens of CPU hungry plugins on project tracks.

So, no big issues with X1, but as a consumer and a Cakewalk customer, I think I have a right to tell here or anywhere my opinions about their product or marketing tactics - the good ones AND the bad ones.

And what comes to Roland/Cakewalk/Sonar, there is definitely something going on and I think there will be big changes in near future...

I am not aware of a single 'show stopper' bug in X2a itself.

I DO see threads where some folks have crashes, but I have not seen a single case where Sonar crashes universally on any task it is asked to do.  (if I am incorrect on this point, please someone fire up a new thread, listing system specs and COMPLETE detail on steps that are REPRODUCIBLE where Sonar X2a crashes doing something, and I will do my best to dive in and figure out what is happening).

I have seen where threads reference other threads that mention other threads in a sort of a 'too many people reporting problems I will skip X2a or X2b or Z1 or whatever the next speculative name for the next release may be.  Many of these kinds of posts are from people that do not seem to have bothered to ask for assistance in fixing their issues, they just say that they are tired of all of the problems.  If you are having issues please detail each issue in a separate new post with details.  


I have seen quite a few cases where someone will post a request for assistance, ignore requests for information, and/or just stop participating in the thread, leaving the forum community unable to do anything for them.

I believe X2a is a stable release with some work-flow bugs.  Some number of the bugs that do exist have workarounds and some do not.  Some bugs have been present for more than one release of Sonar, and some are present in some of the new functionality.

So, other than displeasure for some over having to wait for the next release, what's with all of the pitchforks and torches?  As I have stated before, folks complain about patches too soon - blaming incomplete development or testing.  Other folks (and sometimes the same folks) complain as now, about too long between releases.  It can't be both ways without being a no-win situation for Cakewalk.  

Me, I have a functioning X2a that has not crashed since I have installed it.  I'm going to start my day out being musically productive, and keep an eye out for opportunities to assist folks who provide reasonable threads looking for assistance.

Bob Bone

X1 is pretty stable for me as well although there are bugs with the undo feature that can be agrivating.  They can be worked around so not show stopping.

Still I am looking forward to an update as cake changed the status of these to development.

J4R10

So, it's like "pay, like it or not, but shut up"? Or "It's software, of course it's buggy!"? What is wrong with you guys?! If someone is having problems with the software they have paid for, you say it's not ok to "complain"?!

I couldn't agree more - he who pays the piper calls the tune.
 
I've said it countless times before, and I'll say it again - if you pay for your Cakewalk software (or more accurately, the Licence to use it), you have every right to express an opinion about it in here and elsewhere, good or bad, providing you remain civil and don't transgress the TOS. And it's up to Cakewalk whether those opinions remain on this forum, not other members, much as though a few of them like to take on the self-appointed role of forum cop.
 
And here's another thing I've said before - looking to the future, companies like Cakewalk have absolutely no use whatsoever for threads and posts telling them how good their products are. It's by listening to and acting on the criticisms they receive that the product will improve for everyone.
 
 

J4R10

And what comes to Roland/Cakewalk/Sonar, there is definitely something going on and I think there will be big changes in near future...

I get the same feeling.
 
I just hope the change is a change for the good.
 
 

J4R10


"It's simple really. If you don't like Sonar, how they run their business, how they patch, how they release their products, their tech support, how long they make us wait, how they keep all these secrets, the list goes on and on, right? If a person doesn't like all that and feels the need to vent or complain here or in front of clients, isn't it time to change your weapon of choice?"

So, it's like "pay, like it or not, but shut up"? Or "It's software, of course it's buggy!"? What is wrong with you guys?! If someone is having problems with the software they have paid for, you say it's not ok to "complain"?! No emphaty? I understand completely those who use DAW daily to make their living and are frustrated of annoying bugs or crashes they're reporting.

I've had no big issues with X1d. Ok, maybe some, but not very big ones... Example everytime I've exported audio (or bounced track), I have to close and reopen the project or otherwise there will be loud cracks and pops with level meters hitting at 100 during playback. I guess it has something to do with those tens of CPU hungry plugins on project tracks.

So, no big issues with X1, but as a consumer and a Cakewalk customer, I think I have a right to tell here or anywhere my opinions about their product or marketing tactics - the good ones AND the bad ones.

And what comes to Roland/Cakewalk/Sonar, there is definitely something going on and I think there will be big changes in near future...

I think what most are suggesting is what is the worth of sophomoric rants when they can neither be substantiated nor proven to be true. Bugs are another issue and should be reported and discussed.

Tom Riggs


X1 is pretty stable for me as well although there are bugs with the undo feature that can be agrivating.  They can be worked around so not show stopping.

Still I am looking forward to an update as cake changed the status of these to development.

Well, I've never heard of any bugs relating to the undo feature, so do you want to share what you perceive as a bug?

I don't just perceive it Cake acknowledged it and has sent it to development. It may also be fixed but when I dug through my emails about the trouble ticket I guess I had deleted the email. 
 
edit: I found the email and they said the issue was fixed by an update but I am still having it.  Hmmmmm

The undo issues have be mentioned before by me an others although my issue is not the same as others.

My issue is that I record a midi clip then mute the first lane and record another take.
 Then I decide I don't like and use ctrl-z to undo recording. When I do that sonar removes the recording but also unmutes the first lane. If I forget to mute the lane again before I start recording again then I have the previous clip playing back.

I can get around this by muting the clip in the first lane instead of the lane itself. I could also delete the second lane and then record again without using the undo function.

After the first 2 lanes are populated I can mute lanes as needed and use the undo and it works fine.

Someone else mentioned on a post I was reading another time when the undo function was not behaving as expected. I don't remember the specific problem.

As I said I can work around it but its annoying when I forget.

I think I initially expressed the issue as a problem with lanes not so much undo.

Why do I need a B patch?

I have a number of graphical related issues that annoy me quite a bit while trying to get work done. These issues are only evident when using Sonar X2a. Support was enaged months ago and I still have no resolution or idea as to whether they are working on it or not. I feel enough people on this forum have posted about similar graphic issues where it should have gotten enough attention to be addressed by now.

Tom Riggs


I don't just perceive it Cake acknowledged it and has sent it to development. It may also be fixed but when I dug through my emails about the trouble ticket I guess I had deleted the email.

The undo issues have be mentioned before by me an others although my issue is not the same as others.

My issue is that I record a midi clip then mute the first lane and record another take.
 Then I decide I don't like and use ctrl-z to undo recording. When I do that sonar removes the recording but also unmutes the first lane. If I forget to mute the lane again before I start recording again then I have the previous clip playing back.

I can get around this by muting the clip in the first lane instead of the lane itself. I could also delete the second lane and then record again without using the undo function.

After the first 2 lanes are populated I can mute lanes as needed and use the undo and it works fine.
 
Someone else mentioned on a post I was reading another time when the undo function was not behaving as expected. I don't remember the specific problem.

As I said I can work around it but its annoying when I forget.

I think I initially expressed the issue as a problem with lanes not so much undo.
 
edit:
I should add that it only happens on a track that was created by the template when the project was created. If memory serves if I create a new track thinks behave as expected.

I believe there is indeed some quirky annoying behavior with the Undo functionality in X2a.  For sure this would drive someone a bit batty.  Hopefully this kind of annoyance will get addressed when the next update comes out.


Bob Bone

Yeah, I have found a few issues with X2. But there are no show stoppers for me to where I need a patch. If there were, Cakewalk would deliver something for us. They have ALWAYS done that when an outbreak of "wtf's" are all posted in one thread. I saw it happen with Sonar 8, I saw it happen with X1 and we saw it with X2. Anything that stops the show or is detrimental gets fixed in a timely fashion even if it's a hot fix. That's commendable in my opinion.

This is true.  I have my work arounds and things to avoid but there aren't any problems that cause catastrophes for me.