musescore / musescore/MuseScore

Automatic duplication of fermata on adjacent staffs of the score

Open
#21,712 3 comments 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 suggest adding the function of automatically placing the fermata on the beat (or subdivision) on all adjacent staffs of the score.
Снимок экрана (145)

Problem to be solved

Currently, this can only be done manually (by adding a fermata to each note carrier individually). I suggest this approach at the automatic level, since a priori the fermata should cover not only the note in the beat, but also the rest (and at full coverage of the bar).
It should be noted that the fermata should be duplicated exactly in the place where the pause occurs.
Снимок экрана (146)

Workarounds

At the moment, fermatas can be applied to all notes in the system by selecting the appropriate area. But this is not what one would expect from the last bar of the score. For some reason, MuseScore duplicates the fermatas to the last bar-line.
https://github.com/musescore/MuseScore/assets/134041121/eafbbb74-121c-4e8c-b27e-e05a76b75ea5

Prior art

No response

Additional context

It should also be noted that in the score it is not necessary to display on a non-first page all the parts in which the fermata is present in the event that there is a check mark opposite "Hide empty staves within systems". Only those on which there are notes in the current system are sufficient.
Снимок экрана (147)

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.