Re: Staff Stretching problem in 2.13.50+

[James Lowe]

Keith,

-----Original Message-----
From: Keith OHara <address@hidden>
Date: Wed, 9 Mar 2011 08:18:17 +0000
To: bug-lilypond <address@hidden>
Subject: Re: Staff Stretching problem in 2.13.50+

>> It seems that any markup on the page causes version 2.13.50+ to prefer
>> stretching the lines, if one line was forced to be stretched.
>> ---
>> \version "2.13.51"
>> \score {\relative c'' {
>> c1 c \break
>> d1 d d d d d d d
>> } }
>> \markup "hello"
>>
>[...] 
>> I think this is a bug/regression.
>>
>
>Probably not a bug.
>I think the behavior of stretching lines near a forced-stretched line is
>intentional -- to keep note-spacing locally uniform.  What newer versions
>do to this example is just beautiful :
>
>{c''1 \break
>\repeat unfold 200 d''
>}
>
>The way the markup affects line-spacing behavior in 2.13.51 is odd,
>but within the discretion we give to LilyPond.  If we need drastically
>different line spacing on neighboring lines, then we have to take back
>control with \noBreak
>

Odd?

Actually if you go back to my example that I reported this with

\header {
title = "S C H E R Z O"
}

\relative c'' {
  \time 3/8
  \compressFullBarRests
  R1*19*3/8 \break| cis4. | d8 r r | R1*2*3/8 | cis4. | d8 r r | \break
R1*20*3/8
}


There is no \markup.

Take away the \header or make it 'blank' and all is fine.

As \header (should have) has no bearing whatsoever on the \score - it'
supposed to just title a page, then the fact this affects the spacing of
my notes is not expected and it isn't a 'little' either.

I can't even play about with the length of the multimeasure rest as it
just makes things worse and springs about all over the place.

You might as well say page numbers affecting the score is acceptable.

While it might be 'expected' behaviour it certainly isn't 'wanted' - at
least from my part. Can tell me how I can get the two MMR on a line each
and my 4 bars on a line on their own, I'll at least be happy if not still
concerned. I've half a dozen scores this is going to affect - otherwise I
have to go back to 2.13.40.

James





>