On 9 Mar 2015, at 19:48, Flaming Hakama by Elaine < address@hidden> wrote:
This one transposes up from c to d...
…but because the scale goes up as c d e f g a b c’, this one transposes from bes (just below c’) down to c - a minor seventh DOWN.
Relative pitch (in the lilypond \relative sense) isn’t involved here, only the interval between “current key” and “new key” (which is an upward movement in the case of c to d, but downward in the case of bes to c).
In a simple version, I would write \TheHead and \TheChords in the target key, and transpose them at the \book stage for the various instruments. This has to be done in eight different places, and is prone to error.
This is why I defined functions for the individual instruments that need never be changed, and did the concert key transposition using \PieceTranspose - only one character to change!
Indeed, it does do nothing as it stands, but it’s there so that all I have to do when I want to transpose the whole piece up a fifth is to change the “c c” part to “c g”.
I do use the functions several times - once for each instrument.
OK. The choice there is either to compile the file three times, adjusting \PieceTranspose in the sequence c c then c f then c a, or to make two more copies of the book-generating section, with (e.g.) \PieceTransposeFourth and \PieceTransposeSixth in between.
This would make it all a bit unwieldy, and as I want to be able to share this with novice LilyPond users, I don’t want the make the file too long or too clever!
This comes to the same thing, but uses two extra variables.
But I can see the advantage in doing this in terms of clarity if it comes immediately after the definition of the PieceTranspose function.
I’m trying to keep all the stuff that has to be changed for a given piece in the top part of the file, and ensure that I don’t have to fiddle with the final part - less scope for error if I don’t have to remember to fix up whole piece transactions for the four different parts.
Thanks for your help in clarifying my thoughts!
Michael
|