musescore / musescore/MuseScore
Tablature staff mismatch occurs after Instrument change
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
UX/Interaction bug (incorrect behaviour)
Bug description
Tablature staff mismatch occurs after making an Instrument change on linked tablature system.
Steps to reproduce
New Score>Guitar + Tablature
As expected the Instrument properties are (for the upper and lowers staves respectively:
• Treble clef 8va bassa
• LINK [Tablature]
Toggle open Instruments>Guitar
Click the Guitar settings icon
Click the Replace button
Choose: Ukulele
Normal result (and the state of the attached score): The Instrument is now named Ukulele and attains the ukulele tuning data.
Unexpected result:
• the staff is still Treble clef 8va bassa but should be a regular Treble Clef staff
• Staff/Part Properties>Staff Properties>Lines should be 4 but is still 6.
Remedy: Set Lines = 4
• Prior to the last step, click the LINK [Tablature] setting button the see that the Staff Type is undefined.
Remedy: Choose Tab. 4 str. simple
• Also note that the ukulele tablature staff can't accept notes below Middle C; nor can the user drag tablature
"notes" to the lower 3 strings.
Recommendation: When changing Instruments on a linked tablature staff, as from Guitar to Ukulele,
rather than leaving the 6-string TAB staff it would be more elegant and
logical if MuseScore also set Staff Type to Tab. 4 str. simple as previously it was Tab. 6 str. simple.
(In kind, if it was previously set to Tab. 6 str. common update it to Tab. 4 str. common).
Screenshots/Screen recordings
These settings are seen after changing a Guitar Instrument to Ukulele starting, as described above, starting with a solo Guitar + Tablature template. (Maybe there's a reason, but I don't see why such conflicting values should ever be allowed.)
MuseScore Version
4.2.1
Regression
In MuseScore 3.6.2 there was a similar issue
Operating system
MacOS 13.5.2
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Guitar-to-Ukulele replacement using the attached Changing Instrument on linked TAB staff.mscz.zip and the steps in the report. Check the resulting clef, line count, and linked staff type against the instrument's tuning data. Done when linked tablature updates to the matching four-string ukulele staff settings without the reported note and drag limitations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100