[MusicXML export] Slur start missing for slurs when importing MuseScore 1.3 file

• Aug 24, 2014 - 17:14
Type
Functional
Severity
S2 - Critical
Status
closed
Project
MuseScore

1. Open attached mscz (produced in 1.3).
2. 'File'>'Export…'.
3. Choose 'MusicXML'.
4. 'Save'.
5. Open MusicXML.

Expected result:
Slurs over glissando or two notes don't appear (Expected result).png

Actual result:
Slurs over glissando or two notes don't appear (Actual result).png

Note: Also attached is the produced MusicXML.

Using MuseScore 2.0 Nightly Build (1c07b89) - Mac 10.7.5.

Attachment Size
Slurs over glissando or two notes don't appear.mscz 1.6 KB
Slurs over glissando or two notes don't appear.xml 4.43 KB
Slurs over glissando or two notes don't appear (Expected result).png 25.81 KB
Slurs over glissando or two notes don't appear (Actual result).png 16.63 KB

Comments

• Sep 2, 2014 - 15:06

Yes, the MusicXML Export with slurs is buggy in v1.3 and v2.0.0 beta.

I've attached another example:
test
There first note got a
{syntaxhighlighter brush:xml;first-line:90}

{/syntaxhighlighter}

The third got a
{syntaxhighlighter brush:xml;first-line:113}

{/syntaxhighlighter}

But the second note need a
{syntaxhighlighter brush:xml}

{/syntaxhighlighter}

Attachment Size
slur.png 9.11 KB
Slur.mscz 1.48 KB
Slur.xml 3.68 KB

Reply

• Sep 3, 2014 - 09:36

Yes Marc Sabatella, you're right, type="continue" is optional.
Music XML slur

[...] Most slurs are represented with two elements: one with a start type, and one with a stop type. Slurs can add more elements using a continue type. This is typically used to specify the formatting of cross-system slurs, or to specify the shape of very complex slurs.

Sorry for my unnecessary comment.

Reply

• Sep 14, 2014 - 11:20
Title [MusicXML] Slurs over glissando or two notes don't appear ⇒ [MusicXML export] Slur start missing for slurs when importing MuseScore 1.3 file

This is not related to the glissando or the number of notes. When importing a 1.3 file with slurs, the slur start is not exported to MusicXML. Set to critical as it causes loss of information. Fix known, will be available soon.

Must-have for 2.0.

Reply