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
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.
The text was updated successfully, but these errors were encountered:
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.
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).
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.
The text was updated successfully, but these errors were encountered: