Thanks Torsten!

For completeness, here is the MusicXML data.

It’s interesting to observe that MusicXML import is not done the same way by 
different tools, hence my post.

JM

--

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE score-partwise PUBLIC "-//Recordare//DTD MusicXML 1.0 Partwise//EN"
                                "http://www.musicxml.org/dtds/partwise.dtd";>
<score-partwise>
  <identification>
    <miscellaneous>
      <miscellaneous-field name="description">Nested repeats, each with 
          alternative endings.</miscellaneous-field>
    </miscellaneous>
  </identification>
  <part-list>
    <score-part id="P1">
      <part-name>MusicXML Part</part-name>
    </score-part>
  </part-list>
  <!--=========================================================-->
  <part id="P1">
    <measure number="1">
      <attributes>
        <divisions>1</divisions>
        <key>
          <fifths>0</fifths>
          <mode>major</mode>
        </key>
        <time symbol="common">
          <beats>4</beats>
          <beat-type>4</beat-type>
        </time>
        <clef>
          <sign>G</sign>
          <line>2</line>
        </clef>
      </attributes>
      <note>
        <pitch>
          <step>C</step>
          <octave>4</octave>
        </pitch>
        <duration>4</duration>
        <voice>1</voice>
      </note>
    </measure>
    <!--=======================================================-->
    <measure number="2">
      <barline location="left">
        <ending number="1" type="start"/>
      </barline>
      <note>
        <pitch>
          <step>E</step>
          <octave>5</octave>
        </pitch>
        <duration>4</duration>
        <voice>1</voice>
      </note>
      <barline location="right">
        <ending number="1" type="stop"/>
      </barline>
    </measure>
    <!--=======================================================-->
    <measure number="3">
      <barline location="left">
        <ending number="2" type="start"/>
      </barline>
      <note>
        <pitch>
          <step>F</step>
          <octave>5</octave>
        </pitch>
        <duration>4</duration>
        <voice>1</voice>
      </note>
      <barline location="right">
        <bar-style>light-heavy</bar-style>
        <ending number="2" type="stop"/>
        <repeat direction="backward"/>
      </barline>
    </measure>
    <!--=======================================================-->
    <measure number="4">
      <note>
        <pitch>
          <step>G</step>
          <octave>5</octave>
        </pitch>
        <duration>4</duration>
        <voice>1</voice>
      </note>
      <barline location="right">
        <bar-style>light-heavy</bar-style>
      </barline>
    </measure>
  </part>
  <!--=========================================================-->
</score-partwise>




> Le 25 juin 2018 à 20:08, Torsten Hämmerle <torsten.haemme...@web.de> a écrit :
> 
> Hello Jacques,
> 
> Without knowing the original MusicXML file, the LilyPond solution looks much
> more like a standard volta repeat with alternatives than the
> Finale/Musescore output.
> 
> In any case, nested or not, a repeat barline will have to be set between
> adjacent volta brackets.
> Finale/Musescore misses out this repeat barline between the two volta
> brackets, whereas LilyPond's output is correct.
> 
> Apart from that, these nested repeats can be confusing for several reasons
> and there may be better alternatives. But, in the end, this about faithful
> MusicXML representation and I'd say LilyPond wins this time.
> 
> HTH,
> Torsten
> 
> 
> 
> --
> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
> 
> _______________________________________________
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to