Volta interpretation (Literal vs. classical )
Musescore follows the classical approach when interpreting volta or repeats:
• On the first pass the repeat or 1st ending is honored.
• On the second pass (after Da Capo or Dal Segno) the repeat or 1st ending is ignored.
This is an important feature. But often I'd like to turn off this behavior and have
Musescore interpret the second pass—post Capo or Segno—the same as the initial pass,
playing both the first and second endings. Is that possible in Musescore?
I haven't found a toggle anywhere.
Nor do I see Measure Properties>Play Count as a viable solution.
Comments
If I understand correctly, you simply need to enable "Play repeats" on the DC/DS (see Inspector).
In reply to If I understand correctly,… by Marc Sabatella
Thanks Marc!
Your solution works in my example score, but not in a page long score I’m working on ... due perhaps to my possible misuse of a coda mark?
I don’t want to post the score to the forum. Is it possible for me to send it directly to you?
Thanks!
scorster
In reply to Thanks Marc! Your solution… by scorster
Save a copy of that score and remove all notes from it. (Right click one, select all similar > delete).
Then attach that score for repeat/jump logic analysis.
In reply to Save a copy of that score… by jeetee
Thanks everybody!
Here's the skeleton of the score. Marc's input allowed me to get the "double repeats" I wanted, but now there's an issue with the 1st ending playing twice or not at all:
Repeat and Volta test.mscz
scorster
In reply to Thanks everybody! Here's the… by scorster
Well, a) volta 1 has a repeat list of 2 and volta 2 has it set to 1, that certainly is confusing
b) voltas are alternattove ending foe simple repeats, not for jumps, here there is no end repeat barline between them C9 you have to coda markers, both with a tag of "codab", so which of the 2 should the D.C. al Coda jump to? d) you have a D.C. which is a D.C. al fine in disguise
In reply to Thanks everybody! Here's the… by scorster
So the roadmap you're looking for isn't really a thing supported in standard notation in the sense that there are a few limitations in jump processing:
1) A jump in itself does not influence the number of repeats; the only way to determine a "last" repeat is to look at the repeat barlines and the play count associated with them via their measures.
2) A jump label needs to be unique within a section. Having two "real" coda markings in the same section gives no guarantee as to which one is "found" first by MuseScore's scanning algorithm (nor by any human scanning the score).
3) A jump can only ever be followed once, and there is currently no way to specify which jump should be taken in which order if more than one jump instruction is present in a measure.
Knowing these limitations however means that you can get your desired playback order by removing the D.C. and replace it with a normal end repeat barline. Then you can use voltas to control the playback order of A and B for the repeats.
Also note that the end repeat barline of part B uses a play count that is one too high under "normal" circumstances, but it is used here to allow the "last" playback after the D.C. to be playback 7, which is not encountered in the normal playback map, but now found as "final" playback to use after the jump.