Kylotan
 
Ultimately I've had to consider whether people are right when they basically say, "if you don't like Sonar, and don't want to use it the normal way, why are you here?" I can try and argue here for the inclusion of features that I like in other DAWs... or I could just use the other DAWs and stop complaining. :)

Don't know WHAT the first part of that sentence is suppose to mean.  Sonar is such a huge, powerful, diverse program there is NO "normal way" to use it and can't imagine the people here saying that.  
 
Arguing for what you want is great... It is part of EVERY DAW forum. I've tried a number of DAWs over the years and even have a couple others like S1v3... and what I find is that the grass always looks greener...till ya get close enough to notice all the brown spots... and given the power of mainstream DAWs today, the learning curve is huge.  Can't imagine going back and forth... coitus interruptis with the confusion it would cause in my little brain.
 
 

 
 
Workflow is not set in stone. You discover it for each DAW, you don't force it. I like the fact that Sonar gives us some workflow choices, we don't all do this thing the same way.

Anderton
People need to be specific about MIDI editing, it's not enough to say "better MIDI editing."

Yes, it's a complex question, but the answer is pretty easy.
1. Solve reported bugs.
2. Implement requested features.
 
Some examples:
http://forum.cakewalk.com/A-feature-for-those-that-write-string-arrangements-MIDI-note-chase-m3100396.aspx
http://forum.cakewalk.com/Duplicate-Ctrl-D-m3099521.aspx
http://forum.cakewalk.com/Drum-Map-Manager-UI-UpdateRefurb-m3097383.aspx
http://forum.cakewalk.com/Feature-Request-MIDI-Patch-Point-Or-a-MIDIHUB-m3348419.aspx
http://forum.cakewalk.com/Bring-back-drawing-tool-customization-m3228674.aspx
 

Vastman

Kylotan
 
Ultimately I've had to consider whether people are right when they basically say, "if you don't like Sonar, and don't want to use it the normal way, why are you here?" I can try and argue here for the inclusion of features that I like in other DAWs... or I could just use the other DAWs and stop complaining. :)

Don't know WHAT the first part of that sentence is suppose to mean.  Sonar is such a huge, powerful, diverse program there is NO "normal way" to use it and can't imagine the people here saying that.

Certain tasks, in Sonar, require an awkward set of steps to perform. In other DAWs, they are often a single click, or a single click-and-drag. But when I talk about this, people often say "what's so hard about doing A, B, C, D, then E? No big deal."
 
I'm sure exactly the same problem applies in reverse in other DAWs, with other features where Sonar has a great approach. I'm just not qualified to comment on them, having not seen them yet.
 

Can't imagine going back and forth... coitus interruptis with the confusion it would cause in my little brain.

I expect it'll be a hassle. But then I've used a bunch of music programs in my time - Sonar, Reaper, FL Studio, Modplug Tracker, Fasttracker 2 - and one more isn't going to kill me.

The two biggest "MIDI related" for me are 1) lighten the overhead from mating MIDI to audio and allow manipulation of tempo in an elegant manner (e.g., allow Melodyne 4 to adjust SONAR's tempo map), and 2) enhanced MIDI routing (drums maps/graphical drag/drop note routing), especially for multitimbral plugins that can route MIDI through as well as fire on other channels (e.g., a user being able to monitor MIDI notes "in play" that SONAR is seeing and mate them accordingly - for me this is simple channel/note mating, but others would want more resolution).

I'm still hoping for a chord track for Splat, similar to the one in Cubase.

I hope you guys are putting feature requests in

Adq

Anderton
People need to be specific about MIDI editing, it's not enough to say "better MIDI editing."

Yes, it's a complex question, but the answer is pretty easy.
1. Solve reported bugs.
2. Implement requested features.
 

Just to clarify;  From what I am reading it seems to me that the main focus for CW will be on implementing touch screens into Sonar's workflow.  It will be hard work for all involved (programmers and users) but if it comes off this could be a real game changer in the world of DAWs.  I will probably lock in Sonar at the end of my membership (March) and sit this year out since I have a control surface.  I'll have a look at Sonar in a year or so.  In the mean time I will use my $ to take a look at another DAW.
 
BTW; Specific suggestions for MIDI editing and routing exist throughout the Forum as so eloquently posted by Adq. 
 
Cheers.

I hardly ever use the keyboard shortcuts, like someone else stated, I don't use SONAR for hours every day, every single day to memorize all those shortcuts.  I use some basic ones like copy/paste.  But I DO like the programmable shortcut buttons on the top ribbon bar.  Those are just as quick as keyboard shortcuts.
When I'm playing my MIDI keyboard, it's easier to grab the mouse and click then to look away from the screen to find the right buttons on the computer keyboard.   Just my 2 cents.

Leee
I hardly ever use the keyboard shortcuts, like someone else stated, I don't use SONAR for hours every day, every single day to memorize all those shortcuts.  I use some basic ones like copy/paste.  But I DO like the programmable shortcut buttons on the top ribbon bar.  Those are just as quick as keyboard shortcuts.
When I'm playing my MIDI keyboard, it's easier to grab the mouse and click then to look away from the screen to find the right buttons on the computer keyboard.   Just my 2 cents.

The opposite is true for me. When I've got my guitar strapped to me it is WAY easier while tracking to reach out and slap at the keyboard (QWERTY) to control transport and delete functions.
I find myself doing it with my eyes closed.
 
R
Spacebar
Repeat
 
or
 
R
Spacebar
Ctrl + Z
 
The alternative is having "palm" my pick, take my eyes off the guit (or open them... lol), grab the mouse, navigate to the areas that control those settings and manually click everytime. It would slow things down immensely.
 
I'd like to map all this to my padKontrol one day to make it even easier (just pads so I could TOTALLY do it with my eyes close). The Undo part of it was the problem before because Transport could be controlled with MIDI before reltaively well but I don't think the Undo was (or at least not as easily mappable). Now with the Custom Module I am under the impression I could assign that to a cell and that cell to MIDI note/controller.
 
But that also would mean having the pK hooked up and programmed on my cluttered desk every time when the keyboard is already there and ingrained in my muscle memory.
 
Just goes to show though everyone works in their own way. Flexibility is always good in a program like this so the Custom Module really was a good addition. Much more important/useful than many seem to realize I think.
 
Cheers.