[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
Severity
S5 - Suggestion
Status
active
Regression
No
Workaround
No
Project

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).