I entered a 64 measure piece of music, saved it, printed it, closed MuseScore and, on opening two days later, the stems for all notes from measure 27 to the end were missing. Why is this happening and how may I restore the stems without starting over?
Comments
What is your operating system? What version are you running?
Please read and follow: http://musescore.org/en/handbook/how-report-bug-or-ask-support
Your goal in reporting a problem should always be to make it as easy as possible for others to reproduce the problem. Attach a score showing the problem, if possible give steps to reproduce the problem starting from a blank score, etc.
How do I attach a score to this message?
I am Using Windows XP Sp 3 MuseScore 9.6 Beta. I entered the notes as I understand that the proper way to do this is, i.e., click on note value, drop on score, enter the next note. E:\Desafinado.mscz I have tried to enter the image here - hope it works.
Edited to say it did not work; may I attach a .pdf to some e-mail ? to what address?
There is a link at the bottom that says "File attachments" click on it. Browse to choose your file and then be sure to click "Attach" to actually upload the file. Please attach the MuseScore file.
You are using a prerelease version of 0.9.6. Could you state the revision number? Go to Help > About to find the revision number.
Thanks for the messagge about attaching files - I am somewhat visually inpaored and don't see small things at the end of pages but I have it now so lets try it.
Let's try it again.
I see that the missing stems are missing in the file you attached. Any idea what steps are needed to recreate this problem on a new score? What revision number of MuseScore are you using? (From the MuseScore main menu choose Help > About to find the revision number.)
Let me briefly point out a couple of things. At the end of bar 26, there is a funny (dark) bar line - it is really two bar lines tight against one another. Second, notice bar 25 has only 3.5 beats. Everything after that bar line loses its stem. In entering a measure beginning with a rest (an eighth rest, in this case) I usually enter two notes on the same pitch and of the same duration as the rest, then delete the first rest.
Second, when I created this piece, it was with r.2186, an unstable 9.6. It opened fine until I downloaded Beta 9.6. That's when I had the problem. I reentered the piece on Beta 9.6 (2811) and it worked fine but the previous piece (I am afraid to try to open more of the pieces I entered with r.2186) opened without the staffs. I am trying to find away to repair the staff sloughing.
Thanks for your interest. .
This may be unrelated, but ...?
I use windows. In the past there were times when there were various strange results, basically gone now in the pre-release that I am using.
However, the "dark barline, 2 bar lines together" is a similar artifact to some that I had in the past.
I found that I could salvage most of the writing if I could remove the appropriate improper bars, so I suggest you try adding a few bars before the 1st instance of a glitch and then delete the first glitched bar. ( I also used to remove the bar previous to this bar and another 1 or 2 after the apparent glitch).
I would then redo the bars that I added. This procedure often cleaned up the problem, although I don't remember that we ever solved what was actually causing the problem.
I hope this helps. Good luck.
Regards,
I believe I had done this before so I tried it again and I can not get past the addition of bars; as I either fill in the number I wish to insert or try to insert just one, MuseScore abends and I can only restart and try again, but never successfully adding measures. btw, it treats the the bar with 3.5 beats in it as a part of the last bar of the piece, not a single bar. This is shown by the "box" extending from the 3.5 beat bar to the very end of the piece. So, I conclude that the software does not recognize anything after the as being a bar line or, indeed the end of the piece.
At this point, I am trying to simply open other entered music without this disaster. I have other pieces entered where this anomaly has occurred; I have avoided opening them because I would like to avoid having to re-enter them, as I did with the piece in question.
If you haven't tried it, start the removal a couple of bars before the "Compound (if you will) bars".
Add the extra bars later
Yes, I tried that at your first suggestion and it abends MuseScore and closes. I went three bars back then an entire line back - still abends. :-(
I deleted from the faulty measure onwards. See file attached. I did not encounter any crashes.
Is there any chance you accidentally opened and save a file in 0.9.5 after you had edited it in a prerelease of 0.9.6? This would cause file corruption.
When I try to open your score by going to the folder in which I have saved it, it does not appear, even though the "type" box says, all Musescore file types.
When I then change that to "all types", it appears.
When I select it to open it, a "score" appears, but with absolutely no information, names, staffs, notes, etc.
I tried this on an earlier version, and then updated to r3003, windows. Same result.
Regards,
Xavierjazz wrote: "When I try to open your score by going to the folder in which I have saved it, it does not appear, even though the "type" box says, all Musescore file types. When I then change that to "all types", it appears."
It sounds like you are talking about TubaMan's attachment. If you save the attachment and remove the comma from the end of the file name then it will open correctly in MuseScore.
Aah.
Okay, to me the first problem is earlier.
Bar 9 has a truncated 1st ending and bar 16 has a strange "line" artifact.
1st I tried double clicking on the artifact: MS crashed, boom.
I reloaded and tried double clicking on the 1st ending: the result is contained in the attached .png. This pic also shows the artifact, etc.
Regards,
Xavierjazz, In comment #13 above I mention that if you delete the faulty measures first then MuseScore does not crash. I included a file with the faulty measures removed.
See http://musescore.org/en/node/5586#comment-15222 above
David, I opened your version. See attached for .1st png. Same artifact(s).
"b" and "c" show the result on double clicking on the "artifacts". No crashes now on the double clicks and, obviously, selection was achieved.
"d" shows a cleaned up version, but I'm not sure what is being solved. I thought that there were stems missing?
Regards,
If you are able to reproduce the bug starting from a new score please start a new report.