Languages

Cross staff notation doesn't work, shows notes in wrong (origin) staff at wrong (same as target) position

• Apr 14, 2017 - 08:42

Reported version

3.0

Priority

P2 - Medium

Type

Functional

Severity

S3 - Major

Status

needs info

Regression

No

Workaround

Yes

Project

Tags

Came up in https://musescore.org/en/node/187716

See also #114141: Notes collide between cross-staff, which might be related, but shows different behavoir in 1.0 thru 2.1-RC

Reply

Comments

Anatoly-os

• Apr 5, 2018 - 09:06

Tags

Confirmed for 3.0.

dmitrio95

• Oct 22, 2018 - 08:28

Confirmed for 5ad448c

The file opens like this so that the first note of the second measure hides the bass note of the same pitch in the second staff.

Anatoly-os

• Nov 13, 2018 - 10:07

Priority		⇒	P2 - Medium
Regression		⇒	No
Workaround		⇒	No

• Mar 2, 2019 - 17:18

Priority	P2 - Medium	⇒	P1 - High
Tags	View Changes

Relates to #285233: [EPIC] Cross-staff notation issues

• Mar 21, 2019 - 06:37

Priority	P1 - High	⇒	P2 - Medium
Status	active	⇒	needs info
Workaround	No	⇒	Yes

I don't see any sense in which this is not just a duplicate of #114141: Notes collide between cross-staff, with the workaround of manually adjusting one of the notes to avoid the overlap. Is there something I am missing, or can we close this as a duplicate?