Stuck processing
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 |
Comments
If you mean musescore.com, you need to ask there not here on musescore.org
In reply to If you mean musescore.com,… by Jojo-Schmitz
Yes, you have to complain in https://musescore.com/groups/improving-musescore-com , but, I warn you, the maintainers there a few weeks ago claimed to have "fixed the 'score being processed' problem" ...
In reply to Yes, you have to complain in… by [DELETED] 1831606
Thank you for actually answering my question. I feel like these problems aren't brought up by anyone until a user runs into them and only then are they brought to light to everyone else. Communication would be nice.
In reply to Thank you for actually… by BeatsKEI
upload your score when you get a chance and someone can see if it's the score.
There was a corruption that version 3.0.5 wasn't finding but I found in version 3.1. Try the fixed file I attached and see if it works.
In reply to There was a corruption that… by mike320
May or may not be relevant, musescore.com 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 musescore.com). Neither is the case with this score though, so you may well have a point with that corruption.
In reply to May or may not be relevant,… by Jojo-Schmitz
This is actually a bit strange. The last couple of days I've seen a couple of scores that are corrupt but they seem unrelated to the existence of tuplets, which has been the cause of most corruptions I've seen in the past.
In reply to This is actually a bit… by mike320
Those 2 measure are clearly and visibly corrupt in 3.1, but not in 3.0.5, there they look sane and healthy
In reply to Those 2 measure are clearly… 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 It seems the engine running… 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 It seems the engine running… by mike320
So I used your fixed version and completely deleted measures 146-147 then redid them and It will upload but now it will not play
In reply to So I used your fixed version… by BeatsKEI
When I select your score online I get a message that the score is being processed. If your old score is still stuck in the being processed mode, then someone from musescore.com needs to delete it so you can upload it from scratch. Use https://musescore.com/groups/improving-musescore-com for this.
In reply to This is actually a bit… 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 Tuplets have indeed been a… by Marc Sabatella
I could get rid of the 2nd baritone part altogether and just use a lower octave on the tenor. Do you think that would work?
In reply to I could get rid of the 2nd… by BeatsKEI
If that's what you want, but I'd do it only if you want that. Otherwise, just use the fixed version already psoted.
In reply to If that's what you want, but… 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