Upgrade once again changed my score formats
I'm running MuseScore Studio Version 4.5.1.250800846, Revision 602eca8, on Windows 10.
The last two upgrades have changed the formats of my scores. See the examples below -- the first one is a scan of the pre-upgrade printed score; the second is how it appears now.
This is due solely to the upgrade -- I haven't touched that score in 5 months until a few days after the latest upgrade. This happened after the last upgrade as well.
About half of my scores were affected, all more condensed than previously. Yes, most are still playable, though some are very condensed. But they're aesthetically displeasing -- I'm a bit OCD and will have to re-format them once again, a tedious process.
My questions in order of priority:
1. Is there an easy way to restore them to the "proper" appearance?
2. Why does this happen?
3. What can I do to prevent it in the future, other than stop upgrading?
Thanks for any help.
Attachment | Size |
---|---|
Lonesome Town pre-upgrade.jpg | 945.2 KB |
Lonesome Town post-upgrade.mscz | 191.15 KB |
Comments
Just apply system breaks.
In reply to Just apply system breaks. by Jojo-Schmitz
Well I'll be darned -- that fixes it.
Perhaps shouldn't be necessary, but easy enough to correct.
Thank you!
In reply to Well I'll be darned -- that… by camppub
If you care for the layout to stay as it is, a cross versions, use system breaks.
In reply to In your case, you also must… by bobjp
Why increase space scaling, in addition to system breaks? 4.5 1 does not make everything smaller, but allows for a narrower layout, so instead of system breaks increasing stretch might be an option, but system breaks are easier
And almost everyone's advice here is unofficial, as the 'powers to be' rarely post here.
In reply to Why increase space scaling,… by Jojo-Schmitz
If you look at the original image and then the score open in 4.5.1, you will see a bigger gap at the bottom of the page of the 4.5.1 version. So to finish returning it to the original state, you need to increase to scaling. You need both.
In reply to If you look at the original… by bobjp
I'll probably just use system breaks for most of the fixes, but scaling as well for any scores that are too small or tight.
The reason I minimize use of system breaks is because I make a lot of revisions to scores. I try out a lot of different possibilities. If I put breaks in every line and then add/remove measures or the number of notes in measures, I'd usually have to re-do the breaks because lines become too long or short. The program often accommodates adequately without breaks.
In reply to I'll probably just use… by camppub
Well, yes, adding system breaks is like the finishing touch to a score's layout.
But as long as those haven't been added the score isn't finished or you don't care about its layout.
It may happen that on another version there's more space needed, in which case these layout breaks do reveal the issue right way, but showing a singele measure somewhere (and an implictit system breat in the measure before) This too is a GoodThing(tm) as it immediatelly shows the issue (and could get fixed by reducing stretch, decreasing page borders or slighly reducing the space scaling)
In reply to Well, yes, adding system… by Jojo-Schmitz
"But as long as those haven't been added the score isn't finished or you don't care about its layout."
Neither one is absolute. Now the official stance is to defend 4.5 adding breaks and declaring the score finished. When, as you say, it isn't finished. 4.5 also gets to declare that we don't care about layout.
In reply to "But as long as those haven… by bobjp
This my inofficial view, but in contrast to your's it is correct, or at least more correct ahat your's. I'm doing this ever since I started with MuseScore, more than 15 years ago and it went quite well for me across many versions, between 0.94 and 4.5.1.
Just believe someone with lots of experience here
In reply to This my inofficial view, but… by Jojo-Schmitz
The only reason I'm saying anything is that more and more users are posting that 4.5 now changes what they had as a layout. It does this without warning. And in the name of saving space. The users that actually posted, didn't like the result. I can only think that there are many more that don't like it and won't post.
Yes, of course, had proper layout been done, they wouldn't be having problems. People that just started with earlier v4 may not be aware of everything that should be done. And as you know it is totally possible to be done with a score and prepare it for use without system breaks. The change from 3 to 4 didn't require this kind of change
In reply to If you look at the original… by bobjp
Nonsense. As soon as explicit system breaks are entered at the measures where the previous MuseScore version had placed implict system breaks, the layout is (almost) exactly the same,
Only the OP's image has a different width to height ratio (0.77) than the score (0,70), so is probably truncated at the bottom.
(the image's offset needs to get adjusted too, some 5 sp to the left)
Compare the 2 images, exported with 4.4.4 (the score stems from 4.4.2) and 4.5.1
4.4 (as is, only implict system breaks):
4.5 (added explict system breaks and moved image 5 sp to the left):
In short: no need to change the space scaling value, just adding system breaks is enough...
In reply to Nonsense. As soon as… by Jojo-Schmitz
OK. I was just going by the image. As I research further, looks like you are correct.
In reply to OK. I was just going by the… by bobjp
Thanks!