Re: Transposing an entire score

[Flaming Hakama by Elaine]

 

From: Francisco Vila <address@hidden>
To: Flaming Hakama by Elaine <address@hidden>, Simon Albrecht <address@hidden>
Cc: peter bach <address@hidden>, Lilypond-User Mailing List <address@hidden>
Bcc: 
Date: Wed, 8 Nov 2017 12:42:59 +0100
Subject: Re: Transposing an entire score
On 08/11/17 01:52, Flaming Hakama by Elaine wrote:
>
>     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.

This is true, but I think what Simon says is that it is better to leave
the music definitions in concert pitch and transpose the choir staff
only, which is a single << >> music _expression_.

Transposing every definition does work indeed, but it is a potential
source of problems for reusing that music (maybe in another
transposition) unless you want the music definitions transposed at
origin once and forever, for some reason.

--
Francisco Vila. Badajoz (Spain)
paconet.org , csmbadajoz.com

I'll bet that no one else actually looked at the example provided.

Sure, you can \transpose at the score level;
This is my normal practice as well.

However, in this example there were multiple scores across multiple files.
Whereas the music variables, including \key's, were all in one file.

So, actually executing the score-based approach with this project

is a considerable amount more work than what I suggested,

and has higher risk, given that the OP was having such a basic issue.

David Elaine Alt

415 . 341 .4954                                           "Confusion is highly underrated"

address@hidden

self-immolation.info
skype: flaming_hakama
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-