Secondary brace from Emmentaler or Gonville is too far to the left and collides with the instrument names

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

@davidstephengrant is already working on this.

Since Sep 1, 2026.

Assessment

This issue has not been assessed yet.

Description

engraving needs review P2
Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce
  1. Create a score,
  2. Add 2 instruments, 3 staves, like Flute and Piano
  3. Apply a brace to the flute (not strictly needed)
  4. Apply a secondary brace to all 3 staves
  5. Make sure that is on row 1 (or higher), while the others are in row 0
  6. Change Musical Symbols Font to Emmentaler or Gonville

or

  1. Take the attached score (created in 3.6.2)
Supporting files, videos and screenshots

Her's how it looks:
Image

Herr's a sample score (created with MuseScore 3.6.2):
emmentaler-brace.zip

In which versions of MuseScore Studio is this issue present?

All versions as far as I can tell, at least 3.6.2 up to the currently latest, 4.7.4

Regression

No.

Operating system

Windows 11, but that hardly matters

Additional context

For Emmentaler and Gonville the braces are 'hand drawn', not taken from the font, nor falling back to Bravura, like for all other fonts.

This is also why Emmentaler and Gonville are the only fonts that react on Format > Style > System > System Brackets > Brace thickness

The issues magically iresolves if there's a 4th staff... Or just 2...

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
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

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.

More from musescore/MuseScore

All issues in musescore/MuseScore

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.