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
As the Musescore files (mscx) are XML-based, versioning them with git is not trivial.
I thought of discovering the idea of creating a new file format that is based on instruction lists that describe the score bit by bit, an example:
part -id 1 -name "Clarinet in B" -instrument-id "wind.reed.clarinet.bflat"
...
With this, the file format is more like a step-step guide for the program on how to build a score.
As it could then be line-based, it is way easier to read and version these files.
Manual tweaking is also way easier and programmatic generation could be eased.
An other approach that is not XML is possible, too.
This issue is more a discussion issue to explore possibilities into this direction.
Problem to be solved
Versioning Musescore scores is difficult, but sometimes beneficial.
The XML format of the current musescore files is pretty bad when trying to version it.
Sometimes, it is also beneficial to automatically merge multiple scores into one.
A text-based file format could use git in helping with that.
Prior art
No response
Additional context
No response
Checklist
This request follows the guidelines for reporting issues
I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests
The text was updated successfully, but these errors were encountered:
Your idea
As the Musescore files (
mscx
) are XML-based, versioning them withgit
is not trivial.I thought of discovering the idea of creating a new file format that is based on instruction lists that describe the score bit by bit, an example:
With this, the file format is more like a step-step guide for the program on how to build a score.
As it could then be line-based, it is way easier to read and version these files.
Manual tweaking is also way easier and programmatic generation could be eased.
An other approach that is not XML is possible, too.
This issue is more a discussion issue to explore possibilities into this direction.
Problem to be solved
Versioning Musescore scores is difficult, but sometimes beneficial.
The XML format of the current musescore files is pretty bad when trying to version it.
Sometimes, it is also beneficial to automatically merge multiple scores into one.
A text-based file format could use
git
in helping with that.Prior art
No response
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: