How to adjust velocity of all selected MIDI notes? (FIXED)

[TryingToMakeMusic]

I need to raise the velocity for all selected MIDI notes, but when I try, this happens.

I'm just doing a regular click-and-drag on the velocity bar. I'm not doing a click-and-release on that one bar before doing the drag.

(P.S. how do I make the LICEcap GIF appear inline instead of as an attachment?)

[michael diemer]

I'm still a noobie, but I do this like so: select the notes, go to Event List, hit Control+F2, which brings up a dialogue box. You can then change the velocity of all notes there. I sometimes find that the length may also get changed when doing this, so I just adjust that as well using the same method.

[TryingToMakeMusic]

Originally Posted by michael diemer

I'm still a noobie, but I do this like so: select the notes, go to Event List, hit Control+F2, which brings up a dialogue box. You can then change the velocity of all notes there. I sometimes find that the length may also get changed when doing this, so I just adjust that as well using the same method.

Thanks, that works for me. I still hope there's a way to do it with the mouse, since I'd like to immediately hear the adjustment I'm making while dragging through a range of values.

[DarkStar]

Select the notes to change as you have done; then drag the mouse over them in the Velocity lane, starting from an empty area:




For in-line images, upload it to imgur.com first, but not if they are big. Have a look at: How to post screenshots (in Post #2)

[TryingToMakeMusic]

Originally Posted by DarkStar

Select the notes to change as you have done; then drag the mouse over them in the Velocity lane, starting from an empty area: ...

That is a good technique to know, but it's not what I'm looking for in this case. I want to keep all the selected velocities equal to each other, while changing all selected velocities by a constant value.

Originally Posted by DarkStar

For in-line images, upload it to imgur.com first, but not if they are big. Have a look at: How to post screenshots (in Post #2)

Thanks.

And off topic, thanks for your help on Melda forum. I don't post there, but I read. I don't understand his Time-Graphs either. Not clear what the labels apply to. Maybe I'll sign up there to agree with you next time you ask him to improve that feature.

[DarkStar]

Oops, I mis-read.

Select the notes, right-click one of them, select 'Note Properties', then type in the desired velocity, or + followed by a number to increase them all by that number, or ...

[Csabb]

Alt + mouse drag while the notes are selected. It keeps the relative velocity intact.

EDIT: sorry, no need for alt, just drag the vertical line in one of the notes. The cursor will change.

[Reason]

Originally Posted by Csabb

Alt + mouse drag while the notes are selected. It keeps the relative velocity intact.

EDIT: sorry, no need for alt, just drag the vertical line in one of the notes. The cursor will change.

This. Select your notes and hover your cursor over one of the selected notes, within the note boundaries. You should see the cursor change to a vertical arrow pointing up and down. Drag up or down to change velocity. The color of the note will change accordingly and there's also a line in the middle that changes, as well as the number, visibility of these last two depending on your zoom level.

Other tricks
Alt click a note on the "piano" on the far left to select all notes with that value
Hold and drag your alt click down the same piano keyboard to quickly select all notes
Lightly salt your rice krispie treats when stirring in the marshmallows, it's delicious

[FnA]

Originally Posted by TryingToMakeMusic

I need to raise the velocity for all selected MIDI notes, but when I try, this happens.

I'm just doing a regular click-and-drag on the velocity bar. I'm not doing a click-and-release on that one bar before doing the drag.

I think it should do that by default. I've never had it otherwise. Maybe you changed mouse modifiers in preferences? Maybe a problem with your mouse? Can you move all selected notes without losing selection? It seems easy to get a conflict between various mouse modifiers...

Originally Posted by TryingToMakeMusic

(P.S. how do I make the LICEcap GIF appear inline instead of as an attachment?)

Push the quote button on my post to see how I used img and /img in brackets to frame it. Some more info at bottom left corner of this forum page.

[Pet]

My 2 cents:

Select as in the gif, then shift+mousewheel in the CC-lane.

You can also directly select the velocity bars in the CC-lane by dragging right-clicked mouse over the desired CC's. So you can stay in the CC-lane with your cursor for further adjustments.

That's how I do it.
Peter

[TryingToMakeMusic]

Originally Posted by Pet

My 2 cents:

Select as in the gif, then shift+mousewheel in the CC-lane.

You can also directly select the velocity bars in the CC-lane by dragging right-clicked mouse over the desired CC's. So you can stay in the CC-lane with your cursor for further adjustments.

That's how I do it.
Peter

Shift-mousewheel works for me. Excellent, thank you.

[TryingToMakeMusic]

Originally Posted by Csabb

...drag the vertical line in one of the notes. The cursor will change.

That works, thanks; but I had to turn that vertical-line off after accidentally moving it too many times. Now I keep it off, as in my gif.

[TryingToMakeMusic]

Originally Posted by FnA

I think it should do that by default. I've never had it otherwise. Maybe you changed mouse modifiers in preferences? Maybe a problem with your mouse? ... It seems easy to get a conflict between various mouse modifiers...

The method shown in my gif works for a set of notes not overlapping in time. The problem only happens when notes are stacked vertically all at the same time.

Originally Posted by FnA

Can you move all selected notes without losing selection?

Yes.

Originally Posted by FnA

Push the quote button on my post to see how I used img and /img in brackets to frame it. Some more info at bottom left corner of this forum page.

Thank you.

[DogBBQ]

I used to be able to select a group of notes like in the gif and click on one of the velocity bars and it would move all selected notes velocities

But since one of the recent updates i can no longer do this basic edit

I haven't checked with the latest 5.29 release

[TryingToMakeMusic]

Originally Posted by TryingToMakeMusic

The method shown in my gif works for a set of notes not overlapping in time. The problem only happens when notes are stacked vertically all at the same time.

Further testing (just moved to v5.29) shows that Reaper's behavior is random:

[DogBBQ]

Originally Posted by TryingToMakeMusic

Further testing (just moved to v5.29) shows that Reaper's behavior is random:

This is what exactly happens to me

Strange Behavior, not sure what update caused it!

[EvilDragon]

And again, I cannot duplicate that behaviour over here...

[TryingToMakeMusic]

Here is a Reaper project like the one in my gif, if anyone wants to test it:

https://drive.google.com/open?id=0B5...VA3YUNxQl8zWWs

[FnA]

Velocity lane has been worked on for 5.29. Have you updated to try it yet? It looked like some users were having different behaviors in their velocity lane from what I gathered from a recent pre-release thread.

On 5.28 I can adjust all notes in chords made with snap turned on. Even if they are copy/pasted several times and all selected.

[TryingToMakeMusic]

Originally Posted by FnA

Velocity lane has been worked on for 5.29. Have you updated to try it yet?

I updated from 5.28 to 5.29 at this point in the thread (when DogBBQ reminded me that 5.29 was out):

Originally Posted by TryingToMakeMusic

just moved to v5.29

Originally Posted by FnA

On 5.28 I can adjust all notes in chords made with snap turned on. Even if they are copy/pasted several times and all selected.

Thanks for checking. If you are curious, please try it in the Reaper project I posted in my previous post? It's a super-small project, just for testing for this.

[FnA]

Don't know what to tell ya...

[TryingToMakeMusic]

You're selecting different notes than I am, though:

Originally Posted by TryingToMakeMusic

When I select notes like you've done, I get the same results as you get. But what if you selected only the notes I'm selecting in my gif?

[FnA]

You are correct. I can get the same behavior as you show by selecting the same notes.

Bug.

[TryingToMakeMusic]

Originally Posted by FnA

You are correct. I can get the same behavior as you show by selecting the same notes.

Bug.

Interesting. Thanks for your efforts to investigate.

This workaround is available:

Originally Posted by Pet

Select as in the gif, then shift+mousewheel in the CC-lane.

I actually like it better than dragging bars.

[FnA]

You can drag the note too. Alt drag by default, I believe.

I'm not putting that rpp in my non portable install. I can't seem to make something similar happen in it. (5.27. Sorry, said 5.28 earlier). I used portable install I use for pre testing with 5.29 pre 2.

edit Windows 7 Reaper 64

[TryingToMakeMusic]

Originally Posted by FnA

You can drag the note too. Alt drag by default, I believe.

That works too. Thanks.

[Pet]

Originally Posted by TryingToMakeMusic

Here is a Reaper project...

Confirmed.
I tested it on a untouched 5.29 portable and it behaves exactly like in your gif. Then I tested it on 5.30pre2 ("full" install) and there is something weird happening too, but somehow different. I try to post a gif soon to show that.
I also noticed that it makes a difference, if you select the notes in the Editor/Notes window or in the CC-lane...
It looks like it somehow has to do with whether you select the highest, the middle or the lowest notes.

[EDIT:] I think it is better to post this gif in the pre-forum.

Peter

[schwa]

Fixing for the next release, thanks for the report.

[TryingToMakeMusic]

Thanks Pet for the testing, and thanks Schwa.

[MikComposer]

Same things happens here. Glad it's going to be fixed. I was just starting this difficult track, and this shit started happening, I thought I'm gonna have to come up with new slurs towards reaper. Although, this shit shouldn't be happening already. How it is that every time the new update comes out, stuff that used to work well suddenly breaks up? Although I get that in this case, new algo to smooth out vel editing was made, so that fair enough.

@schwa Do you think you guys can leave tiny margin of active area when editing not selected velocity bars? Cause right now, when I edit one with ought grabbing it, if I just move 1px too much to the left, it activates editing of the previous cc bar, even if it is half of the bar earlier. So limiting active area to only half of a selected grid, or even better, half of the distance between neighboring bars, would make work so much more easier.

And you guys really need to think of those things. This is what most annoying about reapers interface, and it is annoying me for years on end. I have precise mouse, I am very fast with it, and I don't want to slow down - I don't want to get neurotic, to get things right. It works like that in any other software, whatever it is, but reaper: a dynamic active padding area is needed. So it's something to really think about.
The active padding area works like this: several pixels of padding are being activated for the object to which mouse cursor has got shortest distance, and deactivates when the cursor is either hovering over the object or is further away then padding value. When you have several button next to each other, the padding activation is still mouse distance dependent and weather it is over an object or not. So object cursor doesn't have to be exactly under a button or item for it to click it ( although due to how tight items are being placed, this would require it to have a specific smaller padding size), and padding up to around 5px would do i reckon.

[DogBBQ]

Thanks!!!

[chriscomfort]

As a side note, this is a nice workflow helper. I'm using Ctrl+Shift Mousewheel to
Edit: Adjust value for events (mousewheel/MIDI controller only)
Here's a gif showing it:
https://www.dropbox.com/s/dccslsq3yq...ocity.gif?dl=0