Within Titan, Trigger is the general concept of having an external signal firing a specific action in Titan. This is rather well documented in the Titan Usermanual.
In general, Titan can handle these trigger sources:
Based on the very hardware only a limited subset of trigger methods is possible:
|Console||Audio||DMX||GPIO||MIDI|| USB-MIDI |
(Titan v12 and up)
|Titan One||x||x||If used as DMX input, a separate output device is necessary, e.g. an Artnet node|
|T1||x||x||If used as DMX input, a separate output device is necessary, e.g. an Artnet node|
|T2||x||x||x||x||Can also be used as audio input for other Titan consoles (not Titan One/T1).|
| Tiger Touch (non-pro)|
Pearl Expert (non-pro)
|Titan Mobile||x||x||x||x||Audio trigger available with T2 from Titan v12|
| Tiger Touch Pro|
Pearl Expert Pro
|x||x||x||x||Audio trigger available with T2 from Titan v12|
|Tiger Touch II||x||x (1 jack input)||x||x||x||Audio trigger available with T2 from Titan v12|
|Arena||x||x||x (1 jack input)||x||x||x|
|Sapphire Touch||x||x||x||x||Audio trigger available with T2 from Titan v12|
Trigger mappings can be regarded as collections of triggers. You can define a number of mappings, and you can enable/disable each mapping as needed. (See Trigger - Toggle Trigger Mappings v10/v11 for an example of how to do this by macro). There are some mappings provided by default which cannot be deleted.
Can be either Hardware (default) or Item.
This select is also named 'Trigger Type' but refers to the trigger source. Each source has specific parameters, and if 'Learn' is set to On Titan tries to find the parameters from the latest incoming signal itself.
|Trigger Type (Source)||Parameters|
|DMX|| DMX Port
|MIDI|| MIDI Channel
Command [Note, ControlChange, Program Change etc.]
Value (not for Program Change)
|Streaming ACN|| Universe
Currently (v12/v13) there are some caveats with triggers - maybe they will be rectified in the future.