Moves all functions related to the `position' property of beam to beam-quanting.cc.

[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 10b793aaaf327226033b59a91592fbd53cf37f30..d1fac5e770142ee07cb92fa0287a5e205b810e1a 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,12 +4,12 @@
 %% and then run scripts/auxiliar/makelsr.py
 %%
 %% This file is in the public domain.
-\version "2.12.2"
+\version "2.14.0"
 
 \header {
   lsrtags = "contexts-and-engravers, midi"
 
-%% Translation of GIT committish: 91eeed36c877fe625d957437d22081721c8c6345
+%% Translation of GIT committish: 70f5f30161f7b804a681cd080274bfcdc9f4fe8c
   texidoces = "
 Al producir una salida MIDI, el comportamiento predeterminado es que
 cada pentagrama representa un canal MIDI, con todas las voces de dicho
@@ -48,7 +48,8 @@ deux canaux MIDI différents, chacun étant affecté de son propre
 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 track.
+are only 16 available per MIDI port, and most devices support only one
+port.
 
 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