Visual Productions CUECORE2 Manual page 54

Figure 9.2: Show Control structure
The CueCore2 is capable of listening to various protocols. These available pro-
tocols are listed in Sources, however, the CueCore2 can only actively listen to
8 protocols at once. The active protocols are listed in 'Action Lists'. Each
action list can contain actions. Within a protocol/source each individual sig-
nal requires its own action. For example, when listening to channel 1 and 2 on
the incoming DMX, the DMX action list needs two actions; one for each channel.
Inside the action we define the trigger and tasks. The trigger specifies for which
signal to filter. In the above DMX example the trigger would be set to 'channel
1' and 'channel 2' respectively. The tasks determine what the CueCore2 will do
when this action is triggered. Several tasks can be placed in the action. There
are tasks available for a wide range of CueCore2 features and external protocols.
Task types are detailed in Appendix B on page 90.
Please consult the API appendix on page 99 before implementing incoming
OSC or UDP messages; the API already exposes typical functionality through
OSC and UDP and therefor it might not be necessary to implement custom
messages.
9.1 Sources and Action Lists
The Sources listing presents all protocols that the CueCore2 is capable of receiv-
ing. It also includes internal features that can create events that can be used for
triggering actions, such as the calendar-scheduler. These sources are available,
however, they will only be actively listened to once moved to the action-list table.
54