Undo would be nice, especially having one for mixing (i.e. fader, pan, EQ, and 3rd-party plug-in changes), but I would love to see a selective History instead. Much like what Photoshop has, but where you can remove a change in the history without having to undo changes after that change. If it has a dependency, it will warn you, or be grayed out as un-undoable. I know there's a program out there that can do this, but don't recall what it was.

+1 for custom bar.  I would like to put undo, cut, copy, etc. there.  Nice to have choices for different styles of working.
This would just be additional icing on the Cake!

My right hand is basically always on the mouse, also. My keyboard is in a slide out drawer and is typically only used to name tracks or files. Now, it's really inconvenient to use for a bunch of keyboard shortcuts (that I usually can't remember and have to look up, anyhow).

bitflipper
 For myself, I'd be happy doing away with the toolbar altogether to reclaim that screen real estate for another track or two.
 

Keyboard shortcut "C"

Mr. Noel, Please take no personal offence.
 

Noel Borthwick [Cakewalk] The buttons were taken out at the time (in X1) to redo the control bar and remove excess clutter.

 
So the "excess" clutter was removed, what type of clutter was deemed worthy?
 
Consequently we got the non-configurable command-ribbon because new users were overwhelmed with the possibilities represented by the non-customized out-of-the-box cluttered-with-all-possibilities button bars?
--------------------
An assessment of clutter is based in knowledge of the work to be done.
 
webster defines clutter as “to fill or cover with scattered or disordered things that impede movement or reduce effectiveness.”
"clutter is anything that is disorganized"
"clutter is anything you don’t need"
"a state of disorder"
Synonyms  = untidiness, mess, disorder, confusion, litter, muddle, disarray, jumble, hotchpotch
 
For me All of these definitions describe the X Series UI. Command-Ribbon items cannot be organized, are not needed, reduced effectiveness (especially the menus), and are distracting, extra-click menus everywhere,...
-------------------

Noel Borthwick [Cakewalk] That said I think with touch screens its not an unreasonable request to want buttons for undo/redo ...

 
But not for mouse users?  ;)
 
When watching the screen it is way easier to click a button than look away from the screen to be assured ones' fingers are on the correct keys. Way inefficient.
----------

Noel Borthwick [Cakewalk] At the time it was determined that most users do not use those buttons but use shortcut keys.

 
This is the first I read about this consideration.
----------
You are saying, MOST of the, about 40,000, at the time, 7/8 Sonar users did not use the standard out-of-the-box-not-customized cluttered-with-all-possibilities button bars?
 
Most meaning 60%? 80%?  At 80% that means 20%  DID use these buttons bars.  About 8,000 users.
 
I would have been INCLUDED in the group that did NOT use the standard out-of-the-box-not-customized cluttered-with-all-possibilities button bars. Because I do NOT use the out-of-the-box button bars for any program. 
 
I DO still use my 8.5.3 customized button bars spread across both screens, positioned where needed, so I do not have to look away from my work.
 
The X series Command-Ribbon covers more space and provides less convienience. It is true clutter (clutter is anything you don’t need).
 
The single row of customized button bars I use in 8.5.3, and the row of screen-context buttons use less space and provide more value. These button bars have links to what I ACTUALLY USE most often, as close to the work my eyes are looking at. Most Sonar key commands require looking at the keyboard. A  distraction best. (I do use many standard windows key commands.
 
With most of the users claiming to use key commands, the same assessment should have been made about the command-ribbon:  Most users do NOT use the command-ribbon, and therefore it is "excess" clutter.. They learn key commands. Or, more probably, for most of us, we find the item on a menu.
 
So why does the command-ribbon exist?
-------------------------------------
Just reviewing THIS thread:: How many thousands of user hours, and user dollars spent, to make the program do what it usedto? Buy a Midi controller with undo button, map a midi key, buy foot controllers, use remote access pads, get an extra program,....
All this could be fixed with a couple of programming hours.
-------------------------------------
 
Is the same to be understood for the removal of color customization? Somebody who could-not-be-refused figgered most users did not use colors? So customization was not needed?
 
And it has only taken nearly 4 years of complaining to get some bit of user color preferences?
 
 
Don't get me started.
 
==========
Bugs, comments & suggestions:
We expect this application to not always perform as described. This is by design. There are no mistakes to be found in our software code, only undefined behaviors, and undocumented results. Enjoy the process of discovery. Please inform us of any unique functions you encounter that we may include them in the list of known features.
 

 I have ran teams of hardware and software developers to produce major communications programs and it is pretty obvious from your post that you have absolutely no idea about software development. As such, I really don't think you should be quoting man-hours to a CTO of a company that produces a significantly sized software program..I mean.. really?..lol
 
You are clearly in rant mode, but the fact is that neither Sonar developments, nor the planet, will revolve around you no matter how long you persist with this thread.
 
There have been several attempts by many in this thread to help you use what tools Sonar has already provided to give you a faster, more economical method of rapid undo than you currently use.. yet you ignore them.
 
The bottom line is that having a midi keybind to "undo" can be fixed by you in 30 secs flat by using the tools already provided by Sonar.. yet instead you spread disinformation and untruths about both Sonar and a number of synth & keyboard controllers.
 
As for a feature request, I think a small box of 6 customizable buttons is not a bad idea but any ongoing comments that you cannot do what you want (one click undo) in Sonar is total BS.

mudgel
If you tie yourself to a mouse then you're not really interested in speeding up your workflow. You really just wanting to hang onto the way you've always done it.

To not adapt your tools to better serve your needs to me sounds unreasonable.

Piano / synth keyboard with a few key combinations and your hands don't have to leave the keyboard to grab hold of a mouse.

Learn keyboard shortcuts (qwerty) again your hand doesn't have to leave the keyboard. It's just so much faster.

Your daw is not just a tool but your recording, mixing, arranging, mastering instrument, why not learn to play it as well as the musical instrument of your choice.

And if you want a feature that's currently not implemented then put In a feature request. Also read the manual. All the info on setting key bindings, both qwerty and MIDI keyboard are covered in quite some detail.

 
I think the mouse is still the most accurate way to tweak faders, knobs, and plug-ins. Even more than a controller, and I've tried both.

 
I put in Feature Requests for 2 Control Bar related items not long after X1 came out:
 

1. Customisable Button Module
   
   I mocked up this at the time using 8.5's buttons to illustrate my idea (using some of the Views menu options):
   
   
   
   
2. Scrollable Control Bar and/or Resizable Control Bar and/or Collapsible Modules
   
   What a right royal PITA the current right click and select/deselect is. How can this be easier than having a scroll bar so you could have all the Modules available all the time - just a quick mouse drag away?