musescore / musescore/MuseScore
Hairpin 'Height (new system)' should apply to both halves of a hairpin split across systems
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
Hairpins split across a system break have a Height (new system) property, but this only applies to the continuation part on the new system.
The first half of a crescendo hairpin at the end of the 'old' system opens to full width, giving the player no indication that the hairpin continues across the break.
The issue is less serious for diminuendos but it would look better for the continuation part to start at a narrower width.
Either - the Height (new system) property should apply to both halves of the hairpin (my preference)
or - there should be a separate Height (old system) property to control the width of the first half independently
Problem to be solved
Good quality scores have a narrower opening width for hairpins which continue across a system break.
This is an important feature for players as it alerts them immediately that a crescendo will continue across the break.
It's more of a cosmetic nicety for diminuendos, but does make the score look significantly better.
This can only be replicated in MuseScore by making the 'real' hairpin invisible and adding graphic lines with the required opening width.
Needless to say this is very tedious and hard to do accurately, but is important for high quality output.
Prior art
I am a long-time Capella user currently converting to MuseScore.
Although I generally prefer the appearance of MuseScore generated scores, this issue really grates with me - it looks bad and is unhelpful for players.
Capella gets this right automatically. Hairpins across system breaks are the same half height at both sides of the break. There is no control over the new system height, but this is still preferable to the rather janky result from MuseScore where the split hairpin has different widths at each side of the break.
Additional context
No response
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.
Assessment
This issue has not been assessed yet.