[EMAIL PROTECTED] writes:
> circumstance, I would imagine that the FretDefinition would need a
> duration, but the duration comes from the chord, so again, it seems that
> the FretDefinition is tied to the chord, and probably shouldn't be a
> separate music object.
>
> I view the \diagram as a mod
On Fri, 2004-11-19 at 07:38, Han-Wen Nienhuys wrote:
> * I suppose that this is still too difficult for "normal" users, and
> that we should also have an option
>
> a. to override fret diagrams for once, eg.
>
> \chordmode { d:add9 \frets "abc9312" }
>
> b. to override a fret diagram
[EMAIL PROTECTED] writes:
> On Sun, 2004-11-21 at 05:25, Han-Wen Nienhuys wrote:
>
> > I think that
> >
> > a. we are storing chords in the wrong way. In retrospect, I find
> >
> >root + list of (step, alteration) tuples
> >
> > more logical
>
> So rather than using the pitches as the key
On Sun, 2004-11-21 at 05:25, Han-Wen Nienhuys wrote:
> I think that
>
> a. we are storing chords in the wrong way. In retrospect, I find
>
>root + list of (step, alteration) tuples
>
> more logical
So rather than using the pitches as the key for the hash table, it ought
to be the chord str
On Sun, 2004-11-21 at 05:15, Giancarlo Niccolai wrote:
> Uhm, since you are working on the chords: is there any possibility to have
> chord names also in other languages? I.e. Am in italian is LAm, Bsus4 is
> SIsus4 (only the note name changes, the chord system is the same all over the
> world)
On Sun, 2004-11-21 at 09:24, Han-Wen Nienhuys wrote:
>
> there is nothing stopping you from entering the chord in \chordmode, i
> believe,
>
> exceptions = \chordmode
> {
> c:dim7-\markup { \fretdiagram "sitnhsoit" }
> }
>
> for ideas, check chord-modifiers-init.ly
>
[EMAIL PROTECTED] writes:
>
> This is a good idea. It's got a lot more flesh on it than the skeleton
> I had worked out. I'll have to study the code some more in order to
> have all this make sense to me.
>
> I'd still like to have some syntax that allows me to enter a fret
> diagram for a chor
[EMAIL PROTECTED] writes:
> will produce two chord labels (both D), and two FretDiagrams (which will
> be different items from the hash table). I think this feature could be
> convenient for those who may prefer to have multiple fret diagrams for a
> chord in a piece.
>
> What do you think?
I th
Alle 04:17, domenica 21 novembre 2004, Carl Sorensen ha scritto:
> In working on this, I discovered another way to handle different fret
> diagrams for the same chord. ChordNames ignores the octave of the
> Chord, but chordmode keeps the octave. That means that we can access
> different fret dia
Alle 04:17, domenica 21 novembre 2004, Carl Sorensen ha scritto:
> On Fri, 2004-11-19 at 07:38, Han-Wen Nienhuys wrote:
> > * Although it is possible to make a #(set-fret-diagram-string ) , I
> > think we can use the mechanism now used for chord exceptions, ie.
> >
> > * I suppose that this is stil
On Fri, 2004-11-19 at 07:38, Han-Wen Nienhuys wrote:
> * Although it is possible to make a #(set-fret-diagram-string ) , I
> think we can use the mechanism now used for chord exceptions, ie.
> * I suppose that this is still too difficult for "normal" users, and
> that we should also have an opt
On Fri, 2004-11-19 at 07:38, Han-Wen Nienhuys wrote:
> * We tack frets onto \chordmode{}, that is, we do
>
> chordScheme = \chordmode { d }
>
> << \new FretDiagrams \chordScheme
> \new ChordNames \chordScheme
> >>
>
> The \chordmode produce . In Fret_diagram engraver (contained
> in F
[EMAIL PROTECTED] writes:
> I've been exploring the architecture of the FretDiagrams context.
>[snip]
> I have some questions as I begin to implement this architecture.
>
> 1) Does the basic architecture make sense?
>
> 2) If this architecture looks OK, what symbol might be available to
> introd
D to C, I don't
want to keep the same notes on the same strings but dropped two frets.
I want to move to a C chord structure, which is entirely different.
Based on these results, I've decided to propose yet another FretDiagrams
architecture. In this architecture, I'd have a big alist
14 matches
Mail list logo