bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the s


From: lilypond
Subject: Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning
Date: Mon, 13 Feb 2012 13:22:16 +0000


Comment #13 on issue 1967 by address@hidden: Concurrent slurs that start and end at the same moment should not produce a warning
http://code.google.com/p/lilypond/issues/detail?id=1967

Well, in this case a problem was flagged because two slur spanners were kept. If the partcombiner has the principle to combine two voices into one chord only if all chord articulations and spanners are the same, then it should suffice to keep just one version of all articulations and spanners, right? Now you might claim with some justification that two spanners _starting_ on a chord might not actually end on the same chord, and so omitting one is not a good idea. But if the voices can't be combined at the end of the slur, they will end up in different contexts and the spanner will not be able to finish anyway.

So to me it would appear that if the partcombiner combines two voices with identical chord articulations (namely separately delivered articulation events not in "articulations" on single notes), we need keep only one version of them.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]