Closed th-we closed 7 years ago
Originally I didn't want to rely on oct.ges
. So I tried to "fake" it (which obviously only works with standard G clefs).
I'll give it some thoughts.
I'll try to take care of it by using the \transpose
approach, at least to the extend that's manageable right now. It might be restricted to <octave>
with @startid/@endid
and a single voice. That would at least cover some use cases, but not others.
this should be ok now
In MEI it seems common to encode written pitch with
@pname
/@oct
so to say "ignoring" ottava brackets (at least that's what one find in the samples). Sounding pitch can optionally be encoded with@pname.ges
and@oct.ges
. Lilypond however wants the resulting transposed pitch encoded.That's not really a problem - I'm currently thinking that I might wrap notes of an ottava bracket inside a
\transpose
. What I don't understand is what\unset Staff.middleCPosition
actually does. In any case it does weird things, e.g. for this example:My plan would be:
\unset Staff.middleCPosition
and use\transpose
instead\transpose
optional as I'm not sure how thought through the convention found in the sample library is and one might want to encode "sounding" pitch rather than written pitch.Any better ideas?