Accidental accidentals
It is annoying when I place several of the same note (key, not length) in a measure and then I want to put an accidental on one note. The notes don't necessarily have to be consecutive. Musescore automatically places naturals on the other notes. I understand why it does it, but is there a setting in Musescore that tells it not to do that with subsequent notes in the same measure? I know there is a courtesy accidental setting, but these are not courtesy accidentals.
Thanks
Comments
according what you want .......say you have , in the same measure 3 C, you change the first for C# by using up arrow . If you want the 2 others C don't change , the natural sign is necessary, and Musescore put the natural sign on the first C after the C#.
If you want the 3 C become C#, select the 3 (with using Ctrl) and up arrow, the 3 C change for C#, and only the first get a sharp, the 2 others are also C# but without the sharp written
if you want first C change to C#, the 2 after don't change , and not have natural sign on them, it's impossible (perhaps in making them invisible) but a musician , if in a measure there is 3 C and the first , only, with sharp, play the 3 C like C#, it's the rule
In reply to according what you want … by Raymond Wicquart
Thank you. I will use the Ctrl + Up solution you mentioned. I was just hoping there was a setting that would do it for you automatically.
To be clear, the reason the naturals are there is because you didn't change their pitch, you only changed the pitch of the one note. So the solution is to be sure to change the pitch of all of them. So, you could ctrl+click them all then hit Up to raise their pitch. Or use something like Select / All Similar Elements / Same pitch + In selection to select all notes of that pitch within a selected measure. Former is probably easier if it's just a couple of notes and it's easy to see them, latter if it's a long complex measure and you're worrying about missing something.
Probably someone could write a plugin to do this job automatically.
In reply to To be clear, the reason the… by Marc Sabatella
Thank you. Yes, I know why Musescore is doing it (because I didn't change the pitch) but I was hoping there was a setting that would stop it from doing that. I will use your solution - faster than my manual solution. It would be nice if someone would write a plugin to handle that.