msk...@ansuz.sooke.bc.ca writes:
> On Sun, 26 Feb 2017, Wols Lists wrote:
>> I'm guessing lily is taking *in* his request for "C 13", converting it
>> into the chord, and then converting that chord *back* into what it
>> thinks is called "C 9 13". With the result that lily's output does *not*
>> match the user's input. Frustrating!
>
> Okay, I think I see the issue - it's the same problem everybody has with
> chord mode and ChordNames, which is that those two things are completely
> separate from each other despite the usual use case treating them as a
> single entity.
>
> \chordmode { c:13 } turns into <c' e' g' bes' d'' a''>
>
> \new ChordNames { <c' e' g' bes' d'' a''> } prints "C9 13"
>
> I agree it looks like a bug, but because of the separation between chord
> mode and ChordNames, each is going to point the finger at the other as
> being at fault, because each one is using its own rules which taken
> independently seem sensible.
To me it would seem that the default mode of operation should be for
them to have matched rules where feasible, in order to have least
element of surprise.
--
David Kastrup
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
