Replies: 2 comments 1 reply
|
Sadly, no replies. Shall I open an issue for this? |
0 replies
|
The spec is clear that |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have a score (created by Capella and converted to MusicXML with its
CapToMusic.pyscript version 2.5 some years ago) that contains measures like the following.This is fully valid MusicXML but semantically invalid AFAICS (so it might be a candidate for issue #621). Looking at the original PDF, the intended output seems to me purely visual, namely to create a time signature after a bar line at the end of a staff:
I've loaded the original
.mxlfile into MuseScore and Finale, and both programs create a measure with a rest in it, i.e., they are trying to 'fix' the input, and which actually worsens the result (musicxml2lydoes the same, BTW 🙂).I wonder whether there are valid use cases for
<measure>elements that don't contain<note>. Otherwise the<measure>specification could change from 'zero or more' to 'at least one' for<note>.All reactions