3.5.0.13199 mis-interpreting musicXML?
As titled with attached, a pdf was scanned and exported to musicXML with correct time signature, but it was interpreted by 3.5.0.13199 to wrong timing?
Scanning Result:
MS Result:
Do you still have an unanswered question? Please log in first to post your question.
Comments
The .xml:
In reply to The .xml: by Xianyue賢越
See: P24.mscz
In reply to See: [inline:P24.mscz] by cadiz1
Yes, it's the result I got.
In reply to Yes, it's the result I got. by Xianyue賢越
??
The score I've attached (first reply) is no longer corrupt!
I.e, this one: P24.mscz
In reply to . by cadiz1
yes, thanks, how do I quickly correct it to 3/8 time signature? as this original.
output.pdf
In reply to yes, thanks, how do I… by Xianyue賢越
That pdf doesn't show a time signature, so no wonder the xml doesn't have it either
Seems there are previous pages missing?
In reply to That pdf doesn't show a time… by Jojo-Schmitz
yes, previous pages (first page has 3/8 mark) were cut with focus on the issues part, experienced no difference. I can provide them if need.
In reply to That pdf doesn't show a time… by Jojo-Schmitz
As a try, I edited pdf by adding 3/8 mark on the page of starting, it resulted the same as before: on scanning software it shows and plays correct and on MS not.
In reply to yes, thanks, how do I… by Xianyue賢越
"yes, thanks, how do I quickly correct it to 3/8 time signature? as this original."
Quickly?! Well, enter your score directly into MuseScore! :)
Rather than expecting all the wonders of a PDF conversion whose results are known to be very random, and sometimes really disappointing, corruption, missing measures, wholly or partly, and so on (at least, for this score, or this excerpt.)
In reply to . by cadiz1
It's not a one page score and I am always scanning and correcting to perfect.
is there a protocol issue with the scanning software?
It is reported as being corrupt:
Measure 1, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 2, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 3, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 4, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 5, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 6, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 7, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 8, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 9, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 10, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 11, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 12, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 13, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 14, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 15, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 16, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 22, staff 2 incomplete. Expected: 1/1; Found: 5/4
Measure 22, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 22, staff 4 incomplete. Expected: 1/1; Found: 5/4
Measure 22, staff 5 incomplete. Expected: 1/1; Found: 5/4
Measure 22, staff 6 incomplete. Expected: 1/1; Found: 5/4
Measure 22, staff 7 incomplete. Expected: 1/1; Found: 5/4
Measure 22, staff 8 incomplete. Expected: 1/1; Found: 5/4
Measure 22, staff 9 incomplete. Expected: 1/1; Found: 5/4
Measure 23, staff 2 incomplete. Expected: 1/1; Found: 5/4
Measure 23, staff 3 incomplete. Expected: 1/1; Found: 5/4
Measure 23, staff 4 incomplete. Expected: 1/1; Found: 5/4
Measure 23, staff 5 incomplete. Expected: 1/1; Found: 5/4
Measure 23, staff 6 incomplete. Expected: 1/1; Found: 5/4
Measure 23, staff 7 incomplete. Expected: 1/1; Found: 5/4
Measure 23, staff 8 incomplete. Expected: 1/1; Found: 5/4
Measure 23, staff 9 incomplete. Expected: 1/1; Found: 5/4
Measure 24, staff 2 incomplete. Expected: 1/1; Found: 5/4
Measure 25, staff 2 incomplete. Expected: 1/1; Found: 5/4
Measure 31, staff 2 incomplete. Expected: 1/1; Found: 5/4
Measure 32, staff 2 incomplete. Expected: 1/1; Found: 5/4
Measure 33, staff 2 incomplete. Expected: 1/1; Found: 5/4
Measure 38, staff 2 incomplete. Expected: 1/1; Found: 5/4
Measure 38, staff 4 incomplete. Expected: 1/1; Found: 5/4
Measure 38, staff 5 incomplete. Expected: 1/1; Found: 5/4
Measure 38, staff 6 incomplete. Expected: 1/1; Found: 5/4
Measure 38, staff 7 incomplete. Expected: 1/1; Found: 5/4
Measure 38, staff 8 incomplete. Expected: 1/1; Found: 5/4
Measure 38, staff 9 incomplete. Expected: 1/1; Found: 5/4
Measure 38, staff 10 incomplete. Expected: 1/1; Found: 5/4
Once ignoring that it does load, but all expectations of it being correct are off
In reply to It is reported as being… by Jojo-Schmitz
From the very beginning I started to use MS, it always reported scanned xml "Corrupt", and I always clicked "ignore" and got almost correct MS score, but not this time with such a big timing mis-interpretation.
In reply to From the very beginning I… by Xianyue賢越
Seems the xml is missing a time signature, so MuseScore assumes 4/4, which here is wrong apparently.
In reply to Seems the xml is missing a… by Jojo-Schmitz
is there a quick remedy?
In reply to is there a quick remedy? by Xianyue賢越
None that I'd know of
Further test reals MuseScore does not interprete time signature correctly:
![1.JPG]()
![2.JPG]()
1. Libiamo ne' lieti calici.pdf was scanned as 3/8 and played correctly
2. saved to xml: Libiamo ne' lieti calici.xml
3. Opened to MS with "ignore"
By cross referencing it in short with soundslice (https://www.soundslice.com/musicxml-viewer/), maybe the first one xml-file is more an issue of the scan application, the second one maybe indeed an import issue of musicxml files with MuseScore.
In reply to By crossrefferencing it in… by kuwitt
Thanks, for this viewer, it could be a very useful online tool late for scoring.
Regarding the two xmls:
The pdf source: https://imslp.simssa.ca/files/imglnks/usimg/9/97/IMSLP392068-SIBLEY1802…
![Capture.JPG]( "Capture.JPG")
The scan application:
The diff of two times processing:
1st one, raw pdf processed with scan application directly and export to xml without manually eliminating warnings and errors;
2nd one, raw pdf processed with "A-PDF Deskew" and then scan application, which had no warnings and errors, as you can see from two screen captures above (the red bars on the left panel).
In reply to Thanks, for this viewer, it… by Xianyue賢越
With the issue solving of 2nd one, the 1st one case would be also fixed regardless other score issues still exsitting.
Even though the time signature is missing, MuseScore does not interpret P24-36.xml incorrectly, the offending rests are already present in the MusicXML file and are interpreted correctly.
The 5/8 corruption is caused by measures containing a whole note plus a quarter. Once again, the are already present in the XML file.
In reply to Even though the time… by Leon Vinken
Both XML files contain many incorrect duration values, this has to be fixed in the generating program. MuseScore cannot be blamed for that (although more precise and explicit diagnosis would be useful).
In reply to Both XML files contain many… by Leon Vinken
MuseScore may be left as good as it is.
![Capture.JPG]()
While https://www.soundslice.com/musicxml-viewer/ interpreted "Libiamo ne' lieti calici.xml" in its own way as:
Are there different music xml standards/protocols/specifications?
In reply to MuseScore may be left as… by Xianyue賢越
Different versions, your's is 2.0, MuseScore uses 3.1 (but that should be compatible)
In reply to Differnt version, IIRC your… by Jojo-Schmitz
OK, thanks, I have already managed other way to go around this timing difficulty.
In reply to MuseScore may be left as… by Xianyue賢越
Only a single MusicXML "specification" exists (in several different but backwards compatible versions). It is sufficiently imprecise to leave a lot of room for different interpretations and thus different behaviour by various applications.
See #309189: [MusicXML import] report error handling when importing incorrect duration on whole notes