Styles in the parts of a MS 3.5 file with parts imported in MS 3.6 are (unwillingly) reset and not saved after changing.

• Jan 27, 2021 - 00:55
Reported version
3.6
Type
Functional
Frequency
Many
Severity
S2 - Critical
Reproducibility
Always
Status
duplicate
Regression
Yes
Workaround
No
Project

Steps to reproduce the issue:
1) Load a MS file with parts in it, made with MS 3.5 (for example the attached file Bach, J.S_Musikalisches Opfer, BWV 1079_Ricercar a 3_vi+va+vc_02PV.mscz ). Choose 'Keep old style' (but other options will give comparable issues).
2) Compare the result of the score and the parts with the versions seen in MS 3.5. The styles of the parts will be changed more than the styles of the score. (See also the attached pdf file, made with MS 3.5 Bach, J.S_Musikalisches Opfer, BWV 1079_Ricercar a 3_vi+va+vc_02PV-Partituur_en_partijen.pdf ). This is especially seen in the music font and text styles.
3) Change some styles in the parts (for example to reflect the styles in the score), especially in the music font and text styles.
4) Save the file and close it.
5) Open the saved file.
6) Check the parts for the changes in the styles you made. No changes are found. They appear not to be saved.
In this process, I used a newly saved style (mss) file for both the score as the parts, but that seemed to have no effect.

The overall status is that I cannot use or change any MS 3.5 file which already has parts in it (which in my case will have many format changes), or I have to rebuilt the parts all over again. In the update process from MS 3.5 to MS 3.6, I was not able to retain MS 3.5, so I'm stuck.

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.6.0.487915773, revision: 1977cb3


Comments

In reply to by vercammenphb

I tried the nightly build 202101270430. Opening a MS 3.5 file with parts and 'Keep old style' gives good results. Only the position of the bar numbers is reset.
But when I save that file and reopen it, then lots of styles (music font, text styles) are reset (to the default?), even in the score itself. So the fix still needs some fixing.
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.6.0.514063336, revision: 379a44d