Default accidentals

• Jan 1, 2020 - 20:57

Is it by design that input of a note that has previously, in the same measure, been given an accidental distinct from the key signature, but not in the same octave, doesn't retain that same accidental without being shown? If so, what are the pros in relation to having equivalent pitches start as in the key rather than in the accident already set, albeit in a different octave?

For example, the following screenshot contains a measure in a score with F-minor signature (four flats). The ledger-lined D has been given a natural, and the next D on the same octave is still natural. After moving downward, the D that is entered has no accidental, but MuseScore shows it in the status bar as D-flat. This is exemplified when moving it up one octave and seeing the accidental automatically project as a flat. Maybe I don't know the standard for notation very well, but it seems to me that this could be/is confusing since the D-flat isn't given any explicit flat marking, and my intuition tells me that this would be a D-natural after reading a flat before it an octave above. I'd be inclined to read it as a D-natural. But MuseScore is saying it's D-flat with the signature.

measureaccidentals.png

And what's more, if the notes are set up so that MuseScore first inserts following D's in the octave below, that means that the natural sign must be toggled each time:

measureaccidental2.png
That is, those last two D's showing required each time a natural-toggling, and then an octave shift. If the octave shift was performed first, the user can't switch to the natural sign because the accidental has to be toggled first while in note-entry mode, and has to either exit note entry mode to fix it, or re-enter the note with first explicitly toggling the natural sign, and this feels a little awkward to be described as correct default behavior.


Comments

And another thing is that toggling doesn't really give the "non-accidental" for natural here. Meaning, the user might have to resort to using the semi-tone up/down method get "naturalness" by way of non-accidental, and this too only after octave shifting. Appropriately though, if the correct natural was given in another octave, it will disappear once shifted to the right octave.

This is potentially confusing indeed. The rules of notation say the lower D is Db, but it would be almost universally agreed that one should add a courtesy accidental here. Someday MuseScore may add courtesy accidentals automatically, but for now you need to add them manually. If you omit it, then it's definitely a Db. but most people will read it wrong.

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