Clef change export/import in MusicXML switches side of barline

• Jul 2, 2017 - 22:04
Type
Functional
Severity
S4 - Minor
Status
active
Regression
No
Workaround
No
Project
Tags

When saving clef changes to a MusicXML file export, and then reloading the same MusicXML file back into MuseScore, the clef change is incorrectly displayed after the barline.

When creating a clef change initially in MuseScore, the position is correct:

Screen Shot 2017-07-02 at 10.19.16 PM.png

The clef change for the second measure was created by dragging the bass clef from the palette into the second measure. This caused the clef to be displayed at the end of the previous measure (as is conventional and expected).

When exporting the file as MusicXML and reloading the same file back into MuseScore, the clef change moves from before the barline to after it:

Screen Shot 2017-07-02 at 10.19.29 PM.png

Loading the same MusicXML file created with MuseScore into Finale 25.2, the clef position is correctly placed before the barline (even though the clef change is placed in the second measure in the MusicXML data).

Screen Shot 2017-07-02 at 10.49.21 PM.png

Saving the same data to a MusicXML file in Finale will place the clef in the second measure as well, so the problem is that when reading a MusicXML file, MuseScore should display clef changes properly at the end of the previous measure when they are stored at the start of a measure.

When saving and reloading a MSCZ file, the clef position remains correct on reload.

Attachment Size
oneclef-finale.xml 7.31 KB
oneclef.xml 6.07 KB
oneclef.mscz 4.26 KB

Comments