|
From: | Malte Meyn |
Subject: | Re: accidentals on merged notes |
Date: | Sun, 13 Aug 2017 10:05:57 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 |
Am 13.08.2017 um 09:53 schrieb Knut Petersen:
Am 12.08.2017 um 20:56 schrieb Malte Meyn:Am 12.08.2017 um 17:05 schrieb Hauke Rehr:Still, the output doesn’t match at least /my/ expectations: notes should either not be merged at all, or there should be stacked accidentals indicating which one applies to which Voice.How should this be a default behaviour? IMO none of those two options looks good and unambiguous. But here are three possible solutions to your problem (I like the third most):We might decide that it is ok to provide an ambiguous engraving, but the engraving lilypond provides is clearly broken and should be fixed.
I agree on that and on the comments to your examples • Hauke A (current default is buggy) • Knut C (why Malte B is no solution) • Malte C (don’t add staves automagically) Some comments of mine to the other examples:• Knut A: I agree it looks a little bit ambiguous but in chords (not in polyphony though) it’s the best solution for a *default* behaviour. (btw it has to be sharp-natural like here, not natural-sharp) • Knut B: This works only unambiguously with much more horizontal space. So IMO not a good solution for default behaviour. • Malte A: Same problem as Knut B but Knut B is better (look at the g-sharp/a-sharp on beat 4) • Malte B: Not a thing for default because of cases like Knut C and the accidentals are too small to read.
So IMO the default should be changed from Hauke A to Knut A. This works only for chords but polyphony should use seperate staves here anyway.
[Prev in Thread] | Current Thread | [Next in Thread] |