cityrat
Yea!!  Outstanding !! Thanks!~! 
 
 (chord pics)

Fixes like this give me hope.  Good work Cake.
 

Year 2013 and X3c - still don`t have hot key for - mute selected midi-note. And soon will be 2014 but X3c still don`t have normal and modern Macros script programming.
Today X3c don`t have normal Velocity edit and other СС# in Cotnroller panel in PRV like in Reaper, Studio One or Cubase.
 
Oh... my dear Sonar Stop Make new Bug and Fix them later. Please, give me more functional in Midi-edit, in Browser...

But... Cakewalk, thank you for your job.

mmorgan
+1 on bettermints (sic)
 
Regards,

On Halloween!  Ha Ha Good One.
 
And thank you Ryan!

Microtonic
Year 2013 and X3c - still don`t have hot key for - mute selected midi-note. And soon will be 2014 but X3c still don`t have normal and modern Macros script programming.
Today X3c don`t have normal Velocity edit and other СС# in Cotnroller panel in PRV like in Reaper, Studio One or Cubase.
 
Oh... my dear Sonar Stop Make new Bug and Fix them later. Please, give me more functional in Midi-edit, in Browser...

But... Cakewalk, thank you for your job.

You can ALT + Right Click to Mute a note super easily in the PRV with the Smart Tool. Check it out: http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR%20X3&Lang=EN&Req=Tools.04.html#1229613
 
You can also edit Velocity and other CC# data in the PRV. This isn't new. More information here: http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR%20X3&Lang=EN&Req=EditingMIDI.22.html#1083405
 
Hope that helps!

Ryan Munnis [Cakewalk
 
You can ALT + Right Click to Mute a note super easily in the PRV with the Smart Tool. Check it out: http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR%20X3&Lang=EN&Req=Tools.04.html#1229613
 
You can also edit Velocity and other CC# data in the PRV. This isn't new. More information here: http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR%20X3&Lang=EN&Req=EditingMIDI.22.html#1083405
 
Hope that helps!

I'm sorry, I forgot about that :) - ALT + Right Click to Mute a note.

Sorry for being a wet blanket here. There number of bug fixes in X3b and X3c are so numerous and extensive that it made me wonder why these weren't discovered during the beta stage. Or perhaps the product was released as a beta product and the early adopters became the beta testers. Don't get me wrong - I'm glad that Cakewalk is releasing patches quickly and faster than compared to previous versions. But there shouldn't be so many fixes needed on a finished product. I hope their beta testing/QA team get their act together.

There are lots of pieces to get in place when building and releasing software.  This can include production deadlines for contractual agreements with retailers and third-party included products, and lots of other things.  Sometimes things have to get released with known anomalies.  That's one of the realities of software development.
 
Many of the things fixed were not even posted as issues in the forums, so I actually commend the Cakewalk folks for obviously busting hump on getting things as cleaned up as possible, on a MASSIVE release that has all kinds of folks cheerfully reporting pleasant experiences in using it.
 
This has been the most aggressive maintenance release schedule I can recall seeing, and am quite pleased with it, and with the results.
 
Bob Bone
 

cheez
Sorry for being a wet blanket here. There number of bug fixes in X3b and X3c are so numerous and extensive that it made me wonder why these weren't discovered during the beta stage. Or perhaps the product was released as a beta product and the early adopters became the beta testers. Don't get me wrong - I'm glad that Cakewalk is releasing patches quickly and faster than compared to previous versions. But there shouldn't be so many fixes needed on a finished product. I hope their beta testing/QA team get their act together.

I don't think that is accurate. We released SONAR X3a to the public on 9/28. It was pretty stable and since that time we have been focusing on resolving issues in the field, many related to VST compatibility. We spent a lot of time this cycle listening to customers and releasing a solid product with some major new features that are no small undertaking (VST3 and ARA).
 
I think that using the reasoning that bc we are issuing more patches, that somehow it's not stable is not true. There's always room for improvement with any product. And we will continue making SONAR X3 the very best product for Windows PC. 

cheez
Sorry for being a wet blanket here. There number of bug fixes in X3b and X3c are so numerous and extensive that it made me wonder why these weren't discovered during the beta stage. Or perhaps the product was released as a beta product and the early adopters became the beta testers. Don't get me wrong - I'm glad that Cakewalk is releasing patches quickly and faster than compared to previous versions. But there shouldn't be so many fixes needed on a finished product. I hope their beta testing/QA team get their act together.

A great release today is better than a perfect release tomorrow. You'll never iron out all bugs. I imagine you do your best- say a release that is 95 per cent solid for 95 percent of users and roll with that. 
 
How many of the irregularities that were fixed were hindering you cheez. You probably didn't know that many of them even existed. So were they bugs to you?

I'm loving X3! Very stable, looks great, sounds great and it's fun to use. Addictive drums more than pays for the upgrade. The rest is free!