Re: partcombine and instrumentSwitch

[Keith OHara]

eluze <eluzew <at> gmail.com> writes:

> Thomas Morley wrote
> > 
> > But while using separate voices, LilyPond prints the instrumentCueName
> > twice, too.
> > Or did I sth wrong?
> 
> if in the definition of instrumentSwitch in music-functions-init.ly you
> change 'Staff to 'Voice it only prints once.
> don't know if this has any impact in other instances.
> 

But the other aspects of the instrument definition need to affect the whole 
Staff.  Sometimes there is a clef change, and Jan-Peters' original example 
changed the short name that goes in front of the staff after each line break.

> \addInstrumentDefinition #"piccolo"
> #`((instrumentName . "Piccolo")
>   (shortInstrumentName . "Pc.")
>   (instrumentCueName . "Piccolo")
>   (midiInstrument . "piccolo"))


I suggested having the Staff print the instrumentCueName rather than the 
voice, but we cannot make that the default because the manual suggests 
using instrumentCueName in a CueVoice to produce the text in the smaller 
CueVoice font-size (Notation Reference 1.6.3).

We could continue to apply the instrumentSwitch to the entire Staff, and 
have both Staff and CueVoice (but not any normal Voice) watch for 
instrumentCueNames to print:
   \layout {
     \context {\Voice \remove "Instrument_switch_engraver" }
     \context {\Staff \consists "Instrument_switch_engraver" }
     \context {\CueVoice \consists "Instrument_switch_engraver" }}
but that seems too tricky to have as the default.

Best would be to separate the two concepts: 1) setting up the staff for a
change to a new instrument and 2) marking cues from a different instrument.