Accidentals

• Feb 29, 2012 - 05:46

1. Open attached score.

2. Select measure 1.

3. Press shift-8 (adds notes an octave below)

Result: Notes appear as they do in measure two, while they should appear as measure 3.
Can we get this fixed in 2.0 please?

Attachment Size
Accidentals.mscz 1.64 KB

Comments

That's an interesting one. And It's not just about the octave. What do you expect when you add a 3rd? is that a minor or major one ?

In reply to by lasconic

FWIW, I have often wished that shift-8 would add a a true octave below the original note, including accidental. So hitting shift-8 while the cursor is on a Bb would always add a Bb, period, regardless of the key signature. It's incredibly rare I'd want it any other way. For other intervals, though, I have no particular expectations. But I think I'd be surprised if adding any other interval ever produced an accidental by default. Which is to say, I think the current behavior is fine for all intervals *except* the octave.

This does sort of relate to another common request, though, and that is what happens is, in the key of C, you enter a B, lower it to Bb, then enter another B. I think most people at first expect this to result in a single note with no accidental - which is to say, it would actually be a Bb, since the previous flat would still apply. Currently, of course, you actually get a B natural, with an explicit natural sign. If MuseScore were to some day support the style of note entry where typing B would enter a note with no explicit accidental (meaning typing B would give you Bb if a Bb existed earlier in the measure), I think I'd expect the "add interval" behavior to behave similarly. So if in that same situation I were to type D followed by shift-3, I'd get a note with no accidental: a Bb.

In reply to by lasconic

I don't expect a major third, no - I expect a *diatonic* third. Which is exactly what it currently does. If you're in the key of C and you've just entered a G, shift-3 should produce an E (which is a minor third), just as it does now. If you've just entered an A, then shift-3 should produce an F (which is a major third), just as it does now. If you're in the key of Bb, then hitting shift-3 after entering a G would produce an Eb (which is a major third), just as it does now. As far as I am concerned, nothing needs changing here except the behavior of the octave, which I think should be a true octave below the original pitch, even if that is not diatonic. In the key of C, shift-8 on a G# should enter a G#. In the key of Bb, shift-8 on an E natural should enter an E natural. It might seem inconsistent to special case the octave, but I do think it would match people's expectations better, and save keystrokes as I am constantly needing to adjust added octaves to make them true octaves.

Certainly understood about not changing basic note entry at this point, though - I was more thinking about how this play out in the future should such a change be considered.

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