strange score behavior

• May 1, 2012 - 01:57

Can someone please tell me under the "notes" menu, how the "concert pitch" toggle affects an entire score? I am completely befuddled. I know if you toggle one way, it makes every instrument in the same key signature. But, if you need the notes AND the key signature to reflect what pitch the instrument is actually in, what do you do? I was under the impression Musescore would automatically change the notes to the proper key.

Somehow, my score got all hosed up and notes appear the same between parts, such as an oboe part (pitched in C) and a clarinet part (pitched in B flat).

If you take an entire line (oboe, say) and COP it, then paste it into, say, the clarinet line on the score, does it automatically get put in the right key, with the right notes? Or, does Musescore paste the notes into the clarinet line EXACTLY AS THEY ARE IN THE OBOE PART I COPIED FROM (causing the notes to actually be a whole step lower than what the part should be)?

I know this isn't very clear, but my score (and consequently all the parts) is really hosed up, key-wise. Yet, when I play it back, everything SOUNDS copasetic. If real instruments tried to play the parts, they would all be sounding in different keys!

I have attached the score, for an experts perusal. thanks.

Attachment Size
Uncle Meat.mscz 71.69 KB


I'm not sure how you created this score, but it appears you did it backwards.. It should be the case that with Concert Pitch enabled, all key signature are the same, and all pitches display as they will sound.. When you turn Concert Pitch *off*, you should see things displayed on the keys they need to be printed, so clarinents should have two more shaprs than flutes, etc.. but your score appears to show the same keys only when Concert Pitch is turned *off*, and when on, it shows clarinets with two *fewer* flats.

What it looks like is that you created the score with no key signature, then while concert Pitch was switched off, you added the key signatures to all the parts, but did so as if you had concert pitch turned on - that is, you added the D major / B minor key signature to all staves while Concert Pitch was off rather while it was on. This would explain the messed p state of the score, I think. But there are probably other possibilities too.

It would help if you described how you went about creating this score - created from scratch versus a template, key signature added during the new score wizard versus after score creation, whether ntes were entered while Concert Pitch was turned on or not, whether you entered the notes at sounding or written pitch, etc.

The way I usually work is to create initial key signatures during the new score wizard, because that way it is applied correctly to all staves. Then after the initial score creation I do all note entry and editing with Concert Pitch turned on, meaning it is all at sounding pitch. Only at the very end do I turn Concert Pitch off', and hen Musescore automatically transposes all parts (notes as well as key signatures) as necessary to be read by each instrument.

In reply to by Timothy Osburn

You could try copying and pasting parts from you existing score into the new one. Set up the score, make sure the key signatures all match when Concert Pitch is turned on, then start copying parts one by one. Save your new score before each copy, because in some cases, copying and pasting from one score to another seems to cause crashes, and I'm not sure what triggers that exactly.

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