_____

piksel2010

The Construction of Situations

../images/rotsm.jpg

new notes

That this discussion could be opened on the piksel list or?

  • what it is, what is the promise?

The promise/preliminary short description:

During six hours within an open space, the construction of situations proposes the destruction of software as architecture (of abstractions), environment, and language (a conversation) which describes and constructs the systematic world. The unknown and programmed event bears witness to the expansion of re-constructed code as a new framework of discussion within the creation and organisation of moments.

A situation is constructed starting from this description, a large room with people, a few tables and chairs, drinks, audio equipment, esoteric technologies; the symbolic destruction of any framework as new codes work towards the collective initiation and fragile construction of a truly unforeseen site of execution.

  • who is involved, who is IT open to?

Core participants: Shu Lea Cheang, Martin Howse, Anthony Iles

Open to all Piksel participants. Do they need to register some interest in advance? How will they be involved on the day?

  • is there a framework, a structure, a model?

Firstly, that the title is borrowed from Guy Debord - Report on the Construction of Situations… (1957):

We must try to construct situations, that is to say, collective ambiances, ensembles of impressions determining the quality of a moment. If we take the simple example of a gathering of individuals for a given time, it would be desirable, while taking into account the knowledge and material means we have at our disposal, to study what organisation of the place, what selection of participants and what provocation of events are suitable for producing the desired ambiance.

From which we can take: study and provocation!

Similar to the Plenum thing I did with Shu Lea Cheang and Armin Medosch - to set up a framework for discussion and then work to change the terms of, disrupt or construct anew this situation.

How this was structured - Around 5 acts each with a particular social/software setup. Devices included groups sitting at tables engaged in discussion, interventions of observers (note takers), PLENUM (plenary session with statement of agendas), duel/boxing ring, spokesperson, post-match analysis, walk out.

Pd patchers/software artists using microphone inputs to process microphone inputs on each table and projecting audio output back into the space. Strategies of interest included rescheduling (time access manipulations, cutting to and fro), simulation (mapping/spatial), data/time slicing, parody, neuron models.

Later framework notes:

a situation which computes something or assists in its computation (perhaps as a pre-processing).

Liquid state machine

any system can be viewed as a system for computation for a particular problem (I am a (fake) neuron) - a pool of water, the fish-farm again.

paranoiac question of what is the problem

input (as) excitation in a social situation with outputs for further processing

plague and sites of execution

masque of the red death as architecture and model

  • what is planned or left unplanned?
  • what is needed in terms of preparation?
  • (what kind of) software and/or technology is there?
  • who might do what?
  • what might happen?

code

see: file:~/collect2010/blackdeath

refine to:

1)rme/JACK-DONE(?) 2)evp renewed with pipes/shared memory-DONE 3)scheduling/bulletin board (what happens/when?) and some link to processes

  • mics?
  • what situations piksel code could be?: cutups, round, schedulers
  • manipulation of (recorded/live) speech
  • modelling
  • primitive means (BASH, OS scheduler-cron/tab)
  • rme for piksel (or /dev/dsp — amixer)
  • round robin say from emacs
  • emacs scheduler and process window: vkill

scheduling notes

some elements:

  • cron/tab
  • bulletin board? (pop/push)
  • interrupts (TASK_INTERRUPTIBLE, TASK_UNINTERRUPTIBLE)
  • nice/renice
  • wait queues
  • signals/states
  • process switching
  • fork
  • scheduling policy (Linux): time multiplexing/slices or quantum, relies on timer interrupts and is transparent to process (p.258+)
  • process priority
  • round robin

former code base

  • plenum and plenum tools

    all pd or scm… (neuron, jekyll, osc piping)

  • code rocks (processes)
    • 1- process table and xxxx….sh yyyyy….sh
      nice -n -10 top -d.1 | tee pipe
      play -t raw -r 44100 -u -b -c 1 pipe
      

      also with: A,M,N,P,T - alt display, sort by memory, PID, CPU, time (and G for group)

    • 2- evp/i_am/speech somehow
      cat /dev/mem | strings | espeak --stdout | ./evp 1 32 8000 1 > pipe
      play -t raw -r 44100 -u -b -c 1 pipe
      
    • 3- self
      ./self > /dev/dsp
      
    • 4- code rocks
      cat /dev/mem > /dev/ttyUSB0
      cat /dev/ttyUSB0 > /dev/dsp
      
    • 5- rock off:
      cat /dev/mem > /dev/ttyUSB0; cat /dev/ttyUSB0 | tee /dev/dsp > /dev/mem
      
  • ex-code:
    • audio re-process (see steganographia)
      gocr ~/projects/steganographia/muja1.png | text2wave > muja2
      
      sox -t raw -r 8000 -c 1 -u -b muja2 muja.wav
      

      // but for pd we must correct header in audacity???

      festival --tts steganography_results.txt
      
      cat steganography_results.txt | text2wave -o test.wav
      
      steghide embed -e none -Z -cf islandencoded.wav -sf islandstegencoded.wav -ef island_encoded_in_itself
      
      steghide extract -sf islandstegencoded.wav -xf - 
      
      cat island.txt | recite -Write_phonemes > island_phonemes
      
    • possible stegging or anagramming
      • methods

        own text-based stego (to embed a text in itself):

        • encode:
          python /root/xxxxx_2/xxxxx/trunk/stego/markov_stego.py -d island.txt
          
          python /root/xxxxx_2/xxxxx/trunk/stego/markov_stego.py -f living island.txt > island.encoded
          
        • decode:
          python /root/xxxxx_2/xxxxx/trunk/stego/markov_stego.py -g island.encoded
          

        anagramming:

        python ~/projects/steganographia/anagrammit.py "wrong word"
        
  • stitch

    pd patches

  • earlier piksels for scheduling

    in experiment?

    file:~/experiment/life_coding/panel.lisp

    in Lisp (Slime fails to find: Couldn't load "/usr/share/emacs/site-lisp/slime/swank-loader.lisp": file does not exist.)

    what is file:~/experiment/prmisc/lp-0.1 ???

technical

  • edit crontab for scheduling of shell scripts
28 *    * * *   root    /root/test.sh
29 *    * * *   root    /root/test.sh
30 *    * * *   root    /root/test.sh
31 *    * * *   root    /root/test.sh
32 *    * * *   root    /root/test.sh
33 *    * * *   root    /root/test.sh
  • recite:
    echo "hello" | recite
    
  • watch
    watch -n1 ps ax
    

also watch -d and watch -d–cumulative (highlights changes)

  • ps
    ps -eo eip, esp
    

short description

  • The Construction of Situations

During six hours within an open space, the construction of situations proposes the destruction of software as architecture (of abstractions), environment, and language (a conversation) which describes and constructs the systematic world. The unknown and programmed event bears witness to the expansion of re-constructed code as a new framework of discussion within the creation and organisation of moments.

A situation is constructed starting from this description, a large room with people, a few tables and chairs, drinks, audio equipment, esoteric technologies; the symbolic destruction of any framework as new codes work towards the collective initiation and fragile construction of a truly unforeseen site of execution.

Participants: Shu Lea Cheang, Martin Howse, Anthony Iles

> The title > >> pretty much describes what this would be - using > discourse, > >> space and software to construct a new form of > situation. It > >> would be a bit similar to the Plenum thing I did > with Shu Lea > >> Cheang and Armin Medosch - to set up a framework > for discussion > >> and then work to change the terms of, disrupt or > construct anew > >> this situation.

cattojack/jacktocat

cat /dev/urandom | ./cattojack 0

cattojack [out] and jacktocat [in]

to first (0) channel of:

/usr/bin/jackd -dalsa -dhw:1 -r48000 -p1024 -n2

…but should be input and output cats: so make a catin (for inputs!)

…ALSO switchers/shell using jack_connect:

jack_connect system:capture_1 system:playback_10

now as shell script:

round.sh [delay]

see also new jack.el and notes in HOWTO.org

further background notes

  • framework: invisible code, plague, black death

latest notes

that (the) crash is a conspiracy - pretending or faking an exposure which is calculated as a necessity (part of twin movement below) and is coded in (a segmentation fault). the system crashes itself. technology or code thus promotes a false transparency.

code as a self-evident enclosure; a twin movement of revealing its own evidence and obscuring itself as a movement against infection or contamination.

examples of enclosures:

  • enclosure (from the) plague
  • an island
  • a container/abstraction
  • the world
  • the earth (boxes, substrates: a number of great wooden boxes filled with mould (p68), the earth placed in great wooden boxes(p41), his earth-home, his coffin-home, his hell-home(p199) - more refs??

relation to pornography - in notes below: the enclosure both permits the system and extends the possibilities of cruelty as in, for example, a fairy tale or pornographic film.

examples of obscurity:

  • blackboxing (could be as abstraction below)
  • obfuscated code
  • encryption/security
  • steganography
  • abstraction of OS, protocols and codes

examples of revealing:

  • open source/free software
  • transparency in networks
  • code commentary
  • crashing
  • media archaeology
  • TEMPEST

island/invisible notes collected

for plague/code.

The figure of the plague ship (Dracula - the Demeter, The Grande-Sainte-Antoine in Marseille in 1720), a plague promiscuity (the voluptuous UN-dead), a blood network of code carriers.

All code is a vampiric execution:

There is no software, only vampiric execution on some kind of earth substrate, homeland earth boxes from the count entering a foreign island/territory at Whitby, a first virus black-dogged distribution or infection vector. Execution and distribution. Precisely this contained earth which is to be sterilised by Van Helsing and his associates.

Infection is the key. How to transfer execution across material and against containment?

A channel (or a mechanism) used by virus to spread is called a vector. There is no dearth of potential vectors on Unix (for example, buffer overflow vulnerabilities).

[Viruses on Unix. Amit Singh]

That code/software/network/protocol/body is precisely this same plague, this virus which is assumed to be contained or to be contained from, to be islanded/enclosed and neutralised.

Code is a play between an ontology of hiding and a functionality of revealing which is in one sense the world (given in that deciding) as a military/philosophical project of a holding of the day and of the world as [un-]certain.

Code is a transparency (the world is described as/for an algorithm). Code is readable as language - language and execution (execution as a binary hiding).

Readable code also as a hiding (as encapsulation and abstraction - the protocol)

To create a software/hardware without organs at the site of execution - not to expose that which is (as it is in that play).

Pornography and/as (the) protocol - as in some ways each inverting the other (in terms of hiding) // or not // a binary.

How this (code) is a place of no exposure (covered bodies).

From Sade, Fourier, Loyola:

Finally in his order of occultation, the libertine contradicts everyday immorality; he takes the opposite tack from sophomoric pornography, which makes the supreme audacity the sexual denudation of Woman. Sade calls for a counter-striptease.

In Sade, no striptease… As narrative the striptease has the same function as revelation… Sade is materialistic in that he substitutes practical language for secret language…

also see: pornogram - fusion of discourse and body - updated!

"You see me completely naked," Eugenie says to her professor: "dissertate on me as much as you want."

That uncovering which has always already taken place/

15:22 < _xxxx`> crash as this exposure of beneath-interface roughly […] crash is like an always fake exposure 15:28 < _xxxx`> and maybe pornography is like putting the code above the crash 15:29 < _xxxx`> so inverse in like a layered model 15:29 < _xxxx`>

An operating system (OS) is an interface between hardware and user.

Defined as enclosure and abstraction:

Functional enclosure or separation of effects (for example blackboxing, dark-caving, the simple enclosure of a logical or electronic device - an opening between enclosures as interface).

Containing as abstraction in its essence.

The same enclosure and isolation (from/as that plague). This time a pornographic enclosure - a place of (no) exposure.

The enclosure both permits the system and extends the possibilities of cruelty as in, for example, a fairy tale or pornographic film.

Enclosure as the foundation of abstraction and language. A theatre of cruelty and of leakage.

black death notes

pure infestation of rendering executable along the line of an infection vector

pornography as ground zero of computation/execution

re-imagined pornographic logic gates

mechanical logic

see island notes/invisible code notes: theatre and the plague, bubonic, skin, interface, crash

promiscuOS as a parasite in that it obviously needs some (controlled) activities

examples of parasites…

code as a simultaneous hiding and revealing in/as an attempt to avoid and contain against contamination and infection. how does this hiding and revealing attempts to guard against contamination (in an open place, a clearing, a red night, red flesh, red death)?

Aletheia (the state of not being hidden, being evident, a revealing related to the hidden).

what actions can be performed which exacerbate or in any way intervene within this double movement?

  • virus contamination (network, filesystem, memory)
  • as extension and bleeding out of the site of execution
  • extend/parody containment and isolation (strategies of enclosure, SALO, salOS)
  • crashing (as fake revelation). find catalogue of crashes: segfault, kernel oops, fault.c…)
  • (hyper)-exposure, rendering visible (of processes, of hardware substrates) - this strategy at a distance (TEMPEST, signals, network sniffing)
  • extend/parody of hiding (all is hidden - steganography, steganographised packeteering - that it might only appear to be a packet), obfuscation
  • exacerbation of the being-substrate (back to the substrate, melting)

but to access this double movement?

– from invisible code identifying:

  • obfuscated code
  • pornography/pornographic code (a willed exposure or exhibition;

there is the relation to crash but what is relation to code?),

  • computer/national security
  • virus -> manipulation of, say, the instruction pointer - shifted to an area which is now rendered executable (by analogy a pornographic virus would shift the site of execution to a place where it should not be - how could we imagine this?) eg. Ballardian extension of pornography into geometry, war porn, fetishisation (of code itself), but how far to be shifted (also towards an interior)

literal pornographic code - algorithms of de sade, multiplications, rules, arithmetic

bubonic eruption of the shift of an instruction pointer OUTSIDE (outside shamanic fly agaric piss logic concentration)

UKI audio

old code base

code rocks (processes)

  • 1- process table and xxxx….sh yyyyy….sh
    nice -n -10 top -d.1 | tee pipe
    play -t raw -r 44100 -u -b -c 1 pipe
    

    also with: A,M,N,P,T - alt display, sort by memory, PID, CPU, time (and G for group)

  • 2- evp/i_am/speech somehow
    cat /dev/mem | strings | espeak --stdout | ./evp 1 32 8000 1 > pipe
    play -t raw -r 44100 -u -b -c 1 pipe
    
  • 3- self
    ./self > /dev/dsp
    
  • 4- code rocks
    cat /dev/mem > /dev/ttyUSB0
    cat /dev/ttyUSB0 > /dev/dsp
    
  • 5- rock off:
    cat /dev/mem > /dev/ttyUSB0; cat /dev/ttyUSB0 | tee /dev/dsp > /dev/mem
    

ex-code:

  • audio re-process (see steganographia)
    gocr ~/projects/steganographia/muja1.png | text2wave > muja2
    
    sox -t raw -r 8000 -c 1 -u -b muja2 muja.wav
    

    // but for pd we must correct header in audacity???

    festival --tts steganography_results.txt
    
    cat steganography_results.txt | text2wave -o test.wav
    
    steghide embed -e none -Z -cf islandencoded.wav -sf islandstegencoded.wav -ef island_encoded_in_itself
    
    steghide extract -sf islandstegencoded.wav -xf - 
    
    cat island.txt | recite -Write_phonemes > island_phonemes
    
  • possible stegging or anagramming
    • methods

      own text-based stego (to embed a text in itself):

      • encode:
        python /root/xxxxx_2/xxxxx/trunk/stego/markov_stego.py -d island.txt
        
        python /root/xxxxx_2/xxxxx/trunk/stego/markov_stego.py -f living island.txt > island.encoded
        
      • decode:
        python /root/xxxxx_2/xxxxx/trunk/stego/markov_stego.py -g island.encoded
        

      anagramming:

      python ~/projects/steganographia/anagrammit.py "wrong word"
      

notes

do we use RME?

sl audio (code): skin, plague, stegged revealing, enclosure, buboe eruption as granulation, virus shell takeover!

code rocks->code skin (skin instead of rock above).

4- code skin

cat /dev/mem > /dev/ttyUSB0
cat /dev/ttyUSB0 > /dev/dsp

5- skin off:

cat /dev/mem > /dev/ttyUSB0; cat /dev/ttyUSB0 | tee /dev/dsp > /dev/mem

[with arduino and bits through skin]

DONE- evp (mix with named pipe opened) /root/pipe

cat /dev/dsp | ./evposcmix 1 3 4 1 > /dev/dsp

skin(gsr)->OSC->evp and others:

[message: [ /test from too ] - on port 7700 - see pd patch]

play to STDOUT:

sox island_test.wav -t raw -r 48000 -u -b -c 1 - > ~/pipe

speak to STDOUT:

cat notes.org | recite -Write_phonemes | espeak --stdout > ~/pipe

or:

echo "hello" | flite -o pipe&; cat pipe > /dev/dsp (distorted)

code base

Author: root <m@1010.co.uk>

Date: 2010-11-10 12:34:04 GMT

HTML generated by org-mode 6.31trans in emacs 23