Reinhold Kainhofer <reinhold <at> kainhofer.com> writes:
> Am Freitag, 4. Februar 2011, um 07:17:43 schrieb Keith OHara:
> Nope, that problem has always been there... My patches didn't change how the
> part-combiner detected combined/apart periods.
>
Right, stable LilyPond 2.12 showed this problem with shorter rests. Now that
you've given height adjustments to full-measure rests, we see LilyPond's
confusion more often.
> > Rests sometimes adopt voiceOne or voiceTwo settings at surprising times. {
> > \partcombine
> > { R1*4 R1 }
> > {R1*2 R1 c' R1}
> > }
> >
[...]
> What does work is using \partcombineSoloIIOnce before the R1 in the second
> voice:
> {
> \partcombine
> { R1*4 R1 }
> {R1*2 \partcombineSoloIIOnce R1 c' R1}
> }
>
That worked well enough for me, updating a full-length symphony.
The workaround and root cause seem identical to issue 261, so I'll note your
workaround there.
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
