junger T-AP, Manual, Page: 55 / 68

T*AP
51
Network trigger are based on the EmBER+ protocol from Co. l-s-b http://www.l-s-b.de/uk
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.
# number of the network trigger
Label 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.
Below is a screen shot of the VSM gadget connector :
For the Ember tree you must select :
"Device" > controller_dsp > network_trigger > parameters > #.
As a value you will receive the trigger name from the T*AP.
In this example it is the default network trigger name.
setup GUI – EVENTS – Trigger – Parameter Sources
Below is an example of a few parameter trigger sources :
Label input field for a label of a parameter trigger source
Category [INTERFACES / DOLBY PROCESSING / AUDIO PROCESSING]
Subcategory e.g. If Category = DOLBY PROCESSING, possible Subcategories
are : [Metadata Routing / Metadata Program / Decoder / Encoder]
check all possible combinations with your T*AP
Parameter 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]
Expression 1 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.
Expression 2 will be implemented soon