Can add same note to chord many times
In both 1.0 and the nightly, when entering notes into a chord you can add the same notes repeatedly. Not only does this seem strange to be able to do, but it messes up the note head alignment. So I can create the quarter note F, (above middle C) then add AC to the chord, then add a B, then another A, now the B and C have exchanged positions. It just gets weirder if you continue doing this. Add a CDC to the chord to see what I mean.
Also, in the nightly, half the time while simply doing the above procedure and either undoing or removing/adding notes to the chord, MS crashes hard.
Comments
Possible duplicate of this?
#8119: Disallow a note to be placed onto another
Not quite, because when you do it the shift-add way, the note heads for one note are all layered on top of each other.
For me, this is a feature. If I want to add a chord C and C one octave higher, I enter C, Shift + C and Ctrl + Up. And so, I do want MuseScore to enter the second C.
I understand some of the usefulness, but it's far too easy to create problems in its present form, accidentally overlaying several notes, causing the most awful looking chord and not knowing later where the mistake was made. Therefore I don't agree that its a minor issue. When you overlay several of the same notes, not only is there no indication you have done this (through the use of a note collision color) but when you select an overlayed note, there's no note color at all.
The mouse entry system does not allow this type of thing at all. In fact, it will remove the duplicate note. It would be better if, when you selected notes to add to a chord, some checks were made to see if a collision is about to happen and adjust the note accordingly, either by moving it an octave up/down, placing it on another unused note, or giving an error beep indicating an action that you can't do.
Moving notes in a chord should also be subject to those same rules. Once a collision is about to happen, skip up/down to the next unused note.
To show just how strange things can get: start a new score, drop a quarter onto E, down arrow to make it an Eb, then lay an E overtop the Eb. Now where's the E? Should it not be visible somehow since the heads are colliding? Now, take the E and down-arrow it down to the Eb and the b will disappear from the dsplay. Reload the score and its back but the E is still being covered.
You also have to remember that there are many instruments which can play notes in unison.
The guitar is one - it is possible to play 3 E's of the pitch of the first string at once, and sometimes you need to show this in the same voice.
So rather than regarding the entry of unisons as a feature, I regard it as an essential part of music engraving software.
Maybe the answer here is for MuseScore to shift the 2nd unison notehead to the other side of the stem. This would certainly make it easier to select.
I understand the unison note requirements. Simply put, one should never be able to stack the same note without having them display differently.
I see now in 2.0 that there is no simple way to enter stacked notes except by adding a different one and manually adjusting the pitch with the up/down arrows to where you want. Attempting to add a note that already exists to a chord will toggle that note instead.
IN actual fact you can still add a unison it's just that the key shortcut has changed to ALT+1.
MuseScore still positions the note on top of the other, however, whereas conventional engraving rules require unison notes to be on opposite sides of the same stem.
It appears to be now impossible to add a unison in the same voice unless you use ALT+1 to do so, and so is unlikely to be done accidentally.
Given that this is the case I suggest that this issue is now fixed and am marking accordingly.
Personally I would like to see an automatic filp of the notehead to the other side of the stem, but as you would know you had done this, following the operation by SHIFT+X is not too burdensome.
Please feel free to change to active if you disagree.
Automatically closed -- issue fixed for 2 weeks with no activity.
Still not fixed in 1.3. When will 2.0 come out?
"When it's ready" is always the standard answer. Still plenty of bugs left to fix.
BTW, the behavior in 2.0 will be, pressing Shift+letter to add a second note of the same pitch will result in the new note automatically mirrored to the "wrong" side of the stem. This is the desired behavior in most of the situations where you might actually want to enter duplicates, and it has the advantage that it will make it obvious if you do this inadvertently.