X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fedit-midi.html;h=cccfb9545bb455a4300baf83df432affbb796259;hb=9d40f142633d32b65f620491ace6f050672286e8;hp=70895a3090ad642fc81d1a8e3ce8877fb4873470;hpb=dfec6899ef2a121ccf2ff1d47008e7ac4844cf70;p=ardour-manual

diff --git a/include/edit-midi.html b/include/edit-midi.html
index 70895a3..cccfb95 100644
--- a/include/edit-midi.html
+++ b/include/edit-midi.html
@@ -8,17 +8,32 @@
 <ul>
   <li>
     All editing is done in-place, in-window. There is no separate piano roll
-    window or pane. Edit notes right where you see them.
+    window or pane. Edit notes right where they appear.
   </li>
   <li>
-    All MIDI I/O is done via JACK for sample accurate timing and maximal
-    efficiency when communicating with external software synthesizers.
+    MIDI, just like audio, exists in regions. MIDI regions behave like audio
+    regions: they can be moved, trimmed, copied (cloned), or deleted. Ardour
+    allows either editing MIDI (or audio) regions, or MIDI region content (the
+    notes), but never both at the same time. The <kbd class="menu">e</kbd> key
+    (by default) toggles between region level and note level editing
   </li>
   <li>
-    Every MIDI track has its own JACK MIDI port for input; it may have an
+    Editing note information in Ardour occurs in only a single region. There is
+    no way currently to edit in note data for multiple regions at the same time,
+    so for example notes cannot be selected in several regions and then all
+    deleted, nor can they be copied-and-pasted from one region to another.
+    Region(s), though, can be copy-pasted just as with audio.
+  </li>
+  <li>
+	When using jackd as the audio server for Ardour, all MIDI I/O is done
+	via JACK for sample accurate timing and maximal efficiency when communicating
+	with external software synthesizers. Otherwise, Ardour connects to midi
+	via the existing OS MIDI system.
+  </li>
+  <li>
+    Every MIDI track has its own MIDI port for input; it may have an
     arbitrary combination of audio and MIDI outputs, depending on the signal
-    processing in the track; the full flexibility of JACK connectivity is
-    present for MIDI just as it is for audio.
+    processing in the track.
   </li>
   <li>
     Full automation for MIDI tracks, integrated with the handling of all MIDI
@@ -30,7 +45,7 @@
     data).
   </li>
   <li>
-    There is a Normal and a  Percussive mode for note data editing.
+    There is a Normal and a Percussive mode for note data editing.
   </li>
   <li>
     The <dfn>scroomer</dfn> is a combination scroll/zoom tool for altering
@@ -41,22 +56,21 @@
 <h2>Notable Differences</h2>
 <ul>
   <li>
-    Fader (volume) control currently operates on transmitted MIDI data, not by sending CC
-    #7.
+    Fader (volume) control currently operates on transmitted MIDI data, not by
+    sending CC #7.
   </li>
   <li>
-    All note/data editing is per-region. There are no cross-region operations at this
-    time.
+    All note/data editing is per-region. There are no cross-region operations at
+    this time.
   </li>
   <li>
     By default, copying a MIDI region creates a <dfn>deep link</dfn>&mdash;both
-    regions share the same data source, and edits to the contents of
-    one will affect the other. To break this link, select
-    <kbd class="menu">MIDI &gt; Unlink from other copies</kbd> from the region
+    regions share the same data source, and edits to the contents of one will
+    affect the other. Breaking this link is done by selecting <kbd
+    class="menu">MIDI &gt; Unlink from other copies</kbd> from the region
     context menu, after which the selected region(s) will have their own copies
-    of <em>only</em> the data that they visually display on screen. You will not
-    be able to trim the region back its original length after an Unlink operation,
-    and the operation cannot be undone.
+    of <em>only</em> the data that they visually display on screen. The region
+    will no longer be trimmable back to its original length after an Unlink
+    operation, and the operation cannot be undone.
   </li>
 </ul>
-