Saving and re-opening after transposing - everything is in the wrong key
I've been using musescore 3 .0.5.5992 to write down some three octave scales
Having entered the first set of scales (these are so-called Galamian scales for violin - so there are five different scales in each key), I then copy the scale set, append some new bars, paste in the bars, select the new set of five scales and then transpose.
However, I have found that if I save as a musescore file and then reopen the file, the new scales are all in the wrong key (everything is in the key of the first set of scales) and everything is off.
I have appended a before save and after save PDF so you can see clearly what I mean
EDIT:
I have discovered I can cure the problem if, after I've reopened the file, I go to the measure where the key change should be, and insert the correct key signature. Once I've done that, I can save the file, and everything is fine
| Attachment | Size |
|---|---|
| AfterSave.pdf | 97.68 KB |
| BeforeSave.pdf | 91.41 KB |
| GalamianScales.mscz | 36.76 KB |
Comments
After testing and properly reading you post, I see what you mean. I duplicated the problem in the 3.1-beta, so it has not been fixed. I can't find an existing issue for it. If you could create and issue at https://musescore.org/en/node/add/project_issue?pid=1236 set the severity to S3-Minor and check the Workaround box and leave everything else programmers will be able to find the issue and fix it.
In reply to After testing and properly… by mike320
It looks to me at first glance like the problem is that the Transpose command is not setting the new key signature to "non-generated", so it doesn't get written on save.
In reply to It looks to me at first… by Marc Sabatella
I've created an issue as requested - thank you
In reply to I've created an issue as… by Tony Leatham
I see it in #287662: Key signatures at start of selection transposed via Tools / Transpose lost on save, thank you.