musescore / musescore/MuseScore

More options for marking pauses

Open
#24,484 1 comment 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
  1. I propose to implement the ability to add a special clarifying text above the pause marks. See the example:
    Снимок экрана (547)
    And of course, the clarifying text should have an appropriate result in terms of stretching time (for example, poco should sound shorter, lunga should sound longer, etc.), i.e. MuseScore Studio should understand these things and make the sound longer in accordance with the degree indicated by the clarifying text.
  2. Currently, you can change the time stretch in the Properties of the pause mark. But the user can only see it in the properties and only in the form of percentages. I suggest implementing the possibility of automatically specifying such things right above the pause mark. For example:
    Снимок экрана (548)
    It is also possible to specify a duration range. Of course, the program will produce an accurate result regarding time stretch, but at the same time the user should be able to edit this text in his own way. For example:
    Снимок экрана (549)

Of course, all these things should be automatically centered above the pause mark.

  1. Break with pause. Add the ability to indicate pause marks over breath marks and caesures.
    Снимок экрана (550)
Problem to be solved

This will allow users (composers) to specify pauses in more detail, which is sometimes important when writing music. Currently, the pause can be specified in the form of a regular fermata, but only the user and the program know how long it should last, since such details are specified only in the Properties, and not in the score itself.

Prior art

No response

Additional context

No response

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

No files, tests, or entry points are named. Start by locating the pause-mark implementation and its Properties handling, then determine how text, duration stretching, centering, and breaks over breath marks or caesuras are represented; done would require all three requested behaviors in the score and playback.

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.