bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Rest position problem


From: Mats Bengtsson
Subject: Re: Rest position problem
Date: Mon, 23 Aug 2004 10:36:54 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616

This looks like a bug to me.

However, why do you use the verticalExtent property instead of
the minimumVerticalExtent, as described in
http://lilypond.org/doc/v2.3/Documentation/user/out-www/lilypond/Vertical-spacing.html
If you change that, it seems that the rests position is correct.


   /Mats

Jefferson dos Santos Felix wrote:
I have a problem with automatic rest position in multi-voice songs when I use Staff.verticalExtent.
For example:

\version "2.3.11"

\score
{
  \relative
  {
      <<
          \new Staff
          {
              \clef treble
              \set Staff.verticalExtent = #'(-10 . 10)
              \partial 4 <<g'4\\r>> |
              <<{e4. g8 g4 e}\\{r8 c c4 c2}>>
          }
                    \new Staff
          {
              \clef bass
              \set Staff.verticalExtent = #'(-10 . 10)
              \partial 4 r4 |
              c,2 c4 c
          }
      >>
  }
}

This file produce wrong rest positions (collision between rests and notes). When I comment the line:
 \set Staff.verticalExtent = #'(-10 . 10)

Lilypond produce correct rest positions, but I want to use this function to extend my staff!
What's the problem?

Jeff


_______________________________________________
lilypond-user mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-user

--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
        Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================




reply via email to

[Prev in Thread] Current Thread [Next in Thread]