Score does not open - unexpectedly quits!
I was just working on my score that I saved on my desktop. I noticed my mouse being sluggish so I closed out of musescore to restart it. As I opened my score, "Musescore quit unexpectedly." It continues to give me this error and will not open my saved file. This is an assignment for my class and I have too much invested in this score to have this problem. Thank you for your help!
I'm running Version 1.2
Computer: Mac OS X Version 10.6.8
| Attachment | Size |
|---|---|
| Build Me Up Buttercup.mscz | 19.49 KB |
Comments
Can't open on using MuseScore 1.2 WIndows 7 either. However, the nightly build of 2.0 I have installed (from a week or so ago) opens it OK. Looks a bit odd in places, but it's hard to know how much of that is score corruption and how much is just 2.0 not being as solid as it can be. Anyhow, if you don't have a recent backup (have you tried opening the backup version of the file MuseScore created, starting with a period and ending with a comma?), you can try starting from this XML file, exported from 2.0.
In reply to Can't open on using MuseScore by Marc Sabatella
BTW, just a complete guess, but the main thing I see odd has to do with placement of dynamics. Perhaps you attempt to fake the "fp" marking by attaching both an "f" and a "p" to the same note is part of the problem. Did you not realize there is an "fp" marking already? It's not in the scaled down subset presented in the palette at the left of the main screen, but it shopws up in the expanded palette you see when you press "L".
I opened the score in the nightly builds, exported a MusicXML, opened it in 1.2 and saved as mscz.
It's not perfect, but just incase the original file can't be fixed directly.
In reply to I opened the score in the by chen lung
the xml opens in Sibelius for me which looks like a jumbled mess. The mscz still won't open. AH!
In reply to the xml opens in Sibelius for by chelsey16may
Are you sure you are looking at the correct MSCZ file? You aren't trying to open the old one, are you? The one chen lung uploaded opens fine for me. Also, you shouyld be able to open the XML file in MuseScore - no need to use SIbelius for that. My limited experience is that Sibelius doesn't do that good a job reading MusicXML's.
Here is a fixed version based on your first file. It was a problem with tuplets.
The same exactthing happened to my arrangement, and I am very upset because worked very hard on it and now it won't open, with the same message. Does anyone know how to restore my file, or make it accessable again? The file is attached below.
In reply to Corrupted File by TigerMercury
Hi TigerMercury -
First, it's not necessary to post the same message both here and in another thread.
Which version of MuseScore are you using? Which operating system do you use?
Have you looked around in the same directory as your score for any backup files? The filename of the backup would begin with a period and end with a comma. You need to rename the file to remove the period and comma. If you do this, make sure to use a unique name, not the original name.
If there are no backup files, you can try downloading and installing a Nightly version. These are pre-alpha versions of the next MuseScore. A nightly build might be able to read your file. It is possible to have both MuseScore 1.2 and a nightly installed at the same time. Just go to the "Download" page by clicking on the Download link at the right side of this page and follow the directions. Be aware that a nightly build isn't really suitable for production work, as it is still under development.
Someone else might be able to repair your file, but you can try the suggestions above in the meantime.
Good luck!
Fifist
In reply to Things to try by Fifist
I can't get a nightly to open it, seems it goes into a tight loop, eating CPU cycles and drivint one of ma 2 cors to 100% busy.
In reply to Things to try by Fifist
Hi TigerMercury -
Have you been able to find a backup file in your working directory? That is certainly the easiest method, as long as it's not too far out of date. Just rename it and try to open it in MuseScore.
TigerMercury, please don't pay too much attention to the following part. I'm asking for help from any developers.
The good news is that the zip file is OK. I was able to unzip it and display the XML in a browser, which didn't complain about unmatched tags or anything.
Is there a DTD or something that can tell whether or not the file is well formed? Or is there at least a description of what the MuseScore 1.2 XML file is supposed to look like?
There are a very large number of tuplets in the file, which are known to have problems in MuseScore 1.2. Can anyone tell me what sorts of problems are "usual" for tuplets? I don't mind trying to fix the file, but I'm not sure what to look for. Any hints would be greatly welcome.
Fifist
In reply to Hi TigerMercury - Have you by Fifist
Hi TigerMercury -
I am attaching a mostly fixed file for you. The problem was in measure 16 of the third staff, which has a series of tuplets.
I put in some tuplets which are undoubtedly not the way you would like them notated, but the file loads and you can edit them yourself to be the way you want them.
When you are working with tuplets, please be very sure to save early, save often, as they can often be the source of problems, such as the one you saw.
Regards,
Fifist
Sally
In reply to Fixed, mostly by Fifist
Thank you SO much for all your help. Also, I apologize for posting twice, and once again, I thank you, you're the best! :)
At least it takes almost 5 minutes, and when it does load it won't do anything. After creating a 'lead sheet' if I actually add a note, or a chord, or do anything the page goes blank and the program freezes. It even takes 3 'force quit' attempts before it goes away!!!
System: Mac Dual Core 3Ghz: 6 gigs ram: OS 10.7.5
Why does it do this?
None of the 'updates' I have downloaded work either. Why not? (MuseScore 1.2 - you know...at the top of this very page where is says Free Download for OS Lion)
Well, your program no longer works. My fault, in the end. I should have purchased a professional program to start with and not tried to use this Micky Mouse joke created by morons without any musical education (and yes - you should get one before you try to design a program like this. When the program did work prior to the Lion upgrade it was a pain, and not very musically savvy.)
Goody bye and good riddance MuseScore - good luck suckers trying to use this joke program.
In reply to MuseScore won't open in 10.7.5 either!! by working-stiff
Um, that's extremely harsh and unfair. You apparently have some sort of unusual incompatibility issue on your system - what, who can say at this point - but the program clearly works for the vast majority of people. If you'd be willing to answer some questions from people more experienced with running MuseScore on Mac, I'm sure they would be able to get your straightened out in a few minutes - providing, of course, you don't insult them by calling them morons.
Byut if you'd rather pay hundreds of dollars for something else, you are of course welcome too. There are some fine options out there. But if you expect them to be 100% trouble free, or to be able to always get support for free, you're deluding yourself.
I believe MuseScore 2.0 (no release date yet) will be far better.
This could be attributed to the following:
1. For those who aren't able to compile, nightly builds are available for testing (they weren't for 1.x).
2. Git is said to be easier for developers and testers (SVN was previously used).
3. More people have come forth to assist and 2.0 is different from 1.2 development-wise - more issues can/have been detected and corrections/implementations are easier, whether it's the basics of notation rules, or something else (I don't think there was many people a few years ago and it was somewhat limiting and difficult to apply certain fixes to 1.x for reasons such as avoiding detriment to the application's function).