Keith OHara k-ohara5...@oco.net writes:
That programmer who added the code didn't know about Lilypond's
engraver/performer method of routing events and property-changes to
output, and didn't know much about midi, so the data flow doesn't make
much sense in the context of Lilypond and MIDI.
Reviewers: Keith,
https://codereview.appspot.com/249980043/diff/1/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
https://codereview.appspot.com/249980043/diff/1/Documentation/notation/input.itely#newcode3279
Documentation/notation/input.itely:3279:
On Mon, 06 Jul 2015 15:19:20 -0700, tdanielsmu...@googlemail.com wrote:
Setting
midiChannelMapping to 'voice often prevents the context properties
from having effect.
Doesn't the paragraph under 'voice above explain explicitly what
happens? That seems better than the rather vague often
Sorry I'm late.
You might still slip in a correction, or just remove mention of
midiChannelMapping='voice since we haven't found a use for it.
https://codereview.appspot.com/249980043/diff/1/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
