Issues Loading MS2 scores into 3 Beta
Reported version
3.0
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project
A couple of issues arise when loading scores made in MuseScore 2 into MuseScore 3.
One score was corrupted, (see attached, mm. 59-60) which I was unable to delete to fix the score. Seems to be mostly an issue with time signature/meter.
A couple different scores do not show measures with music when "Hide Empty Staves" is applied.
Has shift-click and drag to move measures and events been removed from 3? I found it a very useful feature, having using Sibelius 7 & 8. Is there a different way of doing this?
Regards,
Doug
Attachment | Size |
---|---|
Dolphin.mscz | 31.83 KB |
Comments
That isn't a 2.x score, at least not any more - looks like you saved it in 3.0. Do you still have the 2.x version? If it reported as corrupt when you first imported it, that is probably not a bug, at least not in 3.0 - probably it was corrupt, due to a bug in whatever version you used to create it.
Hide empty staves had a bug in the previous beta that should be fixed in the current one. Did you update today? If so, please tell us how to reproduce the problem you are seeing. When I ignore the corruptions and the hide empty staves, I don't see obvious problems.
Shift+click was formerly a way to constrain dragging to one dimension only. This is indeed currently not working, will hopefully be added back. But by far the more precise way to make manual adjustments is using the Inspector.
In reply to (No subject) by Jojo-Schmitz
No longer have the 2 file. Every time I try to delete the problem measure, the program crashes. Is there a way to salvage it, or should I cut my losses, and reengrave?
That is bad, please check again for some backup, as without there's little change to reproduce and then fix.
You should definitely not delete your 2.x scores when trying out the 3 Beta!
To fix your score's corruption see https://musescore.org/en/node/54721
Still having some issues. I believe the rhythm is what is confusing the software. There are eighth note triplets with only every other triplet being played. Perhaps it's reading as a different meter. This shouldn't happen, as it is a pretty routine polyrhythm in contemporary music. It is far and away the cleanest way to notate this, and it is unacceptable that it keeps crashing the program.
In reply to Still having some issues. I… by DougFunky
Hmmmm. Upon closer inspection, it would seem that grace notes are an issue, specifically the first option. It seems to throw off the rhythmic counting of the software.