musescore / musescore/MuseScore

Inconsistent tie placement with chord brackets/arpeggio lines and multiple voices

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

@miiizen is already working on this.

Since Jun 23, 2026.

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

Thank you for implementing chord brackets! I've noticed some strange behaviour though when writing chords with ties that are supposed to cross a bracket. Steps to reproduce my example (Example A) are below. Also, I got the same results when using a squiggly arpeggio line instead of one of the new chord brackets (see Example B).

  1. Create two tied notes such as in the first bar in Example A below.
  2. Add a chord bracket and extend it up-/downwards to make it cross the tie.
  3. Add another note in a different voice such as in the second bar in Example A.

Expected behaviour: No change to the tie placement.
Actual behaviour: Tie no longer crosses the chord bracket with the additional bass note.

Supporting files, videos and screenshots

Example A:

Image

Example B:

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

4.7.3

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.