Alignment issue when beaming across 2 staves and with 2 parts

• Nov 22, 2019 - 10:50

I have two parts on the bass clef piano stave, which play a unison on the first note of the bar.
The upper of these parts has one note which I want to be placed on the treble stave because it's played by the right hand, but I want to preserve the beaming. This works fine with a single part (see 2nd bar, where the G is where I want it).
G on lower staff.png
However, when I use shift+ctrl+uparrow to move the G up, the alignment of the unison isn't adjusted with horizontal displacement, and instead the unison notes are piled on top of each other.
G on upper staff.png

It's the same result if I put the three quavers in the treble staff then move the first two down to the bass clef staff - the Gs get piled up.
I have tried changing the horizontal alignment with F8, but this is really longwinded because the note and the augmentation dot have to be moved separately, and I have a large number of bars where this needs to happen.

Is there a work around for this, or will I have to write it with the G not beamed?


Comments

I don't have a solution to the fundamental failure of automatic collision avoidance, but I think when you are changing the horizontal alignment you are adjusting the X offset of the note head Element, rather than the offset of the Chord (lower down in the Inspector). If you adjust the chord's offset the dot should move with the note head. The adjustments for elements allow one to adjust the location of each element of a note or chord (individual note head, stem, flags and dot) separately. The adjustments for chords moves the whole thing, note head(s), stem, flags and dots together.

Within MuseScore the term chord refers to a group of notes in the same voice that sound together and have the same duration which is pretty much standard terminology, but with the added wrinkle that a chord may consist of just a single note.

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