musescore / musescore/MuseScore

Apply staff style properties on a system/page level

Open
#23,905 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

Your idea

I was referring to a feature that allows changing specific sizes, such as Staff space or Page settings, for each page. For example, if the default Page setting has the Staff size set to 0.059 inches, I want to change it to 0.048 inches for other pages within the same score. As far as I understand, in MuseScore 4, it seems that it's not possible to change the Staff space individually for each page within a single score. Please correct me if I'm wrong.

Problem to be solved

Additionally, using the "Insert staff type change" in the Layer palettes allows for a similar function, but it takes an excessive amount of time, especially after notating modern scores. Moreover, there are numerous errors that occur when using the Staff type changer. Therefore, I would greatly appreciate an update that allows independent setting changes for each page or staff, similar to the feature in Finale.

Prior art

.

Additional context

.

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

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

Start by examining the existing Page settings and the “Insert staff type change” entry in the Layer palettes described in the issue. Define how staff-space and other page properties should vary independently within one score, then verify that the new behavior avoids the reported staff type changer errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
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.