musescore / musescore/MuseScore

MS4.7 nightly: Fret number and Stem misalignments in tablature when tablature Staff Type is set to “Tab. 6-str Common”

Open
#32,892 2 comments 1 reaction 2 assignees View on GitHub

Nobody has claimed this yet.

engraving P3 regression MS4
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

ISSUE: Horizontal misalignments of stems and fret numbers occur on the TAB staff when "Tab. 6-str Common" staff type is combined with reversed or illogical voicing choices, for instance Melody in Voice 2 and Bass notes in Voice 1. Such misalignments didn't happen in MS3.6 or before MS 4.4.0 under the same circumstances.

Steps to REPLICATE:

  1. New>Solo>Guitar+Tablature

  2. Set Staff Type of the tablature staff to "Tab. 6-str Common"

  3. Enter notes in voice 1 and voice 2 as shown in the example score. (No misalignment occurs)

  4. Paste measure 1 into measure 2. Then Exchange Voices 1-2 (Misalignment occurs)

  5. Paste Measure 2 into Measure 3. Then press x to flip stems. (Misalignment persists.)

Excellent commentary by Cadiz1 here on .org

You'll find my example score there as well:

https://musescore.org/en/node/390678#comment-1326200

Supporting files, videos and screenshots

The example score shows the issue clearly.

In which versions of MuseScore Studio is this issue present?

Regression occurred version in 4.4.0. No problem in 4.3.2.

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Mac OS 26 Tahoe

Additional context

Granted the user should use logical choices for voicing, but MuseScores used to properly align tablature fret numbers and stem even when voices 1 and 2 were swapped.

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.