modules to work on: 21:02 (tech_notes#41)

a) liblo: http://liblo.sourceforge.net/ - based commandline modules/sniffers b) ssc/sc modules c) pd OSC modules d) jack drainers/OSC drainers e) scheme/prolog query-ers f) jekyll samplers and timeslicers on commandline (pipers) or in pd/sc

should test some connectivity infrastructure with pipes/OSC and all apps

raw as possible

what else?

packet forth pf link: 17:22 (tech_notes#40)


not getting so far with xdv tcpdump2OSC and friends 17:16 (tech_notes#39)

possibly better write some smaller C clients using liblo

specification of modules 12:47 (tech_notes#38)

1) substance 2) alice 3) jekyll 4) pink light 5) h bomb/audience simulation - simulation made evident

leakage 12:42 (tech_notes#37)

leakage is implied by sniffer functionality (for example OSC conversion ones below from gulli people). further leakage of OSC and jack itself could be coded. pipes also by way of kernel patch - where is pipe code in kernel?


what would determine moment of leakage - some trigger in the data itself matched across a changing sequence - a neuron or series of connected neurons which sniff the data and trigger/balance leakage -

(and is better break up over day tech and other notes with M-x remember rather than one big page)

triggering also for sc/ssc stuff and across PLENUM

ssc, sc and friends 12:31 (tech_notes#36)

1) now back to port 57120 for sclang. maybe binds above this if port is occupied (eg. by pd)

2) doesn't seem any way to automate:

    (sclang-eval-expression "EvalListener.init")
and any changes to ssc.el to do sclang-eval-expression rather than string don't seem to work interactively