Just dropped in here by accident, but...
I've done this type of thing before. One of the simplest things I've
done is have the database have one table for strings (each record
represents a standard string on the guitar), one table for MIDI entries,
and one table for the actual chord definitions.
I know what you're thinking.
"What the heck do I need MIDI definitions for?"
The MIDI definitions are a numeric reference to a given pitch. for
example, I believe 60 is middle C (C3), 61 is C#/Db. It's been a while,
so that might be wrong.
Having said that, you could have the strings table contain records where
one of the field definitions is what pitch the string is tuned to. If
you were to have a collection of strings for a standard guitar, it would
look somthing like this:
Strings
---------------------------
String_Id Description Tuned_To
--------- -------------------- --------
1 Low E (std. guitar) 40
2 A (std. guitar) 45
3 D (std. guitar) 50
4 G (std. guitar) 55
5 B (std. guitar) 59
6 High e (std. guitar) 64
Now you can calculate pitches based on the MIDI interpretation of the
string tuning plus the offset of a fret. So now you need two more tables
(chord definitions and chord names).
The definition of an open "A" chord would be something like this:
Chords
------
Chord_Id Chord_Name
-------- ----------
1 A
Chord_Defs
----------
Chord_Id String_Id Fret_Offset
-------- --------- -----------
1 1 -1
1 2 0
1 3 2
1 4 2
1 5 2
1 6 0
Let me know if you're totally confused, or totally intrigued.
Sometimes the greatest solutions come from the simplest logic.
Being told "No" is merely the incentive to do it anyway.
*** Sent via Developersdex
http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
