MusicXML export version and date tobik • Feb 10, 2019 - 17:10 Reported version 3.0 Type Functional Frequency Once Severity S4 - Minor Reproducibility Always Status by design Regression No Workaround No Project MuseScore Tags musicxml Export any score to musicxml The score contains MuseScore 0.7.0 2007-09-10 This is also what musicxml2ly will detect. Reply Comments Jojo-Schmitz • Feb 10, 2019 - 17:25 Regression Yes ⇒ No Tags View Changes I see <encoding> <software>MuseScore 3.0.2</software> <encoding-date>2019-02-10</encoding-date> Reply Jojo-Schmitz • Feb 10, 2019 - 17:25 Status active ⇒ needs info Reply Leon Vinken • Feb 11, 2019 - 06:38 In reply to (No subject) by Jojo-Schmitz This is caused by running MuseScore in debug mode (using the -d option): to simplify the autotester, it forces a fixed date and version. Reply Jojo-Schmitz • Feb 11, 2019 - 06:43 Status needs info ⇒ by design Reply
Jojo-Schmitz • Feb 10, 2019 - 17:25 Regression Yes ⇒ No Tags View Changes I see <encoding> <software>MuseScore 3.0.2</software> <encoding-date>2019-02-10</encoding-date> Reply
Leon Vinken • Feb 11, 2019 - 06:38 In reply to (No subject) by Jojo-Schmitz This is caused by running MuseScore in debug mode (using the -d option): to simplify the autotester, it forces a fixed date and version. Reply
Comments
I see
In reply to (No subject) by Jojo-Schmitz
This is caused by running MuseScore in debug mode (using the -d option): to simplify the autotester, it forces a fixed date and version.