musescore / musescore/MuseScore

Fretboard diagrams don't respect the setting for Chord symbols Capo fret position

Open
#34,158 0 comments 0 reactions 1 assignee View on GitHub

@davidstephengrant is already working on this.

Since Jul 11, 2026.

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
  1. Input a chord symbol, eg. C
  2. Add a chord diagram for the created chord symbol
  3. Go to Style settings > Chord symbols > Capo
  4. Set Capo: Show transposed symbols only (not relevant to bug, but helps observe the effect)
  5. Set Capo fret position: 1

Observed behavior: The chord symbol is correctly shown as B, but the chord diagram still represents the original C chord instead of the transposed B chord.

Expected behavior: The fretboard diagram should always represent the transposed chord, not the original chord.

Note: there's no difference whether you add the fretboard diagram to a chord symbol before or after adjusting capo settings, the result is the same in either case.

Supporting files, videos and screenshots

Bug: "C" chord with Capo fret position = 1, correctly showing "B" as the transposed chord symbol, but incorrectly showing the fretboard diagram for the "C" chord instead of "B".
Image

Expected behavior: "C" chord with Capo fret position = 1, showing "B" as the transposed chord symbol, showing the fretboard diagram for the capoed "B" chord.
Image

In which versions of MuseScore Studio is this issue present?

4.7.4

Regression

No.

Operating system

Windows 11

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.