X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fhandling-overlapping-notes.html;h=4cc371e1f74e5b4c6d8948098e8209c508f20ef6;hb=e8fed73cb5dcb9d6bc815dc7cd76fe39e13464e2;hp=d55109ab27be7996f90e8f4b4c309b3b02721b8b;hpb=dfec6899ef2a121ccf2ff1d47008e7ac4844cf70;p=ardour-manual diff --git a/include/handling-overlapping-notes.html b/include/handling-overlapping-notes.html index d55109a..4cc371e 100644 --- a/include/handling-overlapping-notes.html +++ b/include/handling-overlapping-notes.html @@ -1,40 +1,40 @@ - +
- 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 + 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 + 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.
-never allow them | +Edits that would create note overlaps are not allowed |
---|---|
don't do anything in particular | +Ardour leaves overlapping notes alone—the behaviour of a MIDI receiver (plugin or hardware) is undefined |
replace any overlapped existing note | +When one note is moved to overlap another, remove the one that wasn't being moved |
shorten the overlapped existing note | +When one note is moved to overlap another, shorten the one that wasn't moved so that there is no overlap |
shorten the overlapping new note | +When one note is moved to overlap another, shorten the one that was moved so that there is no overlap |
replace both overlapping notes with a single note | +When one note is moved to overlap another, merge them both to form one (longer) note |
- Changing the option in use will not retroactively make changes—it will + 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. + 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.