Project unable to open after crash
Hi! I'm currently using Musescore version 4.4.2 on my Macbook Air to work on a full orchestra piece that's about 10 minutes in duration.
I've just duplicated the original file to begin working on percussion part assignments, which caused the first corruption in the score to appear in the cymbals part, crashing when I tried to fix the corrupt measures, so I ended up manually re-entering the notes into a duplicated instrument. That solved that issue, but the incorrect beat count corruption happened again in an instance where I was going to change the 5/4 bar to a 3/4 with a 2/4 following it, so that solved that issue also. I'm guessing since the project was getting so dense with articulations and instrument/staff type changes that it became too large and less stable?
However, the last crash that happened was while I was changing a redundant triplet (image 1).
After the crash, I tried opening but I just keep getting the mac loading circle and over time, my storage starts to fill up to the limit (245gb), and I get this message (image 2). This is my current macbook storage (image 3), and before this, I deleted about 20gb worth of documents to see if that would solve the issue, but it seems that it just keeps generating more space the longer it tries to open the project. I think the file is just too corrupt to open because It shouldn't be that different in size from the one it was duplicated from, which still opens fine, but all of my part assignments, instrument changes, and edits that I've spent the last 3 days working on are on the duplicate.
Any help on this matter would be very greatly appreciated, thank you!
Comments
In reply to Your images did not attach… by mercuree
Sorry, I'm not sure why that is, lets see if this works.
The one titled fallingtidesrise-percussion.mscz is the duplicate.
In reply to Sorry, I'm not sure why that… by joshuaecp2005
Here are the images that were supposed to go with the original post
In reply to Sorry, I'm not sure why that… by joshuaecp2005
In reply to I'm attaching the file… by mercuree
First, thank you so much! I am able to open the file and the biggest changes I made since the last save are still there. Most of the work that I was doing was adding the instrument changes in the percussion parts so those are still present, so the only thing that's gone are the staff type changes in the parts. Also, it is interesting that this issue is only present on Mac. I would appreciate any further look into this, thank you so much again though!
In reply to First, thank you so much! I… by joshuaecp2005
The issue was reported on github https://github.com/musescore/MuseScore/issues/25145
From what I've learned, don't add multiple StaffTypeChange elements to the same measure.
Although I'm not 100% sure that was your case.
In reply to The issue was reported on… by mercuree
mercuree,
FWIW (probably not much) I opened a short string orchestra file. I opened the 2nd violin part and made three changes in one measure. No percussion, so it might not mean much. Anyway, I added a key change, a meter change and an instrument change. Now I use Save As ( title and new version number), not just save, which has saved me on occasion. Reopen and remove one change, and Save As. Close and reopen, remove a change, and so on. I did this with the individual part also. I had no problem. 442 with Musesounds. I think Save As with a new version, may be the reason I didn't have any problem. I'd be interested in knowing if it makes a difference on a Mac.
In reply to mercuree, FWIW (probably not… by bobjp
Saving a copy of the project via "Save as" is a good practice. But in this case it won't help.
![scale_field2.png]( "scale_field2.png")
I can't open fallingtidesrise-percussion.mscz which the author attached.
I found out that the reason for this is the <mag>0</mag> tag with a zero value. It is responsible for the Scale field for the StaffTypeChange element.
But the minimum value for this field is 20% and you can't specify 0 there.
That is, the author didn't put 0 in this field. Musescore does this somehow and it is obvious that this action is incorrect.
Then Musescore saves this value to the file.
Such a file no longer opens, although it is not corrupted.
In reply to Saving a copy of the project… by mercuree
2 observations.
I unzip the original mscz file, open the resulting folder and delete the elements folder. The mscx file in that folder will then open.
I change the extension manually from mscz to mscx. When I try to open, it does say the file is corrupt with this message.
Error=XML_ERROR_PARSING_TEXT ErrorID=8 (0x8) Line number=1.
And does not open.
In reply to 2 observations. I unzip… by bobjp
If you change the extension from mscz to mscx, the contents of the file remain the same. It is still a zip file. But Musescore looks at the extension and tries to open it as an xml document, and when it can't do that, it throws an error.
Something else to think about.
Yes, you are supposed to be able to make changes in parts and have them reflected in the score. But there are time when this does not work. Consider making changes in the score, instead. Do you need all the parts open?
In reply to Something else to think… by bobjp
Hi! No, I didn't need all the parts, just the percussion parts that I was adding instrument changes to. What I was doing was making all instruments that would be used by a given player visible in a part, adding instrument changes to those parts and pasting the lines onto them, as well as changing the staff types. And I did notice that they wouldn't transfer over from the parts onto the score, so I'll consider that after all.
Also, I'm not sure if I'm just missing something but I can't seem to add key signatures after it switches from an unpitched instrument to a pitched one, resulting in awkward accidentals for any notes outside of the key of C. I can't edit this in the parts nor the score.
Which instruments are you switching between?.
In reply to Something else to think… by bobjp
I have 3 percussionists excluding the timpanist sharing different combinations of instruments, including vibraphone, marimba, glockenspiel, chimes, toms, wood blocks, bass drum, mark tree, slapstick, triangle, snare drum, and bass drum. Part assignments were an afterthought with this project, so they all use at least 5 instruments throughout a single percussion part.