Sometimes lilypond tries to use less pages for more music, which is not always wanted. This can be easily fixed by manually adding
\pageBreak , but sometimes an automatic solution is needed.
When vertical compression happens, lilypond log shows something like this:
warning: compressing over-full page by 36.9 staff-spaces warning: page 4 has been compressed
In my particular situation lilypond script is generated by MusicXML analysis program and no manual tweaking of positions or pagebreaks is possible, because we do not know what music user can upload.
How can compression be totally disabled or limited, so that Lilypond would have to add page breaks? Automatic solution is required, which does not include manually tweaking positions of elements and pagebreaks.
Sorry for posting such a big example, but many elements are needed so that page is not enough any more. Here is an example of automatically generated score:
1. Automatic line breaking leads to vertically over-compressing first page (text lines are too close to each other, numbers inside score collide with text spanners):
2. Adding just one
\pageBreak command fixes everything:
I already did a google search of known issues and visited lilypond documentation with no significant progress so far:
\once \overridewith the same properties. Why don’t you just use
\overrideonly once in the beginning? If you can navigate through your code, it’s fine, but it can be simplified a lot! And this would help others to understand it. Now, to your question: did you look into vertical positioning in the doc: lilypond.org/doc/v2.18/Documentation/notation/…