I’ve hit this bug as well, but don’t have a workaround for it. I’ve had to
manually combine tuplets when voices share a note. The issue there, besides
the extra work and the way it muddies the source file, is that the shared note
will be printed with two note heads and a single stem instead of a single note
head and two stems. Your example would look like:
musicC = { \tuplet 3/2 { r4 r <c'~ c'>4 } d'2 }
musicD = { \tuplet 3/2 { r4 r <c'~ c'>4 } c'2 }
\score { \partcombine \musicC \musicD }
In other places, I’ve been able to replace the tuplet in the second voice with
s2, but for some reason that doesn’t work with this example.
partcombine similarly chokes on notes that should be beamed when voices share a
note. For that case, I can wrap the notes that should be beamed together with
\partcombineApart … \partcomineAutomatic. That trick does’t work for tuplets,
though.
David
On Oct 22, 2016, at 8:44 AM, Kieren MacMillan <kie...@alumni.rice.edu> wrote:
> Hi all,
>
> Any ideas why the tuplet isn’t bracketing properly in the following snippet,
> and/or a workaround?
>
> %%% SNIPPET BEGINS
> \version "2.19"
> musicA = { \tuplet 3/2 { r4 r c' } d'2 }
> musicB = { \tuplet 3/2 { r4 r c' ~ } 2 }
> \score { \partcombine \musicA \musicB }
> %%% SNIPPET ENDS
>
> Thanks,
> Kieren.
> ________________________________
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info
> ‣ email: i...@kierenmacmillan.info
>
>
> _______________________________________________
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
