[Top][All Lists]

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

Re: Fw: [PATCH] Eliminate accidental power chords in musicxml2ly.

From: James Lowe
Subject: Re: Fw: [PATCH] Eliminate accidental power chords in musicxml2ly.
Date: Mon, 3 Oct 2016 12:46:55 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0


On 30/09/16 07:37, Johan Vromans wrote:
> Date: Thu, 18 Aug 2016 13:38:21 +0200
> From: Johan Vromans <address@hidden>
> To: David Kastrup <address@hidden>
> Subject: Re: [PATCH] Eliminate accidental power chords in musicxml2ly.
> Hi David,
> On Thu, 18 Aug 2016 07:10:45 +0200
> David Kastrup <address@hidden> wrote:
>>> > > I'll prepare a better solution, which involves changing the way
>>> > > ChordNameEvent (musicexp.py) handles modifications, but I'm going to
>>> > > sleep first. Stay tuned.    
>> > 
>> > The 5 probably was a "lazy fix".  You could probably replace it by 3.5
>> > but, well, I think I'd prefer a less ugly solution if you can reasonably
>> > come up with one.  
> Main reason I do not want the 3.5 workaround is that I wouldn't want my
> major chords to look like c4:3.5...
> Attached is a new patch. It patches scripts/musicxml2ly as before, with
> r'{}' for a major chord.
> The solutions for the invalid combinations are provided in
> python/musicexp.py. A colon is added if a colon-less chord (i.e., major)
> has modifications. Adding additions checks for a trailing digit, if none,
> the leading period is omitted. Note that the changes in python/musicexp.py
> are harmless to an un-patched scripts/musicxml2ly.
> Also attached are chords.xml, a sheet of many chords based on the chart
> from NR A.1, and chords.ly, the desired output after conversion. There are
> a few discrepancies between the output from chords.ly and the chart from NR
> A.1, but these occur in very weird chords so I consider these harmless.
> Regards,
>       Johan

I have created


The Rietveld issue is owned by myself but I have added you as a CC so
you can see any comments from the other developers.




reply via email to

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