MuseScore 3 constantly crashes

• Mar 14, 2019 - 01:37

Whenever I try to move more than one note at once, MuseScore 3 freezes and crashes. Not always, but usually.

Oh, I see what it is! When I move the notes into an area where there's key signature, it switches the note to a natural. That's the way it always worked on MuseScore 2. Here, you can only do it one note at a time, or the system crashes every single time. That makes MuseScore 3 kind of unreliable in its current state.


Comments

Can you explain what you mean? You shouldn't be trying to "move" notes anywher, much less into an area where there is a key signature. Can you attach the specific score you are having trouble and explain in more detail how to reproduce the crash?

EDIT: maybe by "move" you really mean, paste? And by "an area where there's a key signature", yuu mean yo pasting after a key signature? Nothing has changed in this respect. If there more was a natural before you pasted, it remains so after. MuseScore does not change the pitch when you paste. But if you are seeing a crash, probably your score is corrupt, so definitely attach it so we can help you fix it.

In reply to by jamestomk

3.1RC reports a couple corruptions

Measure 142, staff 6 incomplete. Expected: 4/4; Found: 4032/2688
Measure 168, staff 9 incomplete. Expected: 4/4; Found: 4481/4480
Measure 188, staff 9 incomplete. Expected: 4/4; Found: 4481/4480
Measure 264, staff 12 incomplete. Expected: 4/4; Found: 378/252
Measure 267, staff 12 incomplete. Expected: 4/4; Found: 378/252
Measure 268, staff 12 incomplete. Expected: 4/4; Found: 378/252
Measure 272, staff 11 incomplete. Expected: 4/4; Found: 840/560
Measure 274, staff 12 incomplete. Expected: 4/4; Found: 378/252
Measure 380, staff 4, voice 2 too long. Expected: 4/4; Found: 42/28
Measure 380, staff 5, voice 2 too long. Expected: 4/4; Found: 42/28
Measure 388, staff 4, voice 2 too long. Expected: 4/4; Found: 42/28
Measure 388, staff 5, voice 2 too long. Expected: 4/4; Found: 42/28
Measure 396, staff 4, voice 4 too long. Expected: 4/4; Found: 42/28
Measure 396, staff 5, voice 4 too long. Expected: 4/4; Found: 42/28
Measure 397, staff 6, voice 2 too long. Expected: 4/4; Found: 42/28
Measure 404, staff 13 incomplete. Expected: 4/4; Found: 6721/6720
Measure 405, staff 13 incomplete. Expected: 4/4; Found: 6721/6720
Measure 406, staff 13 incomplete. Expected: 4/4; Found: 6721/6720
Measure 426, staff 9, voice 2 too long. Expected: 9/8; Found: 7561/6720
Measure 495, staff 13 incomplete. Expected: 4/4; Found: 6721/6720
Measure 496, staff 13 incomplete. Expected: 4/4; Found: 6721/6720
Measure 497, staff 13 incomplete. Expected: 4/4; Found: 6721/6720
Measure 498, staff 13 incomplete. Expected: 4/4; Found: 6721/6720
Measure 499, staff 13 incomplete. Expected: 4/4; Found: 6721/6720
Measure 500, staff 13 incomplete. Expected: 4/4; Found: 6721/6720
Measure 501, staff 13 incomplete. Expected: 4/4; Found: 6721/6720
Measure 502, staff 13 incomplete. Expected: 4/4; Found: 6721/6720
Measure 503, staff 13 incomplete. Expected: 4/4; Found: 6721/6720

And the score stems from 2.0.3, better upgrade there to 2.3.2.
3.0.5 should deal with it too and faster, in page mode, for faster continuous mode you'd need 3.1. It's is still slow, due to its enormous size, 21 staves in 378 pages.

In reply to by Jojo-Schmitz

I do see these errors if I export musicXML from 2.3.2 and load that file into 3.0.5.

MS 2.3.2 is indeed the last editor I successfully used on this file. It still loads fine and no other difficulties in MS2.3.2.
<---- created in
2.3.2 <---- last edited in

I have tried exporting from 2.3.2 as ".mid" and ".musicXML"

So I guess I hunt down these corruptions and fix in 2.3.2, as 3.0 is less tolerant (more strict).

In reply to by jamestomk

I haven't seen a corruption imported into 3.1 which was released today, and I've been using it since the first beta was released a couple of months ago and had several people report corrupted scores. So try 3.1 and see if the corruptions are fixed, just open the version 2 score with it.

In reply to by Jojo-Schmitz

it appears that 3.1 does tolerate corrupt measures better than 3.0.5, and tolerates them more like 2.3. This is good news.

there are corrupt notes after the MIDI file import, I cannot determine if that corruption originates in the MIDI file... if I export the MIDI import as musicscore.xml and re-open l get the same errors you found previously (e.g., "Measure 167, staff 7 incomplete. Expected: 4/4; Found: 59/56").

MuseScore 3.1.0.22356 (3.1.0.22356), just crashed on macOS Mojave. I opened MuseScore file, trying to save it, it crashed. Reopened, and this time save worked.

If you want the CrashReport, I can post it.

In reply to by mike320

I assume this is the musescore file i posted above "suppersready reinstrumented.mscz". I had originally started by importing a MIDI file into MS 2.x quite a while ago and have worked to re-instrument and edit in MS 2.3.
The file still loads very quickly into MS2.x, suggesting it is not too large. But MS3 seems to be wading through molasses when dealing with this file.

Do you still have an unanswered question? Please log in first to post your question.