Editing Glitch
This has happened many times before, but I've been able to work
around it well enough until now.
I am editing an older score of mine that I downloaded from my profile since I
couldn't find the original file on my computer. Whenever I edit anything
(add a note, move a note, move text, ANYTHING), the entire score suddenly
shifts over one page. I'm left to stop what I'm doing and scroll over to
that page and continue editing. As soon as I edit ANYTHING else, again, the
entire score shifts over one page. I just sat here and tried to move a
dynamic mark over to the left and upward, an action that should take a few
seconds, and it has taken me 3 minutes. I can't drag anything from one place
to the other, it disappears if I try. I'm having to move things via the
arrow keys on my keyboard. Each time a click an arrow key, the score shifts.
It's become impossible to work on my score.
Comments
Welcome, could you attach here your score?
Use the "File attachments" option at the bottom of the page, just above the Save and Preview buttons when you're typing your post. Click on 'File attachments' it will become browse
Try Ctrl+A-> Ctrl+R
In reply to Welcome, could you attach… by Shoichi
Here it is. Journey_FINALLY_FINISHED.mscz
In reply to Here it is. [inline:Journey… by Aaron David
Or I do not understand (likely) or here does not happen much of what you describe ...
Try deleting the page break on page 7
In reply to Here it is. [inline:Journey… by Aaron David
What seems to be happening is on page 9, there is a key change to E/c# and then back to C/am. MuseScore seems to be having a hard time figuring out if there is room for measure 39 on that line or not. The courtesy key signature that is needed if the measure is moved to the next page but not otherwise is what confuses the issue, I believe. We do have code within MuseScore specifically to deal with this situation, but sometimes it still gets confused. I did fix a bug that led to this happening in some cases prior to 2.1, but obviously, there are still sometimes issues remaining.
The good news is, the workaround is very simple: either reduce the stretch of the measure on that line so measure 39 is guaranteed to fit, or else move the page break to measure 38 so measure 39 is guaranteed to be moved to the next page.
Meanwhile, your file can help us diagnose why this still happens, so thanks for attaching it - hopefully we can identify the reason MuseScore is getting confused here. My guess is it will turn out to be specific to the fact that the new key is C/am, and we aren't accounting correctly for the naturals in the key signature when we try to calculate how much space it will take (we handle that key specially). But that's just a guess.