The user can always press Stop

• Apr 8, 2022 - 03:29

I question the default play behavior in a score containing the Italian navigation D.C. al Fine and Fine.

After encountering a D.C. Musescore appropriately plays from the beginning of the score and halts at Fine.

However, I often include a caboose of scales exercises, explanations, and variations after Fine. Musicians using the score may want to hear those post-Fine measures. I also want to hear them to "proofread" my work. BUT MuseScore won't play them when the Play Repeat button is disabled—"semantically" odd as that is.

As mentioned, I'm not surprised that MuseScore halts when encountering Fine during playback. But it seems pointless (and it's inconvenient) that the user can't start playback after the Fine without first disabling Play Repeat. It's not as if things would run out of control. The user can always press Stop.

      DC al Fine and Fine.mscz

Even more peculiar, if a score contains only a Fine MuseScore ignores it completely, and so the user can start playback at any point.

      Fine ... but score continues.mscz

Am I missing something?

scorster


Comments

I'm not surprised by either behavior. It seems to me that if you have more material after the fine than its not really a fine is it.

The solution is to end your first part score with a section break on it's last measure.
Then MuseScore will consider whatever is following as a new section, and thus also allow playing it when honoring the repeat status.

As mentioned by bobjp, if you have a Fine and an instruction that triggers it; then that section is "done". Whatever you notate afterwards is "unreachable" according to standard playback interpretation. A Fine on it's own doesn't take effect, because it lacks the Jump instruction to trigger it; just like a "To Coda" on it's own is not functional without a Jump instruction.

In reply to by Jm6stringer

Ah! Thanks jm6stringer! With the addition of a Section mark I can play portions post Fine. AND as you suggest with Section>Pause = 0 my repeats are now clearly working—previously the default 3.0 second section Pause led me to erroneously conclude that the Repeats were failing outright!

But this leads back to a previously discussed issue: that Section breaks with Pause = > 0 cause MuseScore to mistakenly add an unwanted pause on Repeat or D.C. or D.S. ... whereas the Pause should occur ONLY when the section ends at Fine, NOT on any repeats or D.C.

I can see the value of a pause when a Section completes—and I'd usually want to impart that effect—but there shouldn't be any delays that affect the Section's internal navigation, prior to Section completion.

Scorster

In reply to by scorster

The section pause applied at wrong times is still there (#32696: Section break causes pause before repeats and jumps during playback)
The intent (or at least mine) is to tackle it after public Alpha has been released, in which the underlying playback events system should be stable enough to dive into it. The good news is that the internal informational structure to correct the interpretation is mostly there since 3.5.1.

Now I "just" need to break the current way of how (those) pauses are turned into playback instructions and plug in the new information instead. And then cross my fingers that the new way didn't break all the old ways..

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