Re: Doc: NR section 3.5.x MIDI file creation tidy up (issue 120480043 by address@hidden)

[tdanielsmusic]

Hi James

This is definitely a big improvement, but I have a serious concern over
the confusion you've introduced about what is supported in basic
LilyPond and what is added by the articulate script.  I've tried to
indicate places where this confusion appears.  The clear statement
currently shown in NR 3.5.3 should be reinstated somehow, and reflected
accurately in the text.

Trevor



https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely
File Documentation/notation/input.itely (left):

https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely#oldcode2890
Documentation/notation/input.itely:2890: @end itemize
This information seems to have been lost or erroneously moved into the
section on articulate.ly.

https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely#oldcode2899
Documentation/notation/input.itely:2899: @end itemize
Note that these are the only entities modified by articulate.ly.

https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):

https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely#newcode2702
Documentation/notation/input.itely:2702: (#10) for drums.  Each channel
is allocated for each staff, so a score
Staves are assigned to channels in sequence, so a score ...

https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely#newcode2703
Documentation/notation/input.itely:2703: that contains more than fifteen
staves will result in the extra staffs
staffs -> staves

https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely#newcode2705
Documentation/notation/input.itely:2705: problem if the sharing staffs
have conflicting, channel-based, MIDI
staves

https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely#newcode2872
Documentation/notation/input.itely:2872: A full list of supported items
can be found in the script itself.  See
The list you've placed in the script is not correct.

https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely#newcode2889
Documentation/notation/input.itely:2889: A MIDI player that supports
pitch bend will be needed for Microtones.
This is nothing to do with articulate.ly

https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely#newcode2892
Documentation/notation/input.itely:2892: accent, marcato and portato.
These have nothing to do with articulate.ly

https://codereview.appspot.com/120480043/diff/180001/Documentation/notation/input.itely#newcode2894
Documentation/notation/input.itely:2894: Items that are not supported by
the @file{articulate} script:
Items that are not reflected in MIDI output, even with the
@file{articulate} script.

https://codereview.appspot.com/120480043/diff/180001/ly/articulate.ly
File ly/articulate.ly (right):

https://codereview.appspot.com/120480043/diff/180001/ly/articulate.ly#newcode46
ly/articulate.ly:46: % Rallentando, accelerando, ritard and 'a tempo'.
This list is misleading.  You've merged the list of items supported in
LilyPond without articulate.ly with the few added by articulate.ly,
which are just the last three.

https://codereview.appspot.com/120480043/