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

Helmholtz-Ellis Accidentals for Just Intonation #263

Closed
000masa000 opened this issue Jun 8, 2018 · 3 comments
Closed

Helmholtz-Ellis Accidentals for Just Intonation #263

000masa000 opened this issue Jun 8, 2018 · 3 comments

Comments

@000masa000
Copy link

Is there any possibility of including the Extended Helmholtz-Ellis JI Notation microtonal accidentals, which are already part of the Bravura Font and smufl, into a future update of MusicXML? I am currently working on improving the polyphonic microtonal playback feature offered in musescore so that it can be driven by accidentals, so it is possible to have automatic microtonal and JI playback from notation. Dorico, for example, is offering a similar support of microtonal playback but in a different way. Would be great if the accidentals could be transferred via MusicXML between platforms and then play back in both environments.
Marc Sabat

@mdgood
Copy link

mdgood commented Jun 14, 2018

Marc, I believe what you are looking for is already available in MusicXML 3.1. The <accidental> and similar elements like <accidental-mark> and <key-accidental> now have a smufl attribute where you can specify the exact SMuFL glyph for any of the accidental ranges. For most of the Extended Helmholtz-Ellis range, you probably want to use "other" as the value for the accidental element, e.g.

<accidental smufl="accidentalFlatThreeArrowsUp">other</accidental>

If one of MusicXML's standard accidental values matches the sound but not the appearance, you can use that value instead instead of "other".

You will want the <alter> element to specify the microtonal value in addition to the <accidental> element for the best chance that applications can interpret one or the other correctly.

Does this match what you are looking for?

@mdgood
Copy link

mdgood commented Mar 18, 2019

@000masa000 Did the existing MusicXML 3.1 features work for you? Or is there something additional that you believe is still needed to get this working well? Thanks!

@mdgood
Copy link

mdgood commented Sep 10, 2019

I am closing this issue as I believe it is working in MusicXML 3.1. If there are problems please let us know so we can reopen the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants