Musescore.com .mxl Download sometimes creates invalid dates in archive

• Mar 4, 2019 - 14:35

When downloading certain scores as compressed MusicXML from musescore.com, the date of files in the mxl archive is invalid (00-00-1980).
Exporting to .mxl from MuseScore 3.0.2.20666 and 3.0.4 does create a valid date (current one).

This, for example, leads to an Error in a System Library in C# (ZipStorer), unfortunately. Of course, they should have better error handling and ignore invalid dates.

Still, i think MuseScore shouldn't set invalid dates.
If no date is available, it should give a default valid date (e.g. 01/01/1980 instead of 00/00/1980).

Sample score with invalid date in .mxl download:
https://musescore.com/user/11881/scores/4982061
(unfortunately i could not find a simpler score with this issue yet)

Most other scores have valid dates in the .mxl.

unzip -v output on the .mxl:

Length   Method    Size  Cmpr    Date    Time   CRC-32   Name
--------  ------  ------- ---- ---------- ----- --------  ----
     145  Defl:N      109  25% 00-00-1980 00:00 b76825c4  META-INF/container.xml
 2099134  Defl:N    87092  96% 00-00-1980 00:00 80183128  score.xml
--------          -------  ---                            -------
 2099279            87201  96%                            2 files

Attachment	Size
Mozart-Schmid_Sonata_for_Two_Pianos_arr._solo_piano_1st_mvmt.mxl	85.42 KB

Comments

Jojo-Schmitz

• Mar 5, 2019 - 07:54

Those files do get created a the time of the upload, so not much that could be done to fix this, except to reupload (or ask the author to do it) and hope the current version MuseScore backend doesn't produce this bogus file.
Might be better suited to get discussed on musescore.com, like in https://musescore.com/groups/improving-musescore-com/

SimonPiano

• Mar 5, 2019 - 15:29

Thanks! I will create a discussion on musescore.com.
I'm using another extractor for mxl in my program now, which doesn't throw Errors for invalid dates (ZipArchive instead of ZipStorer in System.IO.Compression).