musescore / musescore/MuseScore

Chord symbols with triple or quadruple accidentals are not represented correctly after transposition

Open
#33,666 0 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

engraving 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

Chord symbols that end up with triple or quadruple accidentals (either in transposing parts or after using the Transpose tool) do not use the correct musical glyphs to represent the accidentals.

Some examples:

  • F triple-sharp becomes FF
  • B triple-flat becomes BB

Double-clicking such a chord and confirming the input causes such a chord to be drawn correctly. Following this, going back to concert pitch causes similar problems (double-flats may use two individual flat glyphs instead of the dedicated double-flat, etc.).

While triple/quadruple accidentals in chord symbols should usually be avoided, misrepresenting these chord symbols makes it more difficult to understand what is going on if you happen to make a questionable transposition.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/148e3970-e32e-4845-ab4c-801c600ae0f4

https://github.com/user-attachments/assets/974e51fc-f793-4492-b06f-d988dfc104fa

In which versions of MuseScore Studio is this issue present?

4.7.x - latest main

Regression

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

Operating system

Ubuntu 24.04.4 LTS

Additional context

Consider forcibly respelling chord symbols exceeding double accidentals. This appears to have been the behaviour in 4.6.5, although any respelling occurring when switching from concert to transposed pitch would permanently change the spelling also for concert pitch representation.

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.