[Top][All Lists]

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

Re: wrong note name conversion in musicxml2ly

From: Torsten Hämmerle
Subject: Re: wrong note name conversion in musicxml2ly
Date: Tue, 11 Feb 2020 08:59:38 -0700 (MST)

In any case, the current musicxml2ly problem is about heses. And the heses
note name definition in LilyPond (scm/define-note-names.scm) is correct and
should not be changed.
musicxml2ly must not produce a German "bes", because this clearly should be

Here's the coding for German pitch names:

Replacing generic "hes" by "b" is OK, but, that way, generic "heses" will
become "bes", wich is clearly wrong and will lead to the error observed.

So obviously, it's a problem with *python substring replacement*.
I don't know much about python, but replace() doesn't seem to work out here.
Probably only a direct string comparison will help here, perhaps someone
knowledgeable has a more elegant solution.

dak wrote
> That looks almost like something I could work with, except for beh .
> For all other note names, the suffix -eh indicates _lowering_ by a
> quarter note, whereas beh _raises_ b by a quarternote.  Shouldn't it
> rather be heh , making b the _only_ exception?

Yes, "beh" should definitely be "heh".

In my never ending triple-flat-issue 3356, here are the triple flat/sharp
range German note names:
The incorrect original beh has been replaced by the correct heh:
"beh" hasn't even been kept because it is inherently inconsistent:

All the best,

Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html

reply via email to

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