Re: change Staff hara-kiri-ability on the fly? SPONSORSHIP?
2007/8/26, Neil Puttock <[EMAIL PROTECTED]>: > I've just added it as "Forcing visibility of systems with multi-bar rests > when using \RemoveEmptyStaffContext"; I hope it's OK. http://lsr.dsi.unimi.it/LSR/Item?u=1&id=312 A bit long, but I couldn't find any shorter title. It's approved now; however, you've mentioned an issue with the PianoStaff thing, which I tend to think that LilyPond should automatically address (a piano, or harp staff, should never ever be reduced to one single staff when using the hara-Kiri engraver). I'm starting another thread right now to discuss this issue. It would be great if both Kieren and you Neil, could express your point of view there. Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: change Staff hara-kiri-ability on the fly? SPONSORSHIP?
Hi Valentin, On 8/26/07, Valentin Villenave <[EMAIL PROTECTED]> wrote: > > 2007/8/25, Kieren MacMillan <[EMAIL PROTECTED]>: > > > p.s. This is *definitely* an LSR-worthy tip/trick! > > It is indeed; feel free to add it and I'll mark it as approved ASAP :) > I've just added it as "Forcing visibility of systems with multi-bar rests when using \RemoveEmptyStaffContext"; I hope it's OK. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: change Staff hara-kiri-ability on the fly? SPONSORSHIP?
2007/8/25, Kieren MacMillan <[EMAIL PROTECTED]>: > p.s. This is *definitely* an LSR-worthy tip/trick! It is indeed; feel free to add it and I'll mark it as approved ASAP :) Regards, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: change Staff hara-kiri-ability on the fly? SPONSORSHIP?
Hi Kieren,
On 8/25/07, Kieren MacMillan <[EMAIL PROTECTED]> wrote:
>
>
> If you read the Hara_kiri_engraver docs, it says
> __
>
> Like Axis_group_engraver, but make a hara-kiri spanner, and add
> interesting items (ie. note heads, lyric syllables and normal rests)
>
> Properties (read)
>
> keepAliveInterfaces (list)
> A list of symbols, signifying grob interfaces that are worth
> keeping a staff with remove-empty set around for.
> __
>
> If that property were settable (on the fly), we could add
> MultiMeasureRest to (or remove it from) the keepAliveInterfaces as
> desired -- that would solve the problem!
I've tried messing around with keepAliveInterfaces, and this is quite
pleasing:
\version "2.11.30"
show = { \set Staff.keepAliveInterfaces = #'(
rhythmic-grob-interface
multi-measure-rest-interface
lyric-interface
stanza-number-interface
percent-repeat-interface)
}
hide = \unset Staff.keepAliveInterfaces
one = { \repeat unfold 4 { a1 b c' d' \break }
R1 \show R1 R1 \hide R1 \break
R1*4
}
two = { \override MultiMeasureRest #'color = #red
R1*4
R1 \show R1 R1 \hide R1
R1*4
R
R1 \show R1 R1 R1
R1*4
}
three = { \override MultiMeasureRest #'color = #blue
R1*4
R
R1 \show R1 R1 \hide R1
R1*4
R1 \show R1 R1 \hide R1
R1*4
}
\score {
\new StaffGroup <<
\context Staff = one \one
\context Staff = two \two
\context Staff = three \three
>>
\layout {
\context { \RemoveEmptyStaffContext }
}
}
The positioning of the overrides is critical (inside each system), otherwise
they tend to interfere with the other staves.
Regards,
Neil
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: change Staff hara-kiri-ability on the fly? SPONSORSHIP?
Hi Neil, I've tried messing around with keepAliveInterfaces, and this is quite pleasing: Nicely done -- I hereby retract my offer of sponsorship... =) Best regards, Kieren. p.s. This is *definitely* an LSR-worthy tip/trick! ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: change Staff hara-kiri-ability on the fly? SPONSORSHIP?
Hi Neil: The closest I've got is in creating a new staff context with the properties of \RemoveEmptyStaffContext, but it only allows you to choose whether a particular stave can be hidden or not. If you read the Hara_kiri_engraver docs, it says __ Like Axis_group_engraver, but make a hara-kiri spanner, and add interesting items (ie. note heads, lyric syllables and normal rests) Properties (read) keepAliveInterfaces (list) A list of symbols, signifying grob interfaces that are worth keeping a staff with remove-empty set around for. __ If that property were settable (on the fly), we could add MultiMeasureRest to (or remove it from) the keepAliveInterfaces as desired -- that would solve the problem! Developers: any chance you can do this (or something similar, with an equivalent result)? I've still got a few Euros burning a hole in my PayPal account... =) Thanks, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: change Staff hara-kiri-ability on the fly?
Hi Kieren, On 8/24/07, Kieren MacMillan <[EMAIL PROTECTED]> wrote: > > > Just wondering if anyone has solved the problem of turning the hara- > kiri-ability of a Staff on the fly? I haven't had much success, unfortunately. The closest I've got is in creating a new staff context with the properties of \RemoveEmptyStaffContext, but it only allows you to choose whether a particular stave can be hidden or not. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
change Staff hara-kiri-ability on the fly?
Hello all, Just wondering if anyone has solved the problem of turning the hara- kiri-ability of a Staff on the fly? i.e., I want to dictate, at any point in the score, whether \RemoveEmptyStaffContext will act on (i.e., remove) a Staff, regardless of whether that Staff has only whole-measure rests in that system. Thanks, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
