Re: RemoveEmptyStaffContext

[Trevor Daniels]

Perhaps the easiest way is to have two \score
blocks, one for the printed output and one for
the midi output.  They can use the same music
variables, so little extra typing would be required.

Trevor

----- Original Message ----- 
From: "Johan Vromans" <address@hidden>
To: <address@hidden>
Sent: Tuesday, February 10, 2009 9:40 AM
Subject: RemoveEmptyStaffContext


> Hi,
>
> I have a score with 3 voices, A, B, and C.
> Voices B and C have a lot in common. For about half of the score the B
> parts is identical to the C part.
>
> By specifying rests in voice B where it is identical to voice C, and
> using \RemoveEmptyStaffContext, LilyPond can eliminate printing of
> voice B. That's good. And a space saver.
>
> But, not surprisingly, this makes the generated MIDI less useful. I
> split the MIDI into separate parts for the individual voices, and now
> voice B will have large gaps where it should sound the same as voice
> C. I hope it is clear what I mean.
>
> What would be a good way to benefit from \RemoveEmptyStaffContext and
> still get a useful MIDI? I'm currently considering to write
> non-printing rests (S-rests) in voice B where it matches voice C and
> then develop a scheme function that copies the measures from C where B
> has S-rests. But I was wondering whether there are other means to deal
> with this situation.
>
> -- Johan
>
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-user