Unrecognized chords containing special characters in 1.3 scores rendered as markup

• Aug 8, 2014 - 23:22
Type
Functional
Severity
3
Status
closed
Project
MuseScore

1. Open attached score (produced in 1.3).

Expected result:

Special Characters in chords of 1.3 scores don't appear (Expected result).png

Actual result:

Special Characters in chords of 1.3 scores don't appear (Actual result).png

Note: The flat was generated via the Special Characters.

Using MuseScore 2.0 Nightly Build (5a616ff) - Mac 10.7.5.

Attachment Size
Special Characters in chords of 1.3 scores don't appear.mscz 1.53 KB
Special Characters in chords of 1.3 scores don't appear (Expected result).png 32.33 KB
Special Characters in chords of 1.3 scores don't appear (Actual result).png 42.21 KB

Comments

• Aug 9, 2014 - 04:33
Title Special Characters in chords of 1.3 scores don't appear ⇒ UInrecognized chords containing special characters 1.3 scores rendered as markup
Severity ⇒

FWIW, that's not how chord symbols are supposed to be entered - that's basically an incorrect input file. You are supposed to enter the flat sign as "b" and have it automatically turned into a flat sign. The chord as you have it is unrecognized in 1.3, that's the source of the problem. But it is true that even incorrectly entered chords should render as closely as possible to 1.3, so I'll take a look.

Reply

• Aug 9, 2014 - 11:47
Title UInrecognized chords containing special characters 1.3 scores rendered as markup ⇒ Unrecognized chords containing special characters in 1.3 scores rendered as markup
Severity ⇒

I think characters unaccessible via keyboard prompted me to use this method.

I know it probably will have been improved for 2.0, but I just wondered if it was possible to be compatible.

Reply

• Aug 9, 2014 - 14:37

Ah, yes, that doesn't work for some chords with stdchords.xml in 1.3.
I use a fixed stdchords.xml for that.
It does work just fine for a plain Eb though, except that the b is too close to the E or B, so it is hard to tell them apart. That too is fixed in my version of stdchords.xml

Attachment Size
jojochords.xml 13.44 KB

Reply

• Aug 9, 2014 - 14:36

Fwiw, the problem isn't your keyboard, or anything generally wrong with the recgonition of "b" for flat sogn. It's that this particular chord symbol was not comfigured correctly in the default chord symbol file (stdchords.xml) in 1.3. The chord was actually recognized just fine when you typed Em7b5; it just didn't render correctly because of a typo in entry for thay chord in that chord style. Had you left it alone, it actually would have imported just fine, since it was nonethless recognzied. But treyng to force a flat sign into a chord symbol guarantees it won't be recognized - meaning it won't transpose, won't export to MusicXML, and won't be converted properly onto 2.0

Unfortunately, while I can fix the rendering of these bad chords in 2.0, they probably still won't be recognized properly. Meaning they won't transpose, won't export, etc.

And of course, the issue of the bad entry in stdchords.xml is rendered moot by the fact that the chord symbol paraing and rendering system was completely overhauled for 2.0; there is no more explicit of chords that have to be typed exactly as expected in order to be recognized.

Reply