how to eliminate double accidentals

• Oct 15, 2019 - 21:58

I'm working with no key signature. In transposing a passage chromatically, a lot of the notes get spelled with double sharps or double flats. Cycling through respellings with the J key does not get rid of the double accidentals without clicking on each note individually. How can I force respelling the passage so there are no double sharps or flats?


What method are you using to transpose? If you are using the Tools->Transpose menu, then there is an option at the bottom to never use double accidentals. No other method of transposition I can think of should result in double accidentals.

Perhaps you can attach a score and tell us what you are doing to get the double accidentals and we can come up with a better solution.

In reply to by mike320

That's a big DUH on me! Yep, down there at the bottom is what I need! But while we're having this conversation, the way Sibelius does its Transpose dialog, the last transpose choices made (e.g, chromatic down a minor third) are kept so that next time I use the Transpose tool those choices are still there. With musescore I have to select everything all over again. Just a suggestion...

In reply to by tmclint

MuseScore considers this a safeguard against accidentally transposing something. If the user presses enter or escape while making no adjustments to the transpose tool, nothing happens.

Though there are times when you are going to transpose different sections the same amount, it often possible to select the entire area at once and transpose several contiguous staves at once so why transpose 4 times if it's the same measures in 4 contiguous staves? It usually doesn't make sense to transpose only the 3 and 7th instruments. If this is what you are doing, there's probably a better way. If something like this is what you are doing, posting a score and explaining what your goal is will enable someone to help find the best way to do that.

In reply to by mike320

Musescore already has a safeguard against accidentally doing ANYTHING you didn't mean to do: it's called UNDO. At the very least it might be nice to let the user choose whether he/she/it wants to keep the last settings (in ANY dialog, for that matter) for use next time it's used.

In reply to by Marc Sabatella

This is just a comment (for once!). I'm slowly learning musescore after having used Sibelius for many years (and Finale for a few years before that). I've been too "busy" (read: lazy) to go through the handbook very much so far, but the more I use it the more I'm impressed by it and the more I think I ought to take the time. My experience with musescore 3 has been overall a very pleasant experience. I had tried earlier versions and while I could see potential in the program, it just wasn't quite there for me until version 3. Using Sibelius was not bad - it has a great sound library and it's generally friendly to use (but quirky), but it crashes more often than a non-free program should, and the only improvements they're making are obscure, rarely-needed ones. musescore on the other hand has never crashed on me (yet...) and you guys/gals not only listen and respond (politely!!) to our (my) whining, but you seem to constantly be making fixes and improvements that matter. So, wow! musescore and its programmers and support staff are pretty $*&#%ing awesome! Thank you for what you do and all the time you spend doing it!

  • Tom McLintock

In reply to by tmclint

As a frequent contributor to the forum, I thank you for the kink words. This is part of a culture of kindness and initiative I have continually experienced in the forums and talking to developers on telegram. Everyone I've met online has always been nice. The people who volunteer to work on the program also use the program, so the fixes tend to be what people actually use. When a user makes a proposal that a programmer agrees with, he tries to implement it. There is also a strong sense of wanting to keep the program from crashing or malfunctioning and many of the volunteer contributors will drop what they are doing to fix a crash.

MuseScore is a good community to be part of and your comments and questions (as well as everyone else) are always welcomed.

In addition, chromatic transpositions in a passage with no key signature generate a seemingly random mixture of sharped and flatted notes. In many cases, a C# (for example) is followed by a C natural followed by a C#, when a better choice would be for musescore to have transposed the passage to Db C Db. Cleaning up after each such transposition is tedious, where musescore could have done a much better job to begin with.

In reply to by tmclint

It shouldn't be random at all - if you choose a chromatic transposition option, MuseScore should be honoring the intervals in your original. So if it started with B Bb B, then a chromatic transposition up a major second is most definitely C# C C#, not Db C Db. If you had wanted that, you would need to have entered it a B A# B or Cb Bb Cb to begin with.

If that does clear up the confusion, please attach your score before the transposition and descirbe exactly what you are doing and what you feel MuseScore should be doing differently.

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