Attached file still triggers this issue with the current 3.x. It contains one of the parts found in the original mscz file in https://musescore.org/en/node/326798, but with most of the notes removed.
And the fix for that it to have the keysig (3 sharps) at the first measure, not at the first after all mm-rests, then also the exported musicxml is clean!
Comments
Came up again in https://musescore.org/en/node/312225
Relates to #270643: [EPIC] MusicXML import/export issues
Sorry for multiple reporting.
I should have searched on "direction-type" to see that the problem was already reported.
Could not get reproduced in current master (e3ec24f of 2021-07-30)
Attached file still triggers this issue with the current 3.x. It contains one of the parts found in the original mscz file in https://musescore.org/en/node/326798, but with most of the notes removed.
Isn't it then a duplicate of #326798: [MusicXML] Ties in cue notes?
The issue does not occur in the current master though.
It does happen in 4.0.0 too
With the XML from https://musescore.org/en/node/341231
Came up again in https://musescore.org/de/node/341863#comment-1191886 (along with mscz and mxl)
Has the issue with 3.6.2, 4.0.2 and the latest development builds
See https://www.w3.org/2021/06/musicxml40/musicxml-reference/elements/direc…
Content
Exactly one of the following
...
But here they are empty:
... <direction placement="above"> <direction-type> </direction-type> <sound tempo="72"/> </direction> <direction placement="above"> <direction-type> </direction-type> <sound tempo="72"/> </direction> ...Here apparently lacking
<words>...</words>?, but in other placxes it is justInterestingly with the score from that report Mu4 crashes when exporting it to MusicXML with Multimeasure rests disabled
And the fix for that it to have the keysig (3 sharps) at the first measure, not at the first after all mm-rests, then also the exported musicxml is clean!