-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Add support for MEI export and import of MuseScore IDs #22978
base: master
Are you sure you want to change the base?
Conversation
src/project/qml/MuseScore/Project/internal/Export/MeiSettingsPage.qml
Outdated
Show resolved
Hide resolved
Great, thank you. Still two problems with the current approach:
Try this file to see duplicated IDs: Also there needs to be an additional check on assigning them on load if they are valid. |
…age.qml Co-authored-by: Casper Jeukendrup <[email protected]>
Yes, this needs to be documented and users should be explained MuseScore IDs should not been edited or made up. I am planning to add that in the documentation.
Yes, this should be fixed, but it can be done separately since this is not strictly related to the MEI exporter. |
Adds an option so enable the use of MuseScore EIDs in the MEI export.
The option is not selected by default at this stage.
When selected, MEI elements take the MuseScore EID as
@xml:id
whenever appropriate, always prefixed withmscore-
The LastEID is stored in the
mei@xml:id
, also prefixed withmscore-
. The values are preserved in the importer. When re-exporting the file, only themei@xml:id
is expected to change in the same way is does with MuseScore files.