"Robert Clausecker" wrote in message
news:1272528558.2297.5.ca...@robert-laptop...
I think the problem which cause this, is that lilypond obvious
calculates the spacing as if the arpeggios were splitted.
BTW, there seems to be another issue regarding arpeggios:
When you have an Ossia PianoStaf
On Sat 24 Apr 2010, 18:59 Robert Clausecker wrote:
> Hi lilypond team!
>
> While typesetting a piece, I found this bug:
> An connected Arpeggio may collide with the previous note when having
> chords in multiple voices.
Thank You, added as 1076:
http://code.google.com/p/lilypond/issues/detail?id=
I think the problem which cause this, is that lilypond obvious
calculates the spacing as if the arpeggios were splitted.
BTW, there seems to be another issue regarding arpeggios:
When you have an Ossia PianoStaff, formatted smaller, the connected
arpeggios are not scaled, but the normal arpeggios
On Mon Apr 26, 17:44 Robert Clausecker wrote:
> No, it's not the same issue. In issue 931, there are two chords at the
> same moment, but I have two following chords, which are colliding. The
> attached image shows the collision.
Yes, it seems to be different.
Now i can tell just that in Your exa
No, it's not the same issue. In issue 931, there are two chords at the
same moment, but I have two following chords, which are colliding. The
attached image shows the collision.
I hope this helps.
Regards, Robert.
<>___
bug-lilypond mailing list
bug-li
On Sat Apr 24, 18:59 You wrote:
> Hi lilypond team!
>
> While typesetting a piece, I found this bug:
> An connected Arpeggio may collide with the previous note when having
> chords in multiple voices.
Hi!
Sorry, isn't it the same as
http://code.google.com/p/lilypond/issues/detail?id=931 ?
> I tr
Hi lilypond team!
While typesetting a piece, I found this bug:
An connected Arpeggio may collide with the previous note when having
chords in multiple voices.
I tried to reduce the example to minimum, the leading note is needed to
make the bug happen.
\version "2.13.18" %current trunk
\score {
