Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

<supports> elements in MusicXML export #710

Open
olin256 opened this issue Dec 28, 2023 · 2 comments
Open

<supports> elements in MusicXML export #710

olin256 opened this issue Dec 28, 2023 · 2 comments

Comments

@olin256
Copy link

olin256 commented Dec 28, 2023

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.

@hbitteur
Copy link
Contributor

@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?

@olin256
Copy link
Author

olin256 commented Jan 2, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants