Complicated Repeats not followed correctly

• Jun 6, 2024 - 19:47

Specifically for the Blue Danube - whenever there's a first ending, a second ending with a ds al fine, and a fine -
The ds al fine always plays the second ending. It should not. I'm also seeing that it hits the fine and then keeps going, although it doesn't play the music after the fine. Probably shouldn't do that and should only keep playing if there is a new section.

I'm not using sections here only because I'm not sure how to tell the program attaca FireShot Capture 005 - An der schönen blauen Donau, Op.314 (Strauss Jr., Johann) - IMSLP - imslp.org_.png

Attachment Size
BlueDanube.mscz 79.67 KB

Comments

Prolly the easiest way would be to make the second ending be two measures long. First measure 2 beats (high D and rest), second measure one beat (second high D). Put the Fine in the first measure.

Something like this:

20240606 150630-endings.png

The notation here isn't really standard. That thing that looks like a third ending isn't, since the second ending doesn't have a repeat. So it is indeed technically correct for the DS to return to the second ending. A human player would forgive the non-standard notation and figure out what was meant but no such AI is built into MuseScore. That "ending" would need to be a coda to be correct.

Also, with section breaks, the Properties panel will allow you to set the pause to 0, if that's what you mean by attaca.

In reply to by Marc Sabatella

Another thing I'm noticing is that the DS al Fine plays all repeats. I highly doubt that's what's intended here - it's likely minuet structure, which now that I think about, I don't know how to implement on MS4.
Wonder if a third ending on the fine without a repeat would fix the 2nd ending problem. There's also two codas on this thing, and as they are conditional on the existence of a choir, I'm not sure if there is a way to write them, but tell it '2nd coda only'

Do you still have an unanswered question? Please log in first to post your question.