musescore / musescore/MuseScore

Changing pitches on a TAB staff can lead to incorrect notation on a linked standard staff

Open
#32,422 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

engraving P2
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

With notes in a tie chain:

  1. Select the first note on the TAB staff, enter note input mode and hit a number key to change the fretted note.
    RESULT: On the TAB staff the whole tie chain changes pitch, but on the standard staff only the first note changes pitch.

Selecting the first note on the standard staff and chromatically re-pitching causes the notes on the TAB staff to change as expected, and on the standard staff the whole tie chain changes pitch maintaining the incorrect interval contour.

Selecting the first note on the TAB staff and chromatically re-pitching causes the notes on the TAB staff to change as expected, but on the standard staff only the first note changes pitch. The following pitches in the tie chain are "picked up" when re-pitching across them.


There is also an issue attempting to change the fretted pitch on any other than the first note on a TAB staff. The corresponding note on the standard staff changes (causing a leap part-way through the tie chain), while the note(s) on the TAB staff do not change.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/ba3555f8-412c-44e5-aa66-69aaf336a6db


Attempting to change any other than the first fretted note:

https://github.com/user-attachments/assets/d867c082-0f1d-4d9b-a9e3-412eeda79053

In which versions of MuseScore Studio is this issue present?

4.0 - latest nightlies

Regression

No.

Operating system

Ubuntu 24.04.4 LTS

Additional context

No response

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.

Research direction

Reproduce the tie-chain cases described in the issue, using the attached videos as reference, and compare pitch changes between the TAB and linked standard staff. Done means changing the first or a later fretted note updates both staves consistently across the tie chain without an incorrect interval contour or mid-chain leap.

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
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.