Crash When Saving .mscz file as MusicXML

• Sep 7, 2010 - 22:01
Type
Wording/Translation
Severity
S4 - Minor
Status
closed
Project

Whenever I try to save ANY arrangement I've entered using MuseScore 0.9.6 Rev. 3145, the program bombs. I get a very small .xml file which MuseScore cannot open. I've attached the .mscz file and the corrupt .xml file.


Comments

Removing the palette lines stopped the crashing (see file attached).

If I create a new score using MuseScore 0.9.6.2 that includes lines it doesn't crash when I save to MusicXML. If you work out the steps that are causing the problem please share. In the mean-time I recommend upgrading to the latest stable version of MuseScore.

In case you aren't aware, MuseScore lyrics have support for syllable extenders built-in so you don't need to worry about creating your own lines and adjusting the size manually. For details see Lyrics in the handbook.

Attachment Size
Under New Mexico Skies.mscx 388.94 KB

I'm having the same issue on the current version of 0.9.6.3.

The attached is a sax quartet piece created in MuseScore 0.9.6.3.

In the attached compressed musescore file, it opens without issue in either Linux or Windows. I started editing in Linux (Ubuntu), finished in Windows.

Have tested the attached file in Ubuntu 10.04, Ubuntu 10.10, as well as with Windows 7. Every time was consistently MuseScore 0.9.6.3. Every version crashes when saving to MusicXML.

I'd like to be able to export this to musicxml so I can give to another player who has Finale.

Any suggestions?

Attachment Size
Sax Quartet.mscz 34.02 KB

Thanks, appreciate the response, could you please provide more information how that helps with MuseScore crashing when attempting to save to MusicXML?

Thanks!

It doesn't. I just thought I'd tell you a workround. Save it as a .mscz then unzip it and it will generate a .xml. The developers will have to look at the bug!

The main thing I'm trying to do is output a MusicXML file so the score can be shared with someone using another music notation software. Are you saying the resultant xml file when unzipping from the .mscz file will be readable by something like Finale? If so, I'd be very happy with that as a workaround :)

ncookit: Removing the palette lines stopped the crashing (see file attached). If you work out the steps to reproduce the problem (starting from a new score) please share.

cwhysall: MusicXML is an exchange format that is different from MuseScore files. For details see [[nodetitle:Export]] in the handbook.

Attachment Size
Sax Quartet.mscz 32.87 KB

Wow, first off let me say how incredibly impressed I am about the remarkable responsiveness of this forum. I had earlier gratefully downloaded the software and made excellent use of it. I had then noticed a possible issue, google-searched to find someone with a similar issue, then created an account to contribute my findings. I sincerely had not expected to receive responses, let alone a workaround for my concern, the same day I entered my issue. Seriously, that is impressive and I am sincerely thankful. :)

I have grabbed the file that David attached and it works great to export to xml, very awesome!

Specifically which palette lines were removed? And how'd you know what to look for? From a quick glance I see that a number of the Lines and Crescendos I entered from the "Line" Palette are still there. I know I added many Lines from the Line Palette due to wanting a squiggly "gliss" line that led into and out of some notes as the gliss from the "Arpeggio & Glissando" Palette wasn't quite what I wanted. Also the squiggly lines from the "Articulations & Ornaments" refused to change their angle (but from what I've researched I expect this may come in a future version).

If I don't hear back or if it's too much of a bother, I'll likely just see about printing off both scores and do a comparison myself. I'm quite impressed and happy with MuseScore so far and I'd like to help in whatever way I can. If I can work out the steps from another fresh score, I will absolutely share :)

I think I just removed the simple, straight lines. I was editing the uncompressed (.mscx) version of the file using a text editor. I removed any tags with the work "line" in them. I knew to look for these based on comment #1 (above).