ADC™ Air Client
Operations and Installation
Appendix B
Appendix B
Secondary Events
Secondary events are associated with the primary event above it in the play list. Multiple secondary events can be assigned to a primary event and are played concurrently. A secondary event’s time is used as an offset in relation to the primary event’s time. You can edit the configuration parameters of some secondary events. When inserting an editable secondary event, a dialog box allows you to configure its attributes and settings.
Editable secondary events include:
GPI Contact, Back Timed GPI, Keyer On/Off, Transition Key, Audio Over On/Off, Transition Audio Over,
External and Data Event with Data.
To access an editable secondary event already in a play
To open the associated dialog box of an editable secondary event already in a play list,
1. Click on the event’s number.
2. From the ribbon tabs select Events > Edit Secondary.
Secondary Switching Parameter (sSP)
The secondary switching parameter contains values depending on the event type. For primary and secondary Audio/Video events, the value is the audio modes, mono and stereo. By default, the audio mode is stereo. The value is initially set in a media prep product, such as Media Client, for the Audio
Format database field. It can be modified in Air Client by clicking an event and entering S or M in the sSP field in Revise mode (ALT + R).
For secondary key and secondary audio over events, the value ranges from 1 to 9. The number corresponds to a keyer or mixer channel number on the master control switcher.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 291
ADC™ Air Client
Operations and Installation Appendix B
If the Audio Mode selection for an existing ADC DB record is modified by the Media Client Operator, then this update is sent to the event if it exists within an active playlist.
Secondary Audio/Video (sAV)
The secondary Audio/Video Audio Over event is used to add another A/V audio source over the primary audio/video source. The A/V audio over source may replace the primary A/V audio source or be mixed with it.
A secondary Audio/Video Audio Over event plays material, in addition to the primary event on air, for
use in effects such as keys, audio overs and mixes.
When inserting a new secondary audio/video event in a play list, play (P) and thread (T), but not auto
(A), are entered into the Type field. Switching is not used for this event. The event can be used to produce the audio/video over for a key/audio over input to a master control switcher or as an
audio/video breakaway.
To switch the switcher
An A/V event may be run to switch the switcher. To do this, enter an A, instead of a P or T, in the Type
field. The secondary event will begin with an audio-follow video transition.
Back Timed Secondary Audio/Video (bAV)
The Back Timed A/V (backtimed secondary audio/video) event is the same as a Secondary Audio/Video, except the secondary’s on-air time is the amount of time before the primary event will begin. (i.e. The offset is measured backwards in time from the start of the associated primary event.)
In the event Type field, these events are inserted with types P and T (but not A). No switching is done on these events, unless this is changed. These events can be used as a key/audio over inputs to a master control switcher. It is possible to associate a switching event with a back timed event. To do this, change the Type field to A. This event starts with an audio-follow-video transition.
Note: Backtimed events cannot be run after up-counting events.
GPI Contact (sGPI)
A GPI contact closure secondary event controls the contact closure on a GPI card. The Device Server must have the optional GPI card.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 292
ADC™ Air Client
Operations and Installation
For each event, an on time (offset) and duration value must be entered.
Appendix B
An offset indicates how long after the start of the primary event the contact closure should occur.
The duration value sets the duration of the pulse or length of closure of the contact.
The offset is entered in the event’s on-air field and duration in the DUR field. The GPI closure may be longer than the associated primary event.
Note: The GPI Contact will play with the corresponding Primary Event at the same time, regardless of value of "Time". The event will display as played at the primary event time, although the actual GPI contact will close at the exact time.
GPI Contact dialog
In following parameter configuration dialog is on the Air Client:
Back Timed GPI (bGPI)
A Backtimed GPI is similar to a standard GPI event, except that the offset is measured backwards in time from the start of the associated primary event. For example, a backtimed GPI event with an offset of 5 seconds fires the GPI contact 5 seconds before the start of the associated primary event.
A backtimed GPI event cannot be attached to an event following a primary upcount event. In this case, the system would not be able to calculate when to begin the GPI event.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 293
ADC™ Air Client
Operations and Installation
Back Timed GPI dialog
In following parameter configuration dialog is on the Air Client:
Appendix B
Keyer On/Off (sKEY)
A Keyer On/Off event allows events to have an offset from the beginning of the event to be specified.
Define a secondary Keyer event in which a hole is cut in the associated primary event’s video output and is filled with the output of the Keyer source.
The task performed by the key depends on the capabilities of the device you are using. This function will only be performed if the primary event’s A/V Switching data is configured to use a Master Control
Switcher.
Key Event dialog
In this window, the following parameters can be set:
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 294
ADC™ Air Client
Operations and Installation Appendix B
Modifier. This parameter specifies how the key source is outlined. The options are normal, shadow, drop shadow and border.
Source. The key fill’s source. When self is selected, the fill input both cuts and fills the hole. When external is selected, the key input cuts the hole and fill input fills it in. When chroma is selected, the key is determined by the colors of the background video.
Matte. When selected, fill input is replaced by a matte source. The matte source color is determined by the mixer controls.
Key Hold. When selected, this option will keep the keyer on through subsequent primary transitions.
On Time. This will determine the start time of the keyer event. This option determines how long after the start of the primary event the key is overlaid. The value must be greater than 1.5 seconds or the key will arrive late.
Note: This secondary event behaves identically to the Transition Audio Over and Transition Keyer secondary events when the value for the On Time field is blank or 00:00:00.00.
Duration. Determines the length of time the key is overlaid. Do not specify a keyer event to turn off during the next event’s preroll, as mixers are not equipped to carry out both actions concurrently. In order to have the key last as long as the primary event, make the duration field blank.
The duration of the keyer event can either be blank, or specified as equal or greater than to:
the duration of the primary minus the secondary's (normal) offset
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 295
ADC™ Air Client
Operations and Installation
the duration of the primary plus the secondary's back timed offset
the duration of the secondary's end-timed offset
The keyer can be removed by the End Key Hold function.
Appendix B
Speed and Effect. The speed option determines the speed of the transition effect. You may also set which type of effect will run between events by using the icons located above the time fields. Effect options are cut, mix, wipe, fade fade, cut fade and fade cut.
Key. Specifies which key source to use. Do not specify a keyer event to turn off during the next event’s preroll, as mixers are not equipped to carry out both actions concurrently. Also, it is not possible to have two transitions overlapping in time; however, you can associate two keys with the same event as long as you set their on time and duration so they do not overlap.
A/V Keyer On/Off
The secondary Audio/Video Keyer event is used to add an A/V Keyer source over the primary audio/video source. The A/V Keyer source may replace the primary audio/video source or be mixed with it.
Transition Keyer (sTKY)
A transition keyer secondary event is similar to Keyer On/Off, except that the keyer is brought up at the start of its associated primary event with the same transition type as that of the primary. This type of secondary event has a configuration dialog box similar to Keyer On/Off; however, for the transition key, the value of the offset cannot be set. It is possible to define a transition key event so it lasts as long as the primary event. To do this, make the duration field blank. If the key hold option is on, the key is held over the transition in the same way as an ordinary secondary keyer event.
Transition Keyer dialog
The following parameter configuration dialog is on the Air Client:
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 296
ADC™ Air Client
Operations and Installation Appendix B
To define a transition key event to last as long as the primary event make the duration field blank.
If the key hold option is on, the key is held over the transition in the same way as an ordinary secondary keyer event.
Audio Over On/Off (sAOV)
The Audio Over secondary event is used to add another audio source over the primary audio/video source. The audio over source may replace the primary audio source or be mixed with it.
To have the secondary audio event end at the same time as its primary event, make the duration field blank.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 297
ADC™ Air Client
Operations and Installation
Audio Over dialog
The following parameter configuration dialog is on the Air Client:
Appendix B
Audio Over. The number of the audio input line on the mixer.
Ratio. The ratio of over audio source to primary source audio, ranging from 0 (all primary sources) to 99
(all audio over source).
Speed and Effect. The Speed option determines the speed of the transition effect. You may also set which type of effect will run between events by using the icons located next to the time fields.
Transition effect options are cut, mix, wipe, fade fade, cut fade and fade cut.
On Time. This determines the start position of the event and how long after the start of the primary event the audio is overlaid. The value must be greater than 1.5 seconds or the event arrives late; however, you may use the Transition Audio Over to restart the audio when the primary event beings.
Note: This secondary event behaves identically to the Transition Audio Over and Transition Keyer secondary events when the value for the On Time field is blank or 00:00:00.00.
Duration. Determines the length of time the event is overlaid. The event is only performed if the primary event’s A/V Data is configured to use a Master Control Switcher.
Transition Audio Over (sTAO)
The secondary Transition Audio Over allows you to specify a secondary audio event to coincide with the primary event in the same manner as a transition keyer event, as described in Keyer On/Off.
This event has a set of options that are identical to the audio over on/off secondary event, except that the ontime option is missing (the ontime for a transition audio over event is set to 0).
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 298
ADC™ Air Client
Operations and Installation Appendix B
To have the secondary audio event end at the same time as its primary event, make the duration field blank.
Transition Audio Over dialog
In following parameter configuration dialog is on the Air Client:
Break
A break may be inserted at a point on the list where you would like the list to stop running. Events will play out normally up to this event.
The first event after the Break event cues up as usual, but does not play and the program switches to black. To restart a list after a break, click Play on the control panel. This list may also begin if a GPI contact input is used or if preroll is initiated on a hard start event that is next on the list.
Comment (****)
Use this secondary event to enter notes into the play list. Comments are ignored during transmission.
Any text may be inserted into the title field of a comment.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 299
ADC™ Air Client
Operations and Installation
Compile ID (cmID)
Appendix B
This type of event is used to label a compilation list with an ID. The tape ID of the compile tape should be entered into the ID field.
Data Event (sDAT)
This type of secondary event is associated with a device but does not generate any video output.
Instead, the action specified by the event is performed at the time the event would be put on air, had the event been associated with a video device.
For video disk servers, a data event is used to control and automate the deletion of spots from the server. The use of this event with video disk servers requires an accurate scheduler or traffic program. If the events are not used carefully, spots may be accidentally deleted in the video disk server. Secondary data events are Secondary Events used to command serial devices requiring a simple command that does not need to run a countdown on the time of an event.
This type of secondary event attaches to a primary event that plays at the time the command is sent to the device to execute the data event command. The primary event can be any primary event for any device.
The command is sent to the device whose device ID matches the event ID. As an example, the commands for the video disk server are entered in the secondary event’s title.
The command, Delete From Disk, is entered as DEL:XXXXXXXX:YY. X’s represent the spot ID and Y’s represent the optional port value.
The command, Get From Archive, is entered as GFA:XXXXXXXX:YY.
The command, Delete From Archive, is entered as DFA:XXXXXXXX:YY.
Note: This secondary event may work differently based on the device being used.
IMPORTANT: The Secondary Data Event command is sent out in preroll. For example, in order to send the command like a sAV or any other type of secondary event when the primary starts, an offset of
3 seconds must be added.
Barter Spot (sBAR)
Barter spot events are associated with a primary event and are logged to the AsRun log when the primary event runs to completion and is logged. Barter spot events are treated as comments by the automation system and are not played.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 300
ADC™ Air Client
Operations and Installation Appendix B
Barter spot is used for reconciliation with traffic systems. A barter spot is a source of audio/video that is part of another audio/video source. It is not played as separate audio/video, but is treated as a comment that is passed to the AsRun log and to the reconciliation process.
This event is attached to the primary event. When the primary event finishes running it is logged to the
AsRun log.
These events appear in the text AsRun log as Barter in the status field. In the enterprise traffic log for example, they appear as BTR in the program type field. The appearance of the spots in the logs does not positively indicate the spots have run. If the primary event runs, the spots are logged; however, the spots may not have actually been on the primary material.
Record Switcher (sRSW)
Record switcher is a secondary event that performs extra switching for inputs. During a recording, this switches to the secondary event’s source.
The name of the source to switch to is entered in the title field. This name must also be in the source name table for the switcher that is supplying the video to the record device.
The event is only performed if the primary event’s device has the A/V data parameters configured to specify the switcher number that has the matching name in its source name table.
Switcher Crosspoint (sXP)
This is a secondary event that performs extra switching for outputs. While an event plays, this function switches to the secondary event’s source:destination. This type of secondary event allows the control of multiple crosspoints during one primary event.
The name of the new source:destination is entered in the title field. Use the format SRC,DEST where SRC is the name of the source and DEST, the destination. You may enter a maximum of 16 characters for the title and the name you enter must also be defined in the switcher’s device parameter field for Source
Name and/or Destination Name for the switcher that is controlling the output for the primary event.
This type of event requires that the primary device have the specified switcher device configured for its switching information. If the secondary event does not specify the source (title =, DEST), the input crosspoint must be specified in the primary event’s device for the secondary event to default the destination.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 301
ADC™ Air Client
Operations and Installation Appendix B
To control a Router other than the configured default: If the user wants to switch a router other than to the one assigned in the primary AV table, then the router name must be entered in the ID field of the sXP event.
Switcher Audio Crosspoint (AUD-XPT)
This is a secondary event – similar to a switcher crosspoint event - that performs extra switching for audio outputs. While an event plays, this function switches to the secondary event’s audio source:destination. This type of secondary event allows the control of multiple audio crosspoints during one primary event.
When selected for logging, the logging is done at zero crossing of the primary event.
When "Switcher Audio Crosspoint" is selected in the configuration, and the "Control Audio Mode" option is selected in the configuration:
The Secondary Switching Parameter (sSP) field is neglected.
A new secondary event "Switcher Audio Crosspoint" is used for the audio routing (shuffling).
If a "Switcher Audio Crosspoint" secondary event is not attached to the primary, default values are applied for routing as per the configuration.
Format of Title field:
x1 x2 x3 x4
x1 to x4 are input values for output 1 to 4
X1 to x4 = 1 to 4.
If any of the input (x1 to x4) is not valid, it is replaced by its default (Configuration) value.
If 2 or more "Switcher Audio Crosspoint" secondary events are found (resulting from an editing mistake), only the first one is taken into consideration.
Note: Audio routing is done on the device specified in the ID field, if valid. If ID field is not valid then audio routing is done on the primary event to which the secondary Switcher Audio Crosspoint is attached.
When the next event is preset, its corresponding cross point is normalized to the default as specified in the configuration, provided the next event audio crosspoint is not the same as the current event.
Secondary Record (sREC)
This type of secondary event allows for the automatic recording and segmenting of live program material for immediate playback to air. Unlike most record events, this event is used in a list that combines record and playback activities. A secondary record event is attached to each primary event that is being recorded.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 302
ADC™ Air Client
Operations and Installation
Break Sync (sSYN)
Appendix B
Break sync contains an estimated time of day a pod will run, a deviation time and a time for a window of opportunity for the operator to react to the event.
This event is normally be used on a list that contains only pods/breaks of commercials. The pods are:
Separated by either an upcount event or by this Break sync event.
Triggered to run by an external contact closure (GPI) or by clicking Play on the control panel.
In normal operation, a contact closure/play button is detected and the next pod on the list is played. The break sync event is marked DONE immediately. The pod plays out until either an upcount event, break sync event or the end of the list is encountered.
If the next pod has not played by the time of day specified on its break sync event, plus its deviation, the automation sends out a user notification to all automation clients. The event then waits for the opportunity time for a client to respond to the notification.
If no response is received at the end of this time, the automation marks each event in the pod and the break sync event as being missed. It stops marking events as missed when it encounters an upcounting event or break sync event.
If the list was running an upcount event, that event is skipped and the next upcount event runs. During the time the automation is waiting when the break sync occurs, the user notification is sent to all clients. One or more clients are enabled to detect the user notification.
The enabled clients display a dialog box prompting the operator to click OK to Delete Pod and Keep
Pod. The dialog box is displayed only during the waiting time and will automatically close if the operator does not respond. This is the equivalent to clicking OK to Delete Pod since the list on the server will time out and mark the pod missed.
If the operator clicks Keep Pod, a message is sent back to the server causing the server to mark the break sync event as done, but leaves the pod intact waiting for the contact closure/play button. There is no other user notification for this pod.
If the contact closure/play button does not occur, the time of day for the break sync event for the next pod may occur. To eliminate a potential problem, the next break sync event is used to mark the previous pod missed. This occurs automatically at the time of day of the next break sync event minus its deviation time. When this occurs, all events before this event are marked missed.
If the automation had been running an upcount event, then this upcounter and the next up-counter before this break sync event are terminated before this event runs.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 303
ADC™ Air Client
Operations and Installation
Secondary System (sSYS)
Appendix B
This event allows the traffic system to schedule device (resource) assignment during the execution of a transmission list. Like all secondary events, this type of event is attached to a primary event.
When this event type is run, it is able to move un-assigned device heads to the list that is running this event or release device heads in order to make them available to another list. It is up to the traffic department to schedule the assignment and release of heads so that two lists will not conflict in their usage of these heads. This event is programmed by filling in the time, ID and title fields of the event with control information. The time field controls the time when the event will run offset from the primary event.
Event IDs
The following event IDs act as commands to the list:
Assign. Will assign the device and head(s) specified in the title field to the transmission list the event is located in. The title format is: DEVICENAME,X,Y
Where DEVICENAME is the device name (5 characters) that is assigned to the device, X is the head number assigned to the list and ,Y is the number of other heads to be assigned.
Release. Will remove the device and head(s) specified in the event title field from the transmission list the event is located in and return it back to the system as an unowned device head. The title format is identical to the above described.
Protect. Performs a protect assignment on the device and head(s) to the device specified in the type field.
The title format is: PROTECTNAME, DEVICENAME,X,Y
Where PROTECTNAME is the name of the device that is to be protected. DEVICENAME is the device name (5 characters) that is assigned to the device, X is the head number assigned to the list, and Y is the number of other heads to be assigned. You must first have assigned the primary device heads to the list before assigning the protect heads. A space character may be substituted for the comma in any of the title field commands.
Backtimed System (bSYS)
This secondary event works in the same manner as secondary system except that this event type runs prior to the primary event by the time specified in the Time field.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 304
ADC™ Air Client
Operations and Installation
System Event
Appendix B
This secondary event allows the traffic system to schedule device (resource) assignments during the execution of a transmission list. Like all secondary events, this type of event is attached to a primary event. When this event type is run, it is able to move unowned device heads to the list running this event or release device heads in order to make them available to another list. It is up to the traffic department to schedule the assignment and release of heads so that two lists will not conflict in their usage of these heads.
External (vDT)
Use an External secondary event to send commands or other information to a device through a device server. This event acts as a secondary A/V event with the capability of sending commands or other information to a specific device on the device server.
To Insert an External secondary event
When you insert this secondary event, a dialog box opens that prompts you for the data you want to send to a device. Normally, the dialog box is a text editor window, but if there is a special .dll file for the device, this may vary.
1. Enter the data you want to send to a device on the network in the text editor.
2. After clicking OK, Air Client inserts a line in the play list or transmission window and enters into
Revise mode.
3. Enter the device ID name in the Id field. vDT is inserted in the Sec field.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 305
ADC™ Air Client
Operations and Installation Appendix B
4. Exit Revise Mode. To exit Revise mode, press <ALT+R> or from the Events ribbon tab select the
Cancel icon ( ).
Data Event with Data (sDAT)
Use this event to send commands and other information to a specific device on the device server.
To Insert a Data Event with Data
When inserting this secondary event, use the text editor, to enter the commands. The commands are sent to the device whose device ID matches the event ID.
1. Enter the data you want to send in the text editor.
2. After clicking OK, Air Client inserts a line in the play list or transmission window and enters into
Revise mode. sDT is inserted in the Sec field.
3. Exit Revise Mode. To exit Revise mode, press <ALT+R> or from the Events ribbon tab select the
Cancel icon ( ).
The time in the time field is the offset from the preroll of the associated primary event.
The commands are sent to the device at the offset time.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 306
