Mistake in transposing instrument key signature

• Dec 4, 2023 - 12:55

I'm using a score downloaded from MuseScore.
It's in Bb maj. So the B clarinet part should be transposed C maj. The notes are right, but the Key Signature is coming out as D maj. on the Score
I can't find a way to correct this. I've tried to isolate this stave; I've tried to change instrument and then change back to clarinet; I've checked that the transposition in the part properties is right (a major2nd).

It doesn't seem to be a general MuseScore problem as I've set up other scores which transpose correctly.

Help!

Attachment Size
Beethoven_Trio_No.4.mscz 196.38 KB

Comments

In reply to by rothers

Interesting. Not in 4.1.1 though
So seemy the backwards compatibility in my 3.7 fixes it on the fly, not bad ;-)

Probably it just ignores

          <KeySig>
            <concertKey>0</concertKey>
            <actualKey>2</actualKey>
            </KeySig>

as when I delete these lines, 4.1.1 reads it correctly too

Edit: actually that's indeed what happens:
Debug: tag in line 320 col 23: actualKey (...\libmscore\xmlreader.cpp:208, void Ms::XmlReader::unknown())
The code in 3.7 does read the concertKey though:

            else if (tag == "accidental" || tag == "concertKey") // + 4.x compat
                  _sig.setKey(Key(e.readInt()));

In reply to by Jojo-Schmitz

Do you update your 3.7 regularly? I'm using 3.7.0.6039870453, revision: 7bd2446 and there it has the same problem as judithamilton describes. No automatic correction ...
I have to set Bb major again to correct it.

EDIT: Clarinet does not have Dmaj but Cmaj. And more strange: switching to concert pitch, clarinet changes to Bmaj but the others not.

In reply to by HildeK

EDIT: Clarinet does not have Dmaj but Cmaj. And more strange: switching to concert pitch, clarinet changes to Bmaj but the others not.
Not strange at all, but as it should be, the others stay ad Bb Major. But your version doesn't have that fix (0957364), it is from September, your version is from August

Thanks everyone. I downloaded it again and it opens ok now, though I haven't tried editing and saving
It's odd that you it opened ok for you from my attached file, which was definitely wrong in my MuseScore! (incidentally the original problem only affected the first movement)

I'm using OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.1.1-232071203, revision: e4d1ddf

Are you saying this problem has been fixed? I wouldn't have the foggiest idea how to debug it myself (my last encounter with basic programming was in 1985)

In reply to by judithamilton

Whatever the reason for your problem, you can fix it by reapplying the Bb key.

What we have discussed is about MuseScore 3.7, a branch of version 3.6.2 of Jojo-Schmitz. This is not an official version, it has the interface of MuS 3, but it can read MuS 4 files and Jojo has fixed a lot of bugs. Many of them will certainly be included in further releases of MuS 4.
You can't debug it yourself, you could only work with version 3.7. which, as I learned today, is constantly being adapted. However, MuS 3.7 cannot work with the new VST soundfonts.

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