Musescore not saving position of measure numbers
Hi all, when I'm getting ready to publish a piece I go through and manually adjust any measure numbers that collide with components. But if I close and reopen my score, despite saving it before closing none of my adjustments have been saved. Very frustrating. Is this a bug or is there a workaround?
Comments
I can't reproduce - works fine for me. In order for us to be able to investigate, we'd need you to attach your score and give precise steps to reproduce the problem. Also say what version of MuseScore, and what OS.
Here is one of the scores in question. I have Windows 10, MS version 3.6.
I just went through and adjusted the measure numbers that had collisions, such as 41 and 43. I used keyboard shortcuts to adjust them rather than the Inspector. Then I saved and closed the file, and reopened it. The measure numbers are now back to their default positions.
In reply to Here is one of the scores in… by AvenueQ
It looks OK to me. No collisions with measure numbers 41 or 43. When I look in the inspector they both have Y offsets of -2.83 sp. Other measure numbers have the style default offset of -2.00 sp. What values of offsets did you apply and what do you see in the inspector after saving and reloading?
In reply to It looks OK to me. No… by SteveBlower
Huh, interesting. Here is a screenshot of what mine looks like after adjusting, saving, and reloading (I have selected measure 43). I adjusted it up to Y offset -3.48, then upon reopening it was reset to Y offset -1.83, as you can see in the photo.
In reply to Huh, interesting. Here is a… by AvenueQ
This is what I see when I open the score you attached
Are you sure you are actually opening the score you saved and not an older, unadjusted copy.
In reply to This is what I see when I… by SteveBlower
Fair question, but no it is definitely the same file. I just tried it again, being very careful to select the same file each time, and still got the same result.
In reply to Fair question, but no it is… by AvenueQ
Well, here's another stupid question: are you sure you are saving the score where you think you are? Can you check the last modified time of the file you are opening?
In reply to Well, here's another stupid… by SteveBlower
And another thing to look at: What do you see if you download and open the score using the link in your earlier post?
In reply to Well, here's another stupid… by SteveBlower
Another fair question. I just carefully went through and made sure I was opening/saving to the right file, and got the same result. The file shows the correct time and date for "last edited."
I wonder if I should just update MuseScore, see if that fixes it? Apparently I have 3.6.0 when the current version is 3.6.2, I didn't realize mine was out of date.
In reply to Another fair question. I… by AvenueQ
This issue, fixed in 3.6.1: #315781: Measure Number Offset Value Changes Everytime Opening the File
So, yes, update.
In reply to Another fair question. I… by AvenueQ
Yes, updating is always a good thing. If I recall correctly 3,6.0 had a lot of issues that are fixed in 3.6.2.
In reply to Yes, updating is always a… by SteveBlower
Well I feel dumb now, updating it fixed the problem. Thanks for still trying to help though, I appreciate it.
No colissions on MuseScore 3.6.2 AppImage, Linux Mint 20.2