Comment #1 on issue 1159 by n.puttock: Fine-tuning manual beaming
http://code.google.com/p/lilypond/issues/detail?id=1159
This seems to be a conflict between Beam #'beaming and Stem #'beaming,
which is acknowledged in beam.cc:
vector<Beam_segment>
Beam::get_beam_segments (Grob *me_grob, Grob **common)
{
/* ugh, this has a side-effect that we need to ensure that
Stem #'beaming is correct */
(void) me_grob->get_property ("beaming");
As a workaround, removing the callback for Beam #'beaming fixes the beaming
(though it might cause weird beam positioning in other situations):
\relative c'' {
\once \override Beam #'beaming = #'()
c32[ c
\once \override Stem
#'beaming = #(cons (list 0 1 2) (list 0 3 4))
c c
\once \override Stem
#'beaming = #(cons (list 0 3 4) (list 0 1 2))
c c c]
}
Attachments:
beaming-fixed.png 2.0 KB
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
