> you type the code on the screen, and it actually executes the
> code as you type it, but all the visuals are made of the onscreen code
> too
hi amy, rest,
curious to see your setup. checking those screenshots as sending this.
let me brag a little below (not)...
i did a disasterous gig exactly a year ago in the south of sweden using
something similar. one and only time i had my now defunct
supercollider2 redFrik livecoding framework running which was er...
more about routing sounds through effects, changing tempo, fading
in/out things with a syntax interface - not true livecoding. it just
looked cool.
in the background i had my max/nato videopatch and it grabbed a small
area of the screen. whatever was in that area got passed through 2-3
effects, scaled up to fullscreen and sent to the beamer. the
trashing/pixelating video effects were in turn controlled by parameters
in the music (iirc tempo and drumfile loopingpoints (bbcut info)). so
the code was visually transformed in sync with the sound.
it was a big event and i screwed up totally. didn't rehears due to
coding to the last minute and my brain went into schimpansee mode as
always when performing. couldn't keep all things in my head
controlling both video and music so both stagnated for long periods of
time while i tried to think clear. add to that the projector was crap
and my video effects possibly a little too brutal so the mess was
totally unreadable :-( me still shivers when thinking about it. so i
figured i need to start rehearse livecoding on a daily basis as any
instrument and also fully automate certain things (like the video part)
and that's where i'm still at.
my framework did have one nice feature tho. a command like filling a
pattern with 60% random hits could be undone with the revert n steps
command.
o.send("/punkBassdrum/patAmp",16,0.6); //fill with new
o.send("/punkBassdrum/patAmp",\revert,1); //go back to previous if bad
or similar filling a pattern with random pitches between 20 and 60.
with revert i could jump back to good sounding patterns. just needed
to remember which index was good sounding -sigh.
o.send("/punkBassdrum/patPitch",16,20,60);
o.send("/punkBassdrum/patPitch",\revert,1);
no cure for the halting problem but having safe positions, in this case
good sounding settings, to retreat back to as you branch out i think is
vital. like a mountain climber at regular intervals drilling for firm
stops. and these couldn't be prepared in advance - they're made up as
you go.
_f
#|
fredrikolofsson.com klippav.org
|#
Received on Sat May 22 2004 - 11:54:41 BST