Setup Gui - Events; Setup Gui - Events - Trigger - Trigger Configurations - junger T*AP Manual

Hide thumbs Also See for T*AP:
Table of Contents

Advertisement

T*AP
setup GUI – EVENTS
As mentioned in the initial paragraphs, you have a sophisticated event management system on hand, that
allows you to initiate events manually (via the X*AP Remote Panel Hotkeys), semi-automatically
(by external commands or GPIs) and automatically (by changes to the internal status or parameters).
The T*AP knows three different event types, which will recall pre-defined presets :
Preset Events
Action Events
Bypass Events
A Trigger is the logical combination of up to two trigger sources. The Trigger will launch one or more
events. An event runs like a flip-book inside the T*AP. This powerful technology spans from simply
recalling a certain parameter to the complete reconfiguration of the T*AP from 4x2 to 5.1 +2 program
configuration, including all signal routing, Dolby metadata handling, processing parameters and so forth.
But it also enables several fail over scenarios where the T*AP will automatically react to the system and/or
parameter status.
The way to set up the EVENT system is as follows :
1.
Define
trigger sources
2.
Configure
a trigger by logical combination of up to two trigger sources
3.
Assign
trigger to event(s)
4.
Decide
what shall happen (select presets for the events)
setup GUI – EVENTS – Trigger - Trigger Configuration
This is an excerpt from the Trigger Configuration pane :
Trigger #
Source 1
invert
type
source
logic
Source 2
Important Note! By accident you are able to set up a recursive behavior (same trigger is used for
trigger setup or in an event that may activate this trigger). The plausibility is not checked so you may
experience strange things if you are not careful.
System / Interfaces / Routing / Dolby Processing / Audio Processing
GPOs / Loudness Measurement
bypass of respective function blocks
here you define a name for the trigger (Preset Load).
the first source of a logical combination of two trigger sources.
if the type of trigger allows an inverted operation it can be defined here.
the device knows different types of triggers [GPI, Hot Key, Network,
Event active, Trigger active, Bypass, Sync Lock].
if the selected trigger type has multiple possible sources you must
define it here [e.g. 1 ... 8 for GPIs]. It acts like an index for the trigger
source type.
kind of logical operation [and, or, xor].
second source of a logical combination of two trigger sources. If only
one source exists, you may leave it unassigned [-].
49

Advertisement

Table of Contents
loading

Table of Contents