Conversation
rdebroiz
force-pushed
the
fix/arpeggio-spanner-per-offset
branch
from
September 22, 2026 08:23
631382e to
5f9405e
Compare
number only tells apart simultaneous arpeggios, so match ArpeggioMarkSpanners on number and offset instead of reusing the incomplete one. Version bumped to 11.0.0b10 to invalidate cached parses. Fixes cuthbertLab#2039.
rdebroiz
force-pushed
the
fix/arpeggio-spanner-per-offset
branch
4 times, most recently
from
September 22, 2026 08:30
93055a3 to
896d367
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #2039: MusicXML import merges every
<arpeggiate>sharing anumberinto one spanner, so MuseScore files (alwaysnumber="1") end up with a single arpeggio per part.The importer now matches an
ArpeggioMarkSpanneron number and offset. Other spanners close ontype="stop", so only arpeggios were affected. Version bumped to 11.0.0b10 since cached parses are wrong.AI-assisted (Claude)