X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fhandling-overlapping-notes.html;fp=include%2Fhandling-overlapping-notes.html;h=eebe24ec16691de74c9ad0bc15fde6540e9a4fb1;hb=2098e011e638b5c86c56e68df7757975fc4d728f;hp=0000000000000000000000000000000000000000;hpb=0e127ce41d7120d505f3aa9ae18dce679f403a3f;p=ardour-manual diff --git a/include/handling-overlapping-notes.html b/include/handling-overlapping-notes.html new file mode 100644 index 0000000..eebe24e --- /dev/null +++ b/include/handling-overlapping-notes.html @@ -0,0 +1,41 @@ + +
+ Every MIDI note consists of two messages, a NoteOn and a NoteOff. Each one + has a note number and a channel (also a velocity, but that isn't relevant + here). The MIDI standard stresses that it is invalid to send a second NoteOn + for the same note number on the same channel before a NoteOff for the first + NoteOn. It is more or less impossible to do this with a physical MIDI + controller such as a keyboard, but remarkably easy to trigger when editing + in a DAW - simply overlapping two instances of the same note will do it. +
++ Ardour offers many options for how to deal with instances where you overlap + two instances of the same note. Which one to use is a per-session property + and can be modified from Session > Properties > Misc > MIDI + Options. +
+ ++ Changing the option in use will not retroactively make changes — it will + only affect new note overlaps created while the option remains chosen. +
++ Ardour does not check for note overlaps across tracks or even across regions. + If you create these, it is your responsibility to deal with the consequences. +
+ +