Completely inaccurate interpretation of MusicXML file

• Mar 4, 2012 - 18:23

I created a MusicXML file with Finale PrintMusic and attempted to import it into MuseScore. I have done this a few times in the past and it's been fine. This time the result is just totally dominated by errors -- empty measures in some lines, wrong durations, etc. If I re-import the MusicXML flle into PrintMusic it looks fine, so I don't think the problem is with the XML. I tried exporting from PrintMusic into several different versions of MusicXML (2.0, 1.1, compressed or not) and got the same result. I don't know what is different about this case other than it is a different piece of music. I am attaching the musicXML file, the MuseScore file, and pdf's made from PrintMusic and from MuseScore.

I don't know if this problem is related to some of the other more specific MusicXML bug reports -- there are just so many errors that I don't know where to start. But if the attached MusicXML file reads correctly into one of the new post-1.1 builds I would be anxious to try one -- except that I don't see any posted for Mac OS X.

I'm running on Mac OS X 10.6, MuseScore 1.1

Attachment Size
Vecher.xml 329.22 KB
Vecher.mxl 14.1 KB
Vecher_finale.pdf 83.73 KB
Vecher_MuseScore.pdf 153.04 KB

Comments

I do think listing specifics helps. At first glance, it looks fine up until measure 17, and that's you start getting blank measures in the piano part. Everything else is fine as far as I can tell until measure 25, at which point the same thing happens in the tneor 2 part. Looking at those bars in the PDF from Finale, they appears already corrupt before you even exported to MusicXML - there are 2.5 beats in each of those measures. I would bet that is the source of the problem.

FWIW, loading it into a more recent build does seem to fix that particular issue - the measures are no longer blank, and the corrupt measures are "correctly" reproduced (same as in original - with 2.5 beats each, and the "actual" signature of those bars altered to reflect this).

In reply to by Ron Cohen

Just checked the current 0.9.6 branch (this will be the 1.2 prerelease early next week), as far as I can tell the problem does not occur. Please check 1.2 prerelease as soon as it is out and report any issues you find, so they can be fixed before the final 1.2 is released.

Also note that currently the MusicXML import in the branch works better than in the trunk. Reason is that 1.2 is near while 2.0 is probably about half a year away. Thus bug fixing has been focused on 1.2. As far as I know the nightly builds are for the trunk only.

Do you still have an unanswered question? Please log in first to post your question.