User manual

automation screen indicating what state was last sent to that device

. For example “DeviceNameToTrigger:State1ForDeviceName”

When a DeviceNameToTrigger button is pressed, a new window showing all the possible

StateXForDeviceName configured within the <DeviceNameToTrigger> tag will be

shown.As this Device is not defined under the <proj> or <Audio> tag, the button will appear in

the Auditorium section of the Automation GUI.

<State1ForDeviceName>MessageChannel Message</State1ForDeviceName>

<State2ForDeviceName>MessageChannel Message</State2ForDeviceName>

In the following example, the <DeviceNameToTrigger> is nested in a special tag of <Proj>

or <Audio>. If a <DeviceNameToTrigger> is

placed within <Proj>, these DeviceNameToTrigger buttons will appear under the

Display/Projector section of the Automation GUI. If a <DeviceNameToTrigger> is placed

under the <Audio> tag, it is placed under the Audio section of the Automation GUI. Under the

Audio section of the GUI interface, the buttons will not appear. Only have Volume level and audio-

channel select buttons are shown. These are hard coded buttons and cannot be changed.

<Proj>

<State1ForDeviceName>MessageChannel Message</State1ForDeviceName>

<State2ForDeviceName>MessageChannel Message</State2ForDeviceName>

</Proj>

In this example, we define the <Audio> section of the automation. However, in this case we are

including an external XML template for the Datasat AP20 sound processor. A list of template files

are available from digitAll for common audio processors. See the manual above on using the

<Include> tag.

<Audio>

<Include>Datasat_AP20.xml</Include>

</Audio>

Trigger types

The <Trigger> configuration option is split into 4 areas. Depending on the Trigger type, these

options must be placed in different areas under the <Trigger> section of the Settings.xml

file;

 Button Not Displayed : If a trigger message is defined but it is not the child of a

DeviceNameToTrigger, it will not be displayed on the Automation Button GUI.;