Transposed instruments in score not displaying transposed unless concert pitch turned on

• Feb 7, 2016 - 03:38

The attached score has somehow become badly corrupted in a whole new way. All the instruments appear to be in concert C with concert pitch turned off. Turn concert pitch on, and the different key signatures appear. One look at instruments like the baritone sax and bass clarinet shows something is drastically wrong.

Before trying to figure out how it happened, I would be very, very grateful if somebody can tweak something in the uncompressed MSCX to restore it. Fixing it manually would be a terrible pain in the neck. Please help if you can.

Attachment Size
Excellence.mscz 562.67 KB

Comments

I turned the concert pitch on and then I dragged the F major key with Ctrl to each instrument (except the drums). Here is the score:

Edit: I just found out: It's even easier when you drag the F major key to all instruments (without Ctrl). The drums will not change.

Attachment Size
Excellence_0-1inF.mscz 546.21 KB

There were some bugs with early early experimental pre-release builds (eg, beta or nightly builds before the release of 2.0) that could cause this type of corruption. might have been a nightly or two *after* 2.0 where such things could happen. I'm not aware of anything in any official release or in any recent nightly build that would do this, though. Is it possible this score was edited with one of those experimental builds? I see it was msot recently saved with a relatively recent nightly build which should be OK.

As I recall, and also thinking about what I know about the structure of the code, I might expect that if there are still bugs in this area somewhere, they might be tirggered by some combination of the C major key signature (which is treated specially in many places) plus perhaps an invisible top staff of the score, or a top staff that is percussion or tab, and then some combination of changing keys (to or from C major) and the state of the concert pitch button. Not that I know of any remaining bugs in this area, but if I were thinking one existed and wanted to try to reproduce it, that's what I'd be playing with trying to force a problem to happen.

If this was created recently from a template that was itself created with a much older nightly build, that could possibly explain it.

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