Event Service

Event-Service-menu

The context menu of the secondary events panel provides the "Event Service" submenu with access to the following supported external devices:

The Open API is available for the customers to implement the support for any other devices. The controlling commands syntax is described in the Cinegy Air Event Service API Manual.

Controlling the "VikinX VD0808" SDI Switcher

Event Commands Format

Having installed the external event service as described in the Cinegy Event Manager section, you can use this service to control the VikinX VD0808 video switcher.

The table below shows the events format used to control this device.

Device Command Op1 Op2 Op3 Description
VIKINX crosspoint <Level> <In> <Out> Set the crosspoint at level <Level> from input <In> to output <Out>.

For example, this event will connect input 1 to output 2 at level 4:

Device: VIKINX

Command: crosspoint

Op1: 4

Op2: 1

Op3: 2

If this event is sent to the VikinX event service, the following message appears in the service console window:

25.08.2016 12:00:32.107 EVENT: VIKINX crosspoint 4 1 2 : succeeded.

It means that the service has received the event successfully.

Device Configuration

You can use the configuration utility to define the device settings (e.g. the COM port number used to connect the "VikinX VD0808" device). This utility is automatically started by running the InsatallLocalService.bat and InsatallRemoteService.bat files.

Controlling the "Protocol 2000" Based Switcher (e.g. Kramer VS1616SDI)

Event Commands Format

The table below shows the events format used to control the Protocol 2000 based devices.

Device Command Op1 Op2 Op3 Description
KRAMER crosspoint_video <Machine number> <In> <Out> Set the video crosspoint only on the device defined by <Machine number> from video input <In> to video output <Out>.
KRAMER crosspoint_audio <Machine number> <In> <Out> Set the audio crosspoint only on the device defined by <Machine number> from audio input <In> to audio output <Out>.
KRAMER crosspoint_all <Machine number> <In> <Out> Set both the video and audio crosspoints on the device defined by <Machine number> from input <In> to output <Out>.

Controlling the NVISION Device

The table below shows the events format used to control the NVISION device.

Device Command Op1 Op2 Op3 Description
NVISION crosspoint <In> <Out> <Level> Set both the video and audio crosspoints from input <In> to output <Out>. The current use of video/audio crosspoint is defined by the <Level> parameter.
NVISION crosspoint_all <In> <Out> or empty Set both the video and audio crosspoints from input <In> to output <Out>. The level <Level> for both video and audio crosspoints and output <Out> (if empty) are defined in the device configuration.
NVISION crosspoint_video <In> <Out> Set the video crosspoint only from video input <In> to video output <Out>. The level <Level> is defined in the device configuration.
NVISION crosspoint_audio <In> <Out> Set the audio crosspoint only from audio input <In> to audio output <Out>. The level <Level> is defined in the device configuration.

Use the configuration utility to define the device settings. This utility is automatically started by running the InsatallLocalService.bat and InsatallRemoteService.bat files.

Controlling the Harris Router

Harris router uses the Leitch serial protocol of two types: terminal and pass-through.

The table below shows the events format used to control the Harris router.

Device Protocol Type Command Op1 Op2 Op3 Description
HARRIS terminal crosspoint <Level>:<In>,<Out> Set the crosspoint at level <Level> from input <In> to output <Out>. To use multiple outputs, list them separated by commas. Additional crosspoint requests can be included in the <Op1> line by separating each set with a "/" separator.
HARRIS pass-through crosspoint <Level>/<Out>,<In> Set the crosspoint at level <Level> and define for output <Out> and input <In> values in Hexadecimal number from 0 to FFF0.

Each crosspoint field is treated as a completely separate command.

For example, with terminal protocol type, the event with the following configuration will connect input 2 to output 3 at level 1 and input 4 to outputs 5 and 6 at level 2:

Device: HARRIS

Command: crosspoint

Op1: 1:2,3 / 2:4,5,6

Op2:

Op3:

For example, with pass-through protocol type, the event with the following configuration will take input 31 (hex. 1F) on levels 0, 1, and 4 to output 4:

Device: HARRIS

Command: crosspoint

Op1: 014/4,1F

Op2:

Op3:

Controlling the UTAH Scientific Router

The table below shows the events format used to control the UTAH Scientific router.

Device Command Op1 Op2 Op3 Description
UTAH crosspoint <In> <Out> <Level> If the level is not defined, this data is taken from the settings.
UTAH disconnect <In> <Out> <Level> If the level is not defined, this data is taken from the settings.

Controlling the Blackmagic Videohub

The table below shows the events format used to control the Blackmagic Videohub router.

Device Command Op1 Op2 Op3 Description
BMDVIDEOHUB crosspoint main crosspoint reserve crosspoint (optional) The "crosspoint" definition has the following format: <[O|M]out>,<[I]in> [<[O|M]out>,<[I]in>…]
Ports can have the following prefixes:
I(i) – input port, no need to use at all;
O(o) – output port (default);
M(m) – monitoring output port (should always be set explicitly).

Delimiters between the output/input pair are , or :, no white space is allowed.

Delimiters between the route commands are: space, ;, \t (tab).

For example:

2,1 – route output port 2 to input port 1;

o2,i1 (or O1,I1 etc.) – route output port 2 to input port 1;

2:1 – route output port 2 to input port 1;

M2,1 – route monitoring output port 2 to input port 1;

3,2 4,2 o5,2 – three route commands in one sequence (output port 3 to input port 2, output port 4 to input port 2, output port 5 to input port 2).

GPI Driven Devices

GPI (General Purpose Interface) is the universal interface that can be used to control any external devices that support the GPI protocol. Cinegy supports the SeaLevel GPI board, which should be installed in order to use the GPI signaling.

Event Commands Format

The table below shows the events format used to control the GPI driven devices.

Device Command Op1 Op2 Op3 Description
GPI setpin <pin number> [0..7] value (0 or 1) Set the value (0 or 1) on the specified GPI pin.
GPI setbyte <byte mask> [0..255] Set all the pins by mask.
You may also be interested in: