Am Mittwoch, 4. Mai 2011, 13:29:48 schrieb Ralph Palmer: > On Mon, Apr 25, 2011 at 8:54 AM, Olexa Bilaniuk <[email protected]> wrote: > > > I'm not top posting. > > > > I have found an issue with the \partcombine tool, but I am not quite > > sure whether it is a definite bug or one of the "various" limitations > > it has. If one starts a tie, slur, crescendo hairpin or other such > > while in one "mode" of \partcombine (\partcombineChords, > > \partcombineApart, \partcombineUnisono, etc.) and then switches to > > another before the tie, slur or crescendo hairpin is complete, > > Lilypond prints a warning about unterminated ____ and does not print > > it. The following source code triggers the bug: > > > > \version "2.13.60" > > > > FlautoI = \relative c''{ \partcombineChords c2~ \partcombineApart c } > > FlautoII = \relative c''{ \partcombineChords b2\< \partcombineApart b\! } > > > > \relative c''{ > > > > \partcombine \FlautoI \FlautoII > > > > } > > > > > > > > I suspect this is because in regular polyphony, inter-Voice spanning > > objects are disallowed?
Yes, exactly. \partcombine internally distributes the note events to 4 different voice (one for voice 1, one for voice 2, one for solo and one for together (i.e. chords or unison)). In your example, the c2 is placed in the TOGETHER voice, while the second c is placed in the VOICE1 voice... Cheers, Reinhold -- ------------------------------------------------------------------ Reinhold Kainhofer, [email protected], http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
