> > But I would also like to automatically transpose these parts for
> various
> > instruments. When I use the \transpose function it transposes the
> notes
> > and not the chords. Is there a way to make the chord names visible
> to
> > the transpose mechanism so that the whole piece including chord
> symbols
> > can be transposed?
>
> No.
>
Not without doing any coding, that is. It should be
not too hard to implement, if you what you want.
> Patches appreciated :-)
>
Which means, i guess, that we don't know all the details
about chords and all the chord-names. And, although it
would be nice if Lily could handle chords, it is not
high on the priority list; there are a lot of things that
would be nice to have.
The first thing to do is to figure out what functionality
we actually need/want.
Some assumptions
Chords can be uniquely identified/represented in three ways:
* using names such as "Cmin7" "Ebmaj9"
* identify the lowest note, and list all other notes
relative to this one; "C: mi-flat, sol, ti"
"Es: mi, sol, re"
* use a list of pitches "<c es g b>" "<es g bes f>"
We'll probably want to represent a chord internally using
a list of pithes.
We'll probably need to devise a "language" that allows one
to enter the chords in a way that closely resemles their names.
How to do
* major/minor
* augmented/diminished?
What we eventualy need is a new type of "staff", ChordStaff
that typesets the chord names e.g. "Cmin7" "Ebmaj9".
Which all means that we need to be able to translate chord
names into pitches and vise versa (Johan, you already had some
ancient code for this?).
Any takers?
Jan
Jan Nieuwenhuizen <[EMAIL PROTECTED]>| GNU LilyPond - The music
typesetter
http://www.xs4all.nl/~jantien |
http://www.xs4all.nl/~jantien/lilypond
