Chord symbols not imported from .gpx files when fretboards are present
Reported version
3.2
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
duplicate
Regression
Yes
Workaround
No
Project
Musescore 3 seems to have lost the ability to export chords? See attached. I imported the same GuitarPro GPX file into v2 and v3 of Musescore and exported MusicXML. The v3 XML contains no tags for chords ("harmony" or "frame") and seems to just throw them away. v2 DOES have chord info retained in the exported XML.
1.) Import GPX
2.) Export uncompressed MusicXML.
I marked regression as this strikes me as a loss of critical functionality.
*Note that the GPX import process also throws away all of the layout information, so I put in my own line and page breaks in Musescore to match the original before exporting these XMLs.
| Attachment | Size |
|---|---|
| v3_12 Days of Christmas.musicxml | 320.94 KB |
| 12 Days of Christmas.gpx | 55.33 KB |
| v2_12 Days of Christmas.musicxml | 427.76 KB |
| _12 Days of Christmas.mscz | 39.41 KB |
Comments
I don't own guitar pro, so I can't confirm anything regarding that. I tested this using version 3.2.3. I opened the v2...musicxml file in version 3.2.3 and saw the chord symbols. I then exported this to .musicxml and examined the contents and the chord symbols were there. I opened this file in both versions 2.3.2 and 3.2.3 and the chord symbols were present.
In reply to I don't own GP, so I can't… by mike320
Correct. Musescore 2 exports correctly, and 3 recognizes chords when importing. The problem is that 3 doesnt EXPORT chord info. If you export from 3 and pull back into 3 ( or anything else) there will be no chords. They're no longer in the XML at all if you export from 3.
As I reported before, I exported the score from 3.2.3 to musicxml and imported it to both versions 2.3.2 and 3.2.3 and the chord symbols were present in both imported versions.
My apologies, I misread your steps.
Interesting. Your steps weren't quite the same as mine. You're correct that with musicXML exported from 2, and then pulled into 3, v3 DOES then export with chords.
These were my steps:
1.) Open the attached .mscz in Musescore 3.2.3 (or open the .gpx), you will see fret diagrams only - no text labels. (This is how it appears in v3 when opening a GuitarPro file).
2.) If you then export from 3.2.3 using the file in this state, it will come out with no chord data.
This "GuitarPro in; XML out" workflow works fine in v2, but not v3. It's as though v3 is interpreting the chords differently - in such a way that they get disregarded on export. Opening the .gpx in v2 results in chords with diagrams AND text labels, so it seems there's something different in the way they're being handled. Let me know if you can't recreate.
Sorry to overgeneralize in the initial complaint.
Where did the .mscz come from? There are no chords on the diagrams. If there are no chords on the fretboard diagrams, how do you expect MuseScore to decide which chord to assign to them?
The .mscz is what it looks like when you open the .gpx file in 3.2.3.
The fretboard diagrams are the correct fingerings for the chord they're describing, so SOMETHING about the identity of the chords is being captured. Musescore seems to know what chord it is.
Again, v2 imports the same .gpx with fretboard diagrams AND labels. 3 is handling these differently.
The point is that v3 is losing some information in this exchange that v2 isn't.
It's starting to sound like the issue isn't actually with the XML export, but with the .gpx import in v3. This issue should probably be re-titled?
I actually forgot that MuseScore can open .gpx files, so yes the problem is with .gpx import. Title changed appropriately.
Duplicate of: #232851: [GP6] Fretboard diagrams are imported but not the corresponding chord symbols