Instrument Change data not properly saved on linked staves

• Aug 21, 2020 - 15:54
Reported version
3.5
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

When changing Instrument properties in Edit Staff (right click on staff after Instrument Change -> Staff Properties) and the instrument has linked staves, the changes are lost when the file is saved/reloaded.

To reproduce:
1) Open attached MuseScore file (or create similar)
2) Edit staff after instrument changes
3) Change Short Names
4) Confirm that the new short names show in next system
5) Save, reopen the file
6) Confirm that only non-linked staves had their changes saved to the file (or properly read from it?)

See also attached images, before and after reload.

One of the problems regarding this issue is that it is not be possible to change an instrument's String Data on a linked staff+tablature score (typically, change to a "Drop D" guitar back and forth, or change a banjo string tunning in the middle of a song)

Attachment Size
linked instrument changes after saving.mscz 17.66 KB
linked instrument changes before saving.jpg 56.65 KB
linked instrument changes after reload.jpg 70.85 KB

Comments

• Aug 21, 2020 - 15:57

FWIW I've traced what I was able to. It seems that only the first of linked staves has its Instrument (change) data applied after Edit Staff. The second staff's Instrument Change keeps the stock instrument data, and this stock data seems to be unused while working on MuseScore.
When saving, both Instrument Changes are saved (first with edited data, second with stock data) and when Read, both are read and it seems that the Second Instrument Change (stock instrument data) overrides the first (edited data). If this makes any sense.

Maybe the solution is to grant that Edit Staff copies the Instrument data (names, string data etc) to all linked staves on Apply/Ok.

Reply

Fix version
3.5.1