Configuring List Types. Imagine communications ADC Device Server and Config Tool

PDF

مستند

ADC™ Device Server and Config Tool

Installation and Operations

Configuring List Types

About Play lists and the Traffic Translator

Play list files are created from the traffic department’s daily programming log by processing them through the Traffic Translator software application (WinCMMS.exe). The rules that the Traffic Translator uses to parse the traffic log are customized to your specific requirements.

The traffic translator application is typically installed on the File Server, a seldom-used client PC, or may be installed and run on a PC in the traffic department. The input and output folders for the Traffic

Translator are specified in the command line for the application. There are several other options that may be specified there as well. The command line for the Traffic Translator should be in the following format:

C:\WINCMMS\WinCMMS.exe <input directory/[input file]> or <input directory/[default extension]>

[-axy]

[<done directory>]

Where,

• <input directory>: Points to the default input directory (folder) where the traffic logs are located.



This may be accompanied by a [input file] name. This is useful when calling the translator from another application. The translator closes itself after the file is converted.



The input directory may also be accompanied by a [default extension] in "*.xxx" format.

• <output directory>: Points to the default output directory where the output play list file will be saved.

• [<done directory>]: Points to the directory where traffic logs will be moved after they have been translated. This option may be used in conjunction with the –a or –x switch.

• -a: Allows the application to run in Automatic Mode. The Traffic Translator will run minimized, converting all the files located in the <input directory>. After each log is translated, it is moved to the <done directory>. If there is no <done directory> specified, the traffic log will be moved to the

<output directory>. The Traffic Translator will remain running in the background as a service

(minimized in the Windows system tray) and translate any new files downloaded to the <input directory>. This switch should not to be used in conjunction with the –x switch.

• -x: Allows the application to run in Batch Mode. The Traffic Translator will convert all the files located in the <input directory>. It closes itself after the last file is converted. This switch should not to be used in conjunction with the –a switch.

• -y: Allows the translator to run without a prompt. The Traffic Translator will overwrite the output file, if it exists. This switch may be used in conjunction with the –a or –x switch.

ADC™ Device Server and Config Tool

Installation and Operations

Examples:

Configuring List Types

C:\WINCMMS\WinCMMS.exe A:\ E:\Playlist

This example will translate traffic logs on a floppy disk and place the translated play lists in the

"E:\Playlist" folder. This option will require manual selection of the traffic log to be translated.

C:\WINCMMS\WinCMMS.exe E:\Traffic\today.txt E:\Playlist –y

This example will translate a file named "today.txt" in the "E:\Traffic" folder and place the translated play list file in the "E:\Playlist" folder. It will overwrite any existing play lists without prompting the user.

C:\WINCMMS\WinCMMS.exe E:\Traffic\*.scd E:\Playlist –xy

This example will automatically translate any traffic logs with an ".scd" extension in the "E:\Traffic" folder and place the translated play list files in the "E:\Playlist" folder. It will overwrite any existing play lists without prompting the user. The application will close after the lat file has been translated.

C:\WINCMMS\WinCMMS.exe E:\Traffic E:\Playlist -ay E:\Traffic\done

This example will automatically translate any files that appear in the "E:\Traffic" folder and place the translated play list files in the "E:\Playlist" folder. It will overwrite any existing play lists without prompting the user. It will also move the original traffic log from the "E:\Traffic" folder to the

"E:\Traffic\done" folder once it has been translated. The application will remain running (as a service, minimized in the Windows system tray) waiting for new traffic logs to appear in the

"E:\Traffic" folder.

Depending on the custom features of your Traffic Translator, it may also be used to translate As-Run logs back into traffic reconciliation logs, combine As-Run and traffic logs for reconciliation, translate multiple traffic logs simultaneously for different Transmission lists. See your automation project manager for more information about the Traffic Translator.

About List Configuration

The automation server creates lists in the following order:



Transmission Lists (Playlists) and record lists.



Media Lists



GMT Lists



Compile Lists (see "Configuring Compile List Options" on page 409)

In the Configuration program the List Assignments window displays the list type next to the list name.

When a new list is added to the server configuration this can change the order of the lists. If a server originally had two playlists (lists one and two) and two media lists (lists three and four), then when a new playlist is added then list three now becomes a playlist and list five is the new media list.

When this new server is started the configuration data in the INI file is read in based on the old configuration. This means that the configuration data for the first media list (list three) is now being

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types used by the new list three, which is a playlist. This often created confusion for the users of the system as well as some on-air problems.

When installing a new version of the server with additional lists the user must always check the configuration. To ease the migration path and prevent some (but not all) configuration related issues:

• The lists when reading the configuration will make sure that what is read for the INI file is appropriate for the target list type being configured.

• Where possible the list will make sure setting options from the INI file that don’t apply to the list type will be corrected.

Configuring Transmission List Options

Once a play list file has been translated from the traffic log, it may be loaded, pasted or appended into a

Transmission window where it then becomes a Transmission List. A Transmission List is the main sequential list used by the Device Server to control the playout of media.

Transmission Lists are composed of primary and secondary events. Primary events may play out media from a physical media device, or may switch a crosspoint on a router or switcher using a Switch-Only device. Secondary events are "attached to" or associated with primary events to perform additional activities on the Transmission List. For example, a primary event may be playing out a clip from a video server’s decoder port while an attached secondary event, at some point during the primary event, may recall a page on a downstream keyer and key a graphic over the primary playout stream. Each primary event on a Transmission List plays out sequentially. When the full duration of a primary event has been reached, the next event will roll automatically. Operators may manually roll events before their full duration has been reached by using the Air Client’s control panel.

Event Registration

When events are placed within the lookahead (see below) of a Transmission list, they are registered with the media devices assigned to that list. The system will query the storage collections of the devices, in the order of their assignment to device channels, and the first device that responds that it has the ID in its storage will register that event. This is indicated on the Transmission list by the event turning blue.

If there are media heads available, the event will be threaded and cued. If there are no media devices assigned to the list that have the ID in their storage collections, the event will remain red on the

Transmission list. The event will remain unregistered until a media device informs the system that the ID has been added to its storage collection.

Media devices are checked for media availability only under certain circumstances. Events are checked only when:

• A new event is inserted into the lookahead

• A new event enters the lookahead because another event has been deleted

• A "done" event is cleared within the lookahead

• The lookahead value is increased, and new events enter the lookahead

• The list "packs" – done events are removed from the top of the list and new events enter the lookahead

ADC™ Device Server and Config Tool

Installation and Operations

• An unregistered event is modified and the media is now available

Configuring List Types

Events are unregistered from devices only when:

• An event is deleted from the Transmission list

• A registered event is modified and the media is no longer available

• An event is marked "done"

• The lookahead is shortened, and previously registered events are now outside the lookahead

• An event is inserted into the lookahead, and previously registered events are now pushed outside the lookahead

Media devices inform the system when their storage collections have changed – when IDs have been either added or deleted. If a device informs the system that an ID has been added to its storage collection, lists that are assigned a media head of that device are rechecked to see if that ID is within the lookahead. If it is, then the event will be registered with that device. Pending record events (if the

Transmission list is being used as a record list) will be rechecked to see if they should now be unregistered.

If a device informs the system that an ID has been removed from its storage collection, events registered with media heads of that device are re-checked to determine if the events should be unregistered.

Pending unregistered record events are also rechecked to determine if they may now be registered.

In short, playout events will register with a media device if the ID exists within the device’s storage collection. Record events will register with a record device if the ID does not exist within the record device’s storage collection.

The Lookahead

The lookahead value, which may be configured in the list options configuration GUI (see below), represents the number of events at the top of the Transmission list that are checked for media availability. The lookahead may be a fixed number of events (default 50), or it may be a fixed time value based on the durations of the events. Events on the Transmission list beyond the lookahead are not checked and are not registered with devices.

• After events have run, they become part of the done count. The done count is a fixed number of

"done" events held at the top of the Transmission list. The done count is configurable and may be set to a value between 1 and the lookahead value minus 1.

• As the Transmission list runs, the list "packs". Events at the top of the Transmission list’s done count are removed and all remaining events on the list move up. Events just beyond the lookahead move up into the lookahead and are registered if possible.

• A duration-based lookahead, instead of looking ahead a fixed number of events, looks ahead a specified time value. The system will sum all of the event durations and keep an equivalent number of events in the lookahead. The actual number of events in the lookahead will vary, depending on the durations of events on the list.

ADC™ Device Server and Config Tool

Installation and Operations

Record Lists and GMT Push Lists

Configuring List Types

Transmission lists may be used for purposes other than playing out to air. Transmission lists may be used as Record lists for automated recording. A Record list is simply a Transmission list with record devices assigned to it. Record events are placed on the Record list either by manually entering them, by translating a record list provided by traffic with the Traffic Translator application (if so customized), or through the use of an automated recording client application like AutoSat.

Record events are timed events. They will roll at the time-of-day specified in the list’s Time column.

Record lists have all the behaviors of a Transmission list with regard to event registration, A/V routing, threading, cueing and rolling events.

Note: For more information about creating and managing Record lists, reference the "Air Client

Installation and Operations Reference".

Transmission lists may also be used as GMT Push lists. A Push list’s purpose is to move media from wherever it exists within the system to where it needs to be to play out ahead of time. Events may be placed on a Push list to populate a playout video server with media needed for tomorrow’s play list.

Note: For more information about GMT Push Lists see Global Media Transfer (on page 436).

To Configure Transmission List Options

A number of options may configured to control the behavior of Transmission Lists. These options are accessed from the Configuration Manager’s List Assignments window.

1. To access the Transmission List options configuration GUI, select a Transmission List (PlayList) in the

Lists pane.

2. Right-click on the entry and then from the pop-up menu select Properties. The Configuration window opens with multiple tab selections. The options configured on these tabs apply to this list only. Configuration options for other lists must be configured separately.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

3. Select the Parameters tab. This tab contains general configuration options for Transmission Lists.

Some options are commonly used and enabled by default.

Configure the following options as required:



Name: Enter a name for this Transmission List. List names are limited to 16 characters.



Options:

• Auto Restart When Cued: (Default: disabled) When enabled, this option causes events to automatically restart, without manual intervention, if the media has been recued.

When this option is disabled, the automation system marks the event as missing and does not automatically cue the event when located.

• Recue On Media Changes: (Default: enabled) When enabled, this option causes events to automatically recue if the event’s SOM (start-of-message time), DUR (duration), or New AFD is changed.

Note: The ID Video ARC is reapplied if the event’s New AFD value is changed while the event is CUED.

• Rewind Compile Material: (Default: disabled) When enabled, this option causes compile tapes to rewind to the head of the first spot when finished. The tape is rewound to the first commercial break (or "pod") minus the preroll.

• Rewind to First Program Segment: (Default: enabled) When enabled, this option causes multi-segment programs played out from a VTR or cart machine to rewind to the head of the first program segment when finished. The tape is rewound to the SOM of the first segment minus the preroll.

• Update Cued Event on Media Change: When this parameter is enabled (checked), all of the database derived metadata for any cued events is updated. o

If ‘Recue on Media Changes’ parameter is enabled, then this parameter is also enabled.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types o

If this parameter is enabled, but the ‘Recue on Media Change’ parameter is disabled, then although the event is updated, the device is not recued or otherwise updated.

CAUTION: This configuration scenario can cause unanticipated or invalid behaviors, such as the device and device driver’s head data to get out of sync. To avoid this ensure

‘Recue on Media Changes is also set. o

If this parameter is disabled, ‘Recue on Media Changes’ must also be disabled and no updates will be applied to cued events. o

If Auto Ripple is enabled, the start time of the event following the an updated event is also updated.

• Update Playing Event on Media Change: When this parameter is enabled (checked), the system partially updates the metadata of an event that is playing at the time of an update.

The device cannot be recued and the SOM of the event is not updated. o

If this parameter is enabled, then ‘Update Cued Event on Media Change’ must also be enabled. o

If this parameter is enabled, the remaining duration of the event is recalculated on an update. Since the duration of an event decrements while it is playing, the duration is changed by an amount equal to the difference between the original duration and the updated duration.

WARNING: If the device is not updated- as in the case of a cued event because Recue on

Media Changes is disabled, or in all cases for playing events- and the updated duration is longer than the duration used to initially cue the device, the device may cease playout at the end of the original duration, even if the event is updated. This typically causes a TapeEnd error and the list skips forward to the next event.

• Block Recue Following an Upcount: Enable (check) this option for the recue behavior to never allow recue following an upcount event. (See also ‘Always Allow Recue Following an

Upcount’.)

IMPORTANT: While the configuration options Always Allow Recue Following an Upcount and Block Recue Following an Upcount are currently shown as available for Media List, GMT

List, and Compile List types, they are not recommended for use with these lists.

Note:If both ‘Block Recue Following an Upcount’ or ‘Always Allow Recue Following an

Upcount’ are DISABLED (unchecked), the recue behavior uses the upcount event’s reported duration to determine the downcount threshold after which the recue command will not be sent. This is illustrated in the following graphic:

AU EVENT

Downcount

Upcount

Recue Sent Recue Not Sent

PLAY

Downcount

Threshold

Upcount

Threshold

Requirements for the setting of both options disabled: The following List Option Parameter tab settings must also be set for this configuration setting:

ADC™ Device Server and Config Tool

Installation and Operations o

Enable Recue On Media Changes: Check to enable.

Configuring List Types o

"Update Cue Event on Media Change: Check to enable. o

The AO Event Thread Time must also be set and this parameter is used to determine the threshold mentioned above. (Note: The total time calculated = AO Event Thread Time:

Cue Seconds + AO Event Thread Time: Cue Frames + Time Parameters: Preroll Seconds +

Time Parameters: Preroll Frames + Time Parameters: Postroll Seconds + Time

Parameters: Postroll Frames)

• Always Allow Recue Following an Upcount: Enable (check) this option for the recue behavior to always allow recue following an upcount event. (See also ‘Block Recue Following an Upcount’.)

IMPORTANT: While the configuration options Always Allow Recue Following an Upcount and Block Recue Following an Upcount are currently shown as available for Media List, GMT

List, and Compile List types, they are not recommended for use with these lists.

Requirements for this Setting: The following List Option Parameter tab settings must also be set for this configuration setting: o

Enable Recue On Media Changes: Check to enable. o

"Update Cue Event on Media Change: Check to enable.

Note: If both ‘Block Recue Following an Upcount’ or ‘Always Allow Recue Following an

AU EVENT

Downcount

Upcount

Recue Sent Recue Not Sent

PLAY

Downcount

Threshold

Upcount

Threshold

Requirements for this Setting (i.e. both options disabled): The following List Option

Parameter tab settings must also be set for this configuration setting: o

Enable Recue On Media Changes: Check to enable. o

"Update Cue Event on Media Change: Check to enable. o

The AO Event Thread Time must also be set and this parameter is used to determine the threshold mentioned above. (Note: The total time calculated = AO Event Thread Time:

Cue Seconds + AO Event Thread Time: Cue Frames + Time Parameters: Preroll Seconds +

Time Parameters: Preroll Frames + Time Parameters: Postroll Seconds + Time

Parameters: Postroll Frames)

• Extended Time To Next: (Default: enabled) When enabled, this option enhances the functionality of the time-to-next feature of the Transmission List. Time-to-next values are calculated correctly regardless of whether there is an intervening upcount event.

Enhanced Functionality includes:

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types o

When the termination event is an O (hard start) event the Time To Next display includes the running short value. o

Zero duration up counters do not stop the rippling. o

When in an up counter, if an O event exists as the termination event, the Time To ext computation computes without any long or short value. It displays exactly how long until the hard timed start begins.

• Release Tension On Record: (Default: disabled) When enabled, this option, if VTRs or cart machines are assigned to this list as record devices, causes the VTR or cart machine to release tension on the tape when the record event has cued. The tape is re-tensioned at the

"standby on" time (see below).

• Rewind Spots: (Default: enabled) When enabled, this option causes single-spot tapes played out from a VTR or cart machine to rewind to the head of the spot when finished. The tape is rewound to the SOM minus the preroll (on a multi-spot tape, the tape is rewound to the

SOM minus the preroll of the last spot played).

• Thread Limited: (Default: disabled) When enabled, this option changes the cueing behavior of the Transmission List. Events are cued within the specified "thread time", taking into account the duration of events registered with the same media device that cannot be threaded due to a lack of available media heads. This means non-threaded but blue

(registered) events count toward the total thread time as if they were threaded.



Time Parameters: These options specify time values for this list.

• Preroll Seconds: Define the number of preroll seconds to be used for the selected list. The valid range is 0-59 seconds. Default is 3 seconds.

• Preroll Frames: Define the number of preroll frames to be used for the selected list. The valid range is 0-29 frames. Default is 0.

All events on this list will preroll for the time (Seconds/Frames) specified here before switching. The list preroll should equal the preroll time required by the slowest device assigned to the list. For example, if a VTR assigned to this list takes 4 seconds to lock up, the list preroll should be no less than 4 seconds.

Note: If a list preroll of less than 3 seconds is used, VTRs assigned to this list will not perform a tape speed override (TSO) when they roll.

Frame-accurate playout from tape cannot be guaranteed if a list preroll of less than 3 seconds is configured. Operators may manually override the list preroll by using the Roll

Now button on the control panel. Only events registered with Switch-Only devices or video server decoder ports (if they are configured to support "instant prerolls") may be rolled using the Roll Now button.

• Postroll Seconds: Define a length of time, in seconds, the automation system plays the current event beyond its duration if it has not yet switched to the next event. The valid range is 0-59 seconds. Default is 1 second.

• Postroll Frames: Define a length of time, in frames, the automation system plays the current event beyond its duration if it has not yet switched to the next event. The valid range is 0-29 frames. Default is 0.

All events on this list will postroll for the time (Seconds/Frames) specified here after their duration has expired. Events registered with video server decoder ports, if the port has been configured to support a "device postroll", may allow shorter postrolls that the list postroll.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

• StandbyOn Seconds: This value determines when "standby on" commands are sent to VTRs by specifying the amount of time the automation system keeps the VTR in tension after cueing an event. The valid range is 10-59 seconds. Default is 30 seconds

If a VTR assigned to this list is configured to perform a "standby off" when a tape has cued - spinning down the video heads and releasing tension on the tape - the tape will be retensioned and recued at the "standby on" time.



AO Event: Hard start event (AO)

• AO Event Thread Time: Specify the following thread times:

Cue Seconds: Specify cue time seconds for the AO event.

Cue Frames: Specify cue time frames for the AO event.

• Thrd AO evnt at last moment: Check to enable threading of the AO event at the last moment.

Checked: (Recommended): If another event occupies the same disk head, thread the disk hard start event when the current time is closer to its On Air time than AO Event Thread

Time. Checking this box give the maximum tolerance for the list events that in front of the

AO events to do playout, and also allows the AO event to successfully register to a disk head to play on time.

Unchecked: Thread disk hard start event based on thread time. If the disk head is occupied by another event, that event will be ejected.

• Only Thread Next AO Event: Enable / Disable threading of the next event. If multiple Hard-

Start (AO) events are within the transmission list lookahead Window:

Checked: Only thread the next Hard Start event without continuously rippling down to reach next AO event on the same list. Since playlist events often are without On-Air date information, this prevents the next day’s AO event (showing later in sequence on the playlist, but with an on-air time earlier than the today’s) being Cued first.

Unchecked: if there are more than one AO event in the future, list will find the earliest timed one as the next AO event to start regardless its position in the list.

Recommendation: Uncheck only when there is a necessary for set AO event out of order.

4. Select the Options tab. This tab contains optional configuration settings for Transmission lists.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

Note: All of the options on this tab may be configured in the Air Client application.

Enable (check)/ Disable (uncheck) and configure the following as required:



Options:

• Auto A-B Routing: (Default: disabled) Enabling this option causes devices to alternate between their primary and secondary audio/video routing paths as configured in this list’s

A/V routing table (see below).

When enabled this setting overrides an event’s channel settings (displayed in Transmission window's CH column in Air Client). During transmission, successive primary events are routed alternatively through switching channels A and B. This function is useful to ensure that two successive events are not played through the same channel (which is needed when transition effects such as mixes are defined between events). Make sure both A and B channel A/V parameters are configured in all devices that are used.

Note: When changing this configuration, existing events on the list, and in particular previously executed events recovered with 'Clear Done Events', may exhibit the previously configured switching behavior.

• Auto Ripple Times: (Default: disabled) Enabling this option causes the time-of-day for events to update automatically, reflecting any changes to event durations made manually.

The time "rippling" ends at hard start events. The calculation assumes that the Duration field for up-counting events is accurately set.

• Contact Start: (Default: disabled) Enabling this option allows this list to be rolled via an external GPI contact-closure trigger. The GPI trigger duplicates the function of the Play button on the control panel.

• Play ID Title Mismatches: (Default: disabled) This option only applies to systems that include a Sony LMS cart machine. The LMS will not register events if the ID and title on the tapes’ barcode labels do not match the ID and title of the events as they appear on the

Transmission list. Enabling this option allows the LMS to register mismatched events.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

• Keep List Threaded: (Default: disabled) Enabling this option causes the Transmission list to thread and cue as many events as possible within the lookahead. If an event is inserted into the list to be played, the event is immediately cued and subsequent events unthreaded as necessary.

When enabled, thread time is not used. This option supersedes the Thread Time.

When disabled, the list only keeps events threaded within the Thread Time window (see below).

Logomotion Note: To ensure all available heads thread normally, enable ‘Keep List

Threaded’.

• Only Swap One Event in A-P: Enable / disable air protect switching for an event.

In an Air/Protect configuration, the playlist will play out an event simultaneously from both

Air an Protect servers. If the Air Server has a failure or malfunction, the playout server switches event playout to the Protect server and stays there. In many situations, event interruption is only caused by one media, not the entire playout server or port. In this situation, some customers want the playlist to switch back to the previous Air server instead of keeping playout with the Protect server. Checking this option box will

Checked: Tells the playlist to switch back to the Air Server for normal playout, on conclusion of this trouble event.

Unchecked: Treat Air and Protect disk equally, assign air or protect disk port to Air column whichever is ready first.

Recommendation: Uncheck when the disk port is the additional port of another video disk.

• Play Hard Hits: (Default: disabled) Enabling this option allows an operator to manually override the start time of "hard start" or "hard hit time" events (timed events).

When disabled, "hard start" events only roll at the time specified in the Transmission list’s

Time column.

• Release Tension When Cued: (Default: disabled) Enabling this option causes the system to send a "standby off" command to any VTRs when they have cued a tape. The tape is retensioned at the standby on time.

• Skip Bad Events: (Default: enabled) When enabled this option the Transmission list to ignore and skip a single unregistered (bad) event. The list will continue playing out and mark the bad event as "missed".

When disabled, the Transmission list stops upon encountering any unregistered event and must be restarted manually.

Note: The Transmission list always stops upon encountering two or more consecutive bad events, whether this option is enabled or not.

• Station ID On Skip: (Default: disabled) Enabling this option causes the switcher to switch to the Station ID source (configured in the master control switcher’s configuration GUI) for the duration of the list preroll when an operator has manually skipped an event using the Skip button on the control panel.

• Switch To Black: (Default: enabled) When enabled this option causes the master control switcher to take the Black source if the list stops. The Black source must be configured in the master control switcher’s configuration GUI for this to occur.

When disabled (or the Black source not configured), the switcher will remain on the last source taken if the list stops.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

• Tension After Up Counter: (Default: disabled) Enabling this option causes tape events following an upcount event to remain tensioned. Since the duration of upcount events is, by definition, indeterminate, there may not be time to re-tension a tape if an upcount event ends abruptly. This option allows events from tape to remain ready to roll immediately.

• Thread After Break: (Default: enabled) When enabled this option keeps the list threaded while the list has stopped due to encountering a Break event on the list. Break events are secondary events inserted in the list to cause the list to stop temporarily and wait for a Play command from either the control panel or an external GPI trigger.

• Timed List: (Default: enabled) When enabled this option allows the list to roll timed events – hard start or record events – at the time of day specified in the Transmission list’s Time column.

When disabled, timed events will not roll.

• Update On Air Time: (Default: disabled) Enabling this option causes the on-air time for events to update to the actual time the event rolled. As-Run logs for the list are updated as well.

When disabled, the As-Run logs reflect the time-of-day that appeared on the Transmission list, rather than the actual time the event rolled.

When disabled, the list must be threaded manually before it can execute a Play command.

• Update Final Upcount Durations: Check to enable update of the final upcount event duration. This gives an actual duration of how long an event ran.

An upcount event type(U) is used for an event of unknown duration, such as a sporting event or any other live broadcast. During playout, the event’s duration will count down to

00:00:00.00 and then will count back up.

This repeats until terminated by either pressing Play or Skip on the control panel or a contact start is reached. The next event will play normally. Up counters only work on events played from Switch Only devices.



Done Count: This value sets the number of "done" events that will be displayed at the top of the

Transmission list. The Done Count may be set to any value between 1 and the lookahead value minus 1. Default is 4 events.

Note: Never set the Done Count to a value equal to or greater than the lookahead value. Doing so causes the list to eventually run out of valid, registered events and stop.



Thread Time: This time value determines the time "window" following the on-air event in which events will be threaded. The valid range is from 0 to 23:59:59:29 (23 hours, 59 minutes, 59 seconds, and 29 frames). Default is 2 minutes.

• Any events within the Thread Time are threaded and cued.

• If the list option "Keep List Threaded" is enabled, this value is ignored.



Match Primary Duration PT=EOM offset. This option provides the ability to define an offset time (HH:MM:SS:FF) for the end point of a secondary event PT=, which should end with respect to the primary event. (i.e. The value of EOM offset is used for all PT= secondary events attached to the primary.)

• This parameter affects the timing of every secondary event that uses the "=" modifier.

• When defined the offset should be less than list preroll time.



Zero Upcount Durations: Enable (check)/Disable (uncheck) the ability to zero the initial duration of upcount events

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

• If Enabled (checked), the duration of Upcount event will setup to zero automatically before the event starts. The list will be rippled and timed as with estimated duration of this event.

• If Disabled (unchecked), the behavior of the list will be as normal- upcount events would decrement from whatever duration is scheduled and then upcount from zero.

5. Select the Lookahead tab. This tab contains the configuration options for this Transmission list’s lookahead.

Configure the following options as required:



Duration Based Lookahead: Enabling this option causes the Transmission list to keep a varying number of events in the lookahead, based on the sum of the durations of events on the list. A duration-based lookahead ignores the on-air event and Done Count, and calculates the lookahead from the sum of the durations of events following the on-air event.

The time values immediately below the checkbox (Hours, Minutes) specify the amount of time for the list to look ahead.

• Hours: (Default: 4 hours) (Range: 0 to 23 hours) Specify a time duration, in hours, for the lookahead window to check. This option has no effect unless the Duration Based Lookahead box is enabled.

• Minutes: (Default: 0) (Range: 0 to 59 minutes) Specify a time duration, in minutes, for the lookahead window to check. This option has no effect unless the Duration Based Lookahead box is enabled.



Count Lookahead: (Default: 50 events.) If the Duration Based Lookahead checkbox is unchecked, the Transmission list will use a count-based (or event-based) lookahead. The list

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types looks ahead a fixed number of events from the top of the list. This lookahead value includes the on-air event and the Done Count.

• This value may be configured in the Air Client application also.



Duration Based Lookahead Toggle: Enabling a duration-based lookahead allows an operator to toggle the lookahead value to either an alternate time value, or to include the all events on the

Transmission list in the lookahead. An operator can select Toggle Lookahead from the Air

Client’s popup menu (or hitting F8) to toggle the lookahead to its alternate value.

• Enable Toggle Lookahead checkbox: (Default: disabled) Check to enable the duration-based lookahead toggle. This setting has no effect unless the Duration Based Lookahead box is enabled (above).

• Toggle To Full List: Select to include all events in the Transmission list within the lookahead.

Selecting this option causes the F8 key to toggle between the Duration Based Lookahead setting and the full list.

• Toggle To Alternate Time: Select to enable the alternate time value configured here (Toggle

Hours, Toggle Minutes). Selecting this option to causes the F8 key to toggle between the

Duration Based Lookahead setting and the alternate time set in the Toggle Hours and Toggle

Minutes box to the right.

• Toggle Hours: (Default: 4 hours) (Range: 0 to 23 hours) Set an alternate time for toggling back and forth from the default setting chosen above.

An operator can use the F8 key to toggle back and forth between the default time setting and the alternate time chosen here.

• Toggle Minutes: (Default: 0) (Range: 0 to 59 minutes) Set an alternate time for toggling back and forth from the default setting chosen above.

An operator can use the F8 key to toggle back and forth between the default time setting and the alternate time chosen here.



Report Missing Media:

• Report Missing Media Within LookAhead: Enable (check) this option to allow sending missing media error message out on Automation LAN. If there an ADC SNMP-Agent client is running on the Automation LAN, it will detect these error messages, and forward them to remote SNMP Manager program for remote monitoring of playlist missing media alerts.

Report GMT Requested Media: (Active when ‘Report Missing Media Within LookAhead’ is selected.) If the Missing media is currently requested through ADC GMT system, enable

(check) this box to allow the missing media error message to be correctly reported to the remote SNMP Manager program through ADC SNMP-Agent program.

6. Select the Events to Log tab. This tab contains configuration options for the As-Run logs created by the Air Client application.



By default, not all secondary event types are logged to the As-Run log. Checking the appropriate checkbox on this tab will enable logging of that secondary event type.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types



If this Transmission list is to be used as a record list and you require a log of what has been recorded, an As-Run log may be created that includes primary record events. Check the Log

Record Events checkbox to enable this.



Secondary Events to Log:

Enable (check)/ Disable (uncheck) the secondary events to log in the As-run log. When all checkboxes are selected (checked), all secondary events associated with a primary are included in the

As-Run log.

For Example: BREAK is disabled and others are enabled – all secondary events except BREAK secondary event are included in the As-run log.



Log Record Events: (Default: disabled) Check to enable logging of record events on normal completion.

7. Select the Mix/Wipe tab. This tab contains configuration options to play mix/wipes early. This allows dissolves (mixes) or wipes to be done between the source that is currently on-air and the next source. Events that include a mix or wipe transition are required to roll several frames early to allow the events to overlap.

Typical uses are to dissolve between VTRs inside an LMS, or when going from a station promo to a station ID. These promos and Station IDs always have extended vision on the videotape, i.e. the actual vision on the videotape have a longer duration, than what is shown in the Database.

About Extended Play Mix/Wipes Early:

These options allow playlist timing to be maintained by playing an event with a transition for an extended duration, so that it finishes at its scheduled time, leaving the list timing unchanged.

The event is played early to provide overlap for the transition, but compensates for the changed

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types playlist time by playing the event for an extended time, which is equal to the mix or wipe transition duration.

The Extended Modes are only available when "Play Mix/wipes early" is enabled and "Enable

Mode Selection" is checked.

Note: "Auto-Ripple List" must be enabled to maintain the playlist’s timing.

Configure the following options as required:

CAUTION: It must be understood that when an operator activates these features, recorded video beyond the database EOM exists for the material affected. This is an issue of Media Preparation.



Enable Mix/Wipe Support.

• Play Mixes/Wipes Early: (Default: disabled) Check to enable the system to roll overlapping events early. It causes the list to pull back any events with the effect type of Mix, Wipe, or

Mixed Transition.

Note: A Wipe effect requires a Wipe number. Each brand of Master Control Switcher may have it own set of Wipes. Each event can have its own wipe number. These are displayed and edited in Effect Number # field in the playlist editors of the windows client. When the event is played the Wipe number in the event is passed to the switcher when the Wipe transition is started. The Wipe number is solely dependent on the Master Control Switcher being used and is not interpreted by the automation as anything but a number.



Effect durations in frames: Set the frame values for slow, medium, and fast effect durations.

Effect durations are the amount of overlap time between the end of one spot and the beginning of the next spot.

• Slow: Valid numbers are 0 to 999 frames. Default is 60 frames.

ADC™ Device Server and Config Tool

Installation and Operations

• Medium: Valid numbers are 0 to 999 frames. Default is 30 frames.

• Fast: Valid numbers are 0 to 999 frames. Default is 15 frames.

Configuring List Types

IMPORTANT: These parameters must match the effects durations configured in your master control switcher. Failure to do so will result in mistimed effects.



Enable Mode Selection: Check to enable Extended mode selection.



Mode Selection: These options become available when Enable Mode Selection is checked.

Select one of the following:

• Extend Old: When this option is checked, the On-Air event is extended to provide overlap material for the transition (e.g. Dissolve or Mix). The list timing is maintained.

• Extend New: When this option is checked, the Next event is played early and for an extended duration. The list timing is maintained.

• Extend Both: When this option is checked, the On-Air event is extended by ½ the effect duration, the incoming event is played early by ½ the effect duration, and the new event is extended by ½ the effect duration.

Note: Extend both is not fully implemented as described above, because currently the playlist always plays early by the full transition duration.



Dwell: Support for a primary transition event that instructs the Versio Master Control Switcher to do a "U-fade". The event permits a variable duration, from 1 frame up to Output<x>_PostRoll for Native Driver (implemented on LLM 80.6.26.0 for Versio 2.2 and higher.)

The duration value may come from traffic, or be manually entered or changed. The duration of the previous and following event in the list are unaffected.

• Dwell event ID: This shows which event ID should be treated as the event for Dwell (should the default: BLACK not be convenient.)

IMPORTANT: This ID must match on the switch-only event configuration and on the playlist event.

Note: To disable this function delete the Dwell event ID

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

• Max Dwell duration: This is ADC’s equivalent of Output<x>_PostRoll. If necessary, the system can automatically adjust duration of BLACK event if it exceeds the limit. The range is

0-150 (decimal) frames, with 150 as the default.

About Output<x>_PostRoll:

Set ADC’s Max Dwell duration setting and Nexio PostRoll registry keys to the same value.

Output<x>_PostRoll extends playback beyond the specified Cue duration . The range is 0-150

(decimal) frames, with 0 as the default. Output<x>_PostRoll will take effect before blanking specified above.

Registry Location: HKCU\Software\ASC Audio Video\LLM\Settings\Output<x>_PostRoll

Prerequisite: LLM 80.6.26.0

Warning: While Max Dwell time can be safely set to less than PostRoll, setting Max Dwell larger than PostRoll can result playback problems – this should not be done.

About Dwell Operation:

The dwell is called by a switch only in the playlist.A duration less than the Output<x>_PostRoll uses the dwell function. Durations greater than that setting can switch to the Black Source available.

Requirement: Configure the AV Tables (at least the drop down pointing to the VMCS) for the switch only event, even if the customer doesn’t expect it to be used with durations greater than the dewll setting.

Note: The real duration of the dwell is ultimately controlled by the switch only event in the list.

CAUTION: If the dwell duration exceeds the Output<x>_PostRoll, the LLM playback pipeline will stop, which could cause the next clip to fail to queue in time.

• The Dwell duration ("dwell time" for the transition) can be used in combination with cuts and fades on previous & next clip to create the following effects: o

\_/ (fade down A, dwell black, fade up B) o

\_| (fade down A, dwell black, cut to B) o

|_/ (cut to black, dwell black, fade up B) o

|_| (cut to black, dwell black, cut to B)

Note: The transition is programmed in the BLACK event. For example, if a Fade-Fade (V) is used, the previous clip will fade to black, and then next will fade up.

• The dwell (black) time can be specified with a primary event that is separate from events that are responsible for playing media.

• When the event begins, VMCS will output black from the Versio. When the event ends,

VMCS will either output: o internal source "Clip A", if doing stacked playback

ADC™ Device Server and Config Tool

Installation and Operations or

Configuring List Types o internal source "Clip A" or "Clip B", as applicable, if doing ping-pong playback

Note: This solution doesn't require using a black source in VMCS directly. By specifying the dwell time, VMCS will output black.

8. Select the Device Owned tab. Use this tab to define the relationship between the list and the specific switcher.

Configure the following options as required:



Channel Number: Select from the drop down the channel number /switcher device the list will be using. This should be configured for normal operation of Manual Intervention.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

9. Select the Manual Intervention Options tab. Use this tab to select the "list behavior" in case of manual intervention.

Configure the following options as required:



List Behavior: From the available options, choose the "list behavior" to use when the

Automation Interface is disabled (manual mode).

• List continues playing with switcher control: When this option is selected the driver continues to send switch commands to the device.

• List continues without switcher control: When this option is selected the driver stops sending switch commands to the device.

• List Stops: When this option is selected the list stops playing.

ADC™ Device Server and Config Tool

Installation and Operations

10. Select the Skip Secondary tab.

Configuring List Types

Configure the following options to enable list linking as required:



Skip Secondary Event after Primary Event is Skipped: Check to enable skip.



Secondary Events To Skip: From the list, enable (check) the secondary events to skip. Uncheck to deselect.

11. Select the Audio Routing tab. (NEXIO AMP only)

The NEXIO AMP Track Router supports re-mapping audio tracks on playout and recording through use of an Output Audio Mask to identify which tracks should play on which audio channels and Input

Mask to identify which input Audio should place on which audio track. These masks are used to set the output port configuration. Primary, secondary, and tertiary tracks may be specified for cases where a backup track should be played if the preferred track (e.g. language) is not present.

Configured options of audio routing are applied to all disk drivers which are assigned to this list. If a driver (of a Video Disk) does not support audio routing (currently audio routing is supported only for

NEXIO driver), then audio routing settings does not affect on the driver. Basic operations on audio routing configuration performed by ADC List include:



Exchange of data on audio masks and audio tags with the List Options configuration.



Storing information about the current settings of audio routing during Device Server is running, saving the settings in the INI file when the Server is shut down, loading the settings from the INI file when the Server starts.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types



Transmission of audio routing settings to the driver, requesting the settings for the drivers.

To Configure Audio Routing:



Select the Audio Routing tab. On this tab the operator can configure Output Masks (Primary,

Secondary, Tertiary) and the Input Mask.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types



Configure Tag descriptions for Output and Input Masks by selecting a Channel and from the enabled Tag Description drop down menu select from a list of available descriptions.



Configure Type for Input Mask by selecting a Channel and from the enabled Type drop down menu select from a list of available descriptions.

Configuration Notes:

Note: While the following example screen shots are for Playlist, they reflect the same functionality

across all other lists.



No device, which supports Audio Routing, is assigned to a List. If no device can provide audio tag descriptions, Tags List will contain conditional strings defining the tag numbers.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

An audio mask can be edited and will be automatically applied when a device with Audio

Routing support is assigned to the list.



One device (one IP) which supports Audio Routing is assigned to the List.

• During initialization List reads saved Audio Routing settings from INI and sets up this settings to assigned device (to all their ports).

• Every device which supports Audio Routing has to store list of descriptions of audio tags.

When an operator opens the List Properties form, the List queries the list of descriptions from the device and passes it to the form to display.

• If an operator changes primary, secondary, ternary, Input audio mask of tags and Input audio mask of types, then these changes are applied to the device. If the device isn’t connected, then the changes are applied after connect.



Two or more devices (with different IP) which support Audio Routing are assigned to the List.

The behavior in this scenario is similar to the One device (one IP) case, except:

• After reading Audio Routing settings from INI, the List will apply up these settings to all devices, assigned to this list.

• List queries the list of descriptions from the first device which is assigned to this list.

• If an operator changed primary, secondary, ternary, Input audio mask of tags and Input audio mask of types, then these changes are applied to the all devices assigned to this list.



Stopping the server. On closing the Server, ADC list saves audio masks to the ADC INI. Tag descriptions aren’t saved.



Input Audio Masks include 2 masks: mask of tags and mask of audio types. The list of audio types retrieves from the device similarly audio tags list (FillAudioTypes function is used). NEXIO supports five audio types: PCM, Neutral/DTC, Dolby-Digital/AC3, Dolby-E, MPEG1 LayerI/II.

Usually audio tags include an audio type name. In this case, after assigning some tag to audio channel, the audio type is set automatically for this channel, but this type is still available for editing.

ADC™ Device Server and Config Tool

Installation and Operations

Note: The audio type must meet the audio tag for similar audio channel.

Configuring List Types

12. Select the Linking tab. Use this tab to put software triggers from one list to another. This functionality provides an alternative to the GPI method; a software solution for triggering one list by another list. These triggers allow all of the same functions available via the GPI inputs- all of the control panel functions plus 'Skip to next N' (ER17504). Also, it is possible to issue a ganged command, and to issue triggers across connected Device Servers.

Historically, in order to have one playlist control the start of another playlist on ADC a sGPI output is used on the Master playist to send a GPI trigger to the Slave playist(s)' GPI Input. The Slave playlists are then configured to accept a 'Contact Start'.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

Note: This software trigger list Linking functionality only applies to playlists. Media, GMT, Compile and Record lists do not need to be linked to each other or playlists.

Configure the following options to enable list linking as required:



To add a link playlist link, in the Available column select a playlist to link with the current playlist and click Add to<-. Lists that are already linked, are unavailable for linking with other playlists.



To remove a playlist link, in Linked column select a playlist to unlink from the current playlist and click Remove->.



To select playlists from other Device Servers, click the dropdown arrow to select from a list of available Device Servers.

IMPORTANT. When working with Linking options for a Playlist from Server1 and adding a Playlist from Server2 to Linked lists, proceed to Server2 list configuration in Config Tool and save its configuration manually. This is required because some parameters for the playlist from Server2 should be saved to its "ListConf.ini" file (see above), but it is impossible to save properties for

Server2 while working with Server1 in Config Tool.

About Device Server Functionality:



Each list of Device Server has information about its triggered lists (if it acts as Master list) and about list, which is Master for it (if it acts as triggered list). In both cases, info about each list consists of its global handle and its name.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

• List global handle is equal to server handle, which is shifted left by 16 bits, plus (OR) list local handle.

• List name is an additional parameter, which is used to correctly display linked lists in the

ConfigTool and the name of the Master list in the Transmission window in Air Client.



Data about linking / triggered playlists is saved in "ListConf.ini" file of Device Server.

Example: Playlist1 on Server1 may have such data in "ListConf.ini":

[LIST1]

...

TriggeredLists=2;210833410;PlayList 2 - Server1;84480001;PlayList 1 - Server2



It is not enough to keep only an array of triggered lists for each playlist. A playlist also keeps information about the list which it is currently triggered by. This data (the exact list name) is used in the caption of a Transmission List in Air Client. The handle of Master list allows it to determine whether this list is triggered by any other list. It is used when creating Available column on "Linking" tab.

Example : List2 on Server1 may have such data in "ListConf.ini":

[LIST2]

...

MasterTrigListHandle=210833409

MasterTrigListName=Server1 - PlayList 1



Ability to send a command to a linked list if current event contains any action except No Action.

When an event has any selected Action except No Action (for example, Play), the appropriate command is sent to a linked list at the appropriate time to allow both lists to roll simultaneously

(i.e. the events on the slave list(s) will typically play in conjunction with the triggering event on the master list.)

• Commands are divided into two groups: o

Those which can be executed immediately as they are received (e.g. Hold, Freeze, and

Skip). These commands are sent exactly when the event starts playing. o

Those which require pre-roll before execution (i.e. Play, Play Secondary, Roll, Skip and

Skip to Next). These commands are sent at the beginning of event's pre-roll.

IMPORTANT. Some commands can be executed only under certain conditions. For example,

Play command can be executed on list which is already threaded. Play to Next and Skip to Next commands can be successfully performed only if list contains "N" event.

Known Issues about Config Tool and Device Server Compatibility:

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

The drop-down combo-box on Linking Tab in Config Tool, allows choosing a Device Server from the list of available servers. This combo-box contains all servers located in the network, regardless their versions.

If an earlier version of Device Server (pre 12.19) is selected from this drop-down list, the

Available column will be empty. This occurs because the Config Tool sends a special object to the Device Server in order to get information about its playlists. Previous versions of Device

Server can’t reply to this object, so the information is not provided.

About Dynamic List Selection for API triggering

ADC v12.23 and higher supports Dynamic List Selection for API triggering. It Incorporates a simple and dynamic means to alter the linked list associations from the Air Client and on an event-by-event bases.

Storing selected lists within the event structure:

Enabled triggered lists are configurable on an event basis; and information is stored within the event structure. Device Server and Air Client keep information about triggered lists in format "list handle" –

"list name (including server name)".

• List handle is used as a destination for list trigger commands.

• list name is used in the UI.

A bit-mask field is used for keeping triggered lists state (enabled/disabled) within event structure. Each bit of this field equals 0 if the list is currently disabled and 1 if the list is currently enabled.

Example: In the following example a user selected 3 of 4 possible lists. Bit-mask is equal to 1101

10 information between Air Client and Device Server

or to

. This method of data organization is invisible for user because it is only necessary for transferring

Bit Mask Field Method Restrictions:

This method imposes several user restrictions:

• A maximum 16 different lists can be triggered by one Transmission List. The Config Tool Linking tab will not allow more than 16 triggered lists to be added to one Transmission List.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

• Since bit-mask addresses lists according only to their order (not names or handles), Triggered lists should not be changed from the Config Tool if triggers are already used in Transmission List.



Violation of this rule can result in triggered lists reordering; causing bits in bit-mask to correspond to wrong lists, and the server to send trigger commands to incorrect lists.



To prevent users from editing the triggered lists array, the Config Tool Linking tab becomes disabled if at least one event within the lookahead of the current Transmission List contains a non-empty trigger action.

Configuration:

1. Select the List Redundancy tab.

This tab is available if the customer has purchased List Redundancy functionality.

Note: Cloning and List Redundancy are considered mutually exclusive functionalities.

Master List: Enable Copy options are available on the Master list only.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

Slave List: To reduce the chance of errors the Enable Copy options are grayed out on the Slave list, so the user can enable/disable it only on the Master list.

Configure the following options to enable list linking as required:



Enable Auto Resync Function: Enable/Disable Auto Resync.

Checked: (Recommended) Enable auto re-sync function of List Redundancy.

Unchecked: Disable auto re-sync function of List Redundancy.

About the current Re-Sync mechanism of List Redundancy:

Users should send Mirror and Sync command manually from LRCC to start the Sync.

When the Master List receives both the Mirror and Sync commands, the Auto Re-Sync mechanism is turned on, and users can disable Auto Re-Sync by sending one of the commands of Disable LR, Stop Sync, or Stop Mirror.

The Master List and Slave List exchanges the current playing event and frame every second.

• If the Events are different or the frames from two lists differ more than 3 frames, out of sync is considered to have happened once.

• If out of sync happens continuously, i.e. more than 20 times, the Auto Re-Sync function is triggered.

The auto re-sync function makes it possible to synchronize with all short events. When the

Master List receives a ‘Sync in 10 seconds’ command from LRCC, it calculates the current event’s duration. If it is shorter than 10 seconds, it adds the next events duration, until there is enough time to put an AO flag (Audio Over) to an event in the Slave List.

If for any reason, the Sync operation fails, the Auto Re-Sync is triggered. So users only need to send the first Sync command from LRCC. The Auto Re-Sync mechanism will handle the rest until successfully Synchronized.



Enable Auto Swap Function: Enable/Disable Auto Swap.

Checked: Enable Auto Swap Function.

Unchecked: (Recommended) Disable Auto Swap Function.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

If the master list is stopped and the slave list is still running, the Auto swap function automatically swaps the role of the master list with the slave list.

Note: Currently, the Auto Swap Function cannot operate swap, so even if the master and slave list swap roles, the output stream will be still from the former master list’s device.



Enable Sync on Next Event During Upcounting: Check to permit the system to partially synchronize lists on the current upcounting event.

Usually, to sync on the next event, an AO must be put on the next event in both Master and

Slave lists. But for an upcounting event, the start time of next event is unknown, so an AO cannot be put on the next event. This means we can never sync on an event next to an AO event.

Partially synchronizing on the event overcomes this problem (i.e. On the current upcounting event, when operator skips to next event, both Master and Slave list roll together and keep synchronized on the next event.



Enable Copy Lookahead Value from Master List to Slave: When using List Redundancy, enabling this option makes the Lookahead on the SLAVE list follow the value of the lookahead that is set on the MASTER list.

• Check to enable this feature and copy the Lookahead Value from the Master List to the Slave

List. The value of this option will be saved in INI-file.

• Uncheck (Default) to disable this feature.

Note: To reduce the chance of errors, this option can only be enabled/disabled on a Master list. This option is grayed out on a Slave list.

This option only works if option "Enable Copy Lookahead Value from Master List to Slave" is enabled, a pair of lists (channel) is created in LRCC and their behavior is specified

(Master/Slave). If the value of Lookahead is changed on the Master list, it is automatically copied to the Slave list. And on a Slave list the Lookahead spin-edit is grayed out.

Note: This enhancement involves only the value of Lookahead in events, which can be specified both in the Config Tool and Air Client, but not invoked duration-based Lookahead.

Copy Lookahead Enabling Rules:

• If option "Enable Copy Lookahead Value from Master List to Slave" is enabled/disabled on a

Master list, it is automatically enabled/disabled on a Slave list (but on the Slave list it is always grayed-out).

• If the value of Lookahead on Master and Slave list is different and the user turns on option

"Enable Copy Lookahead Value from Master List to Slave", the Lookahead value is automatically copied from the Master to Slave at this moment.



Enable Copy Done Count Value from Master List to Slave: Enable (check) / Disable (uncheck) allowing the DONE Count to be mirrored to the Slave list.

• The default value is false (not checked), so the customers who don’t need this feature will have no changes in their work.

• Customers who want to copy done count value can enable this option. The value of this option is saved in INI-file.

If option "Enable Copy Done Count Value from Master List to Slave" is…

• Enabled/disabled on Master list, it will be automatically enabled/disabled on Slave list (but on Slave list it will be always grayed-out, like a read-only option).

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

• Different and the user turns on option "Enable Copy Done Count Value from Master List to

Slave", the Done Count value is automatically copied from Master to Slave at this moment.

This feature will work only if….

• The option "Enable Copy Done Count Value from Master List to Slave" is enabled,

• A pair of lists (channel) is created in LRCC and their behavior is specified (Master/Slave).

If the value of Done Count is changed on Master list, it is automatically copied to Slave list. And on Slave list Done Count spin-edit will be grayed out.



Meaning of the diagnostic information items:

• Redundant Server: The name of the server, which the redundant list of this list is in.

• Redundant Handle: The server handle and list handle of the redundant list of this list.

• Redundant Latency: When the master list receives a command, it sends the command to the slave list and executes the command on both sides after this latency time

• Behavior: Master or Slave or not decided

• Status: LR link status

• RAN IP: This is the server’s RAN network IP address.

• RAN Port: This server’s RAN IP port

• RAN Latency: If Master and Slave cannot get connected after this latency (default 20 seconds), they will give up and run separately.

• Select the List Redundancy tab.

2. When finished click OK, and then Apply.

Configuring Media List Options

Media lists are modified Transmission lists used exclusively by the Media Client application. They are not designed for use as Transmission lists. The Media Client application uses the media devices assigned to the Media lists for automated recording and copying activities. The Media Client application will place events on the Media list, run them and then remove them from the list. Media lists do not require any operator intervention and events generally should not be inserted into them or deleted from them. The

A/V routing tables for devices assigned to Media lists may be configured as they are for Transmission lists to allow automatic routing of A/V streams.

Note: For more information about Media lists reference the "Media Client Operator’s Guide".

To Configure Media List Options

A number of options may configured to control the behavior of Media Lists. These options are accessed from the Configuration Manager’s List Assignments window.

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

1. To access the Media List options configuration GUI, select a Media List in the Lists pane.

3. Select the Parameters tab. This tab contains general configuration options for Media Lists. Some options are commonly used and enabled by default.

Configure the following options as required:

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types

IMPORTANT: While the configuration options Always Allow Recue Following an Upcount and Block

Recue Following an Upcount are currently shown as available for Media List, GMT List, and Compile

List types, they are not recommended for use with these lists.



Name: Enter a name for this Transmission List. List names are limited to 16 characters.



Options:

• Auto Restart When Cued: (Default: disabled) When enabled, this option causes events to automatically restart, without manual intervention, if the media has been recued.

When this option is disabled, the automation system marks the event as missing and does not automatically cue the event when located.

• Recue On Media Changes: (Default: enabled) When enabled, this option causes events to automatically recue if the event’s SOM (start-of-message time), DUR (duration), or New AFD is changed.

Note: The ID Video ARC is reapplied if the event’s New AFD value is changed while the event is CUED.

• Update Cued Event on Media Change: When this parameter is enabled (checked), all of the database derived metadata for any cued events is updated. o

If ‘Recue on Media Changes’ parameter is enabled, then this parameter is also enabled. o

If this parameter is enabled, but the ‘Recue on Media Change’ parameter is disabled, then although the event is updated, the device is not recued or otherwise updated.

CAUTION: This configuration scenario can cause unanticipated or invalid behaviors, such as the device and device driver’s head data to get out of sync. To avoid this ensure

‘Recue on Media Changes is also set. o

If this parameter is disabled, ‘Recue on Media Changes’ must also be disabled and no updates will be applied to cued events. o

If Auto Ripple is enabled, the start time of the event following the an updated event is also updated.

• Update Playing Event on Media Change: When this parameter is enabled (checked), the system partially updates the metadata of an event that is playing at the time of an update.

The device cannot be recued and the SOM of the event is not updated. o

If this parameter is enabled, then ‘Update Cued Event on Media Change’ must also be enabled. o

WARNING: If the device is not updated- as in the case of a cued event because Recue on

Media Changes is disabled, or in all cases for playing events- and the updated duration is

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types longer than the duration used to initially cue the device, the device may cease playout at the end of the original duration, even if the event is updated. This typically causes a TapeEnd error and the list skips forward to the next event.

Enhanced Functionality includes: o

When the termination event is an O (hard start) event the Time To Next display includes the running short value. o

Zero duration up counters do not stop the rippling. o

"standby on" time (see below).

SOM minus the preroll of the last spot played).

(registered) events count toward the total thread time as if they were threaded.



Time Parameters: These options specify time values for this list.

IMPORTANT Preroll Note: For Media Client, there is a dependency between the Preroll setting in the Configuration of a Prep Window (set in Configuration>"selected pre form">General>Time

Parameters) and the Preroll of the Medialist (set in Config Tool -> Medialist

Properties>Parameters >Time Parameters). The prep-form and Media list preroll values should match.

• Preroll Seconds: Define the number of preroll seconds to be used for the selected list. The valid range is 0-59 seconds. Default is 3 seconds.

• Preroll Frames: Define the number of preroll frames to be used for the selected list. The valid range is 0-29 frames. Default is 0.

Note: If a list preroll of less than 3 seconds is used, VTRs assigned to this list will not perform a tape speed override (TSO) when they roll.

Frame-accurate playout from tape cannot be guaranteed if a list preroll of less than 3 seconds is configured. Operators may manually override the list preroll by using the Roll

Now button on the control panel. Only events registered with Switch-Only devices or video

ADC™ Device Server and Config Tool

Installation and Operations Configuring List Types server decoder ports (if they are configured to support "instant prerolls") may be rolled using the Roll Now button.