lilypond-user
[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: Wed, 6 Oct 2010 23:38:31 +0100


Keith E OHara wrote Wednesday, October 06, 2010 9:40 AM


I no longer see any reason to use instrumentCueName for the labels that identify the instrument playing cue notes. Doing so makes it easy to make subtle errors, and offers no advantage over \tag '#part s4*0^\markup\tiny"oboe"

The instrumentCueName is not preserved for re-use next time we cue that instrument; we have to re-\set it each time. It is not automatically placed according to the CueVoice direction; one needs to manually override the #'direction, of the InstrumentSwitch grob. It is not always placed near the first cue note, but rather at the moment where it is \set. It is printed even where killCues remove the cue notes; one needs to \tag it to keep it off the score.

It seems instrumentCueName is primarily intended for labeling the instrument a player switches to, on that player's part. ('CueName' does seem an odd think to call this particular label.) You store it once with \addInstrumentDefinition along with the other things that should change at the same time, and re-use it every time the player needs to pick up that instrument. Using instrumentCueName to label cue notes is a perversion of its intended purpose.

All this is true.

Now, maybe it would be nice if addQuote stored a label, like addInstrumentDefinition does, to be printed on each \cueDuring and supressed by \killCues, but things don't work that way now.

I think this would be a good enhancement request, probably not too
difficult to implement.  It could even use the name given \addQuote
as the name of the quoted music.  If implemented, the name should
be printed as a new grob so it's appearance could be easily
controlled, CueName maybe.

Unless somebody points out redeeming value to using instrumentCueName, I'll sleep on it a couple days then suggest to Trevor specific cuts from the documentation. My motivation is to save some new users from the confusion I went through.

OK.  I'll see what you suggest.

Trevor





reply via email to

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