You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MusicXML: <sound dacapo="yes"/> with a <sound tocoda> elsewhere plays to the end after the da capo instead of jumping to the coda #2860
AI-assisted (disclosure block included as described in AGENTS.md)
Current Behavior
Note
AI-authored disclosure (alphatab-ai-authored-v1)
Portions of this content were authored by an AI agent. The agent has read AGENTS.md and the human submitter accepts responsibility for
compliance with the rules in that document.
A MusicXML score with a To Coda mark (<sound tocoda="coda1"/>) in bar 2, a D.C. al Coda (<sound dacapo="yes"/>) in bar 3 and the Coda
(<sound coda="coda1"/>) in bar 4 plays
1 2 3 1 2 3 4
After the da capo, playback runs past the To Coda mark and through bar 3
again, and only then reaches the coda. The imported directions are
2: JumpDaCoda, 3: JumpDaCapo, 4: TargetCoda
(In this repro the <sound> elements are direct children of <measure>, so
that they are imported at all; see the separate report about <direction>-level <sound>.)
Expected Behavior
1 2 3 1 2 4
In MusicXML the "al Coda" is not a separate attribute. "D.C. al Coda" is
expressed as dacapo on the D.C. bar plus tocoda on the bar where the jump
to the coda happens; tocoda applies on the pass after the da capo or dal
segno (https://www.w3.org/2021/06/musicxml40/musicxml-reference/elements/sound/).
Likewise dalsegno + tocoda means "D.S. al Coda", and dacapo/dalsegno
fine means "al Fine". MuseScore, which wrote the real files we see this
with, plays them that way. The same score entered in alphaTex with \jump DaCapoAlCoda plays 1 2 3 1 2 4.
Steps To Reproduce
Save this as repro.musicxml (or unzip the included repro.zip)
Related to the report about <sound> inside <direction> not being imported
(#2859). Real-world source: MuseScore Studio 4.7.4 exports of choral pieces with
D.C. al Coda.
Is there an existing issue for this?
I have read the contribution rules
AI authorship
AI-assisted (disclosure block included as described in AGENTS.md)
Current Behavior
Note
AI-authored disclosure (
alphatab-ai-authored-v1)Portions of this content were authored by an AI agent. The agent has read
AGENTS.md and the human submitter accepts responsibility for
compliance with the rules in that document.
A MusicXML score with a To Coda mark (
<sound tocoda="coda1"/>) in bar 2, aD.C. al Coda (
<sound dacapo="yes"/>) in bar 3 and the Coda(
<sound coda="coda1"/>) in bar 4 playsAfter the da capo, playback runs past the To Coda mark and through bar 3
again, and only then reaches the coda. The imported directions are
(In this repro the
<sound>elements are direct children of<measure>, sothat they are imported at all; see the separate report about
<direction>-level<sound>.)Expected Behavior
In MusicXML the "al Coda" is not a separate attribute. "D.C. al Coda" is
expressed as
dacapoon the D.C. bar plustocodaon the bar where the jumpto the coda happens;
tocodaapplies on the pass after the da capo or dalsegno (https://www.w3.org/2021/06/musicxml40/musicxml-reference/elements/sound/).
Likewise
dalsegno+tocodameans "D.S. al Coda", anddacapo/dalsegnofinemeans "al Fine". MuseScore, which wrote the real files we see thiswith, plays them that way. The same score entered in alphaTex with
\jump DaCapoAlCodaplays1 2 3 1 2 4.Steps To Reproduce
repro.musicxml(or unzip the included repro.zip)repro.zip
Load it with the player enabled and print
or press play and follow the cursor.
Observe
1 2 3 1 2 3 4.Link to jsFiddle, CodePen, Project
No response
Version and Environment
Platform
Web
Anything else?
Related to the report about
<sound>inside<direction>not being imported(#2859). Real-world source: MuseScore Studio 4.7.4 exports of choral pieces with
D.C. al Coda.