lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Transposing an entire score


From: Flaming Hakama by Elaine
Subject: Re: Transposing an entire score
Date: Tue, 7 Nov 2017 16:52:24 -0800


On Tue, Nov 7, 2017 at 1:25 PM, Simon Albrecht <address@hidden> wrote:
On 07.11.2017 20:13, Flaming Hakama by Elaine wrote:
Looks like all you'll need to do is change one file:
parts/01-ego_flos_campi.ly <http://01-ego_flos_campi.ly>

replace all instances of  "\relative" with "\transpose a, c \relative"

Why? That would only make sense if you used the same variables in different scores and wanted to transpose all of them


I answered the question that was asked.
And it makes sense: to transpose music, you use the \transpose function.
The entire thing is being transposed, so every music definition needs to be transposed.

If there were any other requirements, perhaps a different approach would be warranted.

This can be adapted for any other key in less than a minute with search + replace.

Your comment about using the same variables in different scores is a little off.
For one thing, this file is used in multiple scores.
Also, if we assume that all the variables defined in the file are one piece, then yes, they should all be transposed.  What is your use case for only transposing some of them?

 
– even then you should certainly use a variable:
newTonic = as
\transpose f \newTonic \relative { … }

I agree that using a variable is probably better practice in general,
but doesn't really yield any major benefits in this situation.

 
But if that’s not the case (which it rarely is), the duplication is totally uncalled for.

However, using a variable doesn't really reduce any repetition, at least not of the music.

Which is to say, if you are concerned with publishing in more than one key,
you still need a different file per key, thus repeating all the musical content.


More modular approaches that does not duplicate the musical content might include:

* Use the \newTonic variable in the music definitions file, as you suggest.
Create one (or more) files that only define the newTonic
Include one of these newTonic-defining files before including the music definitions file

* Use some kind of command line option to specify the new tonic, and assign newTonic to this value
Then include the music definitions file after this assignment.




David Elaine Alt
415 . 341 .4954                                           "Confusion is highly underrated"
address@hidden
self-immolation.info
skype: flaming_hakama
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

reply via email to

[Prev in Thread] Current Thread [Next in Thread]