Unwanted clefs

• Dec 4, 2018 - 10:31
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

Im getting a lot of unwanted clefs, don't know where they come frome but it happened multiple Times in the last 30-40 minutes or so. (see attachment)

Attachment Size
ms2.png 187.09 KB

Comments

• Dec 5, 2018 - 13:55
Status active ⇒ needs info
Priority ⇒ P1 - High

Could you please attach the score so we could reproduce the issue on our side?

Reply

• Dec 6, 2018 - 18:44

This happened in the beta but we believe it to be fixed (scores already imported and saved will need to be re-imported, though). If you can still reproduce with a 2.x score using a current build, please attach the score (not just a picture).

Reply

• Dec 6, 2018 - 19:07

It never happened to me in the 2.x version, but im just reporting problems with 3.0 version. (maybe I just don't understand something :) )

Reply

• Dec 6, 2018 - 19:11

You don't see the problem unless you open a version 2 score in version 3. This is supposed to be fixed in version 3. To see if it is truly fixed you need to open the version 2 score in version 3. If you open the score you already saved in version 3, the problem will not go away because the problem is saved in the score.

Reply

• Dec 6, 2018 - 19:38

So, to clarify: we believe you took a score created in 2.x, opened it in 3.0 beta, and saved it. 3.0 beta definitely had a bug here, and now that version of the score you saved with 3.0 beta has that bug "baked in". So it's too late for that score. but we believe if you can find the original 2.x score - from before you saved it in 3.0 - then the current version of 3.0 will import it without problems. We'd like to verify that, so if you still have the original 2.x version, please attach it.

Reply