musescore / musescore/MuseScore

Automatic spacing allowing page with only one measure

Open
#18,135 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Other type of issue

Bug description

Could be viewed as feature or bug, but surely there is some way to set automatic spacing so that if it is calculating a way to fit measures before a page break in such a way that it decides it's okay to have a page with only 1 extremely wide measure on it, that it instead decides to fit that measure into the previous page if possible.

Right now, I encounter this issue often in situations where there is ample room to condense the 1-bar-1-page measure into the previous page in an aesthetically successful manner.

I have faith in the great assembled minds to find a way to implement this!

Steps to reproduce
  1. Create score with a bunch of music.
  2. Add a page break somewhere convenient for a page turn (this issue often happens when transposing an entire part) and later after some editing elsewhere the music will re-scale in such a way that it creates a 1-bar-1-page measure.
  3. Be dissatisfied with the result.
Screenshots/Screen recordings

No response

MuseScore Version

4.0

Regression

No.

Operating system

Windows 10

Additional context

No response

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.

Research direction

No files, tests, or entry points are named. Reproduce the issue in MuseScore 4.0 by adding a page break, editing music so a page contains one wide measure, and checking whether the measure can fit on the previous page without an aesthetically unsuccessful layout.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.