showstack / software / avolites-titan
Avolites Titan
Avolites' lighting control software: the operating software on Sapphire, Diamond, Tiger Touch and Arena consoles, and the same code on Windows as Titan Mobile, Titan Go and Titan Simulator. Standard kit for rock and roll touring and festivals.
Protocols it speaks
| Protocol | Direction | Notes |
|---|---|---|
| art-net | out | One of the two network DMX protocols Titan uses to reach nodes and dimmers. |
| sacn | bidirectional | sACN out to nodes, and Streaming ACN In is also available as an external trigger source on supported consoles. |
| dmx512 | out | Physical DMX512 on console XLR outputs; on a PC, via a T1/T2/T3 interface. DMX In is a separate trigger source on supported consoles. |
| citp | bidirectional | Patch syncs both ways with stand-alone Capture (fixture, position, orientation, legend, user number) and fixture selection follows across. Levels still need Art-Net or sACN enabled on those universes. |
| rdm | bidirectional | Patching by RDM requires an RDM-enabled Art-Net node. The console's own XLR connectors do not support RDM. |
| ltc | in | SMPTE/LTC listed on T2, T3, D3, D3 Core, D7, D9, Arena, Tiger Touch 2 and Sapphire. A T2 plugged into another console adds an audio/LTC input. |
| midi | in | MIDI is one of the external trigger types and is not available on every console; USB MIDI devices are supported for triggering and control. |
| mtc | in | A cue list can read timecode from the system clock, an internal timecode source, MIDI, SMPTE or the Winamp player. Up to 4 separate timecode sources per console. |
What to watch for
Everything is keyed to an AvoKey. Titan Mobile only runs while its panel is connected, Titan Go licenses the AvoKey built into a T1/T2/T3, and Titan Simulator needs an Editor AvoKey.
Titan Simulator does output full Art-Net/sACN on all universes, but deliberately inserts periodic random DMX values as a spoiler. It is not a show controller.
64 lines/universes is the system ceiling. Line numbers can be anything from 1 to 9999 but there cannot be more than 64 of them. T3 needs an optional licence pack to reach 64, and its onboard processing stays at 16 lines.
RDM discovery only works through an RDM-enabled Art-Net node. The console XLRs will not do it, and a non-RDM buffer or splitter anywhere in the chain blocks the reply.
Windows only. Windows 11 is supported from v16.0 onwards, and Avolites explicitly does not support Bootcamp, VMware or Parallels.
Titan Mobile and Titan Go will not launch at all without their hardware connected, so a dead panel also means no offline editing on that machine.
Typical use
- Busking and timecoded playback for touring bands and festivals
- Pre-programming a show on a laptop with Titan Simulator or Titan Mobile
- Small rigs run from Titan Go on a T1/T2 interface
- Previsualisation against the integrated Capture visualiser
Sources
- DMX Settings (DMX output mapping) - Avolites Titan manual — Avolites primary
- Titan Simulator - Avolites Titan manual — Avolites primary
- External triggering - Avolites Titan manual — Avolites primary
- Cue List Timing - Avolites Titan manual — Avolites primary
- Patching New Fixtures or Dimmers (Patching by RDM) - Avolites Titan manual — Avolites primary
- Linking the Console to Stand-Alone Capture - Avolites Titan manual — Avolites primary
- Titan PC Suite: System Requirements & Installation Notes — Avolites primary
Understand the mechanism
Something wrong, or missing?
Every entry here is maintained by people who run shows.
Edit this entry on GitHub — one file, editable in your browser, and your handle goes on it permanently.
Work at Avolites? Confirm or correct this entry — it is free, it stays free, and nothing about it is for sale.