Repeat multiple volta play-back fails

• Nov 18, 2020 - 17:18
Reported version
3.5
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
by design
Regression
No
Workaround
No
Project
MuseScore

1) open attached example and play
2) first line ok: measures 1 - 2 - 3 - 1 - 2 - 4 - 1 - 2 - 5
3) second line - expect measures 6 - 7 - 6 - 7 - 6 - 7 - 6 - 8 - 6 - 9 - 10 - 11
Actual behaviour: 6 - 7 - 6 - 7 then jumps to measure 13 (after D.C.)??
4) then expect 12 (DC wo repeats) 1 - 2 - 5 - 6 - 9 - 10 - 11 - 13 - 14 - 15 - 16 - 14 - 15 - 17 (DS wo repeats) 6 - 9 - 10 - 11
Actual behaviour: 13 14 - 15 - 16 - 14 - 15 - 17 - 6 - 7 - 13 (!) - 14 - 15 - 17
(measures 8 to 12 are never played and actually cannot be played!)

Attachment Size
Test-Repeats.mscz 10.83 KB

Comments

• Nov 18, 2020 - 17:41
Status active ⇒ by design

In measure 7, you have play count in measure properties set to 2, it needs to be set to 4 so it can play m 6 4 times. The repeat and m8 has play count set to 2 so m6 will play 2 more times as expected so it will play voltas labeled 4 then 5.

The DC and DS overlap and you can do that. Musicians will have a problem with it and it's undefined what MuseScore will do with it.

Reply

• Nov 18, 2020 - 18:42

Learned something! Playback does indeed improve by setting the play count of m6 to 4.
But I find that very confusing 'by design': why isn't the Volta repeat setting (1, 2, 3) sufficient to specify the number of repeats? Note also that the Volta repeat setting IS exported to MusicXml but the play count of the measure is NOT.
About the DC and DS: I'm a musician too and don't have a problem with overlapping DC and DS - since I only made this for testing ;-)

Reply

• Nov 18, 2020 - 20:08

By design doesn't mean the design is good. I've talked to the lead developers and they said it's on their list of things to look at for 4.1 when that gets released so we'll continue helping people like you until it's improved.

Reply