Source
Description
Touch Screen
Triggers from Kiosc. For each Action various controls can
be chosen such as buttons and sliders, colour picker etc.
The order of the actions will control the arrangement in
Kiosc.
Art-Net
Receiving Art-Net DMX data
DMX In
Receiving DMX data
MIDI
Incoming MIDI message
Timecode
Triggers set to specific timecode frames
Scheduler
Date and time triggers based on the internal clock
System
Events such as ’Power on’
OSC
OSC network message
GPI
Changes on one of the GPI ports
Variable
The Variable source works in combination with the variable
task (For more information about the Variable task please
refer to paragraph 8.7). The Variable task will set a value
of which an enabled action-list type with Variable as Source
will use as a trigger.
Recorder
A recording changes state
UDP
UDP network messages
Console
Events created by the console function
Randomiser
The randomiser can generate a random number, more
information in paragraph 8.8.
User List 1-4
These action-lists will never trigger an event, however, they
are useful for advanced programming.
Action-lists can be temporarily suspended by disabling their checkbox in the
Show Control page. There is also a task available to automate changing the
state of this checkbox.
8.4
Actions
Actions are executed when a certain signal is received. This signal is defined by
the trigger. A trigger is always relative to the action-list the action belongs to.
For example, when the trigger-type is set to ’Channel’ then it refers to a single
DMX channel if the action is placed inside a ’DMX Input’ list and it means a
single Art-Net channel if the action resides in an Art-Net action-list.
A trigger is determined by the trigger-type, trigger-value and trigger-flank fields.
Although these fields are not applicable for all action-lists and are therefor some-
times omitted in the web GUI. The trigger-type field specifies what kind of sig-
nal the action will be triggered by. For example, when making an action in the
29