[frogs] Re: Capo-ChordNames |
[ Thread Index |
Date Index
| More lilynet.net/frogs Archives
]
On 10/08/10 01:05, Carl Sorensen wrote:
> If you are fine to have the Capo chord names and the non-capo chord names
> stacked, then it's possible to do something like:
>
> myChords = \chordmode {
> c1 g f:7 c
> }"
>
> <<
> \new ChordNames = "capoNames" {
> \transpose c b {
> \myChords
> }
> }
> \new ChordNames = "originalNames" {
> \myChords
> }
>
> Which is what Trevor was suggesting.
>
> And a music function could probably be written to make all of that happen
> automatically
>
> e.g.
>
> \capo 3 \myChords
>
> could be used as syntax to do the transposition and create both ChordNames
> contexts.
>
> Of course, this wouldn't handle the horizontal setting; to do that you
> really would need to modify the ChordNames engraver.
>
Ah... but the horizontal setting is the norm. Sounds like you've guessed
correctly what I meant by vertical|horizontal. And the transposed chord
is ALWAYS parenthesised - how easy is that in a music function? So let's
say I'm in the key of C, capo=3 (weird example I know, but never mind),
and I want to actually have a C chord. It normally prints as "C (A)",
but in vertical mode it would print as
C
(A)
(centred, of course).
I'll take the engraver route, and hope I don't need TOO much
hand-holding (cf Graham's talk :-) If it gets me into Scheme and C++
I'll be well pleased.
I'll look at your long email, probably respond, and then hack at it and
come back with more questions :-)
Cheers,
Wol
---
----
Join the Frogs!