Part of Temporal Constructs Appendix, which contains details behind the research: dates, quotations, descriptions of instruments, and sources.
General definition
Relation to the practice
Magnusson (2009) describes the instrument as a cognitive extension, and Latour (1996) describes the device as an actor that prescribes a program of action. A device in the sense used here is both at once.
In CONDUCTOR, a device translates a module’s controller values into messages for its instrument, and people prototype it in Max or Pd. The Strummer is the worked example. Its builder authors the device and fixes it mostly before performance. Changing the device changes the controller map, so the builder builds it once. Creative intentions reside in the device as rules that extend what both the performer and the hardware can do.
A device is a bridge as well as a translation. It extends the instrument, because the hardware acquires properties it does not have on its own, and it extends the agents, because they reach further through it than they would without it. It is also where the prototyping happens: a device is made by hand in Max or Pure Data through a run of quick interactive changes, and only when that run is finished does it become a component of the system. That work is reserved for humans, which is why the environment for it is a visual one. The agents’ own attempt at patches falls on the other side of the line, since their logic was sound and their layout was not (Discoveries). The device separates from the timeline by authorship. A change placed at a point in time sits with the timeline, while a change produced by a rule at runtime is part of the device.
Unforeseen
Here the unforeseen situations, sometimes difficult, sometimes unexpectedly interesting, will be described as the project runs. Many of these unforeseen situations have already occurred and have been recorded. They will be added in the time to come.