Time signature is not imported with XML file
In version 2.0, when I import a XML file, the time signature is not imported, the score is without time signature.
Do you still have an unanswered question? Please log in first to post your question.
In version 2.0, when I import a XML file, the time signature is not imported, the score is without time signature.
Do you still have an unanswered question? Please log in first to post your question.
Comments
With any score? Can you share an example?
In reply to With any score? Can you share by Jojo-Schmitz
Hi,
Yes it is with any score.
I attached the following files:
original xml file: 14f
file imported in Musecore 1.3: 14f musecore 1.3
file imported in Musecore 2.0: 14f musecore 2.0
In reply to Hi, Yes it is with any by Bomboora
It is definitely not with *any* score; I have dozens that all work fine. In the case of your particular file, it seems to be the "symbol=normal" attribute on the "time" tag that is throwing off the import. I don't know what that is supposed to do, but it is not needed. When I delete it, it works correctly. Or you can simply add the time signature after importing.
In reply to It is definitely not with by Marc Sabatella
Indeed, the importer does not expect / incorrectly cannot handle the "symbol=normal" attribute. Trivial to fix, too bad this was reported just a week after 2.0, or it would have been fixed.
See #53346: [MusicXML import] incorrectly cannot handle the time elements "symbol=normal" attribute
In reply to Indeed, the importer does not by Leon Vinken
The file was generated with Sharpeye 2, one of the best music scan software I encountered.
I use it a lot to scan scores and import them into Musecore. It is indeed not a big problem, you can add the time signature afterwards.
In reply to The file was generated with by Bomboora
It is a big problem if you have a lot of changes in time signatures e.g. 3/4 to 4/4 and back to 3/4 then notes span over different measures and all is messed up.
Work around : import in version 1.3 save as .mscz and then open in 2.0 to do adjustments
Would like to see it fixed as fast as possible.
Daniël Lamair Belgium
In reply to It is a big problem if you by daniellamair
See above - it is already fixed a few weeks ago in the nightly builds. Should be in the next bug fix release 2.0.1 as well.