How do I stop notes from being "auto-transposed" ?
With all due respect, C-sharp and D-flat are not the same note!
To a piano player / computer / MIDI, they are. Oh, and guitar players too mostly. But to an instrumentalist, especially classical string (violin, viola, cello) they aren't.
How do I stop musescore from substituting an F# for a Gb (for instance) ??
Thanks.
Comments
You haven't said how you are entering the notes, and I think that matters. When entering via MIDI, I think the default is a guess based purely on key signature. When starting from the mouse or computer keyboard entry and then hitting up/down, it seems to try to favor keeping the same letter name and simply adding an accidental. So "F, Up" creates F#, but "G, Down" creates Gb. But I believe it does still take key signature into consideration and doesn't let you enter certain accidentals in certain keys this way. So you use the Accidentals palette (or corresponding keyboard shortcuts you can create via Edit->Preferences->Shortcuts) in those cases.
In reply to You haven't said how you are by Marc Sabatella
I've tried everything you said, but it still does it.
In one measure, I have an F followed by an E. It transposes the F into an E# (why? I'm in Eb!) then it leaves the E, but the 2nd E in the measure is also sharped, so....
In one instance, it transposed to notes of a cord to the same ledger line, then put a sharp in front of both.
In reply to Entering with a mouse by ghelbig
As I said in another thread, you've reported you are on MS 0.9.4. I would not be surprised if this issue was dealt with in the ensuing 2.5 years since .94 was released. While we will try to help, there should be some statute of limitations on bug reporting and expections for old(er) versions.
In reply to You haven't said how you are by Marc Sabatella
"But I believe it does still take key signature into consideration and doesn't let you enter certain accidentals in certain keys this way."
This behaviour does take a lot of getting used to, but it doesn't seem to work the way you think it does via the keyboard. The enharmonic going down (flats) is very different from the one going up (sharps), so you usually end up overshooting one way and coming around to get the note to display the way you want. If I have a score in Eb, drop a low Eb and work my way up to an Ab, I _must_ overshoot the Ab and come back down in order to get it to display properly. Otherwise I will end up on a G#.
Note, I understand why this is necessary. Its just frustrating until the methodology sinks in.