[GPx import] Missing clef in MusicXML generated from file in #34781
After fixing #34781: Exporting MusicXML causes crash and #35146: [MusicXML] invalid MusicXML generated from file in #34781, the file produced when exporting the 'E. Guitar 1' part as MusicXML does not import correctly: the TAB staff is imported as a regular staff. This happens both in MuseScore and in Finale NotePad, suggesting the export is incorrect.
Comments
Caused by missing TAB clef for the second (TAB) staff in exported file.
There seems to be an inconsistency (bug ?) in the way clefs are used in MuseScores handling of multi-measure rests, am investigating what happens exactly. Probably not a MusicXML export issue.
Attached two files that illustrate the issue:
E. Guiter 1.mscx is the relevant fragment from the file referred to in #34781
FromScratchByWizard.mscx is similar, but created by the "new score" wizard.
The first exports incorrectly to MusicXML, the second exports correctly. The difference (as shown in the debugger) after import is in the number of clefs present in both (!) measures 1:
E. Guiter 1.mscx has one with two clefs and one with one clef.
FromScratchByWizard.mscx has one measure 1 with 2 clefs and one without clefs.
Furthermore, after creating a similar score, but before saving / reloading, the debugger shows 2 clefs in both measures 1 !
It would seem this not a MusicXML export issue, but a bug in the way clefs in multi-measure rests are handled. I will not investigate that (due to lack of expertise int that area).
Lowering the priority to normal, as I expect it to only affect GPx scores with parts with two staves with different clefs starting with a multi-measure rest.
Could also be a GPx import problem.
relates to #270643: [EPIC] MusicXML import/export issues