In cross staff notation, voice 2 overlaps voice1
Reported version
3.1
Type
Functional
Frequency
Many
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
1) Load this test file: test.mscz
2) Toggle the two last eighth notes in second staff
Expected result (as in version 2.3.2):
Current result:
(I have not yet look at precisely, but I note it worked at the beginning of version 3, Junuary 2019)
- Reported first in French forum: https://musescore.org/fr/node/309680#comment-1022039
Comments
What is the workaround?
I note a change on May 22, 2019
Maybe a side effect of this commit ? : https://github.com/musescore/MuseScore/commit/f2073afc57bf94d2040e18709…
To fix : #289498: [Regression] Bad layout of beam in presence of cross-staff beam in another voice
So that issue got to exist since 3.1 or even 3.1rc
Relates to #285233: [EPIC] Cross-staff notation issues
I can totally believe that commit broke this while fixing other things that needed fixing. Unfortunately the layout algorithm is has lots of independence and we can't always know the info we want when we need it, so sometimes the algoierithm makes guess and tries to correct later, with some things just not possible to correct. Not saying there is no solution here, but it's quite possible the only one that doesn't break other things also would require a major rewrite of the layout algorithms.
For reference, and showing another example, it came up two days ago here: https://musescore.org/en/node/316798
See also #114141: Notes collide between cross-staff. And my comment in https://musescore.org/en/node/289498#comment-920720. As seen there, we've always had an inconsistent story regarding collisions in cross-staff notation, with some things very broken (meaning, not just possible to correct via a simple manual adjustment). Fewer things are broken now, and things are also more consistent overall. But that does mean that some things that we once at least tried (albeit often unsuccessfully) to avoid, we now no longer try to.
See https://github.com/musescore/MuseScore/issues/20104
Allegedly fixed in 4.2
Automatically closed -- issue fixed for 2 weeks with no activity.