musescore / musescore/MuseScore

Vertical space is given to invisible notes outside the staff

Open
#29,455 2 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

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

Engraving prevents staves to overlap space where invisible ledger lines are.
How to reproduce:

  1. Create two staves
  2. Create an invisible note with considerable ledger lines between the staves
  3. Algorithm will not use the space occupied by invisible ledger lines

Expected behaviour:
Algorithm should use the space occupied by invisible ledger lines for other information.

Supporting files, videos and screenshots

Close-up:
Image

Close-up in print layout:
Image

Expected outcome in print layout:
Image

What is the latest version of MuseScore Studio where this issue is present?

MuseScore Studio version (64-bit): 4.5.2-251141402, revision: github-musescore-musescore-ac9d3bc

Regression

I was unable to check

Operating system

OS: Windows 11 Pro Version 24H2 build 26100.4946, Arch.: x86_64 (x64)

Additional context

This is not just the notehead. Offsetting the notehead to staff lines keeps the ledger lines and the unused space, although this might not be true if the offset only moves the rendered position of the notehead and not the actual position.

This is hackable using a fixed staff spacer.

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.