Since a few days with MuseScore from master opening 2.0 files is impossible if they contain
(de-)crescendo lines or voltas
Reproduced today with 76820da37, I guess the culprit is in fe8a3e5
I guess a53bf1e was meant to fix this (and seems to do for voltas), but the files that won't open before (due to crescendo lines) now either crash MuseScore or are reported as being corrupt and load mostly empty
Comments
I guess a53bf1e was meant to fix this (and seems to do for voltas), but the files that won't open before (due to crescendo lines) now either crash MuseScore or are reported as being corrupt and load mostly empty
crashes and corruption -> critical
came up again in #173901: text-tag in certain surroundings prevents musescore from loading files
should be fixed in latest master
Nope, sorry. It doesn't crash anymore nor reports/causes corruption though, it just doesn't open the files at all with an 'invalid format' error
ok, i probably did not catch all cases. A short score snipped to extend our regression tests would be helpful. I
It just takes a (de-)crescendo line, created in 2.0.3 (or 2.1 for that matter), I believe
It stumbles accross the text tags in
{syntaxhighlighter brosh:xml}
cresc.
(cresc.)
{/syntaxhighlighter}
which should be dealt with in `readTextLineProperties()`
I just reactivated the 206 compatibility tests and added my test file (hairpin.mscx). Yours must be different.
fixed (for scores with parts) in 723015c
Automatically closed -- issue fixed for 2 weeks with no activity.