Visual Productions IOCORE, Manual, Page: 28 / 58

Core needs to respond to or perhaps convert into some other signal, needs to be
expressed in an actions. Before programming actions please consider the Show
Control structure in figure 6.2.
Figure 6.2: Show Control structure
The IoCore is capable of listening to various protocols. These available pro-
tocols are listed in Sources, however, the IoCore can only actively listen to 8
protocols at once. The active protocols are listed in ’Action Lists’. Each ac-
tion list can contain actions. Within a protocol/source each individual signal
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 IoCore will do
when this action is triggered. Several tasks can be placed in the action. There
are tasks available for a wide range of IoCore features and external protocols.
Task types are detailed in Appendix B on page 48.
6.1 Sources and Action Lists
The Sources listing presents all protocols that the IoCore is capable of receiv-
ing. It also includes internal features that can create events that can be used for
triggering actions, such as the GPI ports. These sources are available, however,
they will only be actively listened to once moved to the action-list table.
28