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

Suppress redundant natural signs #2

Open
n-armstrong opened this issue Sep 14, 2024 · 1 comment
Open

Suppress redundant natural signs #2

n-armstrong opened this issue Sep 14, 2024 · 1 comment

Comments

@n-armstrong
Copy link

n-armstrong commented Sep 14, 2024

Firstly, thanks for making this package. It's both powerful and intuitive!

I'm wondering if there could be a way to suppress the 'natural' accidental when it is redundant, i.e. when it is prepended by accidentals for the septimal comma and beyond. Instances would be the 3x11, 7x11 and 3x7 in the Wilson Hexany example. To my eyes the 'natural' in these instances create unnecessary clutter.

Thanks for your help!

@levinericzimmermann
Copy link
Owner

Hello @n-armstrong! Yes I see what you mean. I think the purpose of the naturals are to prevent:

nonatural

\version "2.24.1"
\language "english"
\include "ekme-heji.ily"
{
    aoaaoba'2
    aoba'
}

which looks a bit confusing to me. However if you wouldn't mind about this, we could very easily generate and add something like a ekme-heji-simple.ily file.

Generally I think the very best would be to teach Lilypond to automatically decide if there should be a natural or not. But I think this is outside the scope of ekme-heji.ily which is really quite simple. The second best option would be to provide two versions for all pitches with the natural accidental. Then users would need to explicitly decide whether it's okay or not to skip the natural accidental. If the Lilypond code is manually written, this would be quite tedious. However if it's algorithmically generated, this may be ok. What do you think of this? How should we name pitches without the natural accidental?

Did you already see heji-ly? It takes a more flexible and advanced approach of HEJI Notation in Lilypond.

Best, Levin

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

No branches or pull requests

2 participants