AudioPixel: Difference between revisions
AudioPixel (talk | contribs) |
AudioPixel (talk | contribs) No edit summary |
||
| Line 11: | Line 11: | ||
We're happy to adapt the software to talk to as much of the tower as possible, through published events or otherwise. | We're happy to adapt the software to talk to as much of the tower as possible, through published events or otherwise. | ||
== Needs == | |||
* Finalized layout of tower, 3D model with lighting placement | |||
* A main computer (Preferably Windows 7, but flexible) | |||
* A backup computer | |||
* Qty 2 [http://www.enttec.com/?main_menu=Products&pn=70303 EntTec DMX interface] (assuming DMX lighting) | |||
== Interaction Scenario == | == Interaction Scenario == | ||
Coming soon | Coming soon | ||
Revision as of 09:48, 15 July 2013
Control Tower video with some screenshots and pre-viz
The Rundown
AudioPixel software provides an abstraction layer where any unit (dmx, midi, udp, etc) can define it's existence and be handled as a mapped node in the 3D pixel mapped universe.
We run 'clips' - which can be custom scripts, algorithms, or any type of content - that centrally drive the behavior of all hardware. Control is mapped in a 3D universe where any type of hardware can be added and intelligently synchronized to be controlled by any type of input.
An one example, during live stage shows, we use a midi dj controller to quickly activate and blend effects, generally without using the GUI. For example, when controlling DMX movers, the animation color data is interpreted as a rotation of it's colorwheel, while the same data is converted into proper RGB data for the LED units.
We're happy to adapt the software to talk to as much of the tower as possible, through published events or otherwise.
Needs
- Finalized layout of tower, 3D model with lighting placement
- A main computer (Preferably Windows 7, but flexible)
- A backup computer
- Qty 2 EntTec DMX interface (assuming DMX lighting)
Interaction Scenario
Coming soon