Key Signatures are inaccurate in parts compared to the score

• Jul 6, 2020 - 23:35
Reported version
3.x-dev
Type
Graphical (UI)
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project

The key signatures in one of the separate parts in my score does not have the same key signature as the rest of the score, even though it is all in concert key. Not sure if this has anything to do with it, but it is the one part in the score that has a mix of drumsets and melodic instruments, besides the main score.

To reproduce, try creating a separate part with a mix of drumsets and melodic instruments, specifically keyboards in this case.

The screenshots and file show what I mean.

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.5.0.12237, revision: b5add95

Attachment Size
Key Signature Glitch.mscz 78.84 KB
Screenshot (382).png 234.97 KB
Screenshot (383).png 270.39 KB

Comments

I don't see this either when I load the score into a current build of 3.5. There certainly have been known bugs in this area in the past, all of which are now fixed. Was this score by chance begun in an earlier version? If so, it may have been victimized by one of those now-fixed bugs. Otherwise, it would seem one of these bugs does remain, but since we can't reproduce it just by loading the score and looking at the rhythm section part (it looks normal to me and just like the score: a change to four flats at 13, four sharps at 17, back to four flats at 27.

So in order to investigate, we'd need precise steps to reproduce the problem.

The score was created in an earlier version, probably in a pretty early version of 3.0 now that I think about it.

Honestly I'm not sure how else to reproduce it besides what I said

Ok, so very likely the problem was caused by a bug in the earlier version and would not be reproducible in a score created today. If you do eventually find otherwise, please attach that score - ideally in a state before the problem appears and then give steps to reproduce the problem. But I’m guessing you won’t see this issue any more except where it already exists in older scores.