Velocity of new note in midi editor doesn't match velocity of previously edited note

The velocity of a newly inserted note in the midi editor doesn't match the velocity of the previously edited one: This bug has been in REAPER forever, and it is very annoying because you essentially need twice the clicks to set up a melody. (one after each note to correct the broken velocity) If this is a user error instead, I apologize. I am happy to hear suggestions on how I am supposed to use the midi editor instead to avoid this issue.

Ok. So is this still a bug, or intended behavior? If intended, what is the purpose/use case of the current way it behaves?

As far as I can remember it never used to work with the velocity lane. It does work though if you use the velocity handle on the note, or alt + drag on a note for velocity changes (the latter is what I do most of the time, instead of travel down to the lane and back up to draw the next note). Or just click on an existing note that has the velocity you want to use for your next one. It also works with click on the piano keys, as Ollie mentions, but I would rather switch it off there. Although the idea - click on the keys to pre-listen until you're cool with the velocity and pitch you hear and then insert your note - is well meant. I don't know whether the behavior on the velocity lane is intentional, but I do use it, as I do not always want the next note to have the velocity I just dialed in for another one. So I am pretty glad there is a way to change velocity without changing the current default for the next one, other than switch the whole feature off.

* Using the velocity bar in the lane doesn't work for me - REAPER won't correctly remember the velocity for the next note. * Using ALT+drag on the note itself however does. Consistency?? * Clicking the existing note works, but it is kind of unintuitive. After setting the first note and altering the velocity, I need to click it again which seems to do nothing (it was already selected obviously, since I just created it) but will actually fix REAPER forgetting about the velocity change. Confusing.. Conclusion: please fix that depending on the way I altered velocity, REAPER will sometimes remember it (e.g. ALT+drag) and sometimes not (drag of bar down in velocity lane)!

It could be argued that it is consistent because it consistently works for the methods mentioned and it consistently does not work for the lane. Now that you know how it works, you could use it to your benefit. I am not against including the lane into the feature, but would like to have the option to keep working like I am used to (use the lane when I don't want the new velocity to be used) - I'd request it to be optional, please.

Any chance this inconsistency will be reviewed? Similar to the time bar at the top where the main window will use a click to make the edit cursor jump there always, while in the midi editor it will do "scrubbing" of the playback cursor if it's in the way which can be very confusing if you're not expecting it, this is an annoying inconsistency of how stuff works in REAPER. While this might be useful to various seasoned people, those inconsistencies are simply confusing and irritating to newcomers and even year-long users like me before they find out it's intended and why. Why not make it an option for people who need it, and go with a more reasonable consistent default behavior? (in this case, to always remember the velocity of the previous altered note no matter which method of the UI was used to change it)

THIS ↑↑↑↑