Key signatures at start of selection transposed via Tools / Transpose lost on save

• Apr 13, 2019 - 18:28
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
MuseScore

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

• Apr 13, 2019 - 19:19
Title Saving and re-opening after transposing - everything is in the wrong key ⇒ Key signatures at start of selection transposed via Tools / Transpose lost on save
Severity S4 - Minor ⇒ S3 - Major
Priority ⇒ P1 - High

It appears that when transposing using Tools / Transpose, and you use the option to transpose key signatures, the Transpose command leaves them marked "generated" if they were originally. That is, if you transpose a passage that didn't already contain a key signature but happened to start at the beginning of a line and thus already had a generated key signature, it remains generated after transposing, and thus gets lost on save.

Reply

Fix version
3.5.0