Did anyone mention the Control Bar?
 
Select the notes you want in PRV and change the value in the Event module.
 
If they have differing values you need to "normalize" them to a common value 1st, then change to the target value.
 
Sometimes the curser thingy doesn't work so well on short notes unless you zoom way in on them.
 
 
Steve

Kev999

john6448
 
...Easier PRV view editing of velocities...

In Sonar 6 it was possible to grab the top of a velocity tail and drag it up or down to adjust the height.  I found this useful as an easy way to do fine tweaking of individual note velocities.  I was surprised and annoyed to find that it was no longer possible after upgrading to version 7.  I can't imagine why they removed this feature. 

The problem you get with grabbing the top of a velocity tail and dragging it up or down is if you've for example have a chord and just want to change the velocity of one of the notes; With this method it would be impossible to choose which note's velocity tale you want to select and change, since they're all just stacked together and show as one single tail.

The feature to grab the top of a note and drag up or down I find much better, since it's essentially the same function except you never get this problem. Just grab the top of any note in the chord (with the smart tool) and drag up or down :)

Loptec

Kev999

john6448

...Easier PRV view editing of velocities...

In Sonar 6 it was possible to grab the top of a velocity tail and drag it up or down to adjust the height.  I found this useful as an easy way to do fine tweaking of individual note velocities.  I was surprised and annoyed to find that it was no longer possible after upgrading to version 7.  I can't imagine why they removed this feature. 

The problem you get with grabbing the top of a velocity tail and dragging it up or down is if you've for example have a chord and just want to change the velocity of one of the notes; With this method it would be impossible to choose which note's velocity tale you want to select and change, since they're all just stacked together and show as one single tail.

The feature to grab the top of a note and drag up or down I find much better, since it's essentially the same function except you never get this problem. Just grab the top of any note in the chord (with the smart tool) and drag up or down :)

a.  I often adjust chords so that the notes each hit at slightly different times.  Piano chords in particular sound much better this way.  Whichever note is loudest or most prominent, I leave exactly on the beat.

b.  If the notes are all concurrent and the velocities are all different, then (in Sonar 6) the tops of each different tail can be identified by running the mouse pointer up and down and seeing the cursor change. 

c.  If the notes are all concurrent and the velocities are all the same value, then the current method of adjustment is definitely easier.  But I see no reason for getting rid of the tail adjustment feature just because another method was introduced.  Both methods could exist together happily.

Kev999

Loptec

Kev999

john6448

...Easier PRV view editing of velocities...

In Sonar 6 it was possible to grab the top of a velocity tail and drag it up or down to adjust the height.  I found this useful as an easy way to do fine tweaking of individual note velocities.  I was surprised and annoyed to find that it was no longer possible after upgrading to version 7.  I can't imagine why they removed this feature. 

The problem you get with grabbing the top of a velocity tail and dragging it up or down is if you've for example have a chord and just want to change the velocity of one of the notes; With this method it would be impossible to choose which note's velocity tale you want to select and change, since they're all just stacked together and show as one single tail.

The feature to grab the top of a note and drag up or down I find much better, since it's essentially the same function except you never get this problem. Just grab the top of any note in the chord (with the smart tool) and drag up or down :)

a.  I often adjust chords so that the notes each hit at slightly different times.  Piano chords in particular sound much better this way.  Whichever note is loudest or most prominent, I leave exactly on the beat.

b.  If the notes are all concurrent and the velocities are all different, then (in Sonar 6) the tops of each different tail can be identified by running the mouse pointer up and down and seeing the cursor change. 

c.  If the notes are all concurrent and the velocities are all the same value, then the current method of adjustment is definitely easier.  But I see no reason for getting rid of the tail adjustment feature just because another method was introduced.  Both methods could exist together happily.

For sure, I know what you mean.. (about the chords) I'm a pianoplayer myself.

It's just that you said that; you got suprised and annoyed to find that it wasn't possible to fine tweak individal note velocities since version 7.
This is where you and I think differently..

And even though they could have both features implemented I see no reason for it. It's just as easy just to grab one or more notes and change the velocity now as it was back then.

Isn't it just a matter of getting use to it?

And even though I'm a pianoplayer this isn't the only instrument I play. So I think it's better to have a feature that works in all scenarios instead of having to change how you work depending on how the notes are arranged. 

Loptec

And even though they could have both features implemented I see no reason for it. It's just as easy just to grab one or more notes and change the velocity now as it was back then.

Isn't it just a matter of getting use to it?

I am used to it by now, but I definitely preferred the original method.  It seems more direct when you are adjusting the height of the tail to actually grab the tail itself rather than click on a point above the note with which the tail is associated, which may be some distance away.