Disallow a note to be placed onto another
1. Create piano score.
2. Enter a C and D note chord.
3. Move either one of them on top of each other.
Desired behaviour: If moved by keyboard, the note should go to the next space/line. If it's being dragged, the occupied note should be greyed out if you hover over it.
Actual behaviour: The note is placeable on top of it. Applying an accidental to it will produce a cluster upon playback (because of the remaining natural note underlying).
Using 0.9.6.3 and Mac 10.4.11.
Comments
Actually, I don't know that it should really be disallowed like that, but rather it should be changed to be noticeably two different notes. There could be situations where you would want to have both notes there.
I do not know what is standard notation practice, but observe in the picture what occurs when you make a B# and Bb at the same time on Finale. I believe Sibelius does similarly.
MuseScore shouldn't skip over the note or grey out. It just needs to place one of the note heads on the opposite side of the stem so that you can tell that there are two notes (see "Capture1.PNG" attached).
The Music Publishers' Association of the United States recommends something like "Capture2.PNG" when the two note heads require different accidentals ("Standard Music Notation Practice", MPA, page 8). But I have never seen this so I assume it is pretty rare. Finale and Sibelius do not bother to create diagonal stems for these situations (at least not by default).
I did think of that, but I wasn't aware you could do that in notation. Thanks for letting me know.
I think if that's the case, we could propose that you should only be allowed to place the same note if there's an accidental there already.
Thanks David. If the second diagram is the generally correct way, then we could go for that. What could happen is, when you click on the same note, it generates the diagonal stems. If you delete one of the notes, it just goes back to the normal vertical stem.
Here's the original discussion .
I recommend the opposite side of the stem even for unison notes (rather than disallowing it). It would allow you to create the two unisons and then drag the accidentals afterward instead of having to strictly add an accidental first (for mouse based users).
I'll trust your judgement David :)
What do you want to do with the issue now? Do you want to create another with what you've recommended?
It would hopefully help towards avoiding situations like in the image (notes in a treble clef: E♭, F, F♯ and G).
Is cluster shown in #8 a bug?
There are also instruments which are capable of playing two unison notes simultaneously - the guitar immediately springs to mind, and most stringed instruments will be the same.
One needs, therefore, to be able to add at least two unison notes to the same chord. These are usually notated one on either side of the stem.
Unison notes in a chord are not uncommon in guitar music, particularly in Flamenco music.
It is actually possible to play 3 unisons on some notes of the guitar, although you have to stretch the hand in order to do it. How you would notate this I have no idea unless you laid the 3 notes out touching horizontally with the stem attached to the centre head.
I think here we are discussing 2 things:
(1) UNISON notes (e.g. D + D).
(2) Bitonal clashes (e.g. D# + Db).
For (1) I'd suggest a new "unison notehead", because the current convention of deleting a note by clicking it is quite cool.
For (2), I already posted an issue: #14449: Bitonal chords (eg. G# plus Gb)
I close this for the sake of unison notes.
Please post if you disagree.