a let­ter to my friend marty:

ahh my most lob­strous brother, my most south-shore-dialect-breathing dragon of post-pilgrim vicis­si­tu­di­nal, non-orthogonal, pere­gri­na­tional tra­jec­tory of johnny-come-lately style and suave sig­nif­i­cance.
…
how i miss thee, like a lit­tle lea­guer miss­ing the rou­tine pop-fly.

like my black, witch-black, even LOVECRAFT-black cof­fee misses the cloudy dis­per­sion of cow cream.
.…
it has most obsti­nately been too long. as they say. in the king­dom of sea-land. where the rules do not pre­vent illicit porn from being stored on servers.

where to even begin? there is too much. rumours always abound– this much, as you say, is true. my jour­ney home will be brief in June, one week­end alone to usher my drummer-friend john ocon­nor in to nup­tial bliss. then i must return for finals and col­lec­tive ass-kicking of my poor lazy or just dumb students.later in the sum­mer, i will be home for a more sig­nif­i­cant period of time. or shall i just say longer, for i do not want to belit­tle the sig­nif­i­cance of my friend’s marriage.

been check­ing out your cthulu doings. you are like a snifter of heaven’s secre­tions, per­haps from some uncharted nether region, a drip­ping off the rhi­zomatic root that buries its hooded cov­er­let beneath the soft­est peat. it is early here, and the words do floweth.

school will be com­ing to a close shortly. which is only to say, they now must ready them­selves for the pitched bat­tle of mak­ing me leave. they are such fools to approach me unarmed. i am teach­ing (read: inflate TAing) in the writ­ing pro­gram out here next year… i will fin­ish my MFA require­ments in Sep­tem­ber (i could actu­ally do it any­time, but i say, fuck them. i’ll teach ‘em to give me a fuck­ing SCHEDULE!). i am right now kick­ing my ASS to throw together a show next week: it will be a clus­tered linux net­work that i pitch into heated bat­tle with another linux clus­ter, where they select files from their own archi­tec­ture, read them as audio files, play the inhu­man screech­ing in vol­leys of artillery at each other. as such, i am :1. try­ing to hack pro­gram a clus­ter– which i do not know how to do, 2. try­ing to hack pro­gram some Arti­fi­cial INtel­li­gence bots to deter­mine each “nodes” behav­iour in the con­flict– which i do not know how to do, and 3. get it all done by next tue­sady– which i do not know how to do.

i enter­tain even myself in moments like this.

i am off to teach in moments… when wil we catch up? you do your self a dis­ser­vice stay­ing in one place… come visit me, and start your wan­der­ings fol­low­ing the path of Alexan­der the Great or Ozy­mandius from the Watchmen.

… burn­ing some ISO images to for­mat the upcom­ing cluster-ish project with mr. Tucker Dulin. Going to get the Planet CCRMA suite of tools on the brain­storm clus­ter. The imme­di­ate premise is to encode a sort of Sound-War, mak­ing some dif­fer­en­ti­ated rule-based pro­files for each node and putting 2 con­nected teams of com­put­ers at odds with vol­ley­ing aural­iza­tion of their own data and pro­gram files. If this sounds con­fus­ing, I apol­o­gize. I will iron out some details later.

Just wanted to give you a state-of-the-distribution update. Cur­rently Jon, Nathaniel, and I are work­ing on a dis­trib­u­tive pro­gram or rather, the mod­i­fi­ca­tion as well as an OS-X port of a dis­tri­b­u­tion pro­gram we think will suit our needs well. Work­ing on this port seems to be the best route to a suc­cess­ful ini­tial dis­tri­b­u­tion project (dwz) instead of the more stan­dard logged inter­faces of exist­ing pro­grams such as IM, etc.. We felt that open­ing up the dwz at this point would result in mostly unpro­duc­tive cacoph­ony, which while being inter­est­ing to the noise-art con­tin­gent, doesnt seem to be the most pro­duc­tive envi­ron­ment to test drive many of our ideas (of course, later, noise will be essen­tial to the inter­face; but at present there needs to be a con­cen­trated effort to decide how and in what ways we want to try and affect noise generation).

The interface/program were cur­rently work­ing on is called the Net­work Text Edi­tor (nte). There has been some ques­tion as to how we want the inter­face to be han­dled, but were all in agree­ment that no mat­ter what, the nte needs to be as has­sle free as pos­si­ble. It seems likely, espe­cially at this early junc­ture, that we may require dwz par­tic­i­pants to down­load a small eas­ily instal­lable pro­gram in order to access the dwz inter­face. This seems like the sim­plest route to an early imple­men­ta­tion. How­ever, later ver­sions will likely try to cap­i­tal­ize on any num­ber of more open-platform tech­nolo­gies, such as a Java run­time envi­ron­ment, in order to over­come OS and other related inter­face issues. There is still some ques­tion, as I men­tioned above, to what degree we will pur­sue both client-side and server-based (not nec­es­sar­ily exclu­sive) options.

In any case, the nte will allow us to achieve some of our early and most impor­tant goals such as a real­time shared edit­ing envi­ron­ment. While we had dis­cussed other direc­tions of data (music, image, etc.), we also acknowl­edged the sim­plic­ity and power of text, and so its to this were giv­ing our great­est focus. From this stand­point the nte will be a bare­bones, no frills envi­ron­ment to ini­ti­ate the achieve­ment of these early goals. For some sim­pli­fied back­ground into the nte see: http://www-mice.cs.ucl.ac.uk/multimedia/software/nte/

Weve also moved for­ward in devel­op­ing a web space and inter­face. One option for an ide­al­ized inter­face envi­ron­ment that was devel­oped can be seen in the image that I have attached for you. We can dis­cuss what you think of the gen­eral struc­ture and direc­tion. At this stage the image/ maque­tte is mostly for hypoth­e­siz­ing and trou­bleshoot­ing our ideal inter­face goals for an user environment.

Hope this helps in detail­ing our cur­rent posi­tion. If things con­tinue as planned we hope to open up an ini­tial test run of the dwz early next week. In the mean­time, we look for­ward to any com­ments or sug­ges­tions you might pass our way. Thanks for all. Yours,
–Patrick [writ­ing in con­junc­tion with Nathaniel and Jon.]

let’s try all this a gain iii­iii sdknv
sd wdfe befh­befn­uo­huoh o oeruh oue houaeh be
kyf tu t ry yjje tye jmet te tye tye
teuymte tme te

edit your blog: yippeeeeee

some more stuff to try

this is a test. will it work

Sean Burke, The Death and Return of the Author: Crit­i­cism and
Sub­jec­tiv­ity in Barthe, Fou­cault, and Der­rida (Edin­burgh, Edin­burgh
Uni­ver­sity Press, 1992).�

quincy troupe recommends..

Cane Jean Toomer

The Col­lected Poem Aime Cesaire

The Heights of Mac­chu Pic­chu Pablo Neruda

Autumn of the Patri­arch Gabriel Gar­cia Marquez

The Star Apple King­dom Derek Walcott

Jazz Toni Morrison

Trilce Cesra Vallejo

Alta­zor Vicente Huidobro

Sun­stone Octavio Paz

Cer­e­mony Leslie Mar­mon Silko

Omeros Derek Walcott

monom … ideas from 1st record­ing: 1. nice if two pitch shift voices inter­play; 2. think tran­si­tions and reap­pear­ance; 3. vari­ance– pitch shift­ing always has same motion and voice.

other pieces

• gran­u­late the whole
• stacatto+verb: think patter
• just the tone gen­er­a­tion– lay­ers of flux­u­a­tion resonance
• more polyrhyth­mic beading
• use con­tact mics… another level of the recording
• con­tact mic feedback
• Lucier-ism