Re: MusicXML2Ly: Problem with minor chords

[David Kastrup]

Johan Vromans <address@hidden> writes:

> Johan Vromans <address@hidden> wrote:
>
>> is translated into
>> 
>>   d:m5
>> 
>> and apparently not understood -- lilypond renders it as a major D chord
>> without warning.
>
> The code in musicxml2ly.py does, indeed, generate :m5 for minor.
>
> Surprisingly, the NR, A.2 Common chord modifiers, reads:
>
>   Major   Major third, perfect fifth   5 or nothing   c1:5   notes: c g
>   Minor   Minor third, perfect fifth   m or m5        c1:m   notes: c ees g
>
> Despite the examples showing otherwise, this could easily be
> interpreted to mean that c is the same as c:5, and that c1:m is the
> same as c:m. However, the trailing '5' makes a power chord (no
> 3rd). In the case of minor the distinction with the major chord is
> lost.
>
> I really wonder if it is intentional behaviour for musicxml2ly to use m5
> for minor.
> Same goes for :5 (for major), :aug5, :dim5, :dim5m7, and :maj5m5.

Well, musicxml2ly.py presumably also generates a \version header, and
running convert-ly on the resulting file possibly fixes a number of
those problems (even though it complicates the rules, the change to let
c:5 exclude the third was introduced as late as version 2.19.28).

Nevertheless it seems like a good idea to change musicxml2ly.py to
generate output compatible with both older and newer versions.

-- 
David Kastrup