lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Doc: Issue 4059: Document MIDI mapping and MIDI effects (issue 24998


From: tdanielsmusic
Subject: Re: Doc: Issue 4059: Document MIDI mapping and MIDI effects (issue 249980043 by address@hidden)
Date: Mon, 06 Jul 2015 22:19:20 +0000

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: @ref{MIDI channel mapping}).
On 2015/07/04 03:59:36, Keith wrote:
This is the part that doesn't work.  We could say
"the MIDI channel associated with the current Staff (or the current
the Voice if
you have moved the Staff_performer to the Voice context).  If you set
midiChannelMapping to 'instrument, all staves with the same instrument
are
affected when you set one of these context properties.  Setting
midiChannelMapping to 'voice often prevents the context properties
form having
effect."

Doesn't the paragraph under 'voice above explain explicitly what
happens?  That seems better than the rather vague "often prevents the
context properties ...".  There already is a reference back to that
explanation.

Trevor

Description:
Doc: Issue 4059: Document MIDI mapping and MIDI effects

  Based on original text supplied by Heikki Tauriainen

Please review this at https://codereview.appspot.com/249980043/

Affected files (+214, -4 lines):
  M Documentation/notation/input.itely





reply via email to

[Prev in Thread] Current Thread [Next in Thread]