|
From: | lilypond |
Subject: | Re: [Lilypond-auto] Issue 4403 in lilypond: Patch: Part_combine_iterator: stop tracking the last-playing part |
Date: | Tue, 19 May 2015 11:53:44 +0000 |
Comment #4 on issue 4403 by address@hidden: Patch: Part_combine_iterator: stop tracking the last-playing part
https://code.google.com/p/lilypond/issues/detail?id=4403The difference in the test output at the "unison" markup comes from the iterator's choosing to use part 1 where it chose part 2 before. Either one works for the notes. The oddity is that unison is forced when the parts are not actually identical: part 1 includes the markup but part 2 does not. In real music, parts with differing instructions should be double-stemmed for clarity.
I don't consider this a problem with the patch, but it is another example of difficulty related to markups (Issue 2253).
--You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at: https://code.google.com/hosting/settings
[Prev in Thread] | Current Thread | [Next in Thread] |