MusicXML import issue: slur and barline-group

• Jan 9, 2014 - 00:43
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore
Tags
musicxml

Report from Primus developer regarding MusicXML import into MuseScore.

Original score in Primus: image.png
MusicXML exported from Primus: Rosseau_Suite Concertante Satz 1 primus2.zip

The MusicXML import into MuseScore (nightly) indicates two problems:
- slur not correct
- barline-goups not imported

import.png

Attachment Size
image.png 17.75 KB
import.png 65.79 KB
Rosseau_Suite Concertante Satz 1 primus2.zip 61.11 KB

Comments

• Jan 11, 2014 - 10:46

Issues confirmed.

Barline-group issue caused by part-group numbers 100..104. MuseScore (incorrectly) expects part-group numbers to be small integers. This is easy to fix, will do.

Slur issue not understood yet, MusicXML exported by Primus seems correct (certainly for the first measure in the viola part). MuseScore does report a number of null anchor slur issues, something is definitely wrong. Will investigate.

Reply

• Jan 12, 2014 - 13:04

Further analysis: the attached file does not contain bar line groups (which are indicated by the group-barline element in MusicXML). Instead, each part group has both a bracket (OK) and a line symbol (which is probably not what is intended).

MuseScores import behavior was to interpret a missing group-barline as meaning "no bar lines" in a part group. Our commercial competitors interpret this as "(yes) bar lines". I have changed MuseScores default to be the same as the competitions, which also adds bar lines to the attached file.

Reply