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

Handle one file with parts #3

Open
rettinghaus opened this issue May 25, 2018 · 3 comments
Open

Handle one file with parts #3

rettinghaus opened this issue May 25, 2018 · 3 comments

Comments

@rettinghaus
Copy link

Perhaps a more generic approach would be, to input one file with different parts then multiple files with one score each, i.e. merge the files prior to processing, so that one piece of music is encoded completely in one file, and then use that as an input.
I think, that would be a great improvement, as, when separated into python modules, the program could be more easily re-used by different projects.

@rettinghaus
Copy link
Author

(or make it an option?)

@rettinghaus
Copy link
Author

My idea was to have all parts encoded as a <part> within <parts> instead of using <score> in different files. This is how MEI is meant to be used.
So you have your complete edition of the source in one file, and this then could be scored-up.

@martha-thomae
Copy link
Collaborator

Thanks! Yes, this was clear. I just meant that I was tackling these two issues (#3 and #2).

Even though I think that <parts> is the best way to encode the music in parts (such as mensural music), I don't like to use it because I cannot render it in Verovio (so I cannot quickly see if there was an error in the file that is to be processed by the scoring-up tool).

Anyway, I am working on this now :)

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