Enharmonic changes by user should persist at least through the same measure.

• Sep 6, 2015 - 02:33
Graphical (UI)
S5 - Suggestion

When the user makes an enharmonic change, either on note entry or during later editing, I would like it to apply to all equivalent notes later in the same measure. After correspondence, Marc Sabatella said I could submit this, whether as an option or a default I don't know. It seems to me to apply to all forms of note input, but he may disagree. I usually make such choices when editing later, at which point I would have thought MuseScore wouldn't know how the notes were input.


Well, the only forms of note input where you are not already making the spelling explicit upon first entry is the Piano Keybaord toolabr. With both keyboard and mouse input, you enter G# different than Ab, so there is no need to "correct" the spelling afterwards.

To be more specific, the request as I understand it is this:

During note input via MIDi or piano keyboard toolabr, when pressing a key that is not in the key signature and MuseScore has to guess how to spell it, it should first check to see if there is an existing pitch in that measure and use its spelling if so. So in other wors, if you are in the key of C and enter an F# and then change to Gb then press that same MIDI key again, it should enter as Gb automatically, because the previous Gb in that same measure is assumed to still be relevant.

Yes, that is my request. Well, more, since I often make enharmonic corrections in an editing phase. If you edit an F# to Gb, then that should be applied to the rest of the measure also. Of course if you really want an F# later in the measure, then you will have to edit again, but this is far outweighed by the advantage of not having to fix every note in a written out trill (or select and raise and lower, which may change other notes).

I don't altogether understand what you say say about keyboard and mouse, but it doesn't matter. (I don't use them. Maybe I should, but the bible does seem to favor piano keyboard and MIDI.) The reason the spelling is explicit is that you have made it so in another step. In fact, if I understand the foot of p47, you are already doing for keyboard and mouse the first part of what I requested for piano keyboard and MIDI. And I would think the second (editing) part of my request would apply to keyboard and mouse also. Cheers!

Except it's the more part I specifically *disagree* with. Making a change to one note should not affect other notes - that would be the wrong behavior 99% of the time. Better to just get the spelling right during entry.

What IO am saying abut keybaord and mouse is that one would never enter a G# if one meant Ab. This happens with MIDI because there is only one button to press that could possibly be interpreted either way and MuseScore has to guess which you mean. When using regular keyboard or mosue input, you always enter G# directly. There would be no way to say "I want a note between G and A, guess for yourself how to spell it". There is a way to enter G#, and a way to enter Ab. So the situation you see with MIDI input does not happen with keybaord or mouse input.

I am not following. With piano keyboard, you first select a piano key and then correct the accidental if necessary. You can do the same with a MIDI keyboard. If you do it with piano, the same interpretation is maintained through the measure, at least that's what I thought it said at the bottom of p47. Why not with MIDI also? The "more" is, if you make the same correction when editing, why not the same as if you had made it when entering the note to begin with? I must be missing something.

Ah--I just tried it with piano keyboard, and the same interpretation is not maintained. That's not what p47 meant. I clicked on the black key between C and D, got C#, changed it to Db by raising and lowering, clicked on the same black key, got C# again. Is that really what you want? I'm definitely confused. How would you enter C Db C Db from the piano keyboard in the key of C? With the mouse I understand: you enter D's and they stay flat after the first one is flatted.

Neither of the being discussed is the one you use to type. One is MuseScore's piano keyboard on the screen. The other a MIDI keyboard attached to the computer

I didn't say the built in piano keyboard (which hardly anyone knows about or uses) is different from MIDI - I specifically said it is quite similar and suffers the same inherent drawback of not having a way to differentiate spellings. It is the *computer* keyboard - the usual method of entering notes into MuseScore - that works more efficiently in that G# and Ab are entered completely differently, so you don't normally enter a note and then have to hope MuseScore guesses which one/ You simply type what you meant the first time, no guesswork or changes necessary. So, typing "G Up G G G" enters four G#'s, each and every time without fail, while typing "A Down A A A" enters four Ab, each and every time without fail.

Thanks. But I have used computer keyboard entry enough to know that MIDI keyboard is WAY faster for me, and would be faster still if the enharmonics persisted through a measure. How would rocking 5ths or octaves be on a computer keyboard?

Not so rare in piano music, and it is of course rarer still for MuseScore to guess the spelling wrong. :-). A single line can probably be done quickly by any method, once you get good at it, though for me MIDI is far the fastest. But then there are chords, as you say in your book. So MIDI wins hands down in most piano music. It's true I use a 49-key MIDI keyboard, so occasionally I have to raise or lower a note or passage by an octave.