Impossible to remove natural accidental in cross-stave notation
In the snapshot shown below (harp music) I‘m using cross-stave notation for a left to right hand glissando. The music to the left is exactly the same as to the right with the exception cross-stave notation is used.
Now, while the notes can be changed, inserted or removed in both examples, it is not possible to remove a natural accidental (by selecting and pressing del). In the left example, however, the natural accidental can be removed by selecting the sign and pressing delete.
Moreover, sharp and flat accidental can be inserted and removed in both examples. However, while it's possible to insert a natural accidental in both examples, it can only be removed in the left case (select + delete), i.e. when cross-stave notation is not used. As a work-around, you can "remove" the natural accidental by selecting the note an move it up or downwards and then back again.
Is this a bug or an unintended design feature?
| Attachment | Size |
|---|---|
| CrossStaveNotation_accidentals.jpg | 60.19 KB |
Comments
Instead a picture, please attach the .mscz file, or simply the excerpt (these 5 measures): select them / Menu "File" / Save selection.
Ok, here it is. I thought it was so simple that a file isn't necessary. By the way, the part is copied out from the original score, but the anomaly is the same.
Ok, here it is. I thought it was so simple that a file isn't necessary. By the way, the part is copied out from the original score, but the anomaly is the same.
IMS OS details as follows:
Windows 11 Version 2009 or later, Arch.: x86_64,
MuseScore Studio version (64-bit): 4.5.2-251141402, revision: ac9d3bc
In reply to Ok, here it is. I thought… by TomStrand
La cancellazione dei ♮avviene rendendo ♭le note!
In reply to Ok, here it is. I thought… by TomStrand
Certainly it's possible to remove the natural: lower the note to the flat. Because the key signature has all those flats, there will be no accidental shown. Alternatively, you could raise the note to the sharp, but that will show the sharp accidental.
But if you want the note to be Bnatural (or whatever) then it must show the explicit natural because of the key signature. If your source shows no natural, then the note is supposed to be flat
In reply to Certainly it's possible to… by TheHutch
I know the use of accidentals . My question was more related to the fact that one can delete any type of accidental including a natural by selecting it and pressing delete. The only exception is for a natural when a cross-stave notation is used and only for the lower stave. Why?
In reply to I know the use of… by TomStrand
Why? Well, I think it's a regression. It works with version 3. With version 4, it's also possible up to version 4.3 (and 4.3.2, I think, I'll have to check again), but not from version 4.4 onwards.
You should report this on Github: https://github.com/musescore/MuseScore/issues
In reply to Why? Well, I think it's a… by cadiz1
It's not a regression. I found the same behavior in 3.6.2.
In reply to It's not a regression. I… by HildeK
Sorry, I disagree. In a score from scratch created with 3.6.2, I can completely remove the naturals in crosse-stave notation, which I can't do with 4.5.2 (and some earlier versions)
In reply to Sorry, I disagree. From a… by cadiz1
An example with this scenario:
In reply to An example with this… by cadiz1
I had not understood that you wanted to delete the accidental in order to explicitly change the pitch. Sorry.
I see the same behavior in 4.5.2 that your screen-cap shows in 4.4.4. I don't have 3.6.2 to try it there. The other four accidentals can be deleted in the same situation.
I note as well that, when I try to delete the accidental natural, the selection moves from the accidental to the note. This also happens when I (successfully) delete the others, but in those cases the accidental is successfully deleted. It's like someone left a line of code out.
In reply to An example with this… by cadiz1
You are right. I tested it with the file above and with 3.7.
Ok, thanks for the responses. I will report it on github later today.
In reply to Ok, thanks for the… by TomStrand
Thanks for: https://github.com/musescore/MuseScore/issues/28673
For the record, a fix has just been written...
In reply to Thanks for: https://github… by cadiz1
You are welcome. Yes, I saw that. Fix already planned for 3.6.
In reply to You are welcome. Yes, I saw… by TomStrand
Planned for 4.6 ;)