[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 880 in lilypond: Arpeggios collide with notes when connectArpeggi
From: |
codesite-noreply |
Subject: |
Issue 880 in lilypond: Arpeggios collide with notes when connectArpeggios is set |
Date: |
Thu, 29 Oct 2009 10:24:54 +0000 |
Status: Accepted
Owner: v.villenave
Labels: Type-Collision Priority-Medium
New issue 880 by v.villenave: Arpeggios collide with notes when
connectArpeggios is set
http://code.google.com/p/lilypond/issues/detail?id=880
% From Robin Bannister:
% When the connectArpeggios mode includes an arpeggio on a single note,
% the resultant span arpeggio may collide with a previous note.
\version "2.13.6"
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
There are many unresolved collisions with arpeggios: see for instance issue
601 and issue 821.
Attachments:
collision.png 2.5 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Issue 880 in lilypond: Arpeggios collide with notes when connectArpeggios is set,
codesite-noreply <=