Grand staff: Ottava on one staff shouldn't affect cross-staff notes displayed on other staff
The example shows two same passages with concert pitch and ottava notations. The ottava one will guide the player to play correctly as the concert pitch version, but Musescore lays the cross-staff notes an octave higher, and so does the braille transcription. As for braille transcription, We want a result with pitches in correct octave, so is there a way to detect and render cross-staff notes out of the ottava line without doing any fake things like hidden ottava lines for playback and visible line imitating ottava visually? Also, if there's an ottava line added on the other staff, Musescore should detect it and apply ottava correctly. I know the reason why Musescore plays incorrectly: the passage is in a single voice, and ottava line applies to the whole staff. I hope Musescore can exclude ottava from cross-staff notes, so that both sound and braille are correct, and Musescore will be the first notation software handling this correctly.
| Attachment | Size |
|---|---|
| Ottava.mscz | 7 KB |
Comments
There have been many discussion of this over the years and I'm surprised I can't find a bug report for it. The problem you point out is for everyone. The workaround is fine for sighted people but not so good for braille conversion so I think it should be major rather than critical. You at times have the patience of Jojo and don't want to have to stop your conversion because of these workarounds. I agree this should be fixed.
Work around, apply an ottava to individual affected chords. Make these ottavas invisible then add a visible line that looks like the ottava
Finally, here is a summary of what needs to be done. An ottava needs to affect only the notes written on the staff it is applied to without regard to if they are cross staff or not.
In reply to (No subject) by mike320
Of course, I'll not stop the braille conversion. I complain about this because lots of piano scores were input with only hidden notes for playback, not the way you and I said, so I have to be familiar with the score first and change the octave zone mark in braille when such wrong octave zones are met. Few people like you did this in correct way, and this had been included in our braille-specified engraving rules for quite a long time, from Sibelius to Musescore.
Stop was probably the wrong word. Your automation is stopped and you must intervene to manually let the conversion program know how to handle the workarounds like this.
In reply to Stop was probably the wrong… by mike320
Yes, I always do it manually, and if I occassionally miss some, these will become mistakes.
Changing the title to clarify that the ottava should affect notes on its own staff (regardless of whether the notes "belong" to that staff or are just displayed on it due to cross stave notation) but the ottava should not affect notes on the other staff (again, regardless of how they got there).