View Issue Details

IDProjectCategoryView StatusLast Update
0004324ardourfeaturespublic2020-04-19 20:15
Reporternandinga Assigned Todrobilla  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
Target Version3.X 
Summary0004324: A3 should have MIDI velocity editing facilities
DescriptionNot sure if it is the time now (on alpha10) but I think this is important:

It is crucial for a MIDI editor to be flexible about velocity values, in order to produce more close-to-reality results.

MIDI velocity values normally vary not individually but in relation to its neighbors e.g. build-ups, accents, rolls, etc. This is why a velocity editor should offer the possibility to edit values of groups, as opposed to note-by-note editing.

This is what regular "bar graph velocity editors" allow, when e.g. drawing an ascending line to create a build-up, or "humanizing" velocities (randomly increasing/decreasing the values for selected notes).

Several changes are needed for implementing one such editor in A3, but there might be other alternatives. I can think of one, and that is working with dialogs over selected notes.

With this approach we could select a bunch of notes, right-click and select from the menu:

- Randomize velocities: Dialog asks the velocity range.
- Build-up: Dialog asks min and max velocities, and maybe shape of the curve.

Changing channels (current right-click assignment) is also important for expressiveness, so we could leave it as is but with a key modifier.

Also in the menu we could offer other non velocity related options like the following:

- Humanize (randomizing the position in time of the notes)
- Transpose
- Quantize
- even copy&paste?

I understand that every one of this options is a feature itself, but they don't need to be implemented at once. This approach can give us functional flexibility while reducing the development effort. If the need or the will to develop a graphical velocity editor of any sort arises later, the algorithms could be reused, so only the dialogs would be thrown away.

This is probably a feature to take into account for the release of A3, that will be offering MIDI sequencing capabilities as one of its main improvements.
Tags3.0, GUI, Midi, right click, Sequencer


related to 0005608 resolvedpaul Velocity track idea 
related to 0005796 closeddrobilla Midi default velocity value 
related to 0004449 new Simple MIDI velocity interpolation 
related to 0002747 new Humanizer for MIDI editor 
related to 0003243 closeddrobilla Velocity Slider 
related to 0005832 closeddrobilla Midi velocity bar-graph editor; separate pattern editor? 



2011-09-20 14:10

reporter   ~0011542

Some related issues:
0003243: Velocity Slider
0003561: Percussion Editor
0004323: Conflict with CTRL+scrollwheel for both zooming and midi velocity change.
There was also a proposal on making MIDI note editing dialog to work with a group of selected notes, but I couldn't find it.


2011-09-26 23:51

reporter   ~0011576

I totally agree that the MIDI region context menu needs some work. A bar graph velocity editor could be nice but that sounds a bit too flash to make it into 3.0 now maybe. Instead I'd like to see an 'Interpolate' option added to the context menu when you right-click a range of notes with sufficiently varying velocities at either end of the selection.


2011-09-28 12:51

reporter   ~0011597

This is the other bug I comented before:

0004096: MIDI note edit dialog should work with multiple notes selected


2014-01-22 10:54

reporter   ~0015605

Separate bar graph velocity editor/midi pattern editor feature request:


2014-12-23 14:22

reporter   ~0016078

See also ,


2014-12-28 23:09

developer   ~0016130

There is now (as of 3.5-4112-g4973ddc) a context menu for editing the selection only (actually this is what the usual MIDI edit context menu was actually doing, but now it's clear).

From this you can quantize, legatize, or use the new transform window to do things like velocity crescendos and velocity or time humanization. It probably needs some "presets" for easily doing these common things, but it's relatively straightforward to figure out how to use the thing (in my ridiculously biased opinion, anyway).

Since this addresses all the main points in this ticket except a separate velocity bar graph editor, and there is a separate ticket for that, I'm considering this one closed.


2020-04-19 20:15

developer   ~0022748

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2011-09-20 14:01 nandinga New Issue
2011-09-20 14:02 nandinga Tag Attached: 3.0
2011-09-20 14:02 nandinga Tag Attached: GUI
2011-09-20 14:02 nandinga Tag Attached: Midi
2011-09-20 14:02 nandinga Tag Attached: right click
2011-09-20 14:02 nandinga Tag Attached: Sequencer
2011-09-20 14:10 nandinga Note Added: 0011542
2011-09-20 22:18 cth103 cost => 0.00
2011-09-20 22:18 cth103 Target Version => 3.0-beta1
2011-09-26 23:51 danboid Note Added: 0011576
2011-09-28 12:51 nandinga Note Added: 0011597
2011-11-15 15:00 cth103 Target Version 3.0-beta1 => 3.0
2012-01-18 18:48 paul Target Version 3.0 => 3.X
2014-01-22 10:54 naught101 Note Added: 0015605
2014-01-22 12:21 x42 Relationship added related to 0005832
2014-01-22 12:23 x42 Relationship added related to 0005608
2014-01-22 12:24 x42 Relationship added related to 0005796
2014-01-22 12:27 x42 Relationship added related to 0004449
2014-01-22 12:28 x42 Relationship added related to 0002747
2014-12-23 14:22 naught101 Note Added: 0016078
2014-12-26 09:10 x42 Relationship added related to 0003243
2014-12-28 23:09 drobilla Note Added: 0016130
2014-12-28 23:09 drobilla Assigned To => drobilla
2014-12-28 23:09 drobilla Status new => resolved
2014-12-28 23:09 drobilla Resolution open => fixed
2020-04-19 20:15 system Note Added: 0022748
2020-04-19 20:15 system Status resolved => closed