Ok, here's what I've come up with to show the bug a little better:
-----
\version "2.9.21"
\score
{
<<
\new Staff
{
\relative c'
{
c4 c c c |
c4 c8 c c4 c8 c |
c8 c4 c8 c c4 c8 |
c8 c c c c c c c |
\times 2/3 {c4 c c} c4 c |
c4 \times 2/3 {c4 c c} c4 |
c4 c \times 2/3 {c4 c c} |
\times 2/3 {c4 c c} \times 2/3 {c c c} |
}
}
\new Staff
{
\repeat unfold 8 {\clef treble d''4 r \clef bass f r |}
}
>>
\layout
{
indent = #0
line-width = #30
}
}
-----
I know this is artifically compressing the systems, but it's the
closest I could get it to how lilypond formatted it automatically for
me in the real piece. In any case the bass clef is misplaced in
measures 3, 5, and 8. In the good measures the rest's position is
adjusted to make room for the clef while in these it is not.
I'll see if I can isolate the bad tie problem a bit later. Thanks again.
-----Jay
On 10/6/06, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> By 'better' I meant that it shows the problem more clearly. I haven't
> tweaked much at all yet. This is default Lilypond and it doesn't
> complain one bit about it getting too dense:
The new image definitely classifies the collision as a bug. It would
be great if you could extract a minimal example (probably by reducing
the line length), reducing it as much as possible.
BTW, there is another bug hidden in the image: the tie in the bass
line from the first to the second bar appears as a dot only. This is
something serious... According to your other mails I presume that you
already use the latest lilypond version. Again I ask you to isolate
the problem to the smallest possible case. I know that it is quite
time consuming, but it enormously increases the chances to get a quick
fix.
> I've done this to make it smaller:
>
> -----
> \new Staff
> \with
> {
> fontSize = #-3
> \override StaffSymbol #'staff-space = #(magstep -3)
> }
> {\hornNotes}
> -----
>
> Is this not good practice?
This is fine, I think.
Werner
bug2a.png
Description: PNG image
_______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
