Importing XML from finale results in dynamics being improperly defined.

• Oct 14, 2017 - 23:32
Reported version
2.1
Type
Functional
Severity
S5 - Suggestion
Status
active
Project

Dynamics markings, in a score that was imported from Music XML, are all over the place, and in general, actually appear next to the staff ABOVE the staff that the dynamic marking was added to. See dynamics anywhere in attached score.

Attachment Size
I_Heard_the_Bells_on_Christmas_Day.mscz 42.36 KB

Comments

Title Dynamics all over the place Importing XML from finale results in dynamics being improperly defined.
Status (old) needs info active
Status needs info active

Comparing the XML which came from Finale v25 to the score, it seems that MuseScore is not doing the dynamics correctly. For example, the first dynamic in the XML is the mf in measure 39 of the descant. The velocity in the XML is 90, in MS it's 81 which is not the MS default of 80. Why did it chose 81? I'm note sure about the height/Vertical offset, but the XML puts is location as above and default-y="15". I'm not sure how that gets translated into vertical offset of -9.62. In measure 21 of the Soprano 1 XML says dynamics default-x="95" default-y="21" with a velocity of 69. MS displays it at vertical offset -9.62 and velocity = 62 which is a mystery number for mp. I search through the XML for some sort of default dynamic offset, but the only dynamic defs I see are for each individual dynamic. One other note, all dynamics have a direction placement="above" on them.

I haven't looked at every dynamic and compared them to MuseScore's output, but it seems every dynamic is at -9.62 with a random velocity.