What determines the Musescore version used in the .com repository?
Here's my specific question. I have a piece in the .com repository, from 2014, that was created in v1.3 . It looks and plays fine on the site, via the browser. I want to tinker with it a tiny bit. However, that .mscz file, when loaded into the current v2.3.2 , is somewhat messed up (phrasing lines are all over the place, and playback is faster).
Suppose I open the old .mscz file in the old MS v1.3 , and tinker with it, then upload it again. Will the site know to use the old MS v1.3 , or will it use the current MS... ?
Perhaps the MS version at last save is saved in the .mscz file, and the repository is smart enough to honor that...
Comments
It will use the current, see: https://musescore.com/groups/improving-musescore-com/discuss/1055091
No, musescore.com uses a 2.x version to render any new update. It is doing the rendering only one on upload, so scores uploaded long ago were rendered using the 1.x engine and still look that way, but Un re-upload will get re-rendered using the 2.x engine.
EDIT Oops, sorry, basically what Shoichi's said already
General if you see lines not in the right place when going from 1.3 to 2.3.2, it suggests they had been manually adjusted in the first place in an improper manner (eg, dragging the end of a slur to extend it visually rather than actually changing what note it attaches to, etc). Meaning it also won't look the same even in 1.3 if you make any but the most trivial of changes to the score. So it's best to bite the bullet and correct the errors anyhow.
As for playback tempo differences, I can't think of any reason that should be the case. Feel free to attach your file here so we can take a look and understand better what is going on (also with respect to the layout).
Thanks Shoichi, Jojo, Marc. I had indeed altered the slurs, but did not change the endpoints. They are cross-staff slurs (same voice) and I had to change the shape. I don't think there were any logical errors, but it's a challenge to backward compatibility, to be sure.
As mentioned, the score plays significantly faster in v2.3.2 than in v1.3 .
Here it is. Any suggestions for future-proofing would be good.
[https://musescore.com/user/142755/scores/351206]
MN
In reply to Thanks Shoichi, Jojo, Marc… by MikeN
Yeah, those cross-staff slurs are problematic, probably no way around needing to redo those.
As for tempo, I guess probably it's a difference in interpretation between quarter note or dotted quarter as the unit of measure. MuseScore 1.3 didn't have any way to specify that the way 2.3.2 does. I'd go in and add a metronome marking explicitly with dotted quarter (eg, using the palette or Alt+T), edit the marking to be what you want, hit Esc to lock it in, then you can edit the text to say Andantino again if you want.
In reply to Thanks Shoichi, Jojo, Marc… by MikeN
Thanks for the tip on the tempo. One remark that's a separate topic...
This score has a lot of cross-staff notation. This caused some mild confusion at times. Both piano staffs have a "Voice 1" in them. When I was editing, if I highlighted a note in the piano treble staff, I could not tell where it lived from the "1 2 3 4" voice indicator across the top. I had to do other things and figure it out indirectly.
The obvious thing would be that instead of voice "1" , the full name could be voice "staff1.1" or voice "staff2.1" , etc. This could be a tooltip on the aforementioned indicator.
Not saying it's worth it the trouble, but I thought I'd "voice" my thoughts. I wished I had it at the time.
In reply to Thanks for the tip on the… by MikeN
In MuseScore 2, have the status bar enabled (View → Status Bar).
It mentions for a selected element its type, duration (if applicable), voice, bar, beat, staff. Note that barnumber there is the internal number of the bar, which doesn't necessarily match the visible number.
In reply to Thanks for the tip on the… by MikeN
Ah. Thx!