lilypond-devel
[Top][All Lists]
Advanced

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

Re: anybody understand the instrumentCueName docs?


From: Trevor Daniels
Subject: Re: anybody understand the instrumentCueName docs?
Date: Tue, 19 Oct 2010 21:34:05 +0100


Keith E OHara wrote Monday, October 18, 2010 11:40 PM

I suggest (diff attached) removing the part about instrumentCueName in favor of a fuller example for \killCues. The manual teaches markup elsewhere; the challenge with cue-note labels is to let the label appear with the cue notes in parts, but not in the score.

Your patch is a definite improvement, IMO.  If no one objects soon I
shall push it. I think it might be further improved by a little more text, as someone coming to this for the first time might still find it rather
difficult as it is.  But I'm happy to add that.

(For future reference, please avoid trailing whitespace, and if possible
save the diff or patch with unix line endings - makes life easier :)

Related changes (in the same diff) that you can take if you like :
1) \cueDuring #"flute" may be used *before* \addQuote "flute" \flute appears in the source file, and knowing that empowers users to write parts that quote each other.

It's worth mentioning this - I'll add it.

2) Two pieces of instruction were a bit vague :
"It is possible to tag cued parts with unique names in order to process them in different ways." "[...] when cue notes end, the name of the original instrument should be printed, and any other changes introduced by the cued part should be undone. This can be accomplished by using @code{\addInstrumentDefinition}"

I think the intent was to teach how to handle clef changes (as in the thread <http://lists.gnu.org/archive/html/lilypond-user/2008-02/msg00278.html>)

As replacement I suggest, after the fuller \killCues example, :
 +The @code{\killCues} command removes only the notes and events
 +that were quoted by @code{\cueDuring}.  Other markup associated
+with cues, such as clef changes and a label identifying the source
 +instrument, can be tagged for selective inclusion in the score;
 +see @ref{Using tags}.  Clef changes and instrument labels can be
 +collected into an instrument definition for repeated use, using
 address@hidden described in @ref{Instrument
 +names}.

I think we need a clearer description about using instrument definitions in relation to cued notes (at least I do!) I shall need to investigate this
aspect further.  Unless you can provide an example ... ?

3) The description of transposedCueDuring might have been wrong (or I interpreted it wrongly) in the case of transposing instruments. My suggested replacement comes from experiment and inspection of quote-iterator.cc.

Happy to take this.

Trevor





reply via email to

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