Frames are not read correctly 2.x->3.0
Reported version
3.0
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
See attached MS2 score. To see the problems, open it in MS2 and then in MS3, and compare them.
Many of the default values for frames are not carried across, such as for Staff Text, System Text, Title, Subtitle, Lyricist, Composer etc. There are also some elements for which the frame is just not read (i.e. markers, dynamics, repeats). And, fingerings, when switched from a circle frame to a box, still display as a circle when read in 3.0.
This is all mainly due to the different default values in read206.cpp not being set for frames.
I am working on a fix for this issue.
Attachment | Size |
---|---|
Test_Frames_XML.mscx | 15.96 KB |
Comments
Connected? #277509: Text styles: the displayed font-size in the Inspector does not match the actual value. And the problem with fingerings also affects rehearsal marks.
In reply to This issue was recently… by geetar
I don't think the issues are connected. The fix I'm implementing will fix reading circles for all elements, I think.
Win 10 / MS 3.0.0, 2647ff8
This looks like a similar issue. The offsets in the frame text have been lost.
Shouldn't be marked as regression. Workaround does exist, involving manually setting styles.
PR: https://github.com/musescore/MuseScore/pull/4094
Fixed in branch master, commit 926b3517ef
fix #277639: frames and frame attributes not read correctly from MS2
Fixed in branch master, commit 236c7071f3
Merge pull request #4094 from jthistle/277639-read-frames-206
fix #277639: frames and frame attributes not read correctly from MS2
Automatically closed -- issue fixed for 2 weeks with no activity.