...and it also shows why this forum can be very, very cool.
 
On December 10, THambrecht posted a thread "Mysterious Behavior After Splitting Audioclips." Even though my initial response about Cakewalk being aware of it but not able to reproduce it got dismissed as a "canned response," several forumites realized what I was saying and participated in finding out how to isolate and quantify the issue. Ultimately THambrecht gave a really lucid explanation, I gave some possible workarounds, there was enough info to reproduce the bug, and Keith Albright came into the thread to say Cakewalk would work on a fix because clearly, it was a potentially significant issue that affected all users, and therefore needed to be prioritized.
 
Because I had been involved in the thread, Keith gave me a heads-up earlier today to say that the problem had been fixed, and the fix would be in the next update. I'm sure some people will be able to put some kind of negative spin on this - it's possible to put a negative spin on just about anything - but I think THambrecht, the forum, and Keith deserve some props for underscoring the tangible benefits to having a partnership between the users and the company. 

OK I'll give it a negative spin. Why wasn't it done yesterday? 

 
I feel this forum and it's members have been very instrumental in the direction, development, and maintenance of Sonar. It is without a doubt the best most useful forum I have had the pleasure to belong to. The Bakers have proven once again that they listen and act to resolve problems..  

It probably was , but it had to be passed on the the Secret Sonar BETA testers for evaluation for being released (even on the early release program).  Of course, the Cakewalk BETA NDA prevents the BETA testers from even revealing that they are testing it.

I did ask Keith for permission to mention it...

King_Windom
 
I feel this forum and it's members have been very instrumental in the direction, development, and maintenance of Sonar. It is without a doubt the best most useful forum I have had the pleasure to belong to. The Bakers have proven once again that they listen and act to resolve problems..  

Agreed!

Well I see my negative spin didn't work. 

Anderton
On December 10, THambrecht posted a thread "Mysterious Behavior After Splitting Audioclips."
...
Keith Albright came into the thread to say Cakewalk would work on a fix because clearly, it was a potentially significant issue that affected all users, and therefore needed to be prioritized.
....
Because I had been involved in the thread, Keith gave me a heads-up earlier today

It is good to know that it works.
 
Now my negative spin (tired today, so I am negative ), but in fact just a suggestion for improvements for this procedure: why Keith could not inform users directly? 
 
For the moment, yet another such story is ongoing, with "Insert marker" / "M" / "VS-100" etc. It is ALMOST the same, except the last part. I mean the bug is affecting almost all users, easy to reproduce, confirmed by CW. But since there is no information it is going to be fixed, the number of threads about it is growing, the air is heated, etc.

I am of the understanding that it is fixed (the marker insert issue) and will be in this month's update. I could be wrong though. 

People should also take note that the best way to get bugs fixed is to have a reproduce-able method for causing them that you can thoroughly explain and that works all the time. QA for more places isn't lazy, stupid, or uncaring, it is just that issues are often not something they can reproduce. Someone says "My system does X," their system does NOT do X under the same circumstances, near as they can tell, so they don't know where to go from there.
 
Sometimes software bugs are an obvious thing, lots of users report a fault, developers look at the code, and it is a very simple mistake that they can fix no problem. However often the bug is subtle, relying on the interaction of a number of pieces of code, all of which function correctly in isolation. It can be hard to nail down, unless you know just what to do to cause it, and thus what to look for.
 
If a bug is something you really need fixed it can take some persistence on your part, not in convincing QA to fix it, but in really figuring out what the bug is.