trouble using 2 sets of repeats

• Oct 28, 2020 - 18:21

Hello,
I'm trying to get a piece of music to play back correctly. The A section is repeated; then the B section is repeated. All on the first verse. Then for verse 2 the A section repeats, then the B section repeats.

In my score, the first and second ending work correctly in the A section. In the B section, it repeats well, but on approaching the second ending, it blows right through the 1st ending measures it should be skipping.

Finally, I'm not sure how to make the whole thing repeat again for the second verse.

I spent some time looking for a question similar to mine, but couldn't find anything that helped me.

Thank you in advance, Elizabeth

Attachment	Size
Hark.mscz	31.82 KB

Comments

Jojo-Schmitz

• Oct 28, 2020 - 18:27

The 2nd part is quite easy: add a D.C. to the last measure and switch on it's 'Play repeats' in Inspector

Shoichi

• Oct 28, 2020 - 18:45

With 3.4.2 it works well. Why?

Attachment	Size
Hark3-4-2.mscz	33.14 KB

Jojo-Schmitz

• Oct 28, 2020 - 18:56

jeetee

• Oct 28, 2020 - 22:04

@Shoichi: Can you try out the Alt+ → flow to see if it crashes in 3.4.2 as well?

jeetee

• Oct 28, 2020 - 21:32

There is something fishy going on which even crashes MuseScore:
1. click on the B at the start of m18 in the top staff
2. Alt + → and the lyric "la." becomes selected
3. Alt + → and MuseScore crashes

Investigation to be continued

jeetee

• Oct 28, 2020 - 21:50

Playback order is indeed wrong due to the issue linked by Jojo above. There are incomplete volta remnants available on the measure (likely also the reason for the crash there).

Measure 18 looks as follows:

<Measure>
<endRepeat>2</endRepeat>
<voice>
  <Spanner type="Volta">
    <Volta>
      <beginText>1.</beginText>
      <endings>1</endings>
      </Volta>
    <next>
      <location>
        </location>
      </next>
    </Spanner>
  <Spanner type="Volta">
    <prev>
      <location>
        </location>
      </prev>
    </Spanner>
  <Spanner type="Volta">
    <Volta>
      <endHookType>1</endHookType>
      <beginText>1.</beginText>
      <endings>1</endings>
      </Volta>
    <next>
      <location>
        <measures>1</measures>
        </location>
      </next>
    </Spanner>
  <Chord>
    <durationType>half</durationType>
    <Lyrics>
      <text>la.</text>
      </Lyrics>
    <Note>
      <pitch>71</pitch>
      <tpc>19</tpc>
      </Note>
    </Chord>
  <Rest>
    <durationType>quarter</durationType>
    </Rest>
  <Chord>
    <durationType>quarter</durationType>
    <Lyrics>
      <text>Hark,</text>
      </Lyrics>
    <Lyrics>
      <no>1</no>
      <text>See,</text>
      </Lyrics>
    <Note>
      <pitch>74</pitch>
      <tpc>16</tpc>
      </Note>
    </Chord>
  </voice>
</Measure>

I've manually removed those first two volta entries, which seem to point towards a zero-length volta; which is why you can't select it from the program itself.
So the main question is: how did MuseScore create such a zero-length volta and would it be something created in an older version, or still possible in the current version.

Fixed score attached.

Attachment	Size
312326-Hark-fixed.mscz	31.83 KB

mike320

• Oct 28, 2020 - 21:54

It was created 3/19/19 so it was probably version 3.1.x, I don't think 3.2 had come out yet, even in beta.

Jojo-Schmitz

• Oct 29, 2020 - 07:21

Why doesn't right-click, select all similar, delete, re-add those wanted voltas fix this then?

jeetee

• Oct 29, 2020 - 09:37

Wild guess: because due to their broken 0-lengthness they're perhaps not fully recognized as valid volta's and select all similar then doesn't find them?
Debugging will tell...

sookysunky

• Oct 29, 2020 - 22:16

Thanks for fixing it. I removed a measure at then end and retyped it since I figured this was something I couldn't see, but I guess I didn't know which measure was doing the weird stuff...

Elizabeth

Shoichi

• Oct 29, 2020 - 04:15

@ jeetee, either I did not understand the steps or "la" is not selected on Mint.
Anyway no crash on 3.4.2 or 3.5.2.
Sorry if unnecessary causes delay in response.

mike320

• Oct 29, 2020 - 04:31

I found a 3.2.3 portable version and used that to test also. Using alt+right arrows it only selected notes, staff text and staff items. It never selected voltas or lyrics. Was accessibility improved that much after 3.2.3?

jeetee

• Oct 29, 2020 - 09:32

3.3 did a huge improvement on the number of markings available to the Alt+right/left commands.
So much that Marc made a video for it apparently :) https://www.youtube.com/watch?v=Ocl9gBxmeKg

Marc Sabatella

• Nov 2, 2020 - 03:55

Indeed, 3.3 was a pretty big accessibility release. The redesigned/reimplement palettes allowed them to be navigable for the first time, and I had a blind student in the theory class I was teaching and I wanted her to be able to complete her coursework in MuseScore. So that's when everything really came together.