[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: wrong transposition of horn
From: |
Werner LEMBERG |
Subject: |
Re: wrong transposition of horn |
Date: |
Sun, 26 Sep 2004 15:11:45 +0200 (CEST) |
[The last mail to bug-lilypond to keep the thread intact.]
> I think I now understand what you mean. Am I right if your wish is
> semantically equivalent to telling lilypond to automatically convert
> all occurrences of \clef F to \oldBassClef when transposing?
Yes.
> In this case, I don't agree with you.
I withdraw my request. My logic was flawed. Gee, I need a new brain.
> Why don't you use something like this:
>
> sounding = \relative c { c1 | f,1 }
>
> inScore = <<{\clef G s1 \clef F s1 } \sounding >>
> inPart = <<{\clef G s1 \oldBassClef s1 } \transpose f c' \sounding >>
>
> (or even better, use \tag somehow)
Horn parts will stay difficult, since you have to maintain different
clefs for the score and the part. I'm now using this:
bassclef = {
\tag #'score \clef bass
\tag #'hrn { }
}
With other words, no bass clefs in the part by default. In case it is
necessary to have a bass clef, I will use this:
bassclefhorn = {
\tag #'score { }
\tag #'hrn {
\set Staff.clefGlyph = #"clefs-F"
\set Staff.clefPosition = #2
\set Staff.middleCPosition = #-1
}
}
Thanks for convincing me that I'm on the wrong track. I suggest that
an example file is added to lilypond which documents this.
Werner
- Re: wrong transposition of horn, (continued)
- Re: wrong transposition of horn, Han-Wen Nienhuys, 2004/09/25
- Re: wrong transposition of horn, Werner LEMBERG, 2004/09/26
- Re: wrong transposition of horn, Josiah Boothby, 2004/09/26
- Re: wrong transposition of horn, Han-Wen Nienhuys, 2004/09/26
- Re: wrong transposition of horn, Han-Wen Nienhuys, 2004/09/26
- Re: wrong transposition of horn, Erik Sandberg, 2004/09/26
- Re: wrong transposition of horn,
Werner LEMBERG <=