Multimeasure clef position bug
Hello!
I have a problem with multimeasure clef position on both changes as you can see in attached file. When fixing, saving the file - all is OK, but when opening it again - the same bug appears... The only solution I found at the moment is putting the clef *after* the barline. Then all is well. Thank you!
Attachment | Size |
---|---|
My_First_Score.mscz | 4.24 KB |
Comments
Can you describe step by step how you created the file? We just see the result, which is obviously wrong but I have no idea how you created it.
This one I just created it without multimeasure and then selected the option "create multimeasure". On the other case, I had a score for cello and piano and when extracting the cello part I had the same result.
Please give step by step instruction to reproduce the bug...
What I did with MuseScore 2.0 on Mac OSX
Ok, I also confirm that on Win 7. Thanks!
In some ways, this reminds me of #33381: corruption when saving score containing a system beginning with a start repeat on an mmrest, maybe some of the same issue are involved.
This issue occured there is six months! On October 10
- I receive a correct result with this Nightly: 9b8c7c6
_ Not with this one: fc6fe02
So, the cause is most likely a side effect of this commit: https://github.com/musescore/MuseScore/commit/986f35d14968e127bfae58641…
Well done!
That commit is indeed the fix for the issue I mentioned :-)
Fixed in 3e8cb5b2e5
Automatically closed -- issue fixed for 2 weeks with no activity.