Merge remote-tracking branch 'origin/master' into translation

[lilypond.git] / Documentation / snippets / changing-midi-output-to-one-channel-per-voice.ly

diff --git a/Documentation/snippets/changing-midi-output-to-one-channel-per-voice.ly b/Documentation/snippets/changing-midi-output-to-one-channel-per-voice.ly
index 94412beeef13471f62dc92cb5418a470f9961977..f817d558bbcfc17eafde645a38f5c0888948fca1 100644 (file)
--- a/Documentation/snippets/changing-midi-output-to-one-channel-per-voice.ly
+++ b/Documentation/snippets/changing-midi-output-to-one-channel-per-voice.ly
@@ -4,7 +4,7 @@
 %% and then run scripts/auxiliar/makelsr.py
 %%
 %% This file is in the public domain.
-\version "2.19.2"
+\version "2.18.0"
 
 \header {
   lsrtags = "contexts-and-engravers, midi, real-music"
@@ -13,8 +13,7 @@
 When outputting MIDI, the default behavior is for each staff to
 represent one MIDI channel, with all the voices on a staff amalgamated.
 This minimizes the risk of running out of MIDI channels, since there
-are only 16 available per MIDI port, and most devices support only one
-port.
+are only 16 available per track.
 
 However, by moving the @code{Staff_performer} to the @code{Voice}
 context, each voice on a staff can have its own MIDI channel, as is
@@ -26,7 +25,6 @@ two MIDI channels are created, each with a different
   doctitle = "Changing MIDI output to one channel per voice"
 } % begin verbatim
 
-
 \score {
   \new Staff <<
     \new Voice \relative c''' {
@@ -36,8 +34,8 @@ two MIDI channels are created, each with a different
       \time 2/2
       r2 g-"Flute" ~
       g fis ~
-      4 g8 fis e2 ~
-      4 d8 cis d2
+      fis4 g8 fis e2 ~
+      e4 d8 cis d2
     }
     \new Voice \relative c'' {
       \set midiInstrument = #"clarinet"