Chord Symbols Not Displaying Properly in Parts

• Feb 2, 2023 - 17:35
Reported version
4.0
Type
Graphical (UI)
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
duplicate
Regression
Yes
Workaround
Yes
Project
MuseScore

The issue presenting is that Chord Symbols will not display correctly within parts.

How to recreate:

1.) Open any project in Musescore 4.0.1

2.) Add chord symbol to any measure on any instrument (Ctrl/Cmd+K)

3.) Open the part page of the instrument you added the chord symbol to

4.) You will observe that the chord will not have the note name present and will not be in the correct font style/display the correct notation for chord symbols

This is an especially frustrating bug, as I am someone who frequently uses Musescore for jazz, funk, and other styles that rely on chord symbols. I implore a dev to research this and see what needs to be fixed. Thank you!

(For helpful purpose, I've attached the file I was using when I discovered this bug.)

Attachment Size
KateBush.mscz 184.15 KB

Comments

• Feb 2, 2023 - 20:52
Regression No ⇒ Yes

For chords to work properly in MuseScore the program has to load a chord definition XML file every time you open a score. Once the chord definitions are loaded, everything works great. In V4, this file is no longer loaded as it was in v3.6 and the end result is endless problems with chords everywhere from in fretboard diagrams to file imports. It's always the same thing; chord C7 shows up a 7 and chord G doesn't show up at all.
Anyways, this is a major regression. They know exactly what it is and how to fix it. The only thing left is to convince them to take it seriously.

Reply

• Apr 14, 2023 - 08:38
Status needs info ⇒ active
Frequency Once ⇒ Many
Severity S3 - Major ⇒ S1 - Blocker

I have the very same issue. I want to load an xml that I've written or found and edit it in musescore to upload and share but since the chords "disappear" when I try to input them it's useless.

Reply

• Jun 19, 2023 - 08:19
Regression Yes ⇒ No

I was having the same issue with an imported midi track. For some reason, saving it as a .mscx file seemed to fix the issue.

Reply