>
When the connectArpeggios mode includes an arpeggio on a single note,
the resultant span arpeggio may collide with a previous note.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\version "2.12.1"
ddddd = { d'16 d'16 d'16 d'16 d'4 \arpeggio } % single note
sdf = { s4 <d' f'>4 \arpeggio } % chord
\score {
<< \transpose c c'{ \ddddd \sdf } \\ { \sdf \ddddd } >>
\layout {
line-width = #66
\context {
\Staff
\consists "Span_arpeggio_engraver"
connectArpeggios = ##t
}
}
}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
In span-arpeggio-engraver.cc it says:
> we can't kill the children, since we don't want
> the previous note to bump into the span arpeggio
When arpeggio.cc prints a squiggly arpeggio on a single note, it warns
> no heads for arpeggio found?
and kills the arpeggio.
There is another demo and a proposed workaround on the user list at
http://lists.gnu.org/archive/html/lilypond-user/2009-09/msg00735.html
Cheers,
Robin
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
