unintentional accidentals

• Jan 11, 2012 - 12:17

I am using V1.1 and musescore for the first time. I am a choirmaster and therefore use the hymn palette. Windows 7 (64bit) is my OS on an HP Pavillion dv6 notebook PC.

I have just finished writing a couple of SATB tunes and found musescore very friendly. The only bug that has come up is when an accidental is put on a note, the next same note in that measure immediately goes back to its root although it was not intended to. Eg in the key of F, if I put a sharp on a G, the next G in that measure has a neutral accidental on it although I wanted it to stay a sharp. Then I need to put a sharp on that 2nd G and all other Gs thereafter in that measure if I intend to have them G#s. I now have a weird looking score with all these same notes in a measure displaying the same accidentals in order to play correctly.

I could not find a mention of this problem in the forum hence this query.



Hi Stanu and welcome to MuseScore :)

This is actually a known problem which I believe is going to be addressed in a future version.

The accidental buttons you see in the Note Entry Palette are actually intended for providing courtesy accidentals, which is why you are getting too many :)

If, instead of using the buttons on the palette, you use the arrow keys to move the note up or down, you will get your accidentals appearing properly, however currently using the up key raises a note by 1 semitone and enters a sharp and the down key lowers a note by a semitone and enters a flat.

This means that you may have to go a semitone above/below the note and then use the opposite arrow to achieve the accidental you require.

If you a re requiring enharmonic accidentals such as E# the only way of entering them is to use the palette. In this case, enter the whole bar before entering the accidentals, and then work backwards, adding them from the end of the bar - you will find that MuseScore will adjust the accidentals properly.


MuseScore makes no assumption about what note you actually want to enter, so if you enter a G# and then enter a G it gives you the G that the key signature contains - the root, a G natural. If (while that G is still selected) you hit the Up arrow, it will remove the natural sign and playback will then play it as a G#. So there is no need to add a # sign to get correct playback.

If MuseScore assumed that after entering a G# the next G in the bar (measure) should also be a G#, anyone wanting a G natural would have to adjust it down, so overall it's arguable that there would be no gain in note entry efficiency. The way it works soon becomes second nature, particularly if you use the computer keyboard for note entry.

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