Your skill will accomplish what the force of many cannot |
|
PerlMonks |
Re^5: Reciprocating to the perl communityby Ambidangerous (Scribe) |
on Jun 03, 2004 at 12:05 UTC ( [id://360086]=note: print w/replies, xml ) | Need Help?? |
Actually, I want my program to be rather small. I'm following the Linux model of small programs that can interface with other, share data, and provide services for each other--as opposed to the Windows idea of the single program megalith (that crashes all the time and is packed with bugs). To get an idea of the type of program I'm talking about, have a look at PG Music's "Band in a Box." That, unfortuantely, is a $50 to $250 megalith that does everything (music input, sequencing, printing, etc). Also, it's proprietary, and only works well on Windows (one of my band members has a Mac and BIAB has *never* worked for him). I don't want my program to *produce* sound. I want my program to be able to write files that someone can put into their favorite sequencer, midi program, etc. So there's no need to worry about real time output. I want to be able to dump files so someone could print them in whatever program they already have (Finale, Lilypond, etc.) As far as organizing your tune collection, you should be able to dump into csv or some convenient data format for use in a db or spreadsheet. Think of it as a compiler for sound files. The input is a human readable language, the output is machine readable sound instructions. The problem is, you have to write the machine instructions so that the human articulation, feel, and timing comes through. As you said, I'm trying to essentially build an AI, so that practically demands something capable of deep pattern analysis (eg Perl). About synth sound: thanks for the tip on Logic. Also, strangely, one of the most complex musical sounds out there, a grand piano, can be modeled fairly effectively now--I just wonder why upright bass is lagging so far behind.
$jPxu=q?@jPxu?;$jPxu^=q?Whats?^q?UpDoc?;print$jPxu;
In Section
Seekers of Perl Wisdom
|
|