Musescore website is not processing this correctly for whatever reason

• Apr 5, 2018 - 18:56

For context, this score is not supposed to be made public until it's ready for a certain date. Though since I'm having problems with it, I might as well ask you guys what could possibly be wrong with my Musescore version of this arrangement I made.

I first made this with Finale v25.5 and then exported an XML file so it can be imported to Musescore in order to create a Musescore version.

After I have made the necessary adjustments to make it formatted for Musescore, the website's score processor was not able to process my score for very weird reasons that even with its explanation, is still confusing as to why it just won't process it correctly. :(

Any help will be deeply appreciated. :)

Update: I almost forgot to share this error message I got for it. It should elaborate further on what the problem is:

MIDI file could not be generated.
ERR_NO_SVG <--(??? This makes no sense)
Score images could not be generated.
Thumbnail could not be generated
This may due to
Complete empty measures <---(??? This makes no sense)
Notes without stems <---(??? This makes no sense)
Last measure has no barline <---(??? This makes no sense)
In any of these cases, please remove the measures containing the problem and re-enter the notes. Once done, try to upload your file again.
If you need help, don't hesitate to upload your file in the MuseScore forum and the community will help you out.
ERR_NO_SPACE_JSONP
ERR_NO_SPACESEG
ERR_NO_SPACESEG_JSONP
No metadata file generated


Comments

I can reproduce, the weird error message is:

MIDI file could not be generated. ERR_NO_SVG Score images could not be generated. Thumbnail could not be generated This may due to

  • Complete empty measures
  • Notes without stems
  • Last measure has no barline

In any of these cases, please remove the measures containing the problem and re-enter the notes. Once done, try to upload your file again.
If you need help, don't hesitate to upload your file in the MuseScore forum and the community will help you out. ERR_NO_SPACE_JSONP ERR_NO_SPACESEG ERR_NO_SPACESEG_JSONP No metadata file generated

I've seen that arror message my self a couple days ago, but don't remember the solution anymore...

Ah, see https://musescore.org/en/node/270436, which led to #270920: Incorrect font property of one text block

The problem is with hairpins (crescendos and so forth). If you right click one and select all similar elements, you will see all of the hairpins that have been moved.

In reply to by Jojo-Schmitz

I have no choice but to move them around! They were in the way with the slurs and other conflicting items!

If you would like to elaborate as to why moving them around is not advised, please tell me. I've uploaded several scores in the past where I had to move the hairpins around and I never got an error like this until recently.

In reply to by Jonny Music

If you apply a hairpin to e.g. measure 1, then grab that and move it to e.g. measure 25, it still is attached to measure 1, for playback, but visually sits at measure 25. This is bad.
If you apply it to measure 1, then drag one handle so it extents to measure 2, same thing, visually ot looks right, playback wise it is still measure 1 only.
None of this is MuseScore fault, but yours, wrong usage, as explained in the handbook.
You did the same (bad) thing to some dynamics, they visually sit at places that are different from wher they affect playpack

What indeed is a bug, is that dragging a hairpin off of a page leads to problems

But as mentioned, this was not the cause for failing to render on musescore.com

In reply to by Jonny Music

Well, it can, you did it, and it was not the cause for not being able to save online either (although I still don't know what the cause was). It is bad nonetheless, you certainly want playback match notation, and not go mf at a place where there is no mf dynamic, and not go mf at places where there is one, that had been dragged there just visually, same for hairpins

In reply to by Jojo-Schmitz

I see.

Well, I made the necessary adjustments that would not confuse Musescore, re-uploaded the file and it now works.

Albeit, the formatting is not great. Hence why I will leave a link to the Finale PDF version for those who want a copy for the originally intended formatting.

This sore will be released to the public next Tuesday night (April 10, to be specific).

In reply to by Jonny Music

You can adjust the formatting, you just need to do it the correct way. If you don't like where a hairpin is, use the inspector to move the entire thing or use the dragging method to fine tune the overall length of it. As long as you do this, MuseScore does not normally have a problem with the display.

There is a huge difference between Finale and MuseScore. Finale has a team of high paid programmers writing their code and you pay for it. MuseScore has a few paid employees, one of which writes most of the code and a community of volunteers who do everything else such as fix bugs, write some of the code and keep the documentation current. As you would expect, you pay FAR less for MuseScore than for Finale or Sibelius. Everyone involved with MuseScore wants it to work perfectly, but with such a community project you get the volunteers working on what they see to be most beneficial at the moment.

In reply to by mike320

I could, though since I am a very busy man, I do not want to bother going any further with the adjustments at the moment.

I could pay someone else to do it for me, though that's not a viable option for me at this time.

I'll continue moving forward from here and make any corrections in the future whenever possible.

In reply to by Jonny Music

I think you might be confused about how Finale and Sibelius work. I guarantee you will have problems in those programs as well if you add a marking to one measure and then manually it to appear as if it were in another measure altogether. This will appear to work at first - in MuseScore as well as those programs - but as soon as anything about the layout changes to make the measures appear in different locations on the page, your manual adjustments will be wrong, and things will look screwy. It's not some idiosyncrasy of MuseScore, it's just common sense. Markings need to be attached the notes / measures they are intended to actually affect, not attached to some other random place and then manually adjusted.

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