User manual

however, the TriggerName will still be listed in the full list of triggers, meaning it can

still be fired programatically, but not via the GUI.

 Auditorium : The Auditorium triggers are external triggers that effect the theatre, such

as lights, masking and doors. These devices are children of the <Trigger> tag.

 Audio : The Audio controls effect selections on the audio processor, such as the volume,

mute and audio-input. These triggers must be placed as children of a special <Audio> tag

under the <Trigger> tag. Note: The Audio section of the GUI interface does not add

buttons that correspond to the trigger names. Volume, Mute and channel-select buttons are

always displayed even if not in use. If you need to define any special buttons for the audio

processor but want a button to show on the automation GUI, these must be placed in the

Auditorium section.

 Display : These automation triggers are used to control the display or projector. Display

triggers must be placed as children of a special <Proj> tag under the <Trigger> tag.

Defining a trigger messagePart of defining a trigger requires setting up how and what messages

will be sent from the dCine. The dCine allows for messages to be sent via any of the

following three methods.

1. IO-Contact-Closure Devices: In order to use this device it must be defined in the

<Device> tag as described in the <Device> section explained above. In the device

section support engineers must set a device number (for the prescribed device) and the

terminal types. What follows are examples of sending a message to an IO-Contact-

Closure device; Note:  denotes a comment in the MediaSetting.xml

configuration file.

<Trigger>Device 00 Set PIN:5 On</Trigger>

<Trigger>Device No Pulse PIN:X On/Off [time] </Trigger>

<Trigger>Device 00 Pulse PIN:5 On 1000</Trigger>

<!-- Example of controlling a full bank of terminals in one trigger

This is used to set a bank on relays to a position;

X - leave relay in current state.

0 - Turn relay off.

1- Turns relay on. -->

<Trigger>Device No X000 X111 XXXX XXXX XXXX XXXX</Trigger>