musescore / musescore/MuseScore

Qualifying text for hairpins

Open
#21,708 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 suggest changing the auto-placement of the qualifying text for hairpins as follows (instead of the existing way of placing the text at the beginning/end of the haipins):
Снимок экрана (131)
Снимок экрана (374)

It would also be nice if the software would automatically detect and reproduce the degree of volume change according to the assigned qualifying text (for example: poco cresc. should be played with a slight loudness change, molto cresc. should be played with a significant loudness change, etc.)

Problem to be solved

At the moment, in Musescore, qualifying text can be added to the hairpins either at the beginning or at the end. This placement of the text is ambiguous, as it can be interpreted in different ways (it is not entirely clear what refers to what).
Снимок экрана (132)
Снимок экрана (212)

In addition, the qualifying text shifts the hairpin to the side, which ultimately may lead to a misinterpretation of the designation.

https://github.com/musescore/MuseScore/assets/134041121/92585a81-28e2-4292-bf9c-c89761ce2eb4

If you change the automatic placement of the text so that it is displayed above or below the hairpin, then it becomes completely obvious that the qualifying text refers specifically to the hairpin.

I also ask you to pay attention to the fact that at the moment MuseScore Studio does not respond in any way to such instructions as molto, poco, etc. in terms of playback for the simple reason that it [MuseScore] does not recognize these instructions. Regardless of whether poco a poco, molto, etc. is specified, MuseScore Studio will apply the same degree of loudness change.

Prior art

In Dorico, the qualifying text is automatically positioned above/below the hairpin.

https://github.com/musescore/MuseScore/assets/134041121/b528f9a8-9371-42c8-82b5-ff470f141768

Additional context

I hope this may be related to what @cbjeukendrup said in his comment.

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.