MacOSx - Keeps Closing on its own!
Hey Gang,
Great program, I've been really enjoying working with it....
Except that it keeps closing itself (without saving!) right in the middle of working with it! Just freezes up & closes, then offers to send an error report...
Any Ideas?
S.
Comments
Have you installed MuseScore following the instructions at Installation ?
If yes, can you find a pattern of things you are doing when it closes itself? Can you describe the steps to make it crash? or does it crash even if you don't use it?
I have been having the same problem under Win XP.
I was used to the unstable nature of the last version of MuseScore, and had developed good "saving" habits. The rule was never make two different types of amendment without saving in between.
In this version even that precaution does not seem to be preventing these instant shutdowns. With a great deal of disappointment, I'm pretty close to abandoning MuseScore.
Anyone want to tell me why I should keep away from Sibelius ?
Glyndwr
No it doesn't just quit when I am doing nothing, its when performing some function; adding notes or whatever. Only when I am right in the middle of something!
I've been trying to develop good saving habits as well, but I can hardly get through a single measure without it crashing. And yes I installed as per directions.
S.
glyndwr and sharp21,
Can you share the exact steps that cause MuseScore to crash for you? If you are not able to work out the series of steps, maybe you can share a Screencast that shows the what you do before MuseScore crashes.
The development team has a very good record of fixing crashes once they are fully documented and reported on this website.
In reply to glyndwr and sharp21, Can you by David Bolton
This 12-pager had become corrupted in areas that were out of vision. For instance, the loss of stems in the final A-men. I only saw that later when reviewing the overall appearance.
There were also issues with variable length measures/bars. I found that some bars contained notes which did not add up to the "actual" count I had set in properties. Other bars seemed to overrun a barline, and even to leave a stave with no closing bar line.
This set of preces and responses are the result of a lot of work, using various sources, and considering modern pronunciation. My aim was to reach a definitive 5-voice version, before going on to produce a further 4-part version. With so many difficulties I'm feeling MuseScore may not be the right way to tackle the project after all.
To save space I had decided to combine the bass and tenor lines onto a single clef (as others have done with sets like these). What would be the slickest way of achieving that ?
I'll attach the file so that if there are any lessons to be learned from it other users may benefit.
In reply to Here's my file by glyndwr_
It is possible that the crashes are a result of the issue described here: http://musescore.org/en/node/5903#comment-16304
The best I was able to do to recover the file was save to MusicXML, open in Finale 2007, and re-export to MusicXML (see attached). A lot of the frames and formatting is lost in this process but the file no longer crashes in MuseScore and the notes and lyrics are all there.
At work I have access to Finale 2011. I can try opening the MusicXML file there and see if the more recent version does a better job of retain the formatting.
if you are working with scores that have a number of "actual duration" measure property changes I recommend using a nightly build until 0.9.6.1 is release. Right now the Windows nightly builds are following what will become version 0.9.6.1 (a bug-fix-only maintenance release, no new features) so they are typically be more stable than 0.9.6. After 0.9.6.1 is released the nightly builds will switch over to their normal role of following new developments and features and will no longer be recommended for normal use.
In reply to It is possible that the by David Bolton
First of all a big thank you for looking into this.
I've followed these instructions (and surprised myself). "Nightly build" sounds like something I should avoid!
I've then saved the file as an mscz. I notice a lot of corruption from bar 40 to the end, with notes being a long way from where I felt I had put them! For example, the final bars of the long A-men have several bars following them. I've deleted those.
The bass lines for the final four bars 107-110 are sitting in 75-78, but right clicking on 107 does not give me the option to paste 75-78 into there.
Those are just two examples. A lot of the work from bar 41 to the end is garbled.
I think it would be simplest to delete everything after bar 40 and re-key. I suspect that unravelling, and dealing with bars that won't accept new input just mean it would be a safer way forward to assume everything after bar 40 is lost.
I'll keep the state I've reached now, just in case you tell me I'm panicking and there is an easier solution.
Glyndwr
In reply to A bit techie for me perhaps by glyndwr_
David, I have been very successful using the one nightly build I downloaded, following your instructions. Thank you very much for your help.
I notice that when I insert a frame the preceding bar/measure loses its closing barline. In this particular piece this actually produces quite an acceptable appearance, but most situations would not be like this. One would expect a new barline to be created.
Also, formatting of the Title seems to be lost if any other change is made to a file - even if I format, then save immediately, before say, correcting a note elsewhere in the piece.
Apologies if this is the wrong place to raise those issues. But again, serious thanks for getting me out of the earlier difficulties.
Glyndwr
In reply to Thank you by glyndwr_
I'm not able to reproduce the problems you are describing. Can you share the file you are working with and give exact instructions (where you add the vertical or horizontal frame, how you change the title formatting, etc).
In reply to I'm not able to reproduce the by David Bolton
1) If you open the attached file, double click the heading (which is three lines high) and then insert a space at the beginning of line 1, then a back space, the heading is now nicely centred. Looks good. Save this.
Now close the file, when you next open the file this formatting of the heading is lost. Same if closure is forced on you.
2) In 3272 and the previous nightly, I found that hitting the red X on the tab, to close the saved item I had been working on, produced a forced closure of the program, and an alert to MSN (which I did not send). That is, I cannot save one item, close its tab, and open a new item to work on.
3) When I inserted what is now bar 37 (Our Father, MINISTER on Bass A), I found that if I forgot to hit the N button and merely selected the bar, hit 7 and then A, the program forced closure. I appreciate the proper thing to do is to hit N first, but the previous version of MuseScore did not object to this forgetfulness.
4) You will notice that the MINISTER bars do not have final barlines. They were created by typing the score and lyrics with all staves displayed, then inserting a vertical frame at the appropriate places, and finally ticking "hide empty measures" in Style. The effect here is quite nice, but this lack of a barline would not be welcome in some works.
I now have a final version of these historic responses, set for modern speech patterns, and for a standard English parish church SATB choir. So, for me, MuseScore has finally done its work !
My general use is less demanding, producing SATB of various hymns and songs for this choir.