musescore / musescore/MuseScore

Text line hooks import wrongly from 3.x - 4.5.2 if line is below and hook down and at default length

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

@davidstephengrant is already working on this.

Since Jul 15, 2026.

engraving needs review 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

Open the attach score, created in 3.6.2
brackets.zip

It looks looks this in 3.6.2 and up to 4.5.2:
Image
Some lines (those in measure 2 and 6) have been manually moved further down via Inspector (and their y-offset), so they don't collide with the staff lines (in 3.6.2 and up to 4.5.2).

It looks like this in 4.6.1 (don't have a 4.6.0 PortableApp to test with) and later (4.7.4, as well as with current 4.7 and main branch):
Image
Notice the difference in measure 4. Also notice that the manual applied y-offsets are gone (and not needed, so that's OK)

Supporting files, videos and screenshots

see above

In which versions of MuseScore Studio is this issue present?

4.6.1 and later (can't test with 4.6.0). all versions up to 4.5.2 work

Regression

Yes, this used to work in a previous version of MuseScore 4.x (namely 4.5.2 and before)

Operating system

Windows 11, but that hardly matters

Additional context

Relates to #34164, in so far that it too most probably got introduced by be7505a (and with 4.6.0)

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.