Re: Spacing issues with Mark_engraver and Metronome_mark_engraver in Dynamics context

[Saul Tobin]

I'm less concerned by bad page breaks than I am by inconsistent system spacing caused by bad extent-estimates.

On Fri, Dec 1, 2017 at 12:37 PM, Flaming Hakama by Elaine <address@hidden> wrote:

From: fbous <address@hidden>
Subject: Spacing issues with Mark_engraver and Metronome_mark_engraver in Dynamics context

Hello list,

I have a rather large project,with orchestra, choir, etc., where layouting
the vocal score gives me headaches. I usually have four or five staffs per
system (SATB plus one soloist) but some parts have more (up to 13 staffs per
system). I use extra dynamic lines to print rehearsal- and metronome marks.

My problem is, that lilypond produces a bunch of consecutive half full pages
(see attached image), sometimes it even prints only one system per page,
although there should be enough space for three systems most of the time.

I tried the annotate-spacing option and noticed that the extent-estimate is
about half of the time a lot larger than the final resulting vertical
extent. I looked through the score, but could not find any pattern as to
when exactly a bad estimate occurs. The problem does disappear, though, if I
move the Mark_engraver and the Metronome_mark_engraver back to the score
context

Unfortunately min-systems-per-page does not work for me, due to the highly
varying number of staffs per system. Something like min-staffs-per-page
would be useful for me, but I could not find such a thing. Does anyone know,
how I can tell lilypond to squeeze more systems on the page?

For the vocal score I use a global staff size of 13.5 (a4paper) and the
layout settings below.
\layout{
        \context {
                \Score
                \remove Mark_engraver
                \remove Metronome_mark_engraver
                \override Beam.breakable = ##t
                \override Hairpin #'minimum-length = #7
                \override Glissando #'minimum-length = #7
                \override Glissando.springs-and-rods = #ly:spanner::set-spacing-rods
                \compressFullBarRests
        }
        \context {
                \Dynamics
                \consists Output_property_engraver
                \consists Axis_group_engraver
                \consists Mark_engraver
                \consists Metronome_mark_engraver
                \override VerticalAxisGroup.remove-empty = ##t
                \override VerticalAxisGroup.remove-layer = #'any
                \override VerticalAxisGroup.staff-affinity = #CENTER
        }
        \context {
                \Staff
                \override VerticalAxisGroup.remove-empty = ##t
                \override VerticalAxisGroup.remove-layer = #'any
        }
        \context {
                \StaffGroup
                \consists "Keep_alive_together_engraver"
        }
        \context {
                \ChoirStaff
                \consists "Keep_alive_together_engraver"
        }
        \context {
                \Voice
                \remove "Note_heads_engraver"
                \consists "Completion_heads_engraver"
                \remove "Rest_engraver"
                \consists "Completion_rest_engraver"
        }
}
<http://lilypond.1069038.n5.nabble.com/file/t5500/lilypond.png>

As a workaround for page break headeaches, I've been using \autoPageBreaksOff, combined with explicit \pageBreak's. 

I can't speak to the specific issues that are causing the behavior you describe, but I've certainly had my share of "why is lilypond adding an extra page" headscratching. 

Bypassing the auto page breaks is a sure-fire way to avoid that;  it will place every single grob on one single page if you let it (by not specifying any explicit \pageBreak's).

HTH,

David Elaine Alt

415 . 341 .4954                                           "Confusion is highly underrated"

address@hidden

self-immolation.info
skype: flaming_hakama
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

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