musescore / musescore/MuseScore
G.P. [Generalpause]
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Your idea
I propose to implement the option of automatically specifying the designation G.P. in the event that the entire ensemble is silent, and make it [option] by default.
I suggest using bold italic font for this designation in order to visually distinguish it [designation] from a tempo designation that may be nearby.
In the full score of the ensemble, such designations are duplicated in the same way as tempo ones (and all system objects are currently in MuseScore Studio), but they are aligned in the center of the rest/multimeasure rest (the latter may be in the full score, but more on that below).
G.P. is indicated only if the entire ensemble is silent for at least a bar.
If it is one bar, then the G.P. is placed above the staff. But if it's a multimeasure rest… Practice shows that during a multimeasure rest in separate parts, the G.P. is placed under the staff so as not to merge with the number of the multimeasure rest. But in the full score, putting G.P. under the topmost staff of the full score is somehow inappropriate (in my opinion). Alternatively, you can set a condition that will prohibit combining the generally silent bars of the full ensemble into one with a multimeasure rest (so that each bar is individually marked G.P.).
You already know better here, come up with a design.
I also ask you to take into account that G.P. can be specified together with the fermata, so think about the design in advance so that in the end it does not turn out that G.P. will merge with the fermata.
Problem to be solved
In most scores, it is important to mark the bars where the entire ensemble is silent. This will avoid unnecessary noise from the performers, which will be very noticeable at the moment of silence (for example, turning pages, rearranging harp pedals, etc.). It is also important for the conductor to see this in the full score, since it visually helps to determine the moment of silence better and faster than reviewing a considerable (as a rule) number of staves in the one (or more) bar.
Currently, MuseScore Studio cannot automatically center the text above/below the rest. We have to adjust it manually. And given the fact that the score can undergo multiple changes in the layout during the editing process, all the initial adjustments may eventually turn out to be just a waste.
Prior art
No response
Additional context
If this is implemented, I also ask you to provide the possibility of translating G.P. into other languages in <app.transifex>, since "Generalpause" is in German, and in different countries it can be translated completely differently (in French - "silence", in Italian. - "vuoto", in Russian - "генеральная пауза" [Г.П.], etc.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by tracing how silent bars, rests, multimeasure rests, fermatas, and system objects are laid out in the full score and parts. Done means a configurable, translatable G.P. designation is automatically placed without collisions and follows the requested bar and multimeasure-rest behavior.
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