Forums
My feature request relates to selected notes in the midi editor.
I ask that you consider adding 4 new keybindings to change velocity values for a selected note or notes.
One pair to increase/decrease velocity value in units of 10, and one pair to increase/decrease velocity value in units of 1.
Would prefer the units to be "midi" units, (0-127) but if pixels is easier, or more reliable, then that's ok too.
Alex.
re. raising/lowering velocity values in the midi editor
hi, this is not going to fly as is
the most I can do for the time being is about using the up/down keys to do the same, but it's not there yet
cheers
Understood.
Understood.
re. raising/lowering velocity values in the midi editor
hi,
something already there, in qtractor >= 0.9.39.20git.3e9617 [develop]
regards
Ok, thanks.
Ok, thanks.
Just built and tested.
Just built and tested.
When using the up/down arrows to change the velocity, there seems to be a conflict with "move a note up and down then press enter to confirm its new position". There seems to be two actions for each note up and down, Alt + up/down, and up/down.
I can get the event value changes to work, but only after clicking on the event in the CC lane with the mouse.
Possible duplication of bindings, with the new event value actions?
Alt + up/down is fine for moving the note.
But if the new up/down actions for changing event values for a selected note(s) are, by default, focused in the CC lane, then whichever note we select to modify the event value of, we can do that immediately, without having to click with the mouse in the CC lane first.
re. raising/lowering velocity values in the midi editor
yes, the new up/down value changes only works iif the selection is started or focused on the event value pane (the CC pane as you say).
sorry, this is in fact intentional and the only way to make it work as is.
besides that, what other annoyances have you found? ;)
ps. 0.9.39.21git.61197c [main] is out with some impromtu fixes on this topic, but again, it's just fixes, nothing else.
Within the limitations of
Within the limitations of what you've described, I'd say it's ok. Didn't find anything else that broke, or behaved oddly. Thanks Rui, for adding this.
Add new comment