musescore / musescore/MuseScore

Notehead parentheses property may become unsynchronised between score and parts

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

@miiizen is already working on this.

Since Mar 2, 2026.

  • #32447 by @miiizen — merged
UX/interaction
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. Create a new score with an instrument, and add a note with parentheses.
  2. Switch to the part.
    RESULT: The parentheses are drawn, but the note parentheses property is showing "Normal notehead". Clicking this button makes no change. Clicking the "Notehead with parentheses" button causes no visible change in the score, but the style/appearance of the note is now no longer synchronizing with the score.
  3. Finally, click "Normal notehead" and switch back to the score.
    RESULT: The note is drawing without parentheses, but the note parentheses property shows "Notehead with parentheses.
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/4f70b41e-702b-4335-8df4-7bf659301f5a

In which versions of MuseScore Studio is this issue present?

4.7 nightly

Regression

Yes, this works in the latest released version and is broken in the nightly builds

Operating system

Ubuntu 24.04.4 LTS

Additional context

Found while testing #32379. See also #32420.

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.