-
Notifications
You must be signed in to change notification settings - Fork 185
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implementation for issue MeasuringPolyphony/mp_editor#62
- Loading branch information
Showing
3 changed files
with
191 additions
and
51 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
ae6b495
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This commit does:
(1) Move
<staff>
to<section>
and remove<measure>
for**mens
-to-MEI conversions(2) Allows for mensuraion sign to change in the middle of the music
(3) Add a temporarily allowance of
<staff>
on<section>
, which can be changed to a more proper way of doing it later. In any case, the output MEI data from verovio says MEI-all, so in that case staff should be allowed as a child of section.Test example:
Humdrum data:
MEI conversion:
ae6b495
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@craigsapp think you can solve this issue differently. Namely keep the Measure but mark it as 'unmeasured' with
new Measure(false)
see https://github.com/rism-ch/verovio/blob/256a6e2f41f0a0c3e1991c17d9baced7a3507322/src/iomei.cpp#L3102-L3106. (The Measure object will not be written in the MEI output)The you can probably remove the change in
Object::AddChild
. Can you try it?ae6b495
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I can try it (probably tomorrow). Should there be one measure for such an example:
Or would there be one measure starting at each mensuation/key change?
ae6b495
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Both should work. To get the same as you have now I think it should be one measure.
ae6b495
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I think one measure is best since the goal will be to encode the system breaks (which will match the measures).