Some bugs I found in the past few days (version 2.2.1)

• Jun 2, 2018 - 14:28

OS: Windows , Arch.: x86_64, MuseScore version (32-bit): 2.2.1, revision: 51b8386


*Tempo Markings often do not play back properly (actual playback speed not matching written tempo on the inspector and/or the actual marking).

*System and Staff Text properties (like size, font, italic, etc) are not preserved on score copies.
(For this one I tried both "Save As..." and "Save a Copy..." and the bug was present in both)
(This was not noticed on dynamics text (p, mf, f, etc) and hairpins).

*Changes to Scores are often not present in Parts, for no apparent reason, and vice-versa.
To be more specific, this happened with things like skipping bar counts (when telling musescore to not count a measure as a measure), hiding certain text like bar numbers, etc.
(This one is especially frustrating because it's quite an old bug and makes part editing with Musescore very difficult)
(There also needs to be a sort of automatic system to avoid symbols, notes, etc from overlapping, kind of what Sibelius has)
(Come on... I can't be be only person who edits full scores with Musescore :I )


In order to understand your issue and assist better, we would need you to attach your score and precise steps to reproduce the problem. Otherwise the best we can do is guess. That said:

1) There are a couple of known issues with tempo marks if you try editing them after already generating parts or a couple of other special situations. These mostly clear themselves up after you reload the score. If you continue to have trouble, do attach your score and more information about the problem.

2) I can't reproduce any such problem, so again, attaching your actual score and precise steps to reproduce would help.

3) Some changes are deliberately no synced, to allow you to have them be different in score & aprts. For example, manual positioning very often needs to be applied differently so that is not linked. And it is very common to want to hide something in the score but not the part of vice versa. So that's not a bug but a feature, unless there is is something that in fact should be linked but isn't. To me, the option to exclude a measure from the numbering probably should be linked indeed. See for example #64636: "add to measure number" is not linked between score and parts after reload. But as you can see, there are those wanting even things like this to not be linked. So in general, we do err on the side of not linking things, because you can always reproduce the change in the part, but if we linekd something you didn't want linked, there would be no similarly simple workaround.

4) As for automatic collision avoidance, some of this is indeed in the works and will be coming with MuseScore 3.

Do you still have an unanswered question? Please log in first to post your question.