[MusicXML import] use note type instead of note duration to determine note length

• May 30, 2021 - 11:55
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S5 - Suggestion
Reproducibility
Always
Status
PR created
Regression
No
Workaround
No
Project

Currently, the importer uses MusicXML note duration instead of note length as calculated from the MusicXML note type, dots, time-modification etcetera to determine how long a note takes and where to place the next note. When the MusicXML note duration does not match the calculated value, various types of corruption occur.

See the attached MusicXML file and screenshot of its import into MuseScore 3.6.2. The G is set at 90% of the nominal value, the B at 110%. As a result after import both measures 1 and 2 are corrupt. When trying to replace any of the notes in measure 1 by notes of different length (e.g. replace the G by a whole note), many unwanted small notes appear. Measure 2 has extra small notes after import and exhibits a similar problem as measure 1. Even when using the GUI to remove obvious problems, the remaining notes stay at incorrect beats.

When using the calculated duration, none of these problems occur. This change does not affect correctly encoded MusicXML files.

Attachment Size
Untitled.xml 2.54 KB
Untitled.png 9.54 KB