Table of Contents
Advertisement
T*AP
Network trigger are based on the EmBER+ protocol from Co. l-s-b
The T*AP receives such trigger over the TCP/IP network. The trigger are issued by a device that has
implemented the EmBER+ protocol (e.g. VSM server). You may assign these triggers to virtual as well
as physical (e.g. LBP) buttons of a VSM installation. But also a broadcast automation system may have
an EmBER+ client running that may trigger an event in the T*AP.
#
Label
Below is a screen shot of the VSM gadget connector :
For the Ember tree you must select :
"Device" > controller_dsp > network_trigger > parameters > #.
setup GUI – EVENTS – Trigger – Parameter Sources
Below is an example of a few parameter trigger sources :
Label
Category
Subcategory
Parameter
Expression 1
Expression 2
number of the network trigger
label of that network trigger. It appears on the
Trigger Configuration pane as well as in the EmBER+ tree of the
VSM Studio gadget connector.
As a value you will receive the trigger name
In this example it is the default network trigger name.
input field for a label of a parameter trigger source
[INTERFACES / DOLBY PROCESSING / AUDIO PROCESSING]
e.g. If Category = DOLBY PROCESSING, possible Subcategories
are : [Metadata Routing / Metadata Program / Decoder / Encoder]
check all possible combinations with your T*AP
e.g. if Subcategory = Metadata Routing, possible parameters are:
[D SUB Metadata Input Status / Decoder Metadata Status /
SDI1 – VANC Metadata Input Status
SDI2 – VANC Metadata Input Status]
e.g. if Parameter = Status, possible expressions are:
[NA / FAIL / CORRUPT / PCM / CONSUMER / OK].
The Expression allows multiple values. I.e. you may select PCM &
CONSUMER. Since the drop down box is too small,
both status expressions are marked green and the word
<multiple values> will be used.
will be implemented soon
51
http://www.l-s-b.de/uk
from the T*AP.
Advertisement
Table of Contents
