Re: Best practice for parts with varying number of staves

[Urs Liska]

Am Mittwoch, den 15.05.2013, 09:48 +0100 schrieb Richard Shann:
> On Wed, 2013-05-15 at 10:05 +0200, Urs Liska wrote:
> > c)
> > I could initially create the score with all possible staves and just
> > let
> > \RemoveEmptyStaves do its job (well, that's what it is intended
> > for ...)
> > -> But that would mean the extra overhead of filling the extra staves
> > with rests for all the numerous pages where they aren't needed. 
> You could use Denemo to create the initial skeleton - it will fill empty
> measures with skips. You will need to fill out any measures that contain
> time-signature changes, rehearsal marks etc, because, at the moment,
> Denemo is doing nothing more than inserting skips for completely empty
> measures.
> 
> Richard
> 

Thanks for the idea, but that's not really viable. The initial skeleton
is done by a Python script that creates a 'part' with 90 segments filled
with rests and time signature changes.

Maybe it's the best idea to use this and go for my c) approach. It's
only that I had in mind to use these for each 'part', not for subparts.

Urs

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