Score now crashes randomly and crashes every time I try to generate pdf parts and score
Previous save was working fine. Now my score with changes made today crashes randomly and also crashes at every attempt to generate a PDF Score and individual parts.
021523 - 01 Works
021623 - 01 Crashes
021623 - 02 Crashes
In going back through and trying to generate parts one at a time, Vibe 4 causes the crash. I deleted it and so far am able to generate parts. However...
all corrected pedal markings and graphic dynamics ( > style decrescendo ) are missing agin.
021623 - 02 - SCORE NO VIBE 4
@Marc Sabatella
This is the same score that I had to go back and redo all pedal markings and dynamics. Now I will have to do this yet again. With no exaggeration, this will make about the tenth time I've had to correct pedal markings, graphic dynamics and diminuendo markings.
There is obviously a problem with either Vibraphone instrumentation, pedal marking, dynamics, etc. some where.
Again, I realize you guys are volunteers but this is infuriating and time consuming to have to do the same corrections over and over.
| Attachment | Size |
|---|---|
| Punta_Patri Musescore 4 - 021523 - 01 - SCORE.mscz | 277.13 KB |
| Punta_Patri Musescore 4 - 021623 - 01 - SCORE.mscz | 291.61 KB |
| Punta_Patri Musescore 4 - 021623 - 02 - SCORE.mscz | 292.14 KB |
| Punta_Patri Musescore 4 - 021623 - 02 - SCORE NO VIBE 4.mscz | 288.06 KB |
Comments
I re-saved as a new name. There were also parts for instruments I didn't add (an additional Chime and 2 Crotale parts). I deleted them. Added another Vibe part. Then an additional Crotales part that I did not add just showed up again.
Update: copied and pasted Glock/Crotale part m46 - 47 to paste into vibe 4. Immediate crash.
In reply to Update: copied and pasted… by brandonhbrooks
Prior to the crash I was also adding repeat measures leading up to D.
It is also now mis-numbering measures in the score. There are 2 m46's. I can't get it to change even when I change to numbering only the beginning measure of each system.
https://musescore.org/en/user/9420
Yet more adding notes leading to more crashes.
Update: Use of the 2 bar repeat causes the reused measure number at 46.
Do you have precise steps to reproduce the problem? We'd love to help, but it's pretty much impossible to do anything without precise steps to reproduce the problem. Once you have those and we can confirm the problem, then you can open an issue on GitHub so the developers can begin working on a fix.
In reply to Do you have precise steps to… by Marc Sabatella
The steps were pretty simple. All I did was add a vibraphone part (Vibraphone 4). I changed the name to Vibraphone 4 in all the pertinent places. I either copied and pasted notes from other parts (from Marimba 2, or input them individually. When I went to generate parts and print to PDF and the program crashed. I tried the same with parts after reopening. Crashed again. Went back to a previous save. Add the instrument again, same steps. Same problem.
I even went so far as to delete the Vibraphone 4 part, generate parts to print to PDF and it worked fine.
A good portion of problems that I am having all centered around the Vibraphone (other pieces as well).
Latest version - no Vibraphone 4 - Score / Parts all generated fine.
Punta_Patri Musescore 4 - 021723 - 01 - SCORE NO VIBE 4 - MEASURE FIX
I will attempt to add the Vibraphone 4 part again then fix pedal markings and dynamics and document steps as I go.
It's still not clear to me if you have precise steps. to reproduce a specific problem. I see many different scores attached here, and lots of references to various things to try, no but no specific precise list of steps to follow. Please, attach one single score, and list the precise steps to reproduce the problem - numbered for clarity like this:
1) open the attached score
2) click this
3) click that
4) click this other thing
Result: crash
Once there is a precise set of steps to follow, then someone can attempt to confirm the problem.
In reply to (No subject) by Marc Sabatella
Two options
1. Open Score
2. Click File
3. Click Export
4. Click Select All
5. Click Export
Results in crash
Or
4. Click Vibraphone 4
5. Click Export
Results in crash
Selecting other parts does not cause a crash
Latest development builds reports the score to be corrupt:
Corrupted measure: Full score, measure 42, staff 4.
Corrupted measure: Full score, measure 42, staff 5.
Corrupted measure: Full score, measure 42, staff 9.
Corrupted measure: Full score, measure 43, staff 4.
Corrupted measure: Full score, measure 43, staff 5.
Corrupted measure: Full score, measure 43, staff 9.
Corrupted measure: Full score, measure 47, staff 12.
Corrupted measure: Full score, measure 47, staff 13.
Corrupted measure: Part score: Vibraphone 2, measure 42, staff 1.
Corrupted measure: Part score: Vibraphone 2, measure 43, staff 1.
Incomplete measure: Part score: Voice, measure 47, staff 1. Found: 0/1. Expected: 7/4.
Corrupted measure: Part score: Vibraphone 1, measure 42, staff 1.
Corrupted measure: Part score: Vibraphone 1, measure 43, staff 1.
Corrupted measure: Part score: Marimba 2, measure 42, staff 1.
Corrupted measure: Part score: Marimba 2, measure 43, staff 1.
Corrupted measure: Part score: Marimba 3, measure 47, staff 2.
Corrupted measure: Part score: Timpani, measure 47, staff 1.
See How to fix MuseScore 4 corrupted files
@Jojo-Schmitz thank you. Of the multiple scores I posted above lol, which one does this apply to. I was trying to give as much info as possible and it may have been too much of an info dump.
Punta_Patri Musescore 4 - 021723 - 01 - SCORE NO VIBE 4 - MEASURE FIX.mscz
But the others probably suffer from the same corruptions. Get yourself a nightly builds (from master) and open these scores with it
In reply to Latest development builds… by Jojo-Schmitz
Interestingly enough a lot of those measures contain the 2 bar repeat marking and I instinctively fixed one of those and didn’t have as many problems.
Indeed, that particular score is corrupt, which will of course lead to crashes. I don't get a crash in either 4.0.1 or current builds of 4.0.2 using either of the steps of steps listed, but no doubt, crashes can happen on corrupt scores. So now the question now, how to reproduce the corruption in the first place.
In reply to Indeed, that particular… by Marc Sabatella
OK from my what seem to be safe saves, when I close the program and reopen, MuseScore is again adding extra Crotales parts randomly.
Steps taken:
1. Save
2. Close attached score
3. Open attached score
I don't know what to list as steps other than that.
In reply to Punta_Patri Musescore 4 -… by Jojo-Schmitz
What is the “nightly builds” please? I’m a little confused on that one.
Nightly builds are created every day incorporating the latest bug fixes and other changes and made available for testing. Right now there are two parallel sets available - ones that will eventually become 4.0.2 and include only the fixes targeted for that release, and ones for the "master" branch including all changes, including ones that may not appear in a release until later. You can download and test these builds via the Download menu above, just scroll down until you see the Development builds section.
Anyhow, the score above is corrupted, so as mentioned, it is not really surprising bad things will happen when working on it. The real task is to identify the steps that lead to the corruption.
The extra crotales parts is probably from the same sort of corruption as was seen in #343121: Changes to one specific part not saving. Which could be a clue to the steps - it's probably something you did in both scores that is unusual enough than no other MuseScore user has performed those same steps (or else there would other reports of this).
In reply to Latest development builds… by Jojo-Schmitz
@jojo I downloaded and ran the attempt corruption repair. It said no corruption found.
In reply to @jojo I downloaded and ran… by brandonhbrooks
I also tried the other steps of saving as XML file and opening in MuseScore 3 but it wouldn’t open at all.
In reply to Nightly builds are created… by Marc Sabatella
Ah. Ok. Thank you as always.
Now to ask a newb question. How do I go about getting the nightly builds please?
As per my previous reply: "You can download and test these builds via the Download menu above, just scroll down until you see the Development builds section".
I’m so sorry. I didn’t see it. Teaching and missed it. Thank you.
@Jojo-Schmitz https://musescore.org/en/user/9420
UPDATE: I removed several "Keep measures on the same system" layout marking from the score (that I didn't add) and it fixed the miss numbering of individual parts. Compare my last up load to this one. The Glock / Crotales part m33 I think. Hopefully this will help the developers.
That score is still corrupt (as per the latest development build), so no wonder that MuseScore crashes on it
In reply to That score is still corrupt,… by Jojo-Schmitz
I ran the repair but it said no corruption found so I’m not sure what to do. I did the other steps listed in the “how to fix” directions as well but no luck.
Try the latest nightly build on it, it'll report corruptions and tell you where exactly
In reply to As per my previous reply: … by Marc Sabatella
Marc, and Jojo, I’m sorry to tag you here but I went to add something as an issue, clicked the add issue button, then my list of postings opened up not the prompts for adding anything. It’s not letting me add anything new. Is there something wrong with the web page?
In reply to Marc, and Jojo, I’m sorry to… by brandonhbrooks
Also getting this warning fyi…
Yes, this issue tracker here has been disabled and replaced with https://github.com/musescore/MuseScore/issues/new/choose
That IP address you get the warning about is in your private LAN