[MusicXML] Ties in cue notes
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
Hello,
We bumped into ill-formed MusicXML data in the attached file, that comes from the MuseScore repository. It was created by :
MuseScore 2.1.0
The problem is that it contains several elements in cue notes, starting at line 134434:
E
4
18
1
quarter
up
Opening this file leads to an error message alright, but exporting to MusicXML retains this feature.
HTH!
Jacques Menu
Attachment | Size |
---|---|
The_Legend_of_Zelda_Medley__A_link_to_the_past_Concert_Band_original.mxl | 269.48 KB |
Comments
embed that xml in <xml>...</xml> to have them readable here
The error message on the mxl import is:
Fatal error: line 134434 column 27 Element tie is not defined in this scope.
The xml code at that place is:
It the file comes from MuseScore 2.1.0, why then using an mxl rather than an mscz?
Like from
https://musescore.com/gdupertuis/the-legend-of-zelda-a-link-to-the-past
the mscz from there opens cleanly
But yes, downloading that mscz, exporting as xml and importing it back does lead to that error and in more than one place
I wonder whether this is related to #303793: [MusicXML import] series of tied notes does not work if tied order is start stop
Relates to #270643: [EPIC] MusicXML import/export issues
For easier debugging I attached a (small) snippet from the original file that still demonstrates the issue. Checked the MusicXML spec, which states "Cue notes have a element, as do elements, but no elements.", which may very well explain the issue.
"Cue notes have a element, as do elements, but no elements." What???
Forgot to remove or quote the less than / greater than symbols. Text should have been "Cue notes have a duration element, as do forward elements, but no tie elements".
Indeed the current MusicXML exporter (both 3.x and master) happily generates tie elements for cue notes. Preventing this solves the issue, which is a trivial fix.
In reply to I wonder whether this is… by Jojo-Schmitz
No, I don't think it is related to the other issue (which affects import of all notes, while this relates to export of tied cue notes).
Last reply meant for reply by Jojo-Schmitz • Nov 25, 2021 - 10:15.
Overlooked the fix in master, this is a duplicate of #319776: [MusicXML export] Invalid MusicXML will be generated if exported sheet contains tied cue notes, fixed in branch master, commit 34676d440a, Apr 28, 2021.
I am not closing the issue, it might be useful to fix in the backend, as long as that keeps running on 3.x.
It is part of my https://github.com/musescore/MuseScore/pull/9000 too.
Your https://github.com/musescore/MuseScore/pull/7935 might get used for 3.6.2_backend
Maybe you reopen yours and rebase to that branch?
That XML fails in 4.0.0 to0