musescore / musescore/MuseScore

Copy score layout from part to part

Open
#17,203 0 comments 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

MU4 has greatly improved at the level of automatic layout. Nevertheless, making and tweaking the layout of a part up to the editor's expectation can be time consuming.
In some occasions, the layout of one part would be identical or quasi-similar to another one (e.g. several lead instruments in a jazz pieces, instruments belonging to the same family, ...) and it should be therefore useful to copy the layout of one part to one or several other staves.

The copy of the layout from one part to another part would imply copying:
  • page/line breaks,
  • customised frame margins
  • elements offsets
  • text options such as position, font, bold face, ... (the purpose is not to make a separate text style for every texts)
Screen example (from Dorico's Propagate Part Formatting function):

Dorico Propagate parts

Problem to be solved

Ease the layout of a multi-part score

Prior art

Example from Finale:
https://youtu.be/LTrQd6miAgM

Example from Dorico:
See above screenshot

Additional context

See discussion Copy Part Layout (2023)
See discussion Propagation of the layout of parts (2017)

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

Review the issue’s requested layout elements and the linked MuseScore discussions before defining the scope. Compare the described behavior with the Dorico and Finale examples. Done should let users copy page and line breaks, frame margins, element offsets, and text options from one part to one or more other staves.

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.