Re: RemoveEmptyStaffContext should keep at least one staff alive?

[Paul Scott]

On 03/14/2011 09:00 PM, Andrew Hawryluk wrote:
> On Sun, Mar 13, 2011 at 10:13 PM, Paul Scott<address@hidden>  wrote:
>    
> > Hi,
> >
> > 2.13.54
> >
> > Does it ever make sense for RemoveEmptyStaffContext to remove all staves?
> >   Should not at least one be kept alive showing the rests?
> >
> > Is there a way to force this behavior?  I haven't gotten the following to
> > work yet to see whether it will do what I want:
> >
> > <http://lsr.dsi.unimi.it/LSR/Item?id=312>
> >
> > TIA,
> >
> > Paul Scott
> > Librarian
> > Southern Arizona Symphony Orchestra
> >
> >
> >
> > _______________________________________________
> > lilypond-user mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/lilypond-user
> >
> >      
> Not to distract from the interesting question, but if there really
> were that many rests in a real score, wouldn't you rather display that
> section as a big multi-measure rest? In that case you would always be
> left with some notes in each system...
>    

> Andrew
>
>    

Let's say this was a French-scored bass trombone and tuba part where 
both instruments were resting for a long time which went through several 
sections.  There would be several multi-measure rests with several 
rehearsal letters in between.  This could easily take up one or more 
lines.  Currently RemoveEmptyStaffContexts removes the staves and only 
leaves the bar numbers and rehearsal marks.

In the case I'm working on now I'm adding a voice staff to my reed part 
since we are playing without a conductor.  The original typically has 4 
bars per line and there is a 4 bar rest in the reed part which should 
take up one line.

Paul


--
Paul Scott
Librarian
Southern Arizona Symphony Orchestra