Messed up 8th note connection bar across staves
I have a problem in the attached score, measure 76 on the piano (lowest 2 staves). The piano melody is the accompaniment for the vocals in the upper staves and is displayed in a smaller format. The problem occurs with the 4th note (high "la" ("A")) in the left hand, which should (according to the original printout) be moved to the upper stave (right hand). When trying to move that note (with shortcut ctrl-shift-arrowup or with the button on the menu), it gets all messed up with some parts of the connection being drawn (in both upper and lower staves) and some not. The notehead itself however remains in the lower stave. Futhermore, the move of the note doesn't persist. Whenever changing tabs or saving the score, the note returns back to the lower stave.
The shortcut and the button do work cause I've used them throughout several other scores. It's just this one that is messed up.
The attached screenshots show the current situation,
the messed up situation,
and finally what I want to achieve (done by drawing some manual lines for now).
The MuseScore file itself is also attached.
Attachment | Size |
---|---|
The Seal Lullaby - E. Whitacre, J.R. Kipling.mscz | 123.95 KB |
Comments
Bug confirmed, even after deleting all notes in both staves for m.76 and then re-entering the notes.
This bug is worth reporting on Github: https://github.com/musescore/MuseScore/issues
You will need to create a free Github account before you can generate a New Issue.
In reply to Bug confirmed, even after… by DanielR
Thank you for confirming. I'll make a post about the bug on Github.
Workaround:
a) notate the last three 8th notes in the lower stave, then make them all cross-staff
b) hide the whole-measure rest in the upper stave
In reply to Workaround: a) notate the… by DanielR
Thanks for trying. This does indeed work in all other files I tried to make. It's just in this specific one that it won't work. When moving the last 3 8th notes, the engraving turns to this:
All of the cross-staff notes get bugged.
The corresponding issue in github can be found here:
https://github.com/musescore/MuseScore/issues/19765
In reply to The corresponding issue in… by vlacatocc
Thank you for raising the issue - and I was delighted to see that MuseScore's engraving expert @oktophonie immediately accepted it as a serious bug. Posting on Github does get the problem into the right hands!