Dealing with white-note accidentals within a single bar

• Sep 12, 2010 - 17:02

I've discovered something a little annoying about MuseScore's handling of accidentals like Cb, Fb, B# and E#. I've been working on a piece written in Bb major but which has an extended tonicization sans key change in Gb major, which of course contains Cb diatonically among its six flats. Naturally (no pun intended), there are long passages where C is flatted at the start of each measure and then of course should stay flatted until the next barline.

If you type C to begin entering the Cb, then use the down arrow to adjust the pitch, MuseScore of course moves the note to B as opposed to trying Cb first. This is all well and good and I understand why this is the default behavior-- in most situations, it would be ridiculous and counterintuitive to have to up-arrow through B# before getting to C, or down-arrow through Cb to get to B.

However, if you use the - shortcut to apply the needed flat, MuseScore applies an explicit accidental to *each and every* Cb in that register throughout the measure, the "next barline cancellation" rule be darned. I can sort of understand this behavior too, to an extent; the shortcut is intended to simply apply an explicit accidental as if being dragged from the palette by the user, not to cause MuseScore to consider the surrounding musical context.

Bottom line, though, is that this means each add'l Cb past the initial one in each measure must be Set Invisible. This is not only tedious to apply (especially without an available keyboard shortcut for Set Invisible), but has perceptible effects on score spacing, since MS is still leaving space in the score for all the hidden flats.

I guess I could just leave the Cbs "natural," but that would make playback sort of an unpleasant experience, and also negates the ability to export as MIDI or into another format.

Is there a workaround for this little issue that I'm missing?


Comments

Yes there is a workaround (Thanks to lasconic in another post).
Write the measure with C (natural). Then apply b (flat) from last to first C !! (click last C,blue, click b, click left cursor until next C, click b, and so on)

Greetings.

In reply to by Maximiliano

Somehow I missed this response or was never notified when you originally posted it; thank you (for the advice *and* the welcome), this *does* actually work. My question is, why does MuseScore consider context when moving backward, but not when moving forward?

I wouldn't recommend using "Set invisible" since it affects spacing (as you mentioned).

Instead, add all the Cb's for the measure, leave note entry mode, then select and delete each of the unnecessary flats using the delete key on the computer keyboard.

In reply to by David Bolton

Wow, that works, but it's incredibly counterintuitive. Shouldn't the deletion actually move the affected notes back to C naturals? (...although I've just verified that Sibelius 6 does exactly the same thing!)

I am also not convinced this would work on Macbooks, where there is no separate Delete key, and MuseScore usually treats the actual Delete key (where Backspace is on a PC) as Backspace. Doesn't affect me in my daily Windows use, but it would affect my Mac-happy students. I'm finding myself using the Cut operation a lot when testing things out on my Mac, because pressing Delete does nothing.

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