Key Signature issue

• Apr 6, 2021 - 21:58

I'm trying to learn Musescore 3.6.2. I started a new score, answered all the questions in the dialog boxes, and specifically said the score should be in the key of D. It was a simple fiddle melody, so everything was entered in one session. The score looked good and played back fine, so it was saved for further editing at a later time.

Upon opening the saved score all the F's and C's had natural signs in front of them. Any idea why that would happen?

So, all the natural signs were changed to sharps. So now I have a score written in the key of D with sharp signs in front of all the C's and F's, that's not right. What has happened?


In reply to by wtalley550

The second score has exactly the problem I described before - you must have asked museScore to add accidentals (using the # button on the toolbar or palette), rather than asking it to raise the pitch (using the up arrow key). If you ask it to add an accidental, it will do so, whether needed or not. That's an important feature because it's how courtesy key signatures work. So, dson't use the toolbar to add an accidental if you don't want to physically see an accidental - use the arrow keys to change pitch and let MuseScore calucalte accidentals automatically.

As for how the naturals appeared in the first place. that's still impossible to say. I can just say that in over 10 years of use creating thousands of scores and reading tens of thousands of forum posts, I've never once heard of this happening all by itself. I strongly suspect you accidentally did something to make that happen, but aside from the possibility that you might have somehow delete the key signature then added it back but too late, it's hard to guess what. Maybe you deleted it while creating the pickup measure? I have seen that happen.

As mentioned, we really neeed to see the score in order to do more than guess. But my best guess if, when you added the sharps to the notes, you used the toolbar, which says, add a "sharp sign" - and it follows your instruction literally whether the sharp sign is needed or not. If you just want to change the pitch and have MuseScore automatically determine what accidentals are needed, just use the arrow keys to change the pitch directly.

That still doesn't explain how you ended up with naturals to begin with though.

Thank you everyone for taking the time to try and help me. I "bit the bullet" and made a new score and this time it worked as expected. So, it's obvious I made a mistake somewhere and it would be nice to know how to correct it; but, for now, my immediate problem has been solved.

In reply to by wtalley550

Well, to correct it, we've already explained, simply use the arrow keys instead of the toolbar or palette. And if you've then made that mistake as well, just delete the unnecessary accidentals (eg, right-click one, Select / All Similar Elements, then Delete). They will still be F#'s & C#'s because of the key signature.

If you mean, how to avoid the original mistake, that's harder to say without knowing, but again, this is not something I've ever heard reported before, so it must be some really unusual strange sequence of things you did, chances are good you won't stumble on that exact combination again.

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