Which version of MuseScore are you using currently? Still 2.0.2? Of so update at least to 2.0.3, maybe even also (!) 3.0.5.
There is no issue with the score, nor with the Save online function in general, I could upload it using 3.0.5
If you look at the score properties, there is a source field that show where the score was last saved online. If this is empty (which is the case in 3.0.5 for pre v3 scores) then MuseScore will not replace the score online. You can copy the link from your browser to this field, and save online will update the existing score.
If I'm correct about this field always being empty in V3 for score crated in v2, then this is a bug that needs fixed. I'll do some more testing in a little bit.
It is not, a score save online in 2.x (and saved locally after that) will have that location still stored and obeyed when loading and saving online with 3.x.
But indeed that score has apparently not been saved onleing with 2.0.2, but iunstaled uploaded direcvtly to musescore.com, or has not been saved locally after the save online. And so indeed no update will happen in this case, but a new score should get uploaded instead (and indeed the fix for this is to fill that source tag)
Thanks for catching that, not sure why I missed it, I did look at the score properties...
In my previous post, I was doing a random check of a score I new was saved online and had been imported to version 3. I always save online from the score. There was nothing in my source, so I wasn't sure of the order of events for that score. I imported a couple of scores with info in the source and they survived the import, so I agree, no bug exists here.
As Jojo mentioned in passing, for MuseScore to remember where a score is online, you have to save it locally after you save online to save the "Source" field being discussed here. This is why a score saved online is marked as dirty (has an * next to the name).
Comments
What do you mean by "Nothing happend"? What did you expect to happen?
It sure did save the score. But maybe not where you expected it to be stored?
In reply to What do you mean by "Nothing… by Jojo-Schmitz
the score didn't change at all......
Sure you're looking at the changed version of it? As mentioned, the save might have placed it at a different place as you think it did
Hold on, you're storing the score online and it didn't change there?
Which score? Does the log (online) show any updates?
In reply to Hold on, you're storing the… by Jojo-Schmitz
the gakuentoiro score. it didnt show any update at all
So you mean
https://musescore.com/user/3062771/scores/3338931
right? Created or at least last save with MuseScore 2.0.2
In reply to So you mean https:/… by Jojo-Schmitz
yes, was trying to update that score but when i clicked save its as if like that button wasnt working
Which version of MuseScore are you using currently? Still 2.0.2? Of so update at least to 2.0.3, maybe even also (!) 3.0.5.
There is no issue with the score, nor with the Save online function in general, I could upload it using 3.0.5
In reply to Which version of MuseScore… by Jojo-Schmitz
er the latest soooo 3.0.5
In reply to er the latest soooo 3.0.5 by Alt@ir Works
If you look at the score properties, there is a source field that show where the score was last saved online. If this is empty (which is the case in 3.0.5 for pre v3 scores) then MuseScore will not replace the score online. You can copy the link from your browser to this field, and save online will update the existing score.
If I'm correct about this field always being empty in V3 for score crated in v2, then this is a bug that needs fixed. I'll do some more testing in a little bit.
It is not, a score save online in 2.x (and saved locally after that) will have that location still stored and obeyed when loading and saving online with 3.x.
But indeed that score has apparently not been saved onleing with 2.0.2, but iunstaled uploaded direcvtly to musescore.com, or has not been saved locally after the save online. And so indeed no update will happen in this case, but a new score should get uploaded instead (and indeed the fix for this is to fill that source tag)
Thanks for catching that, not sure why I missed it, I did look at the score properties...
In my previous post, I was doing a random check of a score I new was saved online and had been imported to version 3. I always save online from the score. There was nothing in my source, so I wasn't sure of the order of events for that score. I imported a couple of scores with info in the source and they survived the import, so I agree, no bug exists here.
As Jojo mentioned in passing, for MuseScore to remember where a score is online, you have to save it locally after you save online to save the "Source" field being discussed here. This is why a score saved online is marked as dirty (has an * next to the name).