bug-lilypond
[Top][All Lists]
Advanced

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

Re: Hara_kiri_engraver shouldn't handle both staves of a PianoStaff as s


From: Graham Percival
Subject: Re: Hara_kiri_engraver shouldn't handle both staves of a PianoStaff as separate single staves
Date: Wed, 05 Sep 2007 02:07:55 -0700
User-agent: Icedove 1.5.0.12 (X11/20070607)

Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=442

Cheers,
- Graham

Valentin Villenave wrote:
Greetings,

this issue has been discussed on -user for a few days with Kieren, Neil and Tao:
When typesetting an orchestral score with Piano or Harp parts, and using
RemoveEmptyStaffContext, the PianoStaff can sometimes be reduced to one
single staff (for instance when only one hand is playing).

This doesn't seem to be the right engraving rule in orchestral scores,
where both staves are usually preserved wherever there's enough space
on the page.

Here's Kieren suggestion to deal with this issue:
---------- Forwarded message ----------
From: Kieren MacMillan <address@hidden>
Date: 26 août 2007 17:47

IMO, this should be a setting similar to connectArpeggios -- say,
keepAliveTogether -- where the default is ##t, but it can be set to
##f as desired. I suppose this could also be extended (as an
interface) to ChoirStaff, StaffGroup, etc., for ultimate flexibility.
----------------------------------------------------

In the following example, the piano staves should only be hidden in
the third system.

%%%%

one = {
  \repeat unfold 4 { a4 b c' d'} \break
  \repeat unfold 4 { a4 b c' d'} \break
  \repeat unfold 4 { a4 b c' d'} \break
  a1
}
two = { \clef bass
  \repeat unfold 4 { a4 b c' d'} \break
  \repeat unfold 4 { a4 b c' d'} \break
  R1*4 \break
  a1
}
three = { \clef bass
  \repeat unfold 4 { a4 b c' d'} \break
  R1*4 \break
  R1*4 \break
  a1
}
\score {<<
    \context Staff = one \one
    \new PianoStaff <<
      \context Staff = two \two
      \context Staff = three \three >>
    >>
    \layout {
        \context { \RemoveEmptyStaffContext }
    }
}

%%%%

This is more enhancement than a real bugfix, but maybe it could be
added to the tracker...

Regards,
Valentin


_______________________________________________
bug-lilypond mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/bug-lilypond






reply via email to

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