[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Chord library
From: |
Sébastien Gross |
Subject: |
Re: Chord library |
Date: |
Thu, 21 Dec 2006 23:52:30 +0100 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
On Thu, Dec 21, 2006 at 09:05:20AM -0800, address@hidden wrote:
> Yes, as Mats said please check out the FretBoards context, I sponsored it!
>
> It will allow you to transpose fret diagrams and enter fret diagrams using
> standard lilypond notes, it will auto detect the strings for minimal hand
> stretch and position shifts, etc. recognizes all the base class properties
> for staff alignment, duration, etc.
>
> Building a chord library upon the foundation of the FretBoards context
> should be a snap because most of the work is done for you already. I'm
> still trying different approaches to my own chord library, right now I'm
> leaning toward using \tag where some note clusters give the chord name and
> others in each collection give the various fret fingerings, then I just
> extract the notes I want into the music using \keepWithTag either in
> FretBoards or ChordNames context. My library only needs all the chords
> stated in the key of C then I use \transpose in the piece proper to move the
> library chords up/down the neck to different root notes.
Yes I saw it but I didn't find so much doc on it (maybe my fault ;-/ ).
Nevermind, I would be glad to use the FretBoards context to build a
chord lib.
Please note I originaly started to write thios lib to save (?!?!?) time
when facing similar chords.
I will have a closer look on it.
On an other hand, I am still facing to a human readable naming
convention as long as names only accept letters.
Cheers
--
Sebastien Gross
Re: Chord library, Sébastien Gross, 2006/12/21