Well, yeah. I was just kidding (although I have talked to a guy, a web master for a fairly large website who was complaining that he was getting bored with analyzing the data and stuff. I suggested we put the data to music and see what it sounds like and he liked the idea...).
I would mainly be interested in using the database as a "scratch pad" to store and manipulate various musical events. So, how fast is the response to queries?
So, why not making it available?
./MiS
On Wed, 07 Mar 2001, Iain Mott wrote:
Yes indeed - but as a slightly more realistic suggestion, Postgres can be used as a means of finding matching sounds. Eg. If recorded sounds are analysed for features such as pitch envelope, centroid envelope, duration etc - and this data is placed in tables, one can find "matches" for new sound fragments by searching for files in the database with best fitting characteristic (ie. run searches on the basis of the least error).
Cheers, iain
-----Original Message----- From: Michal Seta [mailto:mis@music.mcgill.ca] Sent: Thursday, 8 March 2001 4:24 AM To: pd-list@iem.kug.ac.at Subject: Re: some externalernals
I'd be interested in that one. It'd be fun to turn sales into music (although the other way around would be nice, too).
./MiS
On Thu, 22 Feb 2001, Iain Mott wrote:
One thing not included (amongst a few more) is a simple Pd interface to PostgreSQL - allows you to send SQL commands to a database and retrieve
the
results. If anyone's interested in this - let me know and I'll scrape it together.