Cross-staff beaming bug
I found this bug when doing a complicated cross-staff beaming.
You can see it in the middle voice of beat 2, where the 32nd notes are in the upper staff, but the bars are in the wrong position.
| Attachment | Size |
|---|---|
| Screen Shot 2017-03-18 at 1.06.03 AM.png | 24.59 KB |
Comments
Welvome Frederic Chiu, could you attach here your score?
(attached with version 2.0.3)
In reply to Welvome Frederic Chiu, could by Shoichi
Attached is the section that had the problem.
In reply to Attached is the section that by Frederic Chiu
As someone else said, this isn't in 4/4 time and the selection is by default in 4/4 measures and MuseScore is very confused by it. If you open the score after you ignore the errors, you will see it looks very different than your screen shot. The best way to isolate a few measures is to select the measure before the selection press ctrl-shift-home and then ctrl-delete, then select the measure after the section and press ctrl-shift-end then ctrl-delete and then save as what is left. This will leave all of the time signature info in the score without changing measure breaks.
In reply to Attached is the section that by Frederic Chiu
The score is corrupt and MuseScore clearly states that when opening it, you'd have to explicitly ignore the corruption.
Check https://musescore.org/en/node/54721 on how to fix it.
In reply to Welvome Frederic Chiu, could by Shoichi
Sorry, trying attachment again - I "saved selection" the last time and didn't open it before attaching. I've now saved a copy, deleted the preceding and succeeding measures. You'll see two instances where the beams are going the wrong way in the attached excerpt.
Thank you!
In reply to Sorry, trying attachment by Frederic Chiu
'Save selection' is knwo to cause corruptions, when not in 4/4, see #99146: File > Save Selection… leads to corrupt score if selection is not 4/4 and does not start with time signature, fixed for the upcomming 2.1.
Ah, you mean the beams are wrong the wrong position, not the bars...
Double-click the beams and move down a tiny bit
In reply to Sorry, trying attachment by Frederic Chiu
Works perfectly
What MuseScore version and OS? It works OK for me in AppImage 2.0.3 on ubuntu . Looks to be in a compound time rather than 4/4 but I tried different time signatures with no change.
In reply to What MuseScore version and by underquark
Seems like the stems are flipped. Select the first note of the "wrong" looking notes and press "x".
This may only work if the position of the beams haven't been altered. Select the beam and reset position in the Navigator.
In reply to Seems like the stems are by musikai
The stems were flipped, and pressing "x' did the trick. This originally happened because of moving the later notes into the bass clef. Plus Strange that flipping the stems only affects the first three notes, and in this way. I think that flipping stems in this case should not have any effect. The way the first three notes react seems to be an anomaly.
Thank you for the solution!
In reply to The stems were flipped, and by Frederic Chiu
X only flips the notes in the same clef. This is a minor bug, so if you could isolate your score down to the measure with the bug showing and upload it, it would be appreciated.
I looked at the notes in question and all the notes attached with the beam and I noticed that the inspector said that the stem directions were auto no matter what I did with the x button. The beam direction changes from auto to down to up and alternates as you change each note rather than the stem directions changing as you would expect. If the stems moved as expected, then the beams would be in the proper position. I get the same results in 2.1 build 858a105.