musescore / musescore/MuseScore

Parts incorrectly get chord symbol style settings set for Score

Open
#32,260 2 comments 0 reactions 1 assignee View on GitHub

@miiizen is already working on this.

Since Feb 20, 2026.

engraving P3 parts
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

I write a lot of scores for my band using a template I've developed, and a style I use for each part.
Whenever I apply the style to each part, the chords are formatted the way I want, but if I ever close the score and reopen, the chords are incorrectly formatted. When that happens I can sometimes get what I want by reloading the style file, but sometimes I have to go chord-by-chord and retype them. This has led to many wasted hours re-engraving.

  1. Load attached Test Score, or create new score from attached template
  2. Open Guitar Part
  3. Apply attached Test Style
  4. See chord format (see "Correct")
  5. Close Score
  6. Reopen
  7. Open Guitar Part
  8. See chord format (see "Incorrect")
Supporting files, videos and screenshots

Template_Score_Style.zip

Correct:
Image
Incorrect:
Image
In which versions of MuseScore Studio is this issue present?

4.6.5

Regression

I was unable to check

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.