Stuck processing

• May 14, 2019 - 12:51

Is musescore having issues again? I'm trying to upload a score that's not extremely large (around 350 kb) and it is stuck in the processing stage. Unfortunately I cant attach the file cause I'm at school but if there isn't a problem with the website then I can be sure it's my file's problem just looking for some confirmation. You can click on my icon and see my scores if it helps. This is really disappointing.
Edit: Score attached and I could get rid of the parts to help in-app speed but I doubt that will help upload speed

Attachment Size
One_Winged_Angel - Advent Children.mscz 322.87 KB


In reply to by mike320

May or may not be relevant, still uses 3.0.5 for rendering.
But indeed 3.1 Beta 2 is reporting this:
Measure 146, staff 27 incomplete. Expected: 4/4; Found: 17/16
Measure 147, staff 27 incomplete. Expected: 4/4; Found: 17/16

What had been causing such hangs before was that exporting to PDF, PRF with parts, MP3 or SVG crashed (all 4 are done on Neither is the case with this score though, so you may well have a point with that corruption.

In reply to by Jojo-Schmitz

It seems the engine running the .com site recognized the corruption and is rejecting the score because of it. You and I realize the .com site does not use the exact same version as 3.0.5, but has some things added to it to permit features of the site. Perhaps finding the difference between 3.0.5, 3.1 and the site would help fix the corruption. Corrupt scores has been a known reason for the .com site having problems with scores for some time.

My point is, until the last couple of days I don't remember scores with corruptions that were not related either to import or tuplets.

In reply to by mike320

Whatever it is, it should say "this hasn't finished in 10 minutes" or "this blew up/erred out" and (1) kill it (2) move on and (3) inform the submitter. Dying is not acceptable no matter what the problem with the score, including being an empty file, not a musescore file, creating a segment fault, etc.

In reply to by mike320

Tuplets have indeed been a big cause of corruptions, and any time you see a difference between 3.0 and 3.1 with respect to corruption, tuplets are going to be even more suspicious, since the main change here was in how we calculate the time position / duration of notes to handle tuplets better.

However, for the record, other causes of corruption we've seen involve multiple voices, particularly in the presence of voice exchange or copy/paste. Also when there is text that is not attached to any specific note (eg, it was added to a note that was later removed but the text left behind). Various combinations here could create situations where voice 1 contained were overlapping notes or gaps.

That said, I don't get a corruption warning when loading this score into a build from current master. EDITED: yes, I do get a corruption, I was using the fixed version of the score. And actually, the corruption is present and visible in 3.0.5 as well, if you view the second baritone part rather than the score. Seems I do recall a bug where corruption could occur in certain cases when using voice exchange with parts?

In reply to by Marc Sabatella

I have reason to believe it may have to do with master effects being saved to a score. Even the fixed version didn't work actually I just didn't say anything cause I didn't want to cause anymore problems. It uploaded successfully when I took out all effects (lucky guess). I then added them back in and it won't play the sound. So I believe (at least for my score) musescore is running into problems whenever there are any kind of effects added in the synthesizer

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