Forums before death by AOL, social media and spammers... "We can't have nice things"
|    rec.music.misc    |    Music lovers' group    |    3,169 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,259 of 3,169    |
|    colonel_hack@yahoo.com to clayvernon@gmail.com    |
|    Re: Need help with my chord analysis pro    |
|    29 Jul 05 14:22:54    |
      XPost: comp.music.misc, comp.music.research, rec.music.theory              On Mon, 25 Jul 2005 clayvernon@gmail.com wrote:              >       >       > Could I compile this with GCC on a Mac?       >       >       >       >       >       The program compiles under FreeBSD w/ the -lstdc++ flag and StdAfx.h       renamed stdafx.h [which appears to check vc version and do nothing about       it...] So it should compile on a mac.                      The output is slightly different that the included F-A-Db-tuning.txt       file. The chord part of the output starts with an F chord but the file       starts with F#/Gb (possibly a fencepost type error?) Is it from the same       version?              What are lines 1,2 and 4 of the output tellin me?               0 ***************************       8 9 10 9 10 11 10 11 12              F A C#/Db F A C#/Db       0 4 4 4 4 4              On Fri, 22 Jul 2005, techbear wrote:       > The heart of the program is the JudgeFitness() function, which is in       > charge of looking at a single chord fingering, and determining its       > score, a measure of how easy this chord seems to be to play.       >       > the current JudgeFitness() test is simplistic and non-optimal. A       > better way to construct the function might be to somehow model my       > fingers, examining exactly how I would place each finger on each       > string. I haven't got a clue how to do that, yet. :)              A comment or two in this part of the code would be nice, If it could know       about bars and partial bars --You might make and that it's easier for       different fingers to be on different frets if the are on adjacent strings       above a bar. Possibly you could give bonus points if the lowerest few       strings are on the same fret and the higher string are all fretted higher,       and if a single string is really hurting the score, drop it, especially if       it is the highest or lowest. And you might even give bonus points for       matching a regular chord pattern that you find easy to make --this would       probably be good for a version/mode that lets you input a set of chords       for a particular song and looks for a tuning for it. Play something       normally impossible w/ just open C A E G and D forms...              > The .importance member of the ChordType class is especially arbitrary.       > It's a weight so that major and minor chords (hopefully) come out more       > easy to play than augmented and diminished chords.              This could be easily weighted to find a tuning for a particular song       too...              > I assume I'll       > mostly play major and minor chords. However, I don't really know the       > true universal chord distribution across all popular songs, or even all       > songs I play. I have some ideas about how to find out, though...       Alternately, the major and minor are harder cus you play them all the time       so you'll learn 'em, and the occasional augmented and diminished are easy       so you can drop to them easier when you barely know them (theown out for       consideration w/ no claim it's a good idea)               3ch              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca