musescore / musescore/MuseScore

"A due" (a2, a3 etc.) or part numbers - duplication on new systems

Open
#21,701 1 comment 0 reactions 2 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 propose to create automatic duplication of part numbers on subsequent systems.
Снимок экрана (119)

Problem to be solved

This will allow the players (or the conductor) to better navigate the process of performing the composition and understand how many players (or which ones) sound on this system.
At the moment, you can only duplicate text in Musescore systems manually. Of course, you can tell me: why don't you do this - manually register each digit in parentheses on each system? I will answer: firstly, it is long and tedious. Secondly, during the process of editing the score, there may be changes in the layout and the system will be divided in another place. And do I have to constantly change the location of the part numbers after that? It seems too dreary.
In Musescore 3, there was an alternative method: add part numbers in the form of a staff line and make the line itself invisible. Currently, such manipulations are not available in Musescore 4. The lines staff cannot be hidden without text (you can only make the line completely invisible, including the text itself).
I suggest creating a special text in Musescore 4 designed for marking parts. And for this, I do not recommend using the staff line, as the line can be visually confusing when editing.

Prior art

No response

Additional context

It is very important to take into account that the numbers should be in close proximity to the notes, but not in any case within the staff!
Снимок экрана (163)
Снимок экрана (164)
Снимок экрана (165)

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.