Re: "smart" transposition of key signatures

[Janek Warchoł]

2013/10/7 Urs Liska <address@hidden>:
> Am 07.10.2013 16:55, schrieb Kieren MacMillan:
>
> Hello all,
>
> I've got a piece in which the key centres move thusly:
>
>    E major  -->  F minor  -->  A major  -->  F major  -->  E major
>
> I need to transpose it up a few pitches, as it was originally written for
> medium voice, but is going to be sung by a high[er] tenor.
>
>   \transpose e g ==>    G major  -->  G# minor  (= B major) -->  C major
> -->  Ab major  -->  G major
>
> would be great… except what's actually happening is
>
>   \transpose e g ==>    G major  -->  Ab minor  (= Cb major, with 7
> flats!!!) -->  C major  -->  Ab major  -->  G major.
>
> Is there any way (like the "naturalizeMusic" function for individual notes)
> to ensure that the key signatures in a transposed piece are the "most
> logical"?
>
> Thanks,
> Kieren.
>
>
> Not that I know of. And from my experience "naturalizeMusic" is a very bad
> idea for that purpose.
> Do these articles help you any further:
> http://lilypondblog.org/2013/06/transposition-with-enharmonic-changes-part-1/
> (follow-ups linked in text)
> ?

I was just going to send this link ;-)

Also, you may be interested in this:
https://github.com/openlilylib/snippets/blob/master/input-shorthands/late-evaluation-of-variables.ly

best,
Janek