On 2020-01-24 3:03 am, David Kastrup wrote:
Aaron Hill writes:
If you do this enough, putting it in a music function will make your
score much more readable:
cueName = #(define-music-function (parser location name) (markup?)
#{ \tag #'cueName \set CueVoice.instrumentCueName = #name #})
Aaron Hill writes:
> On 2020-01-23 8:00 pm, Aaron Hill wrote:
>>
>> \tag #'cueName <>_\markup \tiny \italic "Bsn."
>> \cueDuring #"bassoon" #DOWN { R1}
>>
>
> If you need to use instrumentCueName or would simply prefer not to use
> text scripts, then you can do this:
>
>
> \cueDuri
On 2020-01-23 8:00 pm, Aaron Hill wrote:
\tag #'cueName <>_\markup \tiny \italic "Bsn."
\cueDuring #"bassoon" #DOWN { R1}
If you need to use instrumentCueName or would simply prefer not to use
text scripts, then you can do this:
\cueDuring #"bassoon" #DOWN {
\tag #'cueName \
On 2020-01-23 7:37 pm, Michael Seifert wrote:
However, I can’t seem to get killCues to work correctly in
combination with partcombine. It creates stray notation below the
system in the full score, which is both unsightly and causes the
systems in the full score to be over-compressed. A
Hey there folks,
I’m trying to prepare a score and parts for a concerto using Lilypond,
and I can’t figure out how to make partcombine and killCues work nicely
together. My goal is to have individual parts for the orchestra, containing
cues for the solo instrument; and also to
