You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Audiveris' MusicXML export contains information about beams, staves and accidentals, it should state it explicitly using the <supports> elements in the header like in this example.
For example, MuseScore import behaves differently when beam support is present.
The text was updated successfully, but these errors were encountered:
@olin256
Thanks for this information.
I didn't know we could explicitly declare a support for such basic entities.
Where could we find an exhaustive list of the elements that can be "supported"?
In MusicXML, the "element" attribute is declared as an NMTOKEN type. A bit vague.
In the comments I noticed: beam, stem, accidental, print. What else?
Where could we find an exhaustive list of the elements that can be "supported"?
I have no idea if there is any such list. The specs list only those four that you have noticed. This seems to have been an issue already years ago, but seemingly without any progress. Therefore I'd stick to those four only.
Since Audiveris' MusicXML export contains information about beams, staves and accidentals, it should state it explicitly using the
<supports>
elements in the header like in this example.For example, MuseScore import behaves differently when beam support is present.
The text was updated successfully, but these errors were encountered: