Perhaps the best way I can explain it is the video on this link. I really apologize for doing this, since it pertains to Cubase's capabilities in this area. I would love it if I could do something like this in Sonar.
 
http://www.youtube.com/watch?v=8DU_Vwp3zzU&list=UUugtfsFZyEfylRRJMisWvng&index=16&feature=plcp
 
Notice the visual feedback in the velocity lines, the flexibility and ease. I am really not trying to run down Cakewalk, I am trying to do as you suggest and explain my request.
 
Thanks for your openness, Noel.
 

John - you can do what you want to in X1 - go back and re-read the posts above - it can be done with the smart tool. I work a lot with midi and articulations - this is achievable.

I must be doing something wrong, then, because when I open up PRV, lasso a group of notes, then go down to the velocity pane, I am unable, using the smart tool or just left or right clicking, to move the velocity values in that pane.

I CAN change the velocities by hovering the cursor above the piano roll note until the cursor changes, then I have to watch this tiny readout of a numerical velocity value with no visual feedback from the lines on the velocity pane. Not only that, but I can't see where there is the kind flexibility shown in the video I posted, where you have options to choose how notes will move in relation to each other, for example either absolutely or relatively.
 
I appreciate the suggestions, but unless I'm missing something (and I very well could be) I don't see anything other than lesser workarounds to what should be intuitive and easy with obvious visible feedback on the changes being made.

While I'm working this through on this thread, I'd also like to mention one other thing I'm really happy to see in the upcoming X2: Being able to paint note lengths instead of having to select a  different note length from a pulldown menu every time it changes.

No.. this kind of velocity editing in the PRV isn't possible in Sonar.. (yet..(?))

If you want to create a velocity-fade-in and keep the relation of the velocity values, you can do with a velocity-automation-lane in the track view, though

Just go to the track and select clip->clip automation->velocity and create the fade with the lane. This won't overwrite the values in the clip, but gain or reduce the values you've edited in the PRV

Thanks loptec, and thanks for acknowledging the difference between what has been suggested and motivated by the desire to help me, and what I'm asking for. There are ways to do some of what I am requesting, but none that are as easy as what I've seen elsewhere.

I fully understand that it is not possible for Cakewalk to please everybody, and that some requested features are more in overall demand than others, and that Cakewalk has to respond to demands within the parameters of its programming capacity.

I'd much rather request than complain. Complaining can easily become chronic. To turn an old cigarette commercial on it's ear, I'd rather switch than fight. If it turns out there's a DAW that works better for what I do, then I have to decide if I'm willing to hang in there with what I have in Sonar or spend the money to make a change. And whatever I use, no one DAW will fit all my preferences perfectly.

No worries. My comments are intended to be constructive.

john6448



 
1. Easier articulation management. I like what Cubase does with articulation lanes. It is very helpful for orchestral arrangements.
 

I picked up a great tip for solving this issue on the EWQLSO forum


You set up a drum map in which all the articulations for a particular instrument in EWQLSO where all the keyswitches get mapped.


My prv for each instrument now consists of a drum map for the artics at the top and the note prv screen below. It's SO easy to a) see exactly what you're doing and b) keeps the keyswitch data well away from your note pane and c) makes switching artics an absolute doddle!


Yep, it means I spent about 3/4 nights creating drum maps - 1 for each instrument and about 3 separate ones for percussion, I think there were over 40 maps in the end - but when I finished I just saved it as my default orchestral template (I do not want to have to do that again!)

Thanks for the suggestion, Bristol_Jonesy.

I take it you're saying that a drum map track takes up less vertical space than a traditional clef, and that's why it's better than using note keyswitching on a clef? Am I hearing you correctly?

Oh no, it's nothing to do with vertical space (although thinking about that for a moment - whilst the clef itself is fairly small, once you add in the Staff View Window size, there's nowt much to choose between a drum map 7 a clef)

I find it incredibly easy just for management of the composition itself -  remember also that a drum map gives you the added bonus of being able to mute/solo notes - in this case artics - on the fly.

This is simply not possible in an ordinary prv, nor the Staff View. 

Also, viewing keyswitch data in a clef can be - it's not note data per se, whereas with a drum map you can assign a meaningful name to each note/articulation, so you can instantly see whether you're working Legato, Marcato, Stacatto etc just by looking at it

Bristol_Jonesey

john6448




1. Easier articulation management. I like what Cubase does with articulation lanes. It is very helpful for orchestral arrangements.

I picked up a great tip for solving this issue on the EWQLSO forum


You set up a drum map in which all the articulations for a particular instrument in EWQLSO where all the keyswitches get mapped.


My prv for each instrument now consists of a drum map for the artics at the top and the note prv screen below. It's SO easy to a) see exactly what you're doing and b) keeps the keyswitch data well away from your note pane and c) makes switching artics an absolute doddle!


Yep, it means I spent about 3/4 nights creating drum maps - 1 for each instrument and about 3 separate ones for percussion, I think there were over 40 maps in the end - but when I finished I just saved it as my default orchestral template (I do not want to have to do that again!)

Wow! That's really smart!
Thanks for the tip! :D