-
Notifications
You must be signed in to change notification settings - Fork 12
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
Support for <supplied> #17
Comments
The |
Thanks for reporting the bug. I will look into it. |
Found the problem. This is a typical MEI ambiguity situation, basically a mishmash of information from the graphical and gestural domain where meico has to make the most reasonable choice, even though counter-intuitive at first glance. When processing the In other words, as MEI-wise the semantically correct encoding for this case would be to add |
Hm, ... I keep thinking about it. What I might do is, that such an accidental can propagate up to the |
@axelberndt, I think, you outlined the solution already. MEICO could simply take the information in all |
I have implemented this and tested it. ... Basically, it works in your case BUT the following will sooner or later happen. Therefor, you have to keep in mind that
What I did so far was keeping the ambiguous By the way, the same happens with the regular I am surprised that no one stumbled over this, yet. With this new change, however, it becomes more likely to happen. Before I make a new release I would like to hear some opinions. |
Having been asked on separate channels to comment on this, I don't really see the problem of propagation. If someone supplies |
Alright, thanks Till for reporting the issue and thanks Norbert and Johannes for your opinions, as always very plausible and convincing. The new release version is online. |
Meico seems to skip elements wrapped by a
supplied
element. This becomes particularly evident in cases of editorial additions of accidentals.In the following example, all three notes should sound alike, but Meico plays the third one as c natural.
In the first measure, the sharp is coded as an attribute, in the second measure as an element which is an equivalent to the coding in the first measure; in the third measure, the sharp is wrapped by a
supplied
element, marking it as an editorial addition. The sounding pitch should remain the same, i.e. c sharp. As a fix, Meico should just ignore thesupplied
element, leaving theaccid
intact however.The text was updated successfully, but these errors were encountered: