Part of Temporal Constructs Appendix, which contains details behind the research: dates, quotations, descriptions of instruments, and sources.
General definition
A persistent, labelled map that fuses the parameters of a device and of hardware into one set of controls, readable as a table of possibilities.
Relation to the practice
Norman (1988) describes the surface that shows what can be done, and Suchman (1987) describes the interface as what makes an action accountable. The controller is the name this research uses for that surface.
-screen capture of a controller, the parameters of a device and of its hardware fused into one table of controls-
In CONDUCTOR, each module has a controller. A controller works with control changes and builds snapshots gradually. The system designer authors the controller and fixes it before performance, and its mapping must stay stable, because everything built afterwards depends on it. The controller is the first stage in making presets, and because it fixes part of what is possible ahead of the performer, it constrains what presets can capture. Because commands reach a device through a controller, the mapping a controller provides makes an instrument operable by an agent as well as by a person. The strummer is reached through the controller of the module that serves the synthesiser.
Reached through CUE
Every command that reaches a controller arrives in CUE: a person or an agent addresses the controller, and nothing addresses the device behind it directly. CUE is one way in for commands, and the map a controller provides can also live on a physical surface. The Faderfox EC4 is that physical surface for a person playing by hand.
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.