musescore / musescore/MuseScore

Can't hide courtesy key signature

Open
#31,044 3 comments 0 reactions 1 assignee View on GitHub

@ajuncosa is already working on this.

Since Aug 11, 2026.

P2 regression MS4 UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

Firstly, I'm not sure which type of issue is this, could be UX/Interaction bug or Engraving bug. It's probably Interaction bug. The recent addition of "courtesy key signature" isn't able to hide after saving (I specifically saved mine in the cloud. In this situation I used the following:

  1. Use D.S al Coda
  2. Add "To Coda"
  3. The Coda (with the coda symbol) section has different key signature (which is correct in this case)
  4. Hide the "To Coda" courtesy key signature in the brackets
  5. Save the score
  6. Reopen the score, it'll come back as visible.
Image
Supporting files, videos and screenshots

Sheet score sample measure #68
https://musescore.com/user/69102031/scores/28954763/s/JA_tbT

In which versions of MuseScore Studio is this issue present?

4.6.3

Regression

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

Operating system

macOS 26 Tahoe

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.