Playlist Editing Operations. Imagine communications ADC v4.26.62
Below you will find brief information for Air Client ADC v4.26.62. The Air Client is a software application that allows users to control and manage the on-air playout of video and audio content. It offers a range of features for building playlists, running transmissions, previewing content, and managing events. It also provides tools for monitoring device status, searching for content, and managing errors.
Advertisement
Advertisement
ADC™ Air Client
Operations and Installation
Playlist Editing Operations
Playlist Editing Operations
To Open an Existing Playlist
Use play list windows to create and edit play lists.
1. From the File ribbon tab select the Open Play List icon (
2. Select the play list file you wish to open and view.
).
3. Once the play list file is open, the file can be checked for accuracy, changes can be made, etc.
Note: Your Play List name may be different than what appears here.
Saving a Play List File
1. Select a play list file or the On Air transmission list to save.
2. From the File ribbon tab select the:
Save Play List icon ( ), to save the Play List to the current file name. This will overwrite if filename exists already OR
Save Play list As icon ( selected prior to saving.
), to save the Play List to a different file name. A file type can be
3. In the Save Playlist dialog, type in a new file name or accept the existing file name.
4. Select Save.
Inserting Primary Events
Primary events, such as programs and commercials, constitute the majority of a play list’s events. They may be accompanied by secondary events, and transition effects.
Events can be inserted into a play list using two methods:
Manually. You can type event data directly into a play list.
Move events to the play list. You can move records from the database or spots from a device storage window directly into a play list, via drag-and-drop or copy-and-paste.
Limitation: Do not use the same ID between different record types (i.e. single spot and multi-segment event).
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 118
ADC™ Air Client
Operations and Installation
To Insert a Primary Event
1. Position cursor on the list where you want to insert a new event.
Playlist Editing Operations
2. From the Events ribbon tab select the Insert Primary icon ( keyboard. (A new Primary event is inserted above the cursor.)
) or press the <INS> button on the
3. The cursor will be in Revise Mode. Type in the ID in the ID column. Below is an example of an event in Revise mode.
When an ID is entered, it is checked against its record in the database. If the ID is not found, the remaining fields are checked and their values may be changed or left as is according to list options configured in the Environment dialog box.
4. If the record is in the database, the fields will fill in with data when getting out of Revise Mode.
5. Repeat these steps for additional primary events.
6. When finished inserting primary events, exit Revise mode. To exit Revise mode press <Alt+R> or from the Events ribbon tab select the Cancel icon ( ).
Note: When Insert Primary is selected again while still in Revise Mode the new primary event is placed below the cursor. This speeds up the process of building a play list file or block of events on a transmission list.
Inserting Multi-Segment Events
When inserting an event with multiple segments as defined in the database, you must specify which segment to insert by entering its number in the Segment field. If you do not enter a segment number, the Select Segment dialog box opens and displays all segments of the multi-segment event.
Limitation: Do not use the same ID between different record types (i.e. single spot and multi-segment event).
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 119
ADC™ Air Client
Operations and Installation Playlist Editing Operations
To Insert a Segment
1. Click a segment in the Select Segment dialog box, and then click OK to insert it into the play list.
2. Make changes to event info if necessary.
3. When finished, exit Revise Mode. To exit Revise mode press <Alt+R> or from the Events ribbon tab select the Cancel icon ( ).
About Display Sequence Gaps
Although ADC automatically numbers segments sequentially there are scenarios, such as secondary recording, that can create multi segment records with non-sequential segment numbering (i.e. gaps in the sequence). Air Client displays such a gap properly, including all of the segments with the correct information from the database.
Media Client Note: Media Client allows and preserves multi-segment records that have non-sequential segment numbering (i.e. where there is a gap in the number sequence), although it is not intended that such records would be created within the Media Client prep form.
Managing Duplicate Single Spot and Multi Segment IDs
If duplicate Single Spot and Multi Segment IDs appear in the Database, the operator can choose which to insert on a Transmission List.
1. When a duplicate ID (e.g. ID 00011) is inserted onto a New, Edit, or Transmission List, on exiting
Revise Mode the Select Segment dialog is displayed.
2. Perform one of the following actions as required for the operation. Select Segment dialog:
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 120
ADC™ Air Client
Operations and Installation Playlist Editing Operations
Choose Click on Single Spot to get the Single Spot Database Record.
Highlight the desired Segment number, and then click OK to get that Segment's Database
Record.
Highlight the entire record, (Multi Seg), and then click OK to get the entire Multi Segment
Database Record.
Insert Secondary Events
Secondary events are inserted using the Insert Secondary option in the Events ribbon tab. Secondary events run in along with the primary event that precedes it. For a list of secondary events see: Appendix
B > Secondary Events (see "Secondary Events" on page 291).
IMPORTANT: ADC Air Client operators can attach up to 49 secondary events to a primary event within the ADC Transmission List. This value is critical to know for users who utilize hard start events within their ADC Transmission List. The logic within the ADC Transmission List requires the next hard start event to occur within the next 50 events.
To Insert a Secondary Event
1. Launch a playlist to view.
2. Select an event on the playlist
3. From the Events ribbon tab select the Insert Secondary icon ( in the keyboard. The Secondary Events Directory is launched.
) or press the <Shift + Insert> key
When inserting a secondary event in a play list, Air Client switches to Revise mode, allowing you to edit field data for the event.
You can also click an existing event and manually enable Revise mode to edit the existing ID or info in the event fields. To enter Revise mode press <Alt+R> or from the Events ribbon tab select the
Revise icon ( ).
4. Select the Secondary Events to insert into the playlist.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 121
ADC™ Air Client
Operations and Installation Playlist Editing Operations
Note: The configuration parameters of some secondary events can be edited. For details on
configuring these events see Configuring an Editable Secondary Event (on page 126 ).
Audio/Video: This function will insert a Secondary Audio/Video event into the list. It is used to air effects with the primary, like keys and or audio over mixes.
When inserting a new secondary audio/video event in a playlist, 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.
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. You may also add a transition effect.
Backtimed A/V: Same as a regular Sec. Audio/Video event, but the on-air time is the amount of time before the primary event that this event will begin.
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. You may also add a transition effect.
Note: Backtimed events cannot be run after up-counting events.
GPI Contact: Inserts a GPI Contact Closure to a device that initiates a switch. 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.
For details on configuring this secondary event see Configuring an Editable Secondary Event: To
Configure a GPI Contact (on page 126 ).
Backtimed GPI: 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.
Note: Backtimed GPI events cannot be attached to an upcount event.
For details on configuring this secondary event see Configuring an Editable Secondary Event: To
Configure a Backtimed GPI Contact (on page 127 ).
Keyer On/Off: This allows you to define a secondary Keyer event in which a hole is cut in the associated primary events video output and is then filled with the output of the Keyer source.
For details on configuring this secondary event see Configuring an Editable Secondary Event: To
Configure a Keyer On/Off (on page 128 ).
Transition Key: Similar to a Keyer On/Off event except, the key is brought up at the start of the associated primary event with the same transition type (i.e. brought up with a fade up, cut, wipe etc.).
For details on configuring this secondary event see Configuring an Editable Secondary Event: To
Configure a Transition Key (on page 130 ).
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 122
ADC™ Air Client
Operations and Installation Playlist Editing Operations
Audio Over On/Off: This 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.
Note: This event is only performed if the primary event’s A/V Data is configured to use a Master
Control Switcher.
For details on configuring this secondary event see Configuring an Editable Secondary Event: To
Configure an Audio Over On/Off. (see "To Configure an Audio Over On/Off" on page 131 )
Transition Audio Over: Similar to a standard Audio Over event except that it is brought up with the primary event and corresponding transition type.
For details on configuring this secondary event see Configuring an Editable Secondary Event: To
Configure a Transition Audio Over (on page 132 ).
Break: This is inserted at a point in 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 line will cue up, but will not play out, and the program switches to black.
To restart the list [after the break line], press Roll or 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: Used to enter Notes into the playlist. Any text may be inserted into the title field of a comment. Comment event lines are ignored during transmission. However, they do add events to the list size. You can enter text in the title field up to sixteen characters.
Compile ID: Used to attach a title to the head of a compilation list (i.e. It is used to label a compilation list with an ID). It has no effect on the playlist and is ignored during transmission.
Data Event: 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 (i.e. the time entered in the on-air [or Time] column), had the event been associated with a video device.
Typically used with 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 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.
For 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 on each device…refer to user notes for details on this option.
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: Used for reconciliation with the traffic system. 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,
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 123
ADC™ Air Client
Operations and Installation Playlist Editing Operations 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.
Attached to a program segment that has barter spots in it [network, nat’l]., these events appear in the text AsRun log as Barter in the status field. In the enterprise log, 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: This is a secondary event that performs extra switching for inputs. During a recording, this switches to the source denoted in the secondary events 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.
Note: The proper configurations must be set before this function can perform as dictated.
Switcher Audio Crosspoint: This is a secondary event that performs extra audio switching for outputs. It allows routing audio to a different destination.
Switcher Crosspoint: This is a secondary event that performs extra switching for outputs. It allows routing a program from one list to a different destination. 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.
For example, in the Title field, put source and destination desired (separated by a comma or space) i.e.…Sat1, Telco…The program airing from Sat1 will be routed to Telco. This must be configured first in the Device Parameters and not have the same crosspoint as the air source.
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.
Secondary Record: Allows for the automated recording and segmenting of live program material, for immediate or future playback to air. Unlike most record events, this event type is used in lists that combine record and playback activities. A secondary record event is attached to each primary event that is being recorded. It functions only in lists that combine record and playback material.
Break Sync: 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 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. The pods are triggered to run by an external contact closure (GPI) or by clicking Play on the control panel. In normal
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 124
ADC™ Air Client
Operations and Installation Playlist Editing Operations 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 automatically closes if the operator does not respond. This is the equivalent to clicking OK to Delete Pod since the list on the server times 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.
Secondary System: Used to allow the sharing of resources between lists.
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 unowned 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. 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
[,Y] is the number of other heads to be assigned.
Release: Removes the device and head(s) specified in the event title field from the transmission list the event is located in and returns 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]
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 125
ADC™ Air Client
Operations and Installation Playlist Editing Operations
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.
Y is the number of other heads to be assigned.
Note: You must first have assigned the primary device heads to the list before assigning the protect heads.
‘Space Character’: A space character may be substituted for the comma in any of the title field commands.
Backtimed System: 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.
External: 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. When inserting this secondary event, use the text editor to enter the commands.
For details on configuring this secondary event see Configuring an Editable Secondary Event: To
Configure an External Secondary Event (on page 133 ).
Data Event with Data: Use this event to send commands and other information to a specific device on the device server. 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.
For details on configuring this secondary event see Configuring an Editable Secondary Event: To
Configure a Data Event with Data (on page 134 ).
Event Header: This header is a primary event that has no duration, no device and does not impact ripple. It isn't included in the as-run log. This header provides visual separation between lists and provide an identifier that allows traffic to be able to replace a schedule.
Once the Event Header is added, its title can be manually edited as required.
5. When finished click OK. The secondary event is placed above the cursor in the play list.
Configuring an Editable Secondary Event
The configuration parameters of some secondary events can be edited. 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 Configure a GPI Contact
This procedure configures a GPI Contact Closure secondary event that has been inserted into the list.
IMPORTANT: The GPI event controls the contact closure on a GPI card. The Air Client workstation must have the optional GPI card. For more information about GPI and switch-only device configuration, reference the Device Server Operations and Installation documentation.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 126
ADC™ Air Client
Operations and Installation Playlist Editing Operations
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.
1. To open the associated dialog box of an editable secondary GPI event already in a playlist, click the event’s number, and then from the Events ribbon tab select Edit Secondary icon (
Secondary GPI dialog is opened.
). The
2. Set the following parameters for each event:
ID: Specify the ID of the secondary event (e.g. GPI). If required, click the Browse button (…) to locate.
On Time (offset): An offset indicates how long after the start of the primary event the contact closure should occur. The offset is entered in the event’s on-air field.
Duration: The duration value sets the duration of the pulse or length of closure of the contact.
The duration is entered in the event’s DUR field.
The GPI closure may be longer than the associated primary event.
3. When finished click OK.
To Configure a Backtimed GPI Contact
This procedure configures a Backtimed GPI Contact Closure secondary event that has been inserted into the list. 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.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 127
ADC™ Air Client
Operations and Installation Playlist Editing Operations
1. To open the associated dialog box of an editable secondary Backtimed GPI event already in a playlist, click the event’s number, and then from the Events ribbon tab select Edit Secondary icon
( ). The Backtimed GPI dialog is opened.
2. Set the following parameters for each event:
ID: In the playlist, a switch-only device’s ID must be entered in the secondary event’s ID field. If required, click the Browse button (…) to locate.
Back Time (offset): An offset indicates how long before the start of the primary event the contact closure should occur. The offset is entered in the event’s on-air field.
Duration: Enter the length of time the GPI contact is closed. This value can exceed the duration of the primary event. The duration is entered in the event’s DUR field.
3. When finished click OK.
To Configure a Keyer On/Off
This procedure configures a Keyer On/Off secondary event that has been inserted into the list. This option allows you to 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.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 128
ADC™ Air Client
Operations and Installation Playlist Editing Operations
1. To open the associated dialog box of an editable secondary key event already in a playlist, click the event’s number, and then from the Events ribbon tab select Edit Secondary icon (
Event dialog is opened.
). The Key
2. Set the following parameters for each event:
Note: 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.
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.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 129
ADC™ Air Client
Operations and Installation Playlist Editing Operations
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. 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.
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.
3. When finished click OK.
To Configure a Transition Key
A Transition Key is similar to a Keyer On/Off event except, the key is brought up at the start of the associated primary event with the same transition type (i.e. brought up with a fade up, cut, wipe etc.).
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 130
ADC™ Air Client
Operations and Installation Playlist Editing Operations
1. To open the associated dialog box of an editable secondary event already in a playlist, click the event’s number, and then from the Events ribbon tab select Edit Secondary icon ( ).
2. This type of secondary event has a configuration dialog box similar to Keyer On/Off;
For the transition key, the value of the offset cannot be set.
It is possible to define a transition key event so it will last 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.
3. When finished click OK.
To Configure an Audio Over On/Off
Audio Over On/Off is used to add another audio source over the primary audio/video source. It can be set with a percentage over ratio (For example, if set to 100%, it will completely replace the primary event’s audio.)
Note: The event is only performed if the primary event’s A/V Data is configured to use a Master Control
Switcher.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 131
ADC™ Air Client
Operations and Installation Playlist Editing Operations
1. To open the associated dialog box of an editable secondary audio over event already in a playlist, click the event’s number, and then from the Events ribbon tab select Edit Secondary icon (
The Audio Over dialog is opened.
).
2. Set the following parameters for each event:
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.
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.
Note: To have the secondary audio event end at the same time as its primary event, make the duration field blank.
3. When finished click OK.
To Configure a Transition Audio Over
Transition Audio Over is similar to a standard Audio Over event except that it is brought up with the primary event and corresponding transition type. It allows specification of a secondary audio event to coincide with the primary event in the same manner as a transition keyer event.
1. To open the associated dialog box of an editable secondary Transition Audio Over event already in a playlist, click the event’s number, and then from the Events ribbon tab select Edit Secondary icon
( ). The Transition Audio Over dialog is opened.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 132
ADC™ Air Client
Operations and Installation Playlist Editing Operations
2. The Transition Audio Over dialog options are identical to that of the audio over on/off secondary event, except that the ontime option is missing (the ontime for a transition audio over event is 0).
3. Set the following parameters for each event:
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.
Duration: Determines the length of time the event is overlaid.
Note: To have the secondary audio event end at the same time as its primary event, make the duration field blank.
Ontime: The ontime for a transition audio over event is 0.
4. When finished click OK.
To Configure an External Secondary Event
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.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 133
ADC™ Air Client
Operations and Installation Playlist Editing Operations
1. When this secondary event is inserted into a list, the Secondary External Event Text Editor dialog box opens that prompts for the data to send to a device. Normally this box is a text editor window, but if there is a special .dll file for the device, this may vary.
2. In the text editor, enter the data to send to a device on the network.
3. When finished click OK. Air Client inserts a line in the playlist or transmission window and enters into Revise mode. vDT is inserted in the Sec field.
4. When finished, exit Revise mode. To exit Revise mode on the list, press <ALT + R> or from the
Events ribbon tab select the Cancel icon ( ).
To Configure a Data Event with Data
A Data Event with Data secondary event is used to send commands and other information to a specific device on the device server. When inserting this secondary event, use the text editor to enter the commands.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 134
ADC™ Air Client
Operations and Installation Playlist Editing Operations
1. When this secondary event is inserted into a list, a text editor dialog box opens that prompts for the data to send to a device.
2. In the text editor, enter the data to send to a device on the network.
Limit: 4000 characters maximum
Data separated by carriage return linefeed (CRLF)
3. When finished click OK. Air Client inserts a line in the playlist or transmission window and enters into Revise mode. sDAT is inserted in the Sec field.
4. When finished, exit Revise mode. To exit Revise mode on the list, 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. At the offset time, the commands are sent to the device whose device ID matches the event ID.
Manage Back-Timed Events
It is possible to create a back-timed event by editing the event type instead of having to replace the event with a back-timed event. This is accomplished by placing a "<" feature in the event type field to create a back-timed event.
Event Type Field Syntax:
StartEventEndTimed = PT >
MatchPrimaryDuration = PT =
StartEventBackTimed = PT <
A ">" feature in the event type field creates an end-timed event.
It is recommend to stop using backtime event types (Like: bGPI, bAV, etc) and instead use the normal events (sGPI, sAV) with the backtime modifier (PT <).
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 135
ADC™ Air Client
Operations and Installation Playlist Editing Operations
These events are available on the translator as ExtendedEventControl := [tStartEventEndTimed] or [tStartEventBacktimed]
Secondary Events that can be Back-Timed
The following Lists which secondary events can be back-timed by enabling the
StartEventBackTimed bit in the event control field.
Data Events can be run back-timed. When run back-timed they are run at the offset value before the first frame of the primary they are attached to.
Transition events (KEY and AUDIO OVER) always run at pre-roll of the primary.
Keyer, Audio Over, Combined Audio/Video with Audio Over or Key, Record Switcher, and Source
Switcher Events cannot be back-timed. While it might seem that there are uses for this, these events require using the primary event to handle switching, and the primary event may not be threaded at the time these events are run. Without having a primary device threaded there is no way to establish the audio/video output path to apply the switch to. There may also be a conflict with using the Master Control switcher during the transition of the actual primary.
EVENT TYPE
Break Event (Stops List)
ALLOWED
no
Logo Event (Equivalent to Break Event)
Audio/Video Event
Back-timed Audio/Video Event
GPI Event no
YES no
YES
Back-timed GPI Event
Keyer On/Off
Transition Keyer On/Off
Audio Over On/Off
Transition Audio Over On/Off
Combined Audio/Video with Audio Over
Combined Audio/Video with Key no no no no no no no
BreakSync Event (custom feature)
Data Event
System Event
Back-Timed System Event
Record Switcher Event
Source Switcher Event
Record Device Event (for recording live events)
Comment Event no no no no no
YES
YES no
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 136
ADC™ Air Client
Operations and Installation
EVENT TYPE
Compile ID
Barter Spot
Playlist Editing Operations
ALLOWED
no no
To Specify ‘PT’ Event Type syntax
1. Open a list.
2. Highlight a primary event
3. Insert a target secondary event (See above "Secondary Events that can be Back-Timed".)
Or
Select an existing secondary event. (See above "Secondary Events that can be Back-Timed".)
4. Enter Revise Mode
5. Specify Type as the desired Event Type syntax (PT > , PT = , PT <)
6. Exit Revise Mode.
Manage End-Timed Events
End-timed means offset from the end of the primary event.
Secondary events can be end-timed by enabling the StartEventEndTimed bit in the event control field.
Secondary events can be started at an offset from the end of the primary event (end-timed). This is accomplished by placing a ">" feature in the event type field to create an end-timed event.
Event Type Field Syntax:
StartEventEndTimed = PT >
MatchPrimaryDuration = PT =
StartEventBackTimed = PT <
A "<" feature in the event type field creates a back-timed event.
These events are available on the translator as ExtendedEventControl := [tStartEventEndTimed] or [tStartEventBacktimed]
When Enabling a Key
End-timed events can be used to enable a key on the last 20 seconds of program material. Since the exact program segments length may not be known by traffic at the time the schedule is made, an end-timed event allows traffic to accurately bring the key on for the last 20 seconds.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 137
ADC™ Air Client
Operations and Installation
When Event Duration Matches the Offset
Playlist Editing Operations
When using end-timed offset events whose duration matches the offset, such as an Audio Over device that runs 20 seconds from the end for 20 seconds, there are two ways to specify this event.
Put 20 seconds in for the duration for the event, or
Use any arbitrary duration, but enable the MatchPrimaryDuration bit in the event control field.
Secondary Events that can be End-Timed
The following table lists which secondary events can be end-timed by enabling the StartEventEndTimed bit in the event control field.
Transition events (KEY and AUDIO OVER) always run at pre-roll of the primary.
End-timed events following UpCounter events are not supported.
EVENT TYPE
Break Event (Stops List)
ALLOWED
no
Logo Event (Equivalent to Break Event)
Audio/Video Event
Back-timed Audio/Video Event no
YES no
GPI Event
Back-timed GPI Event
Keyer On/Off
Transition Keyer On/Off
Audio Over On/Off
Transition Audio Over On/Off
Combined Audio/Video with Audio Over
Combined Audio/Video with Key
YES no
YES no
YES no
YES
YES
BreakSync Event (custom feature)
Data Event
System Event
BackTimed System Event
Record Switcher Event
Source Switcher Event
Record Device Event (for recording live events)
Comment Event
Compile ID
Barter Spot
© 2017 Imagine Communications Corp. Proprietary and Confidential. no
YES
YES no
YES
YES no no no no
5/25/2017 | Page 138
ADC™ Air Client
Operations and Installation Playlist Editing Operations
To Specify ‘PT’ Event Type syntax
1. Open a list.
2. Highlight a primary event
3. Insert a target secondary event (See above "Secondary Events that can be End-Timed".)
Or
Select an existing secondary event. (See above "Secondary Events that can be End-Timed".)
4. Enter Revise Mode
5. Specify Type as the desired Event Type syntax (PT > , PT = , PT <)
6. Exit Revise Mode.
Enable a List Freeze
ADC offers the ability to freeze on the last frame of a videodisk clip before a live (generally a promo, or a specific buffer event) in order to wait if the journalist is not ready on time and make the switching to the live manually on the MCS.
Option 1: Using a secondary Backtimed System event (bSYS)
1. For a List with a Preroll of 2 seconds, if a Freeze is required on the last frame of a Profile clip before a live break: (Your display may look different.)
2. Attach a Backtimed System event (bSYS) to the Live event to freeze: (Your display may look different.)
3. Increase the Duration of Profile clip (Demo0001) before the news break (STUDIO1 switch only) to 5 seconds to ensure the preroll of STUDIO1 will not have started when the freeze event plays.
4. Set the Backtimed offset of the freeze event to play on frame 00:00:09.17 after the beginning of
Demo0001. This to effectively address the device latency involved with executing the freeze (7 frames) 00:00:09.24 (i.e. the last frame).
The result is: (Your display may look different.)
5. Once the list is frozen, the operator switches manually the MCS to the live source.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 139
ADC™ Air Client
Operations and Installation Playlist Editing Operations
Option 2: Using a Secondary System event (sSYS)
1. If a Freeze is required on the last frame of a Profile clip before a live break, attach a Secondary
System event (sSYS) to the event to freeze:
2. The result is: (Your display may look different.)
3. Once the list is frozen, the operator switches manually the MCS to the live source.
Enable a Data Event (sDAT)
A Data Event is a type of secondary event that 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.
Note: This secondary event may work differently based on the device being used. For a list of secondary
events see: Appendix B: Secondary Events (see "Secondary Events" on page 291).
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.
Data Event Commands
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 ID of the secondary data event must match the ID MATCH NAME of the disk port to perform the action. Multiple Secondary Data Events may be placed on a single primary event.
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.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 140
ADC™ Air Client
Operations and Installation Playlist Editing Operations
These events are executed at preroll time of the primary event. Since these commands are performed instantly no heads are threaded and the disk status does not change (unless the disk goes BUSY for a moment).
The event is marked done if ADC sends the command to the disk. The event is marked missed if ADC cannot execute the command for any reason.
While many of these functions are not implemented on many disk systems, the following functions have been implemented:
Local Disk System Commands:
Delete: DEL:AnID or D:AnID
Delete Protect: PRO:AnID or P:AnID
Delete UnProtect: UNP:AnID or U:AnID
Archive System Commands:
Get From Archive: GFA:AnID:TapeID or G:AnID:TapeID
Delete From Archive: DFA:AnID:TapeID
Send To Archive: STA:AnID:TapeID or S:AnID:TapeID
Network or Fiber Channel System Commands:
Delete From System: DFS:AnID
Move or Copy To Disk: MOV:AnID:#1:#2 or M:AnID:#1:#2:#3:#4… or C:AnID:#1:#2:#3:#4…
Delete From Disk: DFN:AnID:#1
Abort Disk Transfer: ANC:AnID:#1:#2 or A:AnID:#1:#2:#3:#4… or T:AnID:#1:#2:#3:#4…
Command Parameter descriptions:
AnID is the ID to perform the function on.
#1 is the source unit number of the source video disk in the networked disk system. #2:#3:#4… are destination unit numbers configured for the networked disk system (only one destination is required, but as many that will fit in the title field may be specified.
TapeID is an optional parameter that is the Tape ID of the tape in the archive system that this file should be operated on.
Add a Transition Effect
Transition effects can be added between events in a playlist. A master control switcher is required to use transition effects. A transition effect is configurable according to type, speed, key hold status and mixed audio/video and wipe effect qualifiers.
1. Open a Playlist and ensure Revise mode is off/disabled.
To exit Revise mode on the list, press <ALT + R> or from the Events ribbon tab select the Cancel icon ( ).
2. Select the event in a playlist to assign the transition to by clicking the event number of the event.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 141
ADC™ Air Client
Operations and Installation
3. From the Events ribbon tab select the Edit Transition Effects icon ( dialog is displayed.
Playlist Editing Operations
) The Transition Effects
4. Configure the following options as required:
Transition Type: Select the type of effect to 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.
Transition Speed: Select the speed of the transition effect. Options are Slow, Medium, Fast.
End Key Hold: Checking this box causes the transition of an event to remove any key that was held by a previous keyer event.
#: Specify the qualifier for mixed audio/video and wipe effect. Qualifier values range from 0 to
255 and are facility-dependent.
5. When finished click OK.
Cut, Copy, Paste Playlist Events
The following procedures outline basic Cut, Copy Paste operations that can be performed from a
Playlist.
To Cut an Event from a Playlist
1. Select event to be cut by clicking on event number on list that corresponds to current location of event to be cut.
). The event is cut from the list and put onto a 2. From the Edit ribbon tab select the Cut icon ( clipboard in the software.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 142
ADC™ Air Client
Operations and Installation
To Cut a Block of Events from a Playlist
Playlist Editing Operations
1. Select the first event of a block to be cut by clicking an event number on list that corresponds to current location of event to be cut.
2. Holding down the Shift key, use the mouse to select the last event of a contiguous block of events.
This causes a sequence of events to be highlighted.
3. From the Edit ribbon tab select the Cut icon ( onto a clipboard in the software.
). The block of events is cut from the list and put
To Copy an Event from a Playlist
1. Select event to be copied by clicking on event number on list that corresponds to current location of event to be copied. (The event remains on the playlist or transmission list when copy is chosen).
). The event is copied onto a clipboard in the 2. From the Edit ribbon tab select the Copy icon ( software.
To Copy a Block of Events from a Playlist
1. Select the first event of a block to be copied by clicking an event number on list that corresponds to current location of event to be copied.
2. Holding down the Shift key, use the mouse to select the last event of a contiguous block of events.
This causes a sequence of events to be highlighted.
3. From the Edit ribbon tab select the Copy icon ( put onto a clipboard in the software.
). The block of events is copied from the list and
To Paste Cut / Copied Event(s)
2. Position the cursor on the play list where the event will be pasted.
3. From the Edit ribbon tab select the Paste icon ( specified location.
). This pastes the event(s) into the list at the
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 143
ADC™ Air Client
Operations and Installation
Copy/Paste Cells
Playlist Editing Operations
A cell can be Copied / Pasted in the Air Client Play list form or Transmission list form.
1. Select the cell to be copied.
IMPORTANT: Cell copy is only permitted from three columns: Title, SOM, or DUR column.
2. Copy the Cell: From the main menu select Edit > Copy. The event is copied onto a clipboard in the software.
3. Position the yellow cursor on the play list column where the event will be pasted.
IMPORTANT: The selected pasted cell must have the same column index as the copied cell. (e.g. A cell cut or copied from the Title column can only be pasted in the Title column.)
4. From the main menu select Edit > Paste. This pastes the event(s) into the list at the specified location.
Clear / Delete Playlist Events
Use the following procedure to delete an event from a playlist.
1. Select an event to be deleted. Click the event number on the list that corresponds to current location of event to be cut.
2. From the Edit ribbon tab select the Clear icon ( deletes the event off of the list.
) or press <Delete> on the keyboard. This
Note: This event is not placed on the clipboard. Once deleted it is gone.
To Clear a Block of Events from a Playlist
1. Select the first event of a block to be copied by clicking an event number on list that corresponds to current location of event to be copied.
2. Holding down the Shift key, use the mouse to select the last event of a contiguous block of events.
This causes a sequence of events to be highlighted.
3. From the Edit ribbon tab select the Clear icon ( put onto a clipboard in the software.
). The block of events is cleared from the list and
Note: The events are not placed on the clipboard. Once deleted they are gone.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 144
ADC™ Air Client
Operations and Installation Playlist Editing Operations
Moving Events within a List and Between Lists
An operator can use drag- and-drop or Cut and Paste on the Edit ribbon tab to move (reorder) events within a playlist, copy events between playlists, or copy events from a device storage window or database window directly into a play list.
Edit Operation Notes:
An event must be dragged by its event or spot number to move it to a playlist.
When dragging-and-dropping, all secondary events associated with primary events are moved with the primary event. This is not true when using cut and paste.
Drag and drop only works within the look ahead. You cannot drag an event from beyond the look to within the look ahead.
Cut and Paste will work if an event is Beyond the look ahead and needs to be placed within the look ahead.
WARNING: Unless the List options are set to get around this, copy-and-paste should never be used when using a traffic system that uses reconciliation because this will cause the event to repeat the reconciliation key.
Open the source List(s)
Open the list or lists to be used when moving events:
If moving events within a single playlist, open the playlist.
If moving between playlists, open the destination playlist, and the source playlists.
If moving from other windows to a playlist, open the destination playlist, and the source windows
(device storage window and/or database window)
To Drag-and-Drop a Single Event
1. Select the event to be dragged. Click the event number on the list that corresponds to current location of event to be cut and continue to hold down on the mouse button.
2. Drag up or down to the location the event will be dropped. (note – stay in the event column)
3. Position yellow cursor on the play list where the event will be dropped.
4. Release the mouse button to drop the selected event above the cursor.
Dragging and dropping within one window is effectively a ‘cut and paste’
Dragging and dropping from one window to another is a ‘copy, paste’
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 145
ADC™ Air Client
Operations and Installation Playlist Editing Operations
To Drag-and-Drop Multiple events
1. Press and hold the Shift key and click an event, then click-hold another event to select a range.
2. Drag the selection to an event in the playlist before which you want to insert the selection. The yellow cursor is positioned on the play list where the event will be dropped.
3. Release the mouse button to drop it. The events are inserted above the target location.
Move Events using Copy / Paste
WARNING: Copy-and-paste should never be used if you are using a traffic system that uses reconciliation because this will cause the event to repeat the reconciliation key.
1. As an alternative to drag-and-drop, click an event, spot or record, or the range of, then from the Edit ribbon tab select the Copy icon ( ).
2. Click the event in a playlist after which you want to insert the selection, and then from the Edit ribbon tab select the Paste icon ( ).
Revise Playlist Event Field Text
Revise allows the operator to "revise" (edit) the text in a particular field of an event.
1. Position cursor on a specific event field.
2. From the Events ribbon tab select the Revise icon ( ) or press <Alt+R> on the keyboard.
3. The Revise option is highlighted to indicate the client is in Revise Mode. Revise is also shown at the top of the window. The cursor is now in Revise Mode ready to type.
4. Revise the event as needed. If Enter is pressed prior to getting out of Revise Mode the database will be checked.
If the ID is not found, a warning message will appear. Click OK to continue
5. When finished exit Revise Mode. To exit Revise mode press <Alt+R> or from the Events ribbon tab select the Cancel icon ( ).
Note: If currently in Revise Mode – Cancel can be used to put event back to what it was prior revising the event. Cancel does not work if the operator already clicked off the revised event, or the operator already got out of revise mode).
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 146
ADC™ Air Client
Operations and Installation
Clear Done Events
Playlist Editing Operations
An event that is marked done can be dragged and dropped down the transmission list and then re-activated so it can play on the list again.
1. Position the cursor on the event that is marked Done.
2. Drag and drop this event down the list to where it will need to re-air.
3. With the cursor on the Done event that was dragged, right click on the playlist window and from the popup menu select Clear Done Events.
Note: In order to facilitate proper reconciliation, events which have been As-Run can never be revived. When an ADC user invokes the "Clear Done Events" function to replay an event on the transmission list, the event is treated as a newly inserted event in the Transmission list and a new
GUID is assigned, so this is a new event both in the Device Server, in the Live-Update, and in the
Traffic.
Replace an Event ID
Replace allows operator to find and then replace the ID with a designated ID.
1. Position the cursor at the top of the list in the ID column.
2. From the Edit ribbon tab select the Replace ( ) icon. The Replace ID dialog is displayed.
3. Specify the search parameters:
"Find what" field: Type in the ID to find. (e.g. Demo0001)
"Replace with" field: Type in the ID to replace with.
Match whole word only. Check to have search look for whole word matches.
Match case: Check to have search look only for entries that match the case (Upper or Lower) for the entry specified in the "Find what" field.
Ignore secondary event: Check to ignore secondary events in "Find" operation. (When a search in list is typically done, the result includes secondary events. If there is a secondary event with the same ID, the user may not want to find it.)
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 147
ADC™ Air Client
Operations and Installation Playlist Editing Operations
Direction: Specify the search direction: Up the list or Down the list form the current cursor position.
4. Select Find Next.
5. If the ID is in the database, an information box appears with the database info for the replacement
ID.
6. Select OK to replace the found ID with the replacement ID.
7. (Repeat steps 5 – 6 until all records are found.)
Note: Replace All can be used to speed up the process. Ensure the replacement spot is not already in a break with the ID being replaced. This will prevent the same spot to air back to back.
Ripple Time
AutoRipple is the process of adjusting the time column to reflect the time of day each event will play based on the duration of each event. As an event plays to air, the time field of the events following down the list will adjust as necessary to reflect the approximate time of day they will execute.
This is especially useful if the start time of an event is changed. Ripple time allows the start times of the following events to be updated to reflect the adjusted time.
The exception to this scenario is if a hardstart is located on an event. A hardstart will not allow the times to ripple past it and the events following may not reflect the correct time of day they will actually play.
Due to this blocking of AutoRipple it may be necessary to ripple the times manually to keep the list accurate to what time of day the events will play.
To Manually Ripple Times
1. Position cursor in a column of the event that the Ripple Time will be initiated from. Modify the time as required and if necessary.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 148
ADC™ Air Client
Operations and Installation Playlist Editing Operations
2. From the Events ribbon tab select the Ripple Time icon ( ) or press <Alt+M> on the keyboard.
The time field ripples from the event the cursor is located on down to the next hard start or the end of the list. Each successive event is offset by the duration of the previous primary event.
Note: All events’ start times are changed until a hard start event is encountered. Hard start events interrupt any preceding events whose times overlap its start time.
Checking if a List is Timed Out
Ripple time can be used between hard starts to check if the list is timed out between the hard starts.
If Ripple Time is initiated on an event and a hard start is located on a future event an info box appears if the events are running long or short to the future hard start.
The info box informs the operator if there is overlap (long) or gap (short) time to the next hardstart.
Managing Pull Lists
The Pull List window lists all missing events in a play list. Missing media are events not located in any of the devices assigned to the transmission list that the Pull List was generated from. Once opened, the Pull
List Window can be refreshed on demand (F5 key and Refresh function of its contextual menu).
Review Missing Events using the Pull List Window
Use the following procedure to review missing events using the Pull List Window.
1. Ensure a list is open for viewing
2. From the Events ribbon tab select the Pull List icon (
3. Choose the order to display any found missing material.
). A Choose Order box appears.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 149
ADC™ Air Client
Operations and Installation Playlist Editing Operations
Event #: List entries in order as they appear on the playlist.
ID: List entries in sequential ID order, lowest to highest.
Box ID: List entries in sequential Box ID order: lowest to highest, numbers before letters.
Note: With Air Client v4.26 and higher the ‘@’ character is treated as greater than numbers, but lower than letters, (e.g. #1, #2, 123, 456, @12, @34, fe1, fe2).
Chronological: List all entries by time only as they would fall within a 24hour period. (Not by
Date/Time.)
4. Click OK. Any missing items appear on the Pull List.
Note: The Pull List displays a single entry for a multi-segment program ID. The total number of segments in the list is displayed in the Occurrences column.
The event column designates the location of the missing event on the play list.
The TOD Time of day column is the time of day on the play list the event is scheduled to play.
If the record is not in the database, the Comment column indicates this by a "Not Made" comment.
The Occurrences column shows the number of times the event is scheduled on the play list.
The SOM and Duration on the Air Client Pull List allow it to be used as a Dub List on the Media
Client.
The Segment number (01 to 99) field can be displayed.
The Title field will indicate if an ID is on a Storage Device or not and if it is in the Database or not.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 150
ADC™ Air Client
Operations and Installation
About MultiSegment events
Playlist Editing Operations
The Pull List displays a single entry for a multi-segment program ID. The total number of segments in the list is displayed in the Occurrences column for that event.
Timezone in a Pull List
A Pull List requested for a List with a Time Zone configured will take in account the Time Zone in the TOD column of the Pull List. The Time Zone name is displayed in the title bar of the Pull List window (like for the List window), and the offset value in the status bar.
The following image is provided for reference. The colors are used to enhance readability. Your display will look different.
GMT Pull Lists
The GMT Pull List option allows to list in the Pull List only the clips missing in the devices assigned to the
List and not in a GMT source device usable for this List. This helps operators determine if the missing media is already loaded into a GMT source device if it is not on the Pull List.
To use GMT Pull Lists select the Properties ribbon tab, click the Environment… icon (
List Options tab, and check the option "Use GMT Pull List" option.
), select the
The Administrator or operator with security rights can enable the new GMT Pull List.
As with others options (e.g., Storage Options/ Display Free Disk space), a confirm/warning dialog box is displayed to the operator when this feature is selected. From this dialog the operator can:
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 151
ADC™ Air Client
Operations and Installation Playlist Editing Operations
Click Ok to confirm and enable new option. This parameter is saved in the ini file of the application so the selection is not lost when the Air Client is closed.
Click Cancel to invalidate option.
If Enabled (Checked), when the operator chooses Events>Pull List, the Pull List window is displayed on top of the transmission window and a warning message appears (Job in Progress) along the bottom of the Pull List window. Once complete, the warning message in Pull List window disappears.
It is not listed in the Pull List result.
If Disabled (Unchecked), is it is listed in the Pull List result.
Show/Hide Columns in a Pull List
The ADC Air Client v4, Pull List utility allows the show/hide of columns on the Pull List display. This option is similar in functionality to the Columns option of the playlist/transmission list.
1. Right click on the Pull List and from the right-click popup menu select Columns. The Column setting… dialog is displayed.
2. Use the Column setting… dialog to specify which columns to show or hide.
3. Select a Column in the Available columns or Displayed columns area and choose arrows to move it to the opposite area.
Single arrows (<, >) move individual columns
moves entry from Available pane to Show pane.
moves entry from Show pane to Available pane.
Reset moves all columns to the Show pane.
Cancel aborts the operation and closed the Column Configuration dialog.
Help launches the application Help system.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 152
ADC™ Air Client
Operations and Installation Playlist Editing Operations
4. Click OK. When the Pull List is displayed the columns shown will be as specified.
Add DBStatus Field as a Column
Any one Database field can be displayed in the DBStatus column of the Pull List Window. For example, the status PAD / Not PAD (Ready for air / Not ready for air) could be displayed.
The following parameters of this additional column are configurable in the Air Client ini file.
These parameters are:
The column name (i.e.: Status)
The Database field to display, and the DB table concerned
The value to display if the clip is not found in DB (i.e.: Not Found).
The section corresponding to these parameters in the aclnt32.ini file is done manually (if the feature is required, a Pull-List_Status.txt file to copy/paste and adapt will be provided).
For instance: [Pull List ColX]
Name=DB Status
DBField=ASEXT/Status
Default=Not filled
Recycle Bin Window
When the Air Client software user deletes one or several events from the "Transmission list", if the "Link to Recycle Bin" option of the "Transmission list" is checked, those events are written into the
"RECYCLE.lst" file. The Link to Recycle bin option is located in the "Security" tab of the Playlist Options
Menu (right click menu on transmission list).
This setting if enable is active for each list independently.
Multi-login to several device servers is managed (relative parameters saved in aclnt32.ini).
This "RECYCLE.lst" file is saved in the local directory of the Air Client application.
The Air Client software can retrieve deleted events in the "Recycle Bin" window that displays the
"Recycle.lst" file. This file saves the events deleted from a transmission as well as the cut events, in the case where the user cuts some events but does not paste them, so those events could be lost.
When a primary event with hidden secondary events is cut or deleted from the list, the primary and its relative secondary events are copied in the Recycle Bin.
Any new entry of a cut/deleted block is done at the top of the in the Recycle Bin.
The chronology of the action can be easily found.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 153
ADC™ Air Client
Operations and Installation Playlist Editing Operations
At each modification of "Recycle.lst" file, the "Recycle Bin" window is updated. Possible modifications include: the insertion of events in the "Recycle.lst" file and a purge on an event.
To use the Recycle Bin
From the Tools ribbon tab select the Recycle Bin icon ( any contents.
). The Recycle Bin window is displayed with
To reuse the events of the "Recycle Bin" window in a transmission list or in a playlist, the user can use a copy/paste or a drag&drop operation.
Clicking on a block header selects all the events of the bloc. This allows an easy and fast selection before copy or drag-and-drop action.
Each cut or deleted event or block of events begins with a header that gives information about the edition action made on this range. The header is a comment event giving the following information:
In the Time field: The hour of the edition action.
In the ID field: The action done (DELETE / CUT) on the event(s) under the header.
In the Title field: The Server name - the List name where the action was done - The Date of the action.
Empty Recycle Bin option
An operator can choose to manually delete all events in the Recycle Bin.
1. On the ribbon menus select Tools> Recycle Bin. The recycle Bin window is displayed.
2. Right click on the window and from the context menu select ‘Empty Recycle Bin’.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 154
ADC™ Air Client
Operations and Installation
3. A confirmation box is displayed:
Playlist Editing Operations
Select ‘Yes’ to delete the events in the Recycle Bin.
Or
Select No to cancel the action.
Warning Box when the Recycle Bin exceeds 2,000 events
Added a warning box that warns the user when the number of events in the Recycle Bin exceeds 2,000 events. Since having an excessive number of events in the Recycle Bin can impact client performance, the user is prompted to empty the Recycle Bin when it contains a high number of events. When there are more than 2, 000 events in the Recycle Bin a warning box is displayed: ‘There are a high number of events contained in the Recycle Bin which can impact Air Client performance. Empty Recycle Bin? Yes
No.
Clicking Yes deletes the events in the Recycle bin.
Clicking No clears the warning.
Note: As long as the number of events in the Recycle Bin is over 2,000, the warning message will reappear every 15 minutes until the user clicks Yes, manually empties the recycle bin or the auto-purge deletes the events.
To enable use of "RECYCLE.lst"
In normal operation the "RECYCLE.lst" file is not use as a standard play list, but through the Recycle Bin feature. The administrator sets this option by:
1. Right click on an open playlist window and from the popup menu select Options… This opens the
"Options" dialog box
2. From the Options dialog select Security tab and enable (check) "Link to Recycle Bin" option.
Note: The access to the functions of this Security tab is granted to the System Configuration permission only, from login.
To Configure Colors
The foreground and background colors of the "Header" comment event are configurable from the
"Colors" command of the pop-up menu that opens the standard configuration color of event dialog box
(it is also the case for Playlist and List).
1. Open the Recycle Bin window
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 155
ADC™ Air Client
Operations and Installation Playlist Editing Operations
2. Right click on the Recycle Bin Window and from the popup menu select Colors. The "Select Colors" dialog is displayed.
3. Use this dialog to set Event Colors and select default colors. For details on using this dialog see
Configuring Event and Window Parameter Colors (on page 231).
To Configure a Purge
To prevent the Recycle.lst file from becoming huge, a purge of the oldest part of the file can be configured by the administrator.
Note: The access to the functions of this Security tab is granted to the System Configuration permission only, from login.
1. Right click on the Recycle Bin Window and from the popup menu select Options. The "Recycle Bin
Options" dialog is displayed.
2. Use the Purge tab of the "Recycle Bin Options" dialog to configure purge operations for this window.
3. Configure the following parameters as required:
Start Of Day: Define the time of the triggering of the purge.
Hours To Keep: Specify which events, in the "Recycle.lst" file, will be kept or not.
4. When finished click OK. The events, which exist in the "Recycle.lst" file that are greater than the defined hours, are deleted.
© 2017 Imagine Communications Corp. Proprietary and Confidential. 5/25/2017 | Page 156
Advertisement
Key features
- On-Air Playback
- Playlist Management
- Event Management
- Device Control
- Error Management
