-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #16748: Fix articulation combinations on MXML import / export, and ensure placement of articulations is respected #16828
Fix #16748: Fix articulation combinations on MXML import / export, and ensure placement of articulations is respected #16828
Conversation
I'm out of time today but I will have tests for this one tomorrow, please stand by! |
Maybe #8514 would be a better basis? |
|
||
case SymId::articSoftAccentTenutoStaccatoAbove: | ||
case SymId::articSoftAccentTenutoStaccatoBelow: | ||
return { "soft-accent", "detached-legato" }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not return { "staccato", "soft-accent", "tenuto" };
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nope, detached-legato is the glyph for combined staccato and tenuto markings
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, thanks for checking anyway ;-)
One unit test (the newly added one) needs fixing, https://github.com/musescore/MuseScore/actions/runs/4428468868/jobs/7767593095?pr=16828#step:9:9196 |
396667d
to
6206829
Compare
this is a port of PR musescore#8190 with a few alterations, namely, the skipping of combination when the placements are not the same.
and ensure that correct articulation placement information is exported when changed from default
6206829
to
af4bc5e
Compare
from `{ "staccato", "soft-accent", "tenuto" }` to `{ "soft-accent", "detached-legato" }`, and changing the order a bit to match how musescore#16828 is doing it for master now.
af4bc5e
to
0d9003a
Compare
from `{ "staccato", "soft-accent", "tenuto" }` to `{ "soft-accent", "detached-legato" }`, and changing the order a bit to match how musescore#16828 is doing it for master now. Adds to an earlier backport of musescore#8190 to 3.x
from `{ "staccato", "soft-accent", "tenuto" }` to `{ "soft-accent", "detached-legato" }`, and changing the order a bit to match how musescore#16828 is doing it for master now. Adds to an earlier backport of musescore#8190 to 3.x
Resolves: #16748
This PR began as a direct port of #8190, which deals with articulation marks combining (such as tenuto-staccato being a single combined glyph). We also take care not to combine when the placement of the accidentals suggest that they have been manually set at one placement or another.
In testing this PR, I noticed that musescore doesn't export articulation placement at all, so I added that in as well, as per the MusicXML spec.