Re: problem with \RemoveEmptyStaves
What prevents Lilypond to do this automatically? I want an option that staves are only removed if there are at least two systems on a page. I would phrase that there *would* be two systems after removing the empty staves. No, I don't mean that. I mean the situation where Lilypond is only able to put a single system on a page (due to lack of vertical space), and if this is the case, I want lilypond to insert empty staves back to get a vertically well filled page. Maybe my option should be rather a list to handle the concern Keith has mentioned (overfull pages due to a very large number of staves). For example, it could be remove-empty-single-system = #'(celesta harp) so that the staves called `celesta' and `harp' get removed even if all other systems would be added to fill a single system. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
I want an option that staves are only removed if there are at least two systems on a page. A second pass over the full score should be quite cheap, if really necessary, since line breaks are already done. I think this could be done automatically, without a second pass, [...] This would be great! I've added this as issue #3389. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
Thanks. *Very* kludgy. No, not at all. The RemoveEmptyStaves feature was intended to be adjusted in that way, so the solution in that snippet is a safe and direct way to avoid removing staves when you don't want them removed. It will not break at the next LilyPond version or interfere with anything else. But it is a *manual* solution, severely limiting the choices of lilypond to find a good layout. Your point of view is: `Don't remove this staff at that very place.' Mine is: `Don't create pages with bad layout if it can be avoided.' Doing what you want requires compiling twice: once to see where only one system fits on a page, then place \once\showMultiRests and compile again. Yes, it seems to be the only solution right now. However, just imagine that I have to insert a bar: I would then have to disable all `\once\showMultiRests' commands, check what lilypond produces, then re-insert these commands at the proper places, which might be completely different locations. This *is* kludgy. :-) What prevents Lilypond to do this automatically? I want an option that staves are only removed if there are at least two systems on a page. A second pass over the full score should be quite cheap, if really necessary, since line breaks are already done. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
Am 01.06.2013 06:17, schrieb Werner LEMBERG: What prevents Lilypond to do this automatically? I want an option that staves are only removed if there are at least two systems on a page. I would phrase that there *would* be two systems after removing the empty staves. Helge ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
On Fri, 31 May 2013 21:17:02 -0700, Werner LEMBERG w...@gnu.org wrote: Thanks. *Very* kludgy. No, not at all. But it is a *manual* solution, Yep, but (after looking up 'kludgy' I see that) manual and kludgy are different things. What prevents Lilypond to do this automatically? I want an option that staves are only removed if there are at least two systems on a page. A second pass over the full score should be quite cheap, if really necessary, since line breaks are already done. I think this could be done automatically, without a second pass, if the removal of empty staves were to just mark them as removable and as taking no space, inserting a step to put them back and figure their space requirements just after page-breaking. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
Werner LEMBERG wl at gnu.org writes: In a big score, it removes staves even if only a single system fits on a page, see the attached image. In some big scores (say, Mahler) you need to remove the empty staves just to let the rest fit legibly on a page. You might like it if you restore some stretchability at the bottom of the page. (I don't remember the command, but the default has some stretch.) How can I avoid this? The last time this question came up, the suggestion was http://lsr.dsi.unimi.it/LSR/Item?id=312 Probably you will want to adapt that to apply to the whole Score. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
In a big score, it removes staves even if only a single system fits on a page, see the attached image. In some big scores (say, Mahler) you need to remove the empty staves just to let the rest fit legibly on a page. OK. In other words, we would need a new value for property `remove-empty', say, `multiple-systems-per-page-only', to make lilypond do what I want. Would this be possible to implement? I can imagine cyclic dependencies... How can I avoid this? The last time this question came up, the suggestion was http://lsr.dsi.unimi.it/LSR/Item?id=312 Probably you will want to adapt that to apply to the whole Score. Thanks. *Very* kludgy. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \RemoveEmptyStaves
On Wed, 29 May 2013 02:58:44 -0700, Werner LEMBERG w...@gnu.org wrote: In a big score, it removes staves even if only a single system fits on a page, see the attached image. How can I avoid this? The last time this question came up, the suggestion was http://lsr.dsi.unimi.it/LSR/Item?id=312 Probably you will want to adapt that to apply to the whole Score. Thanks. *Very* kludgy. No, not at all. The RemoveEmptyStaves feature was intended to be adjusted in that way, so the solution in that snippet is a safe and direct way to avoid removing staves when you don't want them removed. It will not break at the next LilyPond version or interfere with anything else. I just tried it. I changed Staff to Score in showMultiRests and at the places where I want all the staves to print I put \once\showMultiRests in the voice I use for tempo and time signatures. Doing what you want requires compiling twice: once to see where only one system fits on a page, then place \once\showMultiRests and compile again. Putting the empty staves back where you want them should not change the page breaks, so you won't need go in circles. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
problem with \RemoveEmptyStaves
Folks, the \RemoveEmptyStaves command apparently has a big drawback: In a big score, it removes staves even if only a single system fits on a page, see the attached image. How can I avoid this? Werner inline: remove-empty.png___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
