[Top][All Lists]

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

Re: 2.17.16 vs 2.17.17 Page Breaking

From: Jay Anderson
Subject: Re: 2.17.16 vs 2.17.17 Page Breaking
Date: Sat, 4 May 2013 22:14:52 -0700

On Sat, May 4, 2013 at 7:21 PM, Keith OHara <address@hidden> wrote:
> I cannot reproduce the full problem.  Has anyone seen LilyPond print
> 'annotate-spacing' output where both the limits for the top staff are
> negative numbers?

I figured out where this was coming from. I was using something like

\score << { label #'a } { ... music ...} >>

This is a bad idea (*hangs head in shame*) and I've fixed it (moved
label before score). This specific piece is now back on one page. (I'm
not sure why it wasn't creating an empty staff though.) However others
are still spaced more widely (compared with 2.17.16). I haven't
investigated those yet. I'll try and figure out what's causing this
hopefully in a few days (sorry for my slow responses). Sorry for the
false positive.

> When the top staff ends at 0, the commit cited above gives generally better
> page-breaking estimates of the height of the staff (see
> <http://code.google.com/p/lilypond/issues/detail?id=3342>).  The estimate is
> a bit worse in the case where it allows space for a tempo that is completely
> hidden.  The reason given for hiding the tempo completely was that it is for
> midi only, but the manual says in that case to use  \midi {\tempo...}

This is true for the majority of cases I'm sure, but there are some
drawbacks. \midi { \tempo ... } is a one time thing. But I can put
\tempo commands throughout a piece for changes in tempo. It feels odd
to include only the initial tempo in the midi block. As an alternative
I could use tags or separate midi music sections for midi only items,
but that complicates things since sometimes I want the tempo visible
(\tempo "Allegro" 4=108). So while there are solutions I would still
expect 'tempoHideNote = ##t' to cause the tempo to take no space or to
issue a warning.

> I think I have an implementation of \markLenghtOn that will avoid this
> problem, but if we don't confirm that, then people setting score and parts
> will space the tempo marks in the parts by hand
> <https://lists.gnu.org/archive/html/lilypond-devel/2013-02/msg00075.html>

Yes, I think the tempo work you're doing is great (and will greatly
simplify some of my scores).


reply via email to

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