Improve articulation placement
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No source files or tests are named. Start by tracing MuseScore's articulation and slur placement behavior, then compare the documented examples and prior art; done would require agreed automatic placement rules for accents, other articulation signs, tenuto, staccato, and Schoenberg stress symbols.
Written by the indexing model from the issue text.
Description
Your idea
- Allow automatic adjustment of accents to the slurs in order to avoid large differences in the level of positioning.
First of all, this applies to those cases when, in combination with a slur, accents can "jump" one after another or are too far from the note. For example:
The same applies to signs such as "+" (closed), "o" (open), harmonics, etc. Example:
- As you know, the accent marcato and staccatissimo should usually be placed outside the staff. I suggest making some exceptions and allowing automatic approximation of such articulations to the notes for the greatest legibility. Example:
- As you know, such articulations as tenuto and staccato are not placed between the ledger lines. Instead, they are placed between the first and second lines of the staff. However, for tenuto, this value should be even greater so that the eye does not visually confuse them with ledger lines:
In Dorico, by the way, this practice is set by default. - Stress symbols introduced by Schoenberg. As you know, these symbols should be placed above the staff, except in double-stemmed writing, and outside any articulation marks. But for unknown reasons, MuseScore Studio currently places them under the staff, which is incorrect.
https://github.com/user-attachments/assets/883dc130-946b-48a7-bffe-6ee91d8ad5d4
Problem to be solved
Although accents should be placed outside the staff, in some cases it would still be wiser to make exceptions. At the moment, the user has the opportunity to adjust such things manually, but this takes time and is a workaround, as well as has side effects.
For example, take a look at this:
It looks decent, but only after manual adjustments.
And here's exactly how MuseScore Studio handles it:
By the way, it could also be done like this:
Prior art
Dorico has a setting that allows you to place accents inside the slurs:
Dorico also places tenuto much further away from the ledger lines:
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
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
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.
More from musescore/MuseScore
-
engraving P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
needs design
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
community P3 UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
regression nightly UX/interaction
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in musescore/MuseScore
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·