Make "Classic Phrasing" the default phrasing on Musesounds orchestral instruments.
@matthewreadbass is already working on this.
Since Oct 24, 2025.
Assessment
This issue has not been assessed yet.
Description
Your idea
The "Classic Phrasing" option found in the sound flags of Musebrass instruments should become the default phrasing model of all orchestral Musesound instruments (woodwinds, brass, and strings). Generally, these instruments should distinctly rearticulate the notes on the score, and play legato when notes are inside a slur marking.
The behavior of the playback in classical phrasing, where notes are played detached but the notes inside the slur are played legato, is seen as an ideal default for the rest of the sections of the orchestra. The current default phrasing, which is labeled as "Standard," should then be relabeled as "Legato." Repurposing "Standard" into "Legato" is more fitting since it is the desired effect when there is "Legato" written on the score.
Problem to be solved
There has been some feedback with the current default phrasing model of Musesounds since its release. Its sempre legato phrasing, though graceful and beautiful to the ears, can be out of place when the scenario does not call for legato. It can, to some extent, result in notes being mumbled due to fast pieces that call for snappier note attacks.
#15099
#17602
#15202
#22140
#14464
#14524
#13878
#20701
Prior art
https://github.com/musescore/MuseScore/assets/102687285/a3f14f82-790e-4ad1-bdee-722a5b1f8e09
Attached here is a concept video demonstrating a short arrangement applying this concept. See how the woodwinds and strings play legato inside the slur and play detached when there isn't, resulting in a nuanced and more realistic playback.
Additional context
Having classic phrasing be the default phrasing for woodwinds, brass, and strings would improve the realism of Musesounds playback since orchestral performers in real life play notes detached by default, and play legato when marked with a slur or the legato staff text.
- 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 ·