w3c / musicxml

MusicXML specification
521 stars 58 forks source link

Clarify tuplet metadata should go on type="start" vs. type="stop" element #434

Open adrianholovaty opened 3 years ago

adrianholovaty commented 3 years ago

Given that a single tuplet is represented by two MusicXML elements — <tuplet type="start"> and <tuplet type="stop"> — it's not 100% clear whether additional metadata, such as the placement attribute, should go on the first or second element.

It seems intuitive for that data to live on the start element as opposed to the stop element, but this isn't formally documented (docs here). It might be worth adding this to the docs, if that's indeed the suggested behavior?

As it stands, in our Soundslice MusicXML importer, we check both the start and stop elements for a placement attribute, then prefer the start in case of conflict.

(This issue might be generalizable to other MusicXML elements that have start and stop pairs.)

mscuthbert commented 3 years ago

I think that the general rule (including tied, beam, etc.) is that no formatting/"metadata" except for ending placement if any goes on a "stop", and "continue" continues the formatting from the previous "start" unless explicitly overridden.

adrianholovaty commented 3 years ago

@mscuthbert That makes sense to me. Would be nice to codify this a bit more formally.