This is far from complete and will be refined and enhanced over the coming weeks. The main concern of this document is to answer the most common queries and question since the call for works was issued.

It is intended that this document will enable people to feel confident about responding to the call by providing a technical framework and the beginnings of an aesthetic discussion.

For tape or fixed media composition playback will be provided through a computer based system. Stress and stability testing is currently underway to establish the exact makeup of this system.

Though a 36 channel mix is expectable it is also expected they many artist will look to diffuse sounds live. To do this a variety of solutions are available ranging from keyboard/mouse control, gamepad and traditional fader/knobs hardware.

It is intended that all sound generation code will run hosted on the hardware we provided which will be installed and configured for use. Consequently interaction with code beyond start/stop is only available across a dedicated WIFI network. Connectivity will be available across TCP/UDP as OSC and mxj net.maxhole (yes I know this is easy udp).

For the live and improvised events real time multi-user, multi-source diffusion is available across all of the speakers. The primary method of interaction will be across a wifi network running dedicated applications to control source and routing. This API will be publicly accessible, as an open standard available for hacking and redeployment. This means that diffusion, can be controlled by user written code, manually controlled through laptop based gestures or through external hardware interfaces.

The network topology will be released soon, however a client/server architecture will be used with communication based on OSC style namespaces. UDP and TCP OSC streams will be available as well as net.maxhole.