[MusicXML Import] should not create visual tempo element for <sound tempo="num"/> element

• Oct 12, 2016 - 06:31
Reported version
3.0
Priority
P3 - Low
Type
Functional
Frequency
Few
Severity
S5 - Suggestion
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore
Tags
musicxml
3.0alpha

If I create a new score in Finale Notepad 2012 and don't make a visual tempo element, then Finale Notepad doesn't display any tempo element:
Screenshot (70).png

Exporting to MusicXML has a sound tempo="120" element in first measure by default:
single-staff-no-visual-tempo.xml

Note that is not a "direction text" element http://www.musicxml.com/for-developers/musicxml-dtd/direction-elements/ (which is something that would be visually displayed)

When opening in 2.0.3, the xml import code doesn't create a visual tempo text element, which is correct.

However, when opening in 3.0.0-dev 676b0a3, the import code seems to incorrectly creating a tempo text element:
musescore-after-import.png

If save, that element gets saved to the mscx or xml.

Also another problem is if have multiple parts, then since each part has its own sound tempo element in their first measure, then on import musescore creates multiple overlapping tempo text elements all occupying the same visual space (so it looks like there is only one).

Comments

• Dec 19, 2020 - 03:00
Frequency ⇒ Few

Hi MuseScore! Dropping a note to say that the next version of music21 will increase the frequency of musicxml output with sound tags lacking metronome tags (because of a change to how we parse MIDI) with the intent of those tempo marks being hidden if they lack a metronome tag, much like the described solution here:

https://musescore.org/en/node/56656

Above it is mentioned how drawing the tempo mark in this scenario (tempo but no metronome) is not compliant with the spec. This is in keeping with other sound vs notation pairs of elements like tied/tie etc

That means we are seeing our musicxml display somewhat poorly, like this:

Attachment Size
mulitple-tempo-marks.png 39.67 KB

Reply

• Jan 16, 2021 - 00:58

FYI I created a PR which implements a matching MusicXML export functionality: exporting of hidden tempo text as sound element without direction.

Reply

Fix version
3.6.0