I think any solution that computes it right there is superior to this huge preset table. Well actually I'm curious, because it's truncated to 8 places of decimal afair so I wonder whether anybody with very good musical ears can say how well that works, assuming I got the basic data dump right. What the table offers that a computed solution doesn't is the names, which are in the the CLM catalogue, so you have a handle on the scales instead of trying to remember a sequence of coefficients.
btw what are the proper replacements for unsymbol, list2symbol and tosymbol - some people aren't finding them, what should I use instead? cheers, a.
On Wed, 25 Oct 2006 10:04:45 +0200 Frank Barknecht fbar@footils.org wrote:
Hallo, padawan12 hat gesagt: // padawan12 wrote:
I don't have a musical enough ear to have a clue whether this does entirely what it's supposed to. Any ideas? Has this been done before? To be proper I think it needs to work on the original integer ratio data so it computes at the accuracy of the machine running it.
I did something similar, but much simpler, with [tunetof], which is a replacement for [mtof] using different intonations. The intonations are specified as a simple table which maps "notes" to frequencies. These tables can be generated from tuning files in Scala's file format using a Python script supplied with [tunetof]. Both are available in CVS at /abstractions/footils/tunetof/
[1] http://www.xs4all.nl/~huygensf/scala/scl_format.html
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list