Cannot replace uploaded score on musescore.com (hangs on audio creation).

• Nov 2, 2018 - 12:55
Reported version
2.2
Type
musescore.org
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

Hi,

I have made an update to one of my uploaded scores. When I try to update the score on musescore.com using the "Edit Score" page I am able to select my revised score (see attached) and initiate the upload, but this gets no further than the "Your score is being processed. It will automatically be displayed when finished." message.

I can see my score when I search for it from "My Scores", but clicking on the score takes me to a "page not found" screen.

The updates to the score itself are minor - a few pitch corrections and hiding the top staff when empty. Please can you help - I'd rather not delete the score and re-upload as that would lose my favorite and view counts. I am able to upload other scores without problem.

OS: Windows
Arch.: x86_64
MuseScore version (32-bit): 2.2.1
revision: 51b8386

Thanks,
Phil. (PhilTA)

Attachment Size
Mazeppa.mscz 98.52 KB

Comments

• Nov 2, 2018 - 13:14
Severity S2 - Critical ⇒ S4 - Minor
Status active ⇒ closed

First of all upgrade to 2.3.2

Then fix the corruptions in that score that 2.3.2 reports (but 2.2.1 didn't):

Measure 57, Staff 2, Voice 2 too long. Expected: 4/4; Found: 3302/576
Measure 58, Staff 2, Voice 2 too long. Expected: 4/4; Found: 3302/576
Measure 59, Staff 2, Voice 2 too long. Expected: 4/4; Found: 3254/576

I had to remove measures 57-60 in staff 2 to get rig of the corruptions, after that reenter them.

MuseScore.com won't accept scores with corruptions.

In general better use "Save online" from within MuseScore, rather than then Update Score on musescore.com

You can as well do this right now (after having fixed the corruptions, MuseScore won't allow "Save online" with this), that score on musescore.com seems to have vanished permanently

Then contact support@musescore.com to get the stuck file issue resolved, if there is any
It it is, this is not a MuseScore or musescore.org issue, hence nothing for this issue tracker

Reply