Ottava notes from music staff do not translate correctly to linked tablature

• Aug 18, 2014 - 22:37
P1 - High
S5 - Suggestion

1. Open attached score (produced in 2.0).
2. 'Instruments…'.
3. Change 'Staff type' to tablature.
4. 'OK'.

Result: The ottava is ported.

Ottava ports to tablature.png

Using MuseScore 2.0 Nightly Build (6377816) - Mac 10.7.5.


The end result of the expected behavior is easy enough to describe: ottavas should not be included on tab staves, period. An ottava on a standard staff means a note is being displayed on the staff an octave (or two) lower (or higher) than the actual intended pitch. On a tab staff, you'd never do that - you'd simply display the appropriate fret/string for the actual intended pitch.

This means that when copying from a standard staff to a tab staff, the effect of the ottava must be taken into account in calculating the tab representation, but the ottava itself should not be copied. And the same must be true for the "copying" that occurs with linked staves, both when initially cloning the staff and when adding elements to either staff later. The ottava itself should not be copied, and the notes should be copied according their intended playback pitch, not the written pitch.

It's probably especially tricky to get right when copying from a tab to a standard staff if there is already an ottava in effect on the standard staff - the code would have to look for ottavas and make the adjustment before copying the note.

I am working on this.

The last comment by Marc (copying into a standard staff which already has ottavas) would apply to the best of possible worlds, but it is currently not implemented even when copying between standard staves: if the destination staff already has ottavas, they are not taken into account when filling with the notes copied from another staff (of whatever kind). I think I'll leave this as it is.

For the other aspects, I'm going along the following guide lines:

1) Dropping an ottava onto a TAB staff is simply ignored: no effect whatsoever.

2) Dropping an ottava onto a standard staff linked to a TAB staff: the TAB notes are shifted by appropriate number of semitones and the ottava itself is discarded.

3) Copying from a standard staff a selection containing ottavas onto a TAB staff (not linked): same as above.

I have already implemented the above; I still have issues with undoing 2) and when, in the linked standard staff, the ottava span is changed or the ottava removed altogether: in all these cases, the TAB staff is not notified of the changes in the notes of the standard staff linked to it.

I'll see what can be done.

Ah, good point about results in standard staves not being as one might expect either.

I had this on my "hit list" because I think we need to have a better story than we do now. But I can live with things not being perfect.

Status (old) active needs info

As always, please provide *precise* steps to reproduce, from scratch (score created in older builds won't necessarily be valid). I just tried a simple example and it worked as expected.

Status (old) needs info active

You are quite right - it doesn't appear if applied when a linked stave is present beforehand.

1. Create standard guitar score.
2. Enable 'Note input'.
3. Enter notes.
4. Disable 'Note input'.
5. Drag ottava to notes.
6. 'Edit'>'Instruments…'.
7. Click on stave.
8. 'Add Linked Stave'.
9. Change 'Staff type' to 'Tab. 6-str. full'.
10. 'OK'.

Result: Ottava appears on tablature stave.

Using MuseScore 2.0 Nightly Build 64cfc85 - Mac 10.7.5.

In addition, I doubt the solution A) which has been merged could deal with changing a standard staff into a TAB, without extensively parsing the whole staff and rewriting all the involved notes; for sure, there would be no way to get back from TAB to standard and get the original ottavas back.

I had the general feeling that A) was a much harder way to implement (or better de-implement) ottava management in TAB. I know that solution B) was tricky, but it would have taken into account the point at #10 and the points described above automatically.

Severity S1 - Blocker
Reported version 2.1  
Regression No
Workaround No

Is this still not solved? The attached screenshot has been just made with 3.0.5
8a tab.png

Attachment Size
8a tab.png 8.11 KB
Severity S1 - Blocker S3 - Major
Workaround No Yes
Priority P1 - High

Apparently no change, s9 continue to use the workaround of marking it invisible.

Good point! So instead, maybe notate the tab correctly, then use the "Fix to line" on the standard staff notes in the Inspector to force them to appear in the desired octave.

Title Ottava ports to tablature Ottava notes from music staff do not translate correctly to linked tablature
Frequency Many