Visual Productions QuadCore Manual page 57

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
sometimes omitted in the web GUI. The trigger-type field specifies what kind
of signal the action will be triggered by. For example, when making an action
in the Scheduler list there is the choice between 'DateAndTime' and 'Week-
dayAndTime' trigger-types. The trigger-value specifies the actual signal value.
In the schedular example the trigger-value could be set to "2016-03-24 11:00"
or "Weekend 10:00" respectively.
In some action-lists actions do also need to specify the trigger-flank. The flank
further specifies the value that the signal should have before triggering the ac-
tion. For example, when an action is triggered from the Kiosc list, the flank will
determine whether to trigger only when the button goes down or only when it
goes up. Appendix B provides an overview of the available trigger-types.
An action-list can have up to 48 actions, system-wide there is a maximum of 64
actions.
9.3 Tasks
Tasks are added to an action in order to specify what to do when it gets executed.
Up to 8 tasks can be included in an action, systemwide there is a maximum of 128
tasks. The tasks are executed in the order of the list. There is a wide selection of
tasks available to choose from, they include altering any of the internal software
features like playbacks and recorder but also sending out messages through any
of the supported protocols. The tasks are organised in categories. Once a task is
chosen from these categories each task allows for further choice between several
'Features' and 'Functions'. Tasks contain up to two parameters that might be
required for its execution.
If the event that triggers the action passes a parameter along then this parameter
can be used in a task. The 'set' function makes a task use a fixed value, however,
when using the 'control' function then the trigger's parameter is used. This is
very useful for conversions between protocols.
For example when converting OSC to DMX the OSC action specifies the URI
(e.g. /dmx100) and flank (e.g. OnChange) on which it will trigger. The actual
OSC (float) data received in the message will be passed along and fed into the
action. Then when a task (e.g. DMX) uses the function 'control' this OSC
float-level will be used for setting the DMX value.
A task can be tested by selecting it and pressing the 'execute' button in the
action-edit dialog. The complete action can also be tested; go to the Show
Control page, select the action and press the 'execute' button.When either of
these 'execute' buttons are used, the source of the 'control' value for tasks will
be the 'execute' button. The result will depend on the chosen task and feature,
but will most likely be 100%, 1.0, or 255 when pressed and 0%, 0.0, or 0 when
57