8vb Treble clef on TAB staff — and — TAB clef on standard staff
Reported version
3.6
Type
Graphical (UI)
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
Please see discussion here
UPDATE 2024-04-14: Here's Github issue report dated: 2023-11
Comments
workaround also mentioned there
Happens in MU4 too, basically any change to the clef in one staff changes the other, which I can't think would ever be expected/desired.
On saving the score with an errant clef the resulting .mscx file contains the following structure (as mentioned in the original post):
Seems inherent to linked staves:
{ Pid::CLEF_TYPE_CONCERT, true, "concertClefType", P_TYPE::CLEF_TYPE, DUMMY_QT_TR_NOOP("propertyName", "concert clef type") },
{ Pid::CLEF_TYPE_TRANSPOSING, true, "transposingClefType", P_TYPE::CLEF_TYPE, DUMMY_QT_TR_NOOP("propertyName", "transposing clef type") },
scorster
That isn't the bug. Guitar is octave transposing.
Hmm, maybe it is a bug, but certainly not the one causing this issue.
P.S. Was this ever transferred to github issues?
In reply to P.S. Was this ever… by worldwideweary
@worldwideweary
I think this covers it: https://github.com/musescore/MuseScore/issues/20180
BTW, I think MS4 was not yet released at the 04-14-2021 post date of this MS3 Issue Tracker topic.
Worth noting: Presently, in 2024, the behavior is extant in MS4.2.1
scorster
If so, it is fixed in 4.3.0 and a regression vs. 3.x