The console's automation scenes can be used to trigger events. Follow the configuration steps below:

Select the Automation Output source type in the Event Manager page.

This Automation event source can now be linked to a scene's Output Action. From the console's Automation page, select the desired scene, go to the Output Actions section and select the Event action type.

Select the event from the list of LINKABLE EVENTS and press Apply.

Arm the Output Action to ensure it triggers when the scene is fired.

The linked scene will be displayed in the Event Manager page.

GPI sources can be used to trigger events from the console's local GPIO ports* or from any SSL Live MADI or Network I/O Dante stagebox with GPIO ports.

Select the GP Input source type then use the Route button to open a Routing dialogue listing all GPIs available to the console. Select the GPI to use and press Make. Close the Routing dialogue to return to the event source configuration.

GPIs can trigger based on a number of different Actions:

• Latching : Source state becomes and stays true when GPI signal goes high
• Momentary : Source state becomes true only while the GPI signal is high
• Momentary-On-Hold : Source state becomes true when GPI signal goes high and becomes false if GPI signal goes low after 500 milliseconds, else state remains true

Use the Inverted button to invert the GPI state into the event trigger, i.e. when the incoming GPI signal goes low, the source state should become true.

MIDI sources can be used to trigger events from the console's local MIDI ports*, from the MIDI port on any SSL Live MADI stagebox or via ipMIDI.

Select the MIDI Input source type then use the Route button to open a Routing dialogue listing all MIDI ports available to the console. Select the port to use and press Make. Close the Routing dialogue to return to the event source configuration.

Note On, Note Off, Program Change and Control Change (CC) messages can all be selected for use with events.

The remainder of the source section is used to configure the expected MIDI message (MIDI Channel, Note Number etc. as applicable).

MIDI event sources have a Pulse Fire option. When enabled and a message of the specific type is received, the source state will go true for 500 ms then go false, irrespective of the input state. For program change messages this allows events to be retriggered by a repeated input. Without Pulse Fire enabled the event source state remains high following the program change.

Various console functions can be used to trigger events. A full list is included below.

Path functions require the specific path number to be entered (or engage Any Path to trigger the event source when any paths of the selected type meet the desired state).

The console's User Keys can also be used to trigger events. Select the User Key source type then select the Action required to trigger the event.

The different Actions available are:

• Latching : Source state becomes and stays true when User Key is pressed
• Momentary : Source state becomes true only while the User Key is pressed
• Momentary-On-Hold : Source state becomes true when User Key pressed and becomes false if User Key is released after 500 milliseconds, else state remains true

Only one User Key source can be added per event. The event's User Key source will now be available for assigning to any of the console's User Keys in the usual way, from the relevant User Options page (MENU > Setup > Options > USER KEYS).

Fader Function sources can be used to trigger an event when a path's fader meets a specified dB Threshold.

Fader functions require the specific path number to be entered (or engage Any Path to trigger the event source when any paths of the selected type meet the desired state).

Once a path (or paths) have been selected, set the Threshold and determine if the source should Trigger Above or Trigger Below the threshold value.

Events can be used to trigger specific automation scenes. Follow the configuration steps below:

Select the Automation Input destination type in the Event Manager page.

This Automation event destination can now be linked to a scene's Input Action. From the console's Automation page, select the desired scene, go to the Input Actions section and select the Event action type.

Select the event from the list of LINKABLE EVENTS and press Apply.

Arm the Input Action to ensure it fires the scene when the event is activated.

The linked scene will be displayed in the Event Manager page.

GPO destinations can be used to control external devices from the console's local GPIO ports* or from any SSL Live MADI or Network I/O Dante stagebox with GPIO ports.

Select the GP Output destination type then use the Route button to open a Routing dialogue listing all GPOs available to the console. Select the GPO to use and press Make. Close the Routing dialogue to return to the event destination configuration.

GPO behaviour can be set to a number of different Actions:

• Latching : GPO state toggled when event state becomes true
• Momentary : GPO state follows event state
• Pulse : GPO pulsed closed for 500 milliseconds when event state becomes true
• Turn On : GPO closed when event state becomes true; second event required to re-open GPO
• Turn Off : GPO opened when event state becomes true; second event required to re-close

Use the Inverted button to invert the GPO state relative to the event state, i.e. when the event state goes true, the GPO opens and vice versa.

MIDI destinations can be used to control external devices from the console's local MIDI ports*, from the MIDI port on any SSL Live MADI stagebox or via ipMIDI.

Select the MIDI Output destination type then use the Route button to open a Routing dialogue listing all MIDI ports available to the console. Select the port to use and press Make. Close the Routing dialogue to return to the event destination configuration.

If a MIDI Output has already been routed to a MIDI port, subsequently added MIDI Outputs will be automatically routed to the last used MIDI port.

Note On, Note Off, Program Change and Control Change (CC) messages can all be selected for use with events.

The remainder of the destination section is used to configure the outgoing MIDI message (MIDI Channel, Note Number etc. as applicable).

Various console functions can be actioned from events. A full list is included below.

Console Functions can be set to operate in a number of different ways:

• Follow On : Function state follows event state
• Follow Off : Function state follows inverse of event state
• Toggle : Function state toggled whenever event state becomes true
• Turn On : Function turned on when event state becomes true; second event or direct function interaction required to turn the function off
• Turn Off : Function turned off when event state becomes true; second event or direct function interaction required to turn the function on

Path functions require the specific path number to be entered (or engage All Paths to affect all paths of the selected type).

Events can be used to set path faders to a specified level using the Fader Function event destination.

Fader functions require the specific path number to be entered (or engage All Paths to affect all paths of the selected type).

Once a path (or paths) have been selected, set the desired dB value for the path(s).