[Musicxml Export] - Bad note value export in nested tuplet

• Jan 16, 2020 - 08:58
Reported version
3.3
Type
Performance
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

The attached file shows a measure with an 8th triplet, in which there's a 16th triplet. Normally, the Musicxml hould export 16ths with time modification for the nested 16th triplet. But Musescore exports all 16ths as double-dotted 32nd notes, which is very confusing. I looked into the mscx code, and the three nested notes are all marked as 16ths. It's strange that the xml conversion applies different note value and pluses double dots on them.

Attachment Size
nested triplets.mscz 2.77 KB
nested triplets.musicxml 5.61 KB

Comments

• Mar 22, 2020 - 18:23

Once again, this one was never implemented, mostly due to lack of popular demand. Importing nested tuplets from MusicXML is a bit of a challenge, but exporting should not be difficult.

Reply

• Mar 26, 2020 - 07:01

There are two issues here:
- note type calculation takes only one tuplet into account, leading to bad note values
- only one tuplet start / stop is generated
Both are not difficult to solve.

Reply

• May 3, 2020 - 23:34

I just tried it, the issue is just halfly solved. The result is incomplete, since we can't determine the tuplet number of the second layer. Both should have their own tuplet numbers displayed. The attached is the identical example exported from Sibelius, which is the standard syntax. I looked into Musescore's notation encoding, and the layers are indicated clearly as what the Sibelius xml example shows. So it may not be difficult to have the numbers included.

Haipeng

Attachment Size
nested triplets Sibelius.musicxml 13.73 KB

Reply

• May 3, 2020 - 23:52

PS: If I take the xml exported from Musescore to a braille music translation software, it will export a tuplet of 9 instead of two layers of triplets.

Reply

• May 4, 2020 - 20:53

Thanks for testing. The tuplet-actual and tuplet-normal elements are optional according to the MusicXML spec, so I did not implement them. I did not know your braille music translation software requires them. Please submit a new issue, as this one has already been merged and has status fixed.

Reply

Fix version
3.5.0