User manual

Macros are used to tie together a set of triggers. This is useful for defining a single button to

represent a “Theatre State”. A scripting type language within the XML text of the

Settings.xml file is used to tie together a set of triggers..A Macro can be fired in the same way

a <Trigger> is used, .however in the case of macros, one trigger message will encapsulate all the

triggers defined in the macro.

Note the following example of a macro configuration:

Trigger Lights:House

Trigger Audio:Volume:50

Trigger Audio:Input:NonSync

Trigger Door:Open

Trigger Curtains:Closed

Trigger Proj:Douser:Closed

Trigger Proj:Input:eCinema

</PreSession>

Trigger Curtains:Open

Sleep 5.0

Trigger Lights:Prog1

Sleep 5.0

Trigger Audio:Input:eCinema

Trigger Audio:Volume:70

Trigger Proj:Macro:eCinema

Trigger Proj:Douser:Open

</PreShow>

</Macros>

In the example above, support engineers can use the <Macros> option as a convenient method for

setting up all devices/equipment into the correct configuration for a particular environment. In the

above example there is a macro called <PreShow>. This macro will send all Trigger messages

required to configure the theatre for the PreShow portion of a session. The macros feature is

especially important in more complex sites that may receive feeds from a plethora of sources such

as a DCI-player, an eCinema-player, a BluRay-player, a Satellite box, a Terrestial-TV-box etc. Each

video source requires that multiple devices are specifically configured for the selected video device

to work correctly.

Theatre states

As macros help with setting up the state of all the equipment and theatre, the idea of “Theatre

States” is used in the interface to represent this to the GUI. The heading “Theatre State” is

shown in the middle top section of the “AutoM” automation GUI section of the interface.,. Under