[XML Import] Tempi from Capella XML export don't get imported

• Apr 17, 2015 - 11:41
Type
Functional
Severity
S4 - Minor
Status
closed
Regression
No
Workaround
No
Project
MuseScore
Tags
musicxml

Seems that for a MusicXML exported from Capella, MuseScore doesnt import the tempi.

Not sure at all, but the reason might be that these tempi are lacking metronome, beat-unit und beat-per-minute, they only have "<sound tempo="132">, so it may turnout to be a problem in Capella#s XML export. But maybe something we could handle better?

See also #56661: [CAPX Import] Tempi from Capella don't get imported and https://musescore.org/de/node/56576

Attachment Size
Beispiel 2.xml 143.07 KB
Beispiel 2.pdf 24.16 KB

Comments

• Apr 17, 2015 - 11:58

The same files also show some strangeness with importing the dynamics, it seems to be too high above staff. Also apparently the intention of those dynamics are to apply to all staves within the square bracket, but they apply only to the top staff, MuseScore's idea of a part seems different of Capella's or MusicXML's

Reply

• Apr 21, 2015 - 21:54

You already answered your own question: this is caused by the missing metronome, which describes the displayed metronome mark. The sound element does not describe any marking but directs playback.

We could generate metronome marks for directions where only the sound element is present, but this means not conforming to the spec, something which I personally would try to avoid.

For reference, Finale NotePad does not display metronome marks for this file either.

Reply

• Apr 22, 2015 - 06:56

another option would be 'invisible' tempo marks, to at least get the playback right, maybe?
IIRC we are doing this for midi files (and it seems to cause problems there, because they are invisible)

Reply

• Apr 22, 2015 - 20:44

yes, agreed, completely invisible tempo markings like we seem to get at times with midi import would be a rather bad idea, but indeed an 'invisible' tempo marking (greyed out and not in the printout) seems the way to go

Reply

• Dec 29, 2020 - 07:43

This is quite an old issue, the reference in #137091: [MusicXML Import] should not create visual tempo element for <sound tempo="num"/> element made me look at it again. I think this one can be closed:

Importing sound tempo=... as TempoText has been implemented by @lasconic long time ago (commit db9ca7c of May 20, 2016).
Making these invisible has (finally) been implemented in 3.x (commit 5f8ea1c of Dec 27, 2020) for issue #137091: [MusicXML Import] should not create visual tempo element for <sound tempo="num"/> element.
The PDF shows two metronomes (half note = 132, half note = 144) that are simply not present in the MusicXML file.
The PDF also shows many accents which are not shown by MuseScore because they are simply not present in the MusicXML file.
Finally, MuseScore does not import dynamics style or position from MusicXML.

Reply

Fix version
3.6.0