Cross staff notes retain top staff modifications
Reported version
3.0
Priority
P2 - Medium
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
Save me from my inability to title an issue.
Anyway, here's a picture.
The way that would be played is 8va on all the top staff notes, and regular on the bottom staff. Musescore 8vas all of it.
There is a huge amount of cross-staff problems, but I don't think this one is documented?
Workaround is fix-to-line the wrong notes, and knock them down an octave. Very time consuming.
| Attachment | Size |
|---|---|
| example.mscz | 7.95 KB |
Comments
I take it back, fix-to-line doesn't work, as it removes all accidentals.
Workaround is to unmark the moved notes for play and enter the notes in the bottom staff (in an unused voice) and make them invisible.
> There is a huge amount of cross-staff problems
I think a good few have been fixed recently. The beta version of MuseScore 3.1 released today includes these fixes.
As I recall, there was a report of this, with some discussion about what the expect behavior should be - including a comment from someone who actually corresponded with Elaine Gould on the subject. Bottom line is that this is considered ambiguous and to be avoided in writing, but probably we should indeed playback as requested here.
To be clear though - you are talking about playback only, right?
Indeed, there were lots of layout regressions involving cross-staff notes, but as far as I know they are all fixed for 3.1, along a couple of things that didn't work so well in 2.3.2 either. So overall we should be in better shape than ever with respect to cross-staff notation. There are, to be sure, some things that have always been issues, like no detection of collisions between "cross" and "native" notes on a staff.