X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fhandling-overlapping-notes.html;h=d55109ab27be7996f90e8f4b4c309b3b02721b8b;hb=dfec6899ef2a121ccf2ff1d47008e7ac4844cf70;hp=eebe24ec16691de74c9ad0bc15fde6540e9a4fb1;hpb=e6123839d20de4f903ed74820cc087fc8401f625;p=ardour-manual diff --git a/include/handling-overlapping-notes.html b/include/handling-overlapping-notes.html index eebe24e..d55109a 100644 --- a/include/handling-overlapping-notes.html +++ b/include/handling-overlapping-notes.html @@ -6,7 +6,7 @@ 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. + 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 @@ -19,7 +19,7 @@
- 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. If you create these, it is your responsibility to deal with the consequences.
-