Cmd + Z (undo) hides measures

• Nov 19, 2017 - 13:03

Musescore started to act strangely today. I'm not sure if I have accidentally pushed some key to change the function of "undo" or is this really a bug.

When I have inserted notes and want to undo my last change I usually use the key shortcut cmd + z to undo. And it has worked as it should until today. Now when I push cmd + z it hides a bunch of measures (and everything that was in there) and shows just one empty measure. The only way to get back from here seems to be that I delete this measure and then it returns to the previous state. In the photos below you see how the measure 46 changes to 61 and the key signature and the clef disappears.

46.png
61.png

Any ideas? I'm using Musescore 2.0.3.1 on macOS 10.13.1. (The newer version of Musescore doesn't work with the new macOS.) I tried to relaunch Musescore, but there was no change.

Attachment Size
46.png 32.51 KB
61.png 26.65 KB

Comments

• Nov 19, 2017 - 14:07

First I pasted the notes from another measure into measure 40-something and then undid it. That's when the problem first time occured. In the example above, in first image I have entered the note in measure 47 and then pressed cmd + z that caused the situation in the second image.

Reply

• Nov 19, 2017 - 15:07

I have a couple of suspicions as to what may have led to this.

  1. This is a part being edited in a score with more than one instrument.
  2. You have changed the range of the Volta by using ctrl-arrow or put the volta in edit mode and dragged the end rather than applying the volta to all the measures at once or using shift-arrow to extend it's coverage.
  3. MuseScore is confused because you have multiple D.S. al Codas and to codas with the same labels, play until and continue at jumps locations. (See https://musescore.org/en/node/265130 for more info).

There are other possibilities but these seem the most likely. Some of the problems were fixed in version 2.1 (which you said you cannot use).

Reply

• Nov 19, 2017 - 15:18

I see... There is only one instrument in this piece. But there was indeed incorrectly dragged volta that I corrected before saving. And to that 1. volta bracket I added (what is still missing from the images above) that it is indeed 1. and 3. (Which might make more sense why those segnos and codas are how they are.) Perhaps it was one of these things or both which were affecting my score. Thank you!

Reply

• Nov 19, 2017 - 19:55

I tried posting this earlier but may have forgotten to hit "Save"...

My guess is that you have "Hide empty staves" enabled, and whatever operation you are doing / undoing is affecting whether a staff is empty or not and thus whether it gets hidden or not. Notice how in your first picture there is only one note from measure 46 to the end, and in the second picture, measures 46-60 are hidden. Whatever is being undone between those two pictures is probably having the effect of removing that one note, which makes measures 46-60 empty and thus they get hidden. No idea why the last measure remains visible, but presumably that is also explained by the specifics of the score and the operation you were doing/undoing.

Reply

• Nov 27, 2017 - 11:53

Okay. I was able to recreate this situation. I had a finished score where I was adding page changes etc. I dragged one to a wrong place and pressed cmd + z. And once again the first measures of my coda were hidden and the key signature and the clef disappeared from the coda. I saved this as a different file, closed everything and opened this saved file again and it looked completely normal. Thus I think this must be a bug in MS 2.0.3.1.

Hopefully the newer (working) version will be soon available for MacBook running macOS 10.13.1...

Reply

• Nov 27, 2017 - 16:29

Are you sure you didn't have "Hide empty staves" enabled and that this wasn't just an example of the effect I described previously? If you believe this is a bug and would like us to investigate further and hopefully fix it, please attach your score and precise step by step instructions to reproduce the problem. Meanwhile, though, from your description it sounds like a minor one - a temporary glitch that fixes itself on save/reload. Most sch glitches also fix themselves on almost any other operation that forces the score to be redrawn - even just Ctrl+A to select all.

Reply

Do you still have an unanswered question? Please log in first to post your question.