Bad spacing (gap) when large interval and accidental

[Hudson Lacerda]

Hi. The code below results in a gap between the last notes.
There is enough room below "d" (bottom staff) to draw the sharp of "fis".

P.S.: Concerning to "beams should not collide with accidentals" issue (#76), I
think the clashes are a awful bug, since a score with collisions is hard to
read. One takes effort and time to figure out if a black spot is a sharp or a
natural, if the duration is eight or 16th note, and so on.

\version "2.13.7"
\paper{ ragged-right=##t }
{
  << \relative c'' {d16 c a d,} \\
     \new Staff
     \relative c {\clef bass c!16 a d fis, } >>
}




_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

[James E. Bailey-3]

On 07.11.2009, at 23:08, Hudson Lacerda wrote:

> Hi. The code below results in a gap between the last notes.
> There is enough room below "d" (bottom staff) to draw the sharp of  
> "fis".
>
> P.S.: Concerning to "beams should not collide with accidentals"  
> issue (#76), I
> think the clashes are a awful bug, since a score with collisions is  
> hard to
> read. One takes effort and time to figure out if a black spot is a  
> sharp or a
> natural, if the duration is eight or 16th note, and so on.
>
> \version "2.13.7"
> \paper{ ragged-right=##t }
> {
>   << \relative c'' {d16 c a d,} \\
>      \new Staff
>      \relative c {\clef bass c!16 a d fis, } >>
> }
>

I don't understand the problem here. There is enough room to write  
the sharp of fis because there needs to be a sharp for fis. If you  
remove the sharp and write only f, the spacing adjusts.

James E. Bailey



_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

[Carl Sorensen-3]

On 11/7/09 3:08 PM, "Hudson Lacerda" <hfmlacerda@...> wrote:

> Hi. The code below results in a gap between the last notes.
> There is enough room below "d" (bottom staff) to draw the sharp of "fis".
>
> P.S.: Concerning to "beams should not collide with accidentals" issue (#76), I
> think the clashes are a awful bug, since a score with collisions is hard to
> read. One takes effort and time to figure out if a black spot is a sharp or a
> natural, if the duration is eight or 16th note, and so on.

Nobody has claimed that the clashes are not an awful bug.  At this point
there is nobody with the interest, ability, and time to resolve that bug.
You are welcome to join the development team and work on that bug.  I'll be
happy to provide any support I can.

>
> \version "2.13.7"
> \paper{ ragged-right=##t }
> {
>   << \relative c'' {d16 c a d,} \\
>      \new Staff
>      \relative c {\clef bass c!16 a d fis, } >>
> }
>


While this may be syntactically valid LilyPond code, it seems to me to be
improper (i.e. to not match the intent of the input construction}.

the << \\ >> context is intended to be single staff polyphony (see Learning
Manual 1.5.2).

Why would one add a \new Staff in single staff polyphony?

It seems to me that a better way to get two staffs is parallel is to do the
following:

\version "2.13.7"
 \paper{ ragged-right=##t }
   {
     <<
        \relative c'' {d16 c a d,}
        \new Staff {
          \relative c {\clef bass c!16 a d fis, }
        }
     >>
   }

(Note the missing \\).

HTH,

Carl



_______________________________________________
bug-lilypond mailing list
bug-lilypond@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond