You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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.
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!
The text was updated successfully, but these errors were encountered: