musescore / musescore/MuseScore

Unnecessary vertically spacing in continuous view

Open
#31,348 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

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

Sorry for the bad title, not sure how to word it. I've seen it mentioned on the reddit a few times but didn't find a bug report here.

Sometimes - but only sometimes - any addition to the score will cause unnecessary vertical padding when in continuous view. Spacing returns to normal when I save. This happened in the previous version and still happens after the latest update.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/fcefb749-b136-4665-9a6b-580097890a36

The file in which it's currently happening, but it's sometimes happened in other scores as well

Christmas_Triptych2.zip

In which versions of MuseScore Studio is this issue present?

(64-bit): 4.6.4-253351238, revision: github-musescore-musescore-8af129b

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Windows 10 Version 22H2 or later

Additional context

Apologies for the unclear reproduction steps and if I missed an already existing report

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.