MusicXML files missing <backup> elements for multi-voice sta
Hi,
When Symphony Pro exports to MusicXML music which has more than one voice on a staff, it generates output like:
<measure number="1">
<attributes>
<key> <fifths>0</fifths> <mode>major</mode> </key>
<time><beats>4</beats><beat-type>4</beat-type></time>
<staves>1</staves>
<clef><sign>G</sign><line>2</line></clef>
</attributes>
<direction><direction-type>
<metronome>
<beat-unit>quarter</beat-unit>
<beat-unit-dot/>
<per-minute>80</per-minute>
</metronome>
</direction-type></direction><note><pitch><step>E</step><alter>0</alter><octave>5</octave></pitch><duration>32.000000</duration><voice>1</voice><type>half</type></note>
<note><pitch><step>E</step><alter>0</alter><octave>5</octave></pitch><duration>32.000000</duration><voice>1</voice><type>half</type></note>
<note><pitch><step>C</step><alter>1</alter><octave>5</octave></pitch><duration>32.000000</duration><voice>2</voice><type>half</type><accidental>sharp</accidental></note>
<note><pitch><step>C</step><alter>1</alter><octave>5</octave></pitch><duration>32.000000</duration><voice>2</voice><type>half</type><accidental>sharp</accidental></note>
</measure>
---
The original notation in Symphony Pro is that each C' on voice 2 hits at the same time as each E' on voice 1. The MusicXML, however, indicates that the C's on voice 2 hit after the E's on voice 1. (When you import this into Sibelius 6, that's what you get: two E's followed by two C's. The intent was an E and C at the same time followed by another E and C at the same time.)
Symphony Pro needs to generate a <backup> element before it generates the MusicXML for the voice 2 notes so that those notes land at the proper place in the measure. i.e., simultaneous with voice 1 rather than after voice 1. e.g., in this case,
<backup><duration>64</duration></backup>
gets us back to the start of the measure. The two C's then happen at the same time as the two E's which matches the original notation in Symphony Pro.
When Symphony Pro exports to MusicXML music which has more than one voice on a staff, it generates output like:
<measure number="1">
<attributes>
<key> <fifths>0</fifths> <mode>major</mode> </key>
<time><beats>4</beats><beat-type>4</beat-type></time>
<staves>1</staves>
<clef><sign>G</sign><line>2</line></clef>
</attributes>
<direction><direction-type>
<metronome>
<beat-unit>quarter</beat-unit>
<beat-unit-dot/>
<per-minute>80</per-minute>
</metronome>
</direction-type></direction><note><pitch><step>E</step><alter>0</alter><octave>5</octave></pitch><duration>32.000000</duration><voice>1</voice><type>half</type></note>
<note><pitch><step>E</step><alter>0</alter><octave>5</octave></pitch><duration>32.000000</duration><voice>1</voice><type>half</type></note>
<note><pitch><step>C</step><alter>1</alter><octave>5</octave></pitch><duration>32.000000</duration><voice>2</voice><type>half</type><accidental>sharp</accidental></note>
<note><pitch><step>C</step><alter>1</alter><octave>5</octave></pitch><duration>32.000000</duration><voice>2</voice><type>half</type><accidental>sharp</accidental></note>
</measure>
---
The original notation in Symphony Pro is that each C' on voice 2 hits at the same time as each E' on voice 1. The MusicXML, however, indicates that the C's on voice 2 hit after the E's on voice 1. (When you import this into Sibelius 6, that's what you get: two E's followed by two C's. The intent was an E and C at the same time followed by another E and C at the same time.)
Symphony Pro needs to generate a <backup> element before it generates the MusicXML for the voice 2 notes so that those notes land at the proper place in the measure. i.e., simultaneous with voice 1 rather than after voice 1. e.g., in this case,
<backup><duration>64</duration></backup>
gets us back to the start of the measure. The two C's then happen at the same time as the two E's which matches the original notation in Symphony Pro.
0
Comments
-
We released 1.2 on the 7th. Could you try updating and see if that fixes the problem? There's still some remaining issues with the MusicXML exporter, but we're putting a lot of work into clearing those up by the next update.0
-
This case now works. Thanks.0