X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fedit-midi.html;h=cccfb9545bb455a4300baf83df432affbb796259;hb=182a1f8dfcc6ddb8a45b257beca8d70a4d63faf3;hp=24c48cb9d99cfed35e6fceab4c77c3f54b10436a;hpb=ca8c53473dfbcb7d4b483a5ce792bbf4b5caffe8;p=ardour-manual
diff --git a/include/edit-midi.html b/include/edit-midi.html
index 24c48cb..cccfb95 100644
--- a/include/edit-midi.html
+++ b/include/edit-midi.html
@@ -25,14 +25,15 @@
Region(s), though, can be copy-pasted just as with audio.
- All MIDI I/O is done via JACK for sample accurate timing and maximal
- efficiency when communicating with external software synthesizers.
+ 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.
- Every MIDI track has its own JACK MIDI port for input; it may have an
+ 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.
Full automation for MIDI tracks, integrated with the handling of all MIDI