Imagine Communications v11 ADC Device Server Installation, Configuration, and Operations Reference
Annonce
Annonce
Installation, Configuration, and Operations
Reference
ADC Device Server v11
(and Configuration Manager)
(Current to Device Server v11.61.4)
Release: 5-December-2012
Revision: 22-April-2014
ADC Device Server v11.61.4 Installation, Configuration, and Operations Reference
Publication Information
© 2014 Imagine Communications Corp. Proprietary and Confidential.
Imagine Communications considers this document and its contents to be proprietary and confidential. Except for making a reasonable number of copies for your own internal use, you may not reproduce this publication, or any part thereof, in any form, by any method, for any purpose, or in any language other than English without the written consent of Imagine
Communications. All others uses are illegal.
This publication is designed to assist in the use of the product as it exists on the date of publication of this manual, and may not reflect the product at the current time or an unknown time in the future. This publication does not in any way warrant description accuracy or guarantee the use for the product to which it refers. Imagine Communications reserves the right, without notice to make such changes in equipment, design, specifications, components, or documentation as progress may warrant to improve the performance of the product.
Trademarks
Product names and other brands (such as ADC™, D-Series™, Nexio®, Nexio® Insight, Nexio®
Motion, PowerSmart®, Versio™) are trademarks or trade names of Imagine Communications or its subsidiaries. Microsoft® and Windows® are registered trademarks of Microsoft Corporation.
All other trademarks and trade names are the property of their respective companies.
Contact Information
Imagine Communications has office locations around the world. For domestic and international location and contact information see: http://www.imaginecommunications.com/contact-us/
Support Contact Information
For domestic and international support contact information see:
Support Contacts: http://www.imaginecommunications.com/services/technical-support/
eCustomer Portal: http://support.imaginecommunications.com
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 2 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Contents
Contents
........................................................................... 7
................................................................................................. 16
................................................................................................ 20
......................................................................................... 25
........................................................................................... 37
Configuring Devices using Configuration Manager
............................. 39
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 3 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Contents
.................................................................. 227
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 4 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Contents
................................................................ 245
Configuring Device Assignments
........................................................ 258
.......................................................................... 265
Configuring Audio / Video Routing Tables
......................................... 324
.......................................................................... 329
.................................................................................... 334
Diagnostics and Troubleshooting
........................................................ 336
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 5 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Contents
.......................................................... 350
............................................................... 354
........................................................... 398
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 6 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Device Server Overview
Device Server Overview
About the Device Server
The ADC Device Server is the heart of the automation system. The Device Server controls devices either through RS-422 serial connections, General Purpose Interface (GPI) contactclosure triggers, or an Ethernet connection. The Device Server communicates with remote clients through a Local Area Network (LAN) connection. The Device Server runs the ADC
Device Server v11 application software.
Physically, the ADC Device Server is a rack mount PC. The Device Server contains a PCI
CPU card (motherboard), either four or eight PCI eight-port RS-422 serial boards to which the devices connect, two (or more) PCI GPI cards, a PCI timecode reader / video sync card, and a PCI dual-port network interface card. A Device Server installed with four eight-port serial boards can control a maximum of 32 devices via serial connection. A Device Server installed with eight eight-port serial boards can control a maximum of 64 devices via serial connection.
Both Device Server hardware configurations can control up to 16 lists (Transmission lists,
Compile lists, Record lists, Media lists or GMT lists) simultaneously. If more capacity is needed, additional Device Servers may be added to the system.
The ADC Device Server is configured remotely from any client PC in the Automation System containing the Configuration Manager application. The Configuration Manager incorporates common Windows usability features, such as drag and drop, cut and paste, and a point-andclick graphical user interface.
The system is highly flexible and may be configured for most broadcast operations and equipment. The ADC Device Server controls most types and models of broadcast devices, including cart machines, video servers, VTRs, still stores, character generators, routers, and master control switchers.
One of the ADC Device Server’s major strengths is its powerful software. The software interfaces with and controls the broadcast devices (instead of through hardware interface boxes). The software can be easily modified to incorporate new models or types of devices.
The ADC Device Server integrates the on-air playout system by using station timecode or reference video to maintain timing. The Master Control operator can control the on-air playout from an automation hardware control panel (similar to a Master Control Switcher
Panel). The system’s Transmission lists may also be started automatically by time of day, as well as remotely by a GPI trigger.
Clarification of Nomenclature
Historically, ADC used the term 'Device Server' for both the physical unit (chassis) and the software application.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 7 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Device Server Overview
Current nomenclature designates the chassis as the Device Controller and the software application as the Device Server.
Minimum System Requirements
The following are minimum system requirements for ADC Automation system components as of the release of this document.
Supported Database
The following databases are supported:
SQL 2005, SQL 2005 Express, SQL 2008, SQL 2008 Express
Supported OS Level
ADC Device Server v11.60/12.18 and higher and Client v4.18 and higher support operation on 32-bit and 64-bit operating systems.
Server Requirements
Type
Hardware
Software
Operating System
Network Interface Card
Requirements
- Device Server (PCI Chassis)
- Device Controller (CHP chassis: Common Hardware
Platform)
Device Sever v11.60.x or higher
Note: If an older version of Device Server is used, contact
Automation Technical Support for compatibility
Microsoft® Windows® Server 2008
- CHP chassis only
- GigE Ethernet
- NetBIOS-Over-TCP/IP
- (In conjunction w/ Windows 7 Clients)
- Requires Device Sever v11.55.12 or higher
Note: DSv11.60.19 and higher supports both 32 and 64bit
versions of the Operating System. (See above: Supported
OS Level.)
Note: If your facility utilizes multiple Device Servers and your upgrade plans do not include migrating all of them to the same version resulting in operating in a mixed version environment, please contact ADC Automation Technical
Support to confirm there will be no compatibility issues
between the versions utilized.
When communicating via NETBIOS over TCP/IP a Gigabit
NIC and switch is required
Client Requirements
IMPORTANT Note on Merge of Client V3 and V4 Development Streams:
Air Client / Media Client for Device Server v11 and Device Server v12 are merged into single
Air Client and Media Client streams. Starting with Clients v4.16 and higher, these versions
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 8 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Device Server Overview are compatible with both the v11.59 and v12.15 and higher of Device Server software. For more details, please contact Automation Technical Support.
IMPORTANT Note on Windows Operating System Support:
Automation no longer tests nor provides support for Microsoft® Windows® 2000 or
Microsoft® Windows® XP configurations. However, for customers with existing client PCs running these OS versions, we believe there should be no issue with installing this ADC version on those existing PCs.
All future client versions, starting with v4.16 require Microsoft® Windows® 7 Pro operating system.
For more details, please contact Automation Technical Support.
Type Requirements
Hardware
Network Interface Card
Software
Processor – Pentium 4 3.0 GHz or greater
RAM - 512MB or greater
HD – 80 GB Hard Drive or greater (Required: 25MB of free
Hard Drive Space)
2 TCP 1000BT NICs
Additional Intel Network Interface Cards (Pro 100S) may be required for systems connecting to external networks, or a database using TCP/IP.
When communicating via NETBIOS over TCP/IP a Gigabit
NIC and switch is required.
- Air Client v3.58.x or higher / Air Client v4.16.x or higher
- Media Client v3.58.x or higher / Media Client v4.16.x or higher
Note: Client v4.18 and higher support both 32 and 64bit
Operating Systems. See above: Supported OS Level.
See below: Important Note about nbios32.dll and
apilib32.dll.)
Operating System Microsoft® Windows® 7
- (In conjunction w/ Windows Server 2008 Device
Servers.)
Note: Client v4.18 and higher support both 32 and 64bit versions of the Operating System. See above: Supported OS
Level.
Configuration/Parameters System needs to be set up to use ODBC
Important Note about nbios32.dll and apilib32.dll:
Care should be taken with regards to the support .dll files- nbios32.dll and apilib32.dll- used on various components of the system. The Device Servers and all clients should use the
3.4.1.0 version .dlls supplied with this release and this same version should be used on all clients interconnecting with this release. The current and recent versions of Air Client and
Media Client- all versions of Air Client from 3.14.6.0A forward and all versions of Media
Client from 3.5.3.0 forward- will normally install the same versions. However, the versions installed on each client should be verified, as it is possible for earlier .dlls to have been substituted.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 9 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
About GigE Ethernet Environments
Device Server Overview
It is recommended that a full GigE Ethernet environment be used for both client and server.
While a mixed GigE /100M or 100Mb environment will work, it will result in a maximum
100Mb performance!
Gigabit Ethernet (1000Mb) networks are strongly recommended for all 11.x installations. The majority of development and testing of ADC is done in this environment and certain assumptions have and will be made based on this. However, this impacts all aspects of existing installations- device controllers, clients, file servers, network switches, and wiring.
Therefore, testing has been done to assure that ADC 11.x can be successfully deployed on existing LAN networks. Note that this assumes that there are no major changes to the system scope from the existing operation- the 11.x is built and configured in the same general manner as the previous version that it replaces.
While a complete replacement or upgrading of all the affected components is the ideal course of action, this is of course not possible or practical in all cases. It is acceptable to replace or upgrade portions of the system, but be aware that doing so may provide no immediate benefit- depending on the combination of devices, portions of the system, or the system as a whole, may be limited by the lowest speed component still in place, regardless of other factors. Contact your Imagine Communications representative for assistance in the planning and deployment of new and upgraded components.
Hardware Chassis
The Device Server can be run on a single chassis or as a dual redundant pair.
NOTE: The current chassis is referred to as H-Class ADC Device Controller. For information on the installation and setup of this chassis reference: “ADC Device Controller Hardware
Reference”.
ADC Device Controller
The ADC Device Controller is the computer dedicated to communicating and controlling the broadcast devices and client workstations. This computer runs the Device Server application which controls devices via an RS-422 point-to-point serial connection, a GPI contact-closure trigger, or an Ethernet connection. It also sends and receives frame-accurate information across the Local Area Network (LAN) to and from remote client workstations.
There are two models of Device Controller; a 2RU model and a 4RU model. Both chassis are built around the same single board computer. The chassis model used in a given installation depends on the needs and budget of the customer.
The 2RU Device Controller Chassis
The 2RU model offers a smaller rack footprint and includes limited hardware redundancy with dual power supplies. Serial device control is supported in the following manner:
Up to 3 PC slots can be fitted with ADC 8-Port Serial cards, supporting up to 24 high speed serial ports for device control. It is available in 8, 16 and 24 port configurations.
Up to 2 PC slots can be fitted with ADC 16-Port Serial cards, supporting up to 32 high speed serial ports for device control. It is available in 16 and 32 port configurations.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 10 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Device Server Overview
The 4RU Device Controller Chassis
The 4RU model offers greater expandability and hardware redundancy with dual power supplies and (optionally) raided hard drives. Serial device control is supported in the following manner:
Currently up to eight PC slots can be fitted with ADC 8-Port Serial cards, supporting up to 64 high speed serial ports for device control.
Currently up to four PC slots can be fitted with ADC 16-Port Serial cards, supporting up to 64 high speed serial ports for device control.
Backup (Redundant) Device Controller
(Optional) Redundancy is an important part of automation. The ability to recover immediately from hardware failure in a broadcast environment is crucial. Protection against
Device Controller failure can be achieved through a backup (redundant) Device Controller.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 11 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Device Server Overview
The backup Device Controller is a computer that is identical to the main Device Controller and is configured the same way. If the main Device Controller fails, the backup Device
Controller takes over the tasks handled by the main Device Controller. If the main Device
Controller fails, device control may be manually transferred to the backup Device Controller.
The transfer is accomplished by an RS-422 switching device.
Supported Broadcast Devices
The ADC Device Server is designed to interface with most devices commonly found in broadcast operations including:
• Cart Machines
• Video Servers
• VTRs
• Routing Switchers
• Master Control Switchers
• Still Stores
• Character Generators
• Audio Carts
• External Encoders And Decoders
• Subtitling Systems
• Satellite Systems
• Archive Systems
Most broadcast devices may be controlled by the Device Server through a point-to-point RS-
422 serial connection. Some broadcast devices do not accept RS-422 serial control. These devices may be triggered by a GPI contact closure. Archive systems may be controlled by an
Ethernet connection to the archive manager. See Appendix A of this manual for a list of
supported broadcast devices.
Play lists and Transmission Lists
Play lists are files that contain the schedules of events to be played, recorded or compiled. In a play list, each event contains information such as start time, event type, material identifier
(ID), title, segment number, duration, start-of-message time (SOM), and audio/video output.
Play lists may be created locally at the Air Client workstations or from traffic schedules. Play lists are stored on the file server and are available to all users on the system for viewing and editing. When a play list is ready for transmission, the play list file is loaded into the transmission window where it becomes a Transmission list. A Transmission list can contain a maximum of 2,500 events by default. (This number may be increased if necessary.)
When an event in the Transmission list is activated, the event performs a predefined function such as Play, Record, Switch or Cue. The ADC Device Server supports multiple
Transmission lists; each list may be made up of several appended play lists.
When the system is initially configured, each broadcast device is assigned to a specific
Transmission list. During playout of the Transmission list, the devices assigned to the list are available to run the events in the list. Each Transmission list represents a separate playout channel. This feature allows for simultaneous multichannel operations. Additionally, cart machine VTRs may be assigned to two or more Transmission lists for two (or more) channel
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 12 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Device Server Overview operation, if each VTR in the cart machine has a separate audio/video path through a router.
Cart machine VTRs may be assigned different tasks. For example, two VTRs might be used for playout, one for recording, and one for compiling (see Chapter 4, Compile list). Video servers with multiple decoder ports may be shared among Transmission lists as well.
The ADC Device Server runs each event in the list sequentially for its full duration, unless the operator manually intervenes or until specific types of events, such as live events or timetriggered events, are encountered. If changes to the list are needed during playout, the operator may directly edit an event in the list.
Playout may be controlled by the control panel (software or hardware). Using the control panel buttons, it is possible to skip events, hold events beyond their duration, re-cue events and then restart them. An on-air event may also be edited by either adding or subtracting seconds to the event’s duration using the control panel.
Automated Recording
(Optional) An ADC Device Server record function allows automated recording of material. A recording may be set up for a specific time and duration. Record events may be placed on a
Record list - similar to a play list but containing only primary record events. Like a play list, the Record list is loaded into a transmission window to run the record events in the list. The
Record list has only recording devices assigned to it as resources.
A secondary record event, also an ADC Device Server option, is available to record live events as they play out on a Transmission list. The secondary record event feature uses a play list that has both record and playout events. This feature can store program segment information (for future replay of a live event).
The ADC Device Server may use any VTR or video server encoder port in the system for a recording. For long VTR recordings that require several tapes, or to create duplicate copies of a show, several VTRs may be assigned. This also allows multiple recordings to take place simultaneously using the same Record list.
The ADC Device Server controls input audio and video switching when the recording begins.
Recordings may be made from program output or from external satellite feeds.
NOTE: AutoSat system is available to automate acquisition and recording of satellite feeds.
AutoSat works as an integrated part of the automation system, using a simple menu-driven
system. Contact your autiomation representative for more information on AutoSat.
Global Media Transfer
(Optional) Global Media Transfer (GMT) is the Automation system’s technology for controlling media movement within a broadcast facility. GMT is an integrated component of the automation system. Each Transmission list may request that GMT find media that is not available in the playout devices assigned to the list. GMT finds the media in other devices
(VTRs, cart machines, other video servers on a fibrechannel or wide-area network, or data archives) and copies the media to a destination device (the playout device - a video server) assigned to the Transmission list. The Transmission list is then able to air the media.
The main tasks of GMT are:
• Find media needed by an on-air Transmission list
• Copy that media to a video server assigned to that Transmission list
• Monitor the transfer of the media
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 13 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Device Server Overview
• Log the transfer of the media
• Provide automatic media duplication on multiple video servers for air protection
• Copy media to or from an archive
By accomplishing these tasks, GMT extends the level of automation beyond the basic on-air system. By allowing the automation system to handle the movement of media, less manual operator intervention is required.
Device Server Display Overview
The Automation Device Server(s) operates from a rack mounted computer that is away from normal operational areas of the facility. The Device Server(s) is extremely active in the dayto-day operation of the facility, and it is strongly recommended that no other applications be operated from the Device Server(s).
When installed and running there is actually little to see. The following is only the Device
Server display – visible: the current date, the timing source to the Device Server, timing mode, the current time, software build version and the date of compilation.
Timing sources include:
• TC for local timecode generator
• V for house video reference
• PC for internal clock from the Device Server
Timing modes include:
• DF for drop frame
• NDF for non-drop frame
Main Menu
File menu
Option Description
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 14 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Option Description
Server Handle
Device Server Overview
Used to configure/change the Global Server Number for the
Main Device Server.
Alternate Handle
TCP/IP for WAN addressing
Exit
In an environment utilizing Cloning, this option is used to configure the server handle (Global Server Number) of the backup, or “clone” Device Server.
Note: This option is available only when a customer has
purchased a Cloning build of the Device Server.
In an environment utilizing a Remote Air Client, this option is used to configure the Device Server’s “listen port” (TCP/IP
Socket Listen Port).
Exit and closed the Device Server application.
View menu
Option
Connections
Description
Opens a window that displays all of the Device Server and client applications currently logged into this Device Server.
Help menu
Option
About…
Description
Launch a dialog displaying Device Server version and copyright information.
Note: When calling Technical Support to report a problem,
make sure you have the displayed version number handy.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 15 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Operation
Operation
To Start the Device Server
On the Device Server’s desktop, double-click the Device Server icon. This launches the ADC
Device Server application. (Note: In some installations this icon may be named ADCNT.)
When the Device Server application is running, an application bar is displayed at the top of the screen similar to the one illustrated below.
To Exit the Device Server
Use this procedure to exit and close the main Device Server.
From the Device Server main menu select File > Exit
Or
Click the X button in the upper right corner of the Device Server display.
To View Connections
Use the following procedure to view of the Device Server and client applications currently logged into this Device Server.
1. From the Device Server main menu select View > Connections. The Connections window is displayed showing all connections made via the automation Network to this
Device Server
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 16 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Operation
2. From the Connections window main menu an operator can choose:
• File > Close: Close the Connections window
• View > Refresh: (or Press F5) to refresh the display
• Help > …: Launch Help System.
To View Help Information
From the Device Server main menu select Help > About... The About Device Server window is displayed.
NOTE: When calling Technical Support to report a problem, make sure you have the
displayed version number handy.
To Disable/Enable Cloning
Using Alternate Handle (Recommended Method)
To disable cloning because a cloning-related problem has been identified or is suspected- or simply to disable it for an extended period of time- then the following the 'Alternate Handle' technique provides a more complete de-activation of cloning.
Change Rules
When the DS application is running as "Main With Clone", any attempt to change the alternative handle to 0, displays a popup message informing the user to set the alternative handle to 0 on the clone DS application first.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 17 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Operation
Once the alternative handle on the clone DS application is changed to 0, the main DS application becomes "Main Without Clone". Now the user can set its alternative handle to
0.
If the main DS application is not running as "Main With Clone", it is OK to set its alternative handle to 0.
Disable cloning feature
Once the clone Device Server (DS) is running in synchronization with the main DS, if disabling of the cloning feature is required, implement the following procedure, exactly.
1. On the clone DS from the main menu select File > Alternate Handle and change the alternate handle to 0.
When this is done, there will be empty caption on clone DS and the caption on main DS becomes “Main Without Clone”. The relay position is on the main DS.
2. On the main DS from the main menu select File > Alternate Handle and change the alternate handle to 0.
When this is done, the cloning feature code is completely bypassed. The caption on the main DS becomes empty. The relay position is still on main DS.
Why change the Clone DS Alternate Handle to 0 first?
When the alternative handle on the clone DS application is not 0 (is the handle of main DS), and the alternative handle on the main DS application is changed to 0 first, the clone DS takes over control. The relay position is on the clone DS. This behavior is explained as follows:
When the cloning feature is disabled on the main DS application, the heart beat between the main DS application and the cloning control panel is stopped. However, the clone DS application continues to send heart beat signals to the cloning control panel. In this scenario, the cloning control panel judges that the main DS has failed and that the clone DS is still active. This results in the relay being incorrectly switched from the main DS to the clone DS.
Enable cloning feature again
1. Put back alternate handle on the main Device Server (DS).
The caption on the main DS application will become “Main Without Clone” in RED color.
The relay position is on main DS.
2. Put back alternative handle on the clone DS.
The caption on the clone DS application will become “Clone Of Main”, at the same time, the caption on the main DS application will become “Main With Clone”.
Using Device Server Menu Options (for Information
Only)
IMPORTANT: Do Not Use the Start and Stop Cloning menu options. While the following menu options may be displayed for a Cloning-enabled build of Device Server, they are not
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 18 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Operation
to be used at this time. The following information is provided as a reference for future functionality only. Please contact Automation Support for further information.
For some mission critical TV channels, it is desirable to have a back up (or clone) ADC
Device Server to take over automation control when the main device server fails.
Cloning is optional functionality purchased by a customer.
This cloning feature has two basic functions.
To copy the device status, device storage, list contents, list status, and other state machines from the main device server application to the clone device server application.
To dynamically maintain the synchronization by means of feedback close control looping.
To disable cloning because a cloning-related problem has been identified or is suspected use the Device Server menu options: Stop Cloning and Start Cloning.
To Stop Cloning
The Cloning process may be stopped or started manually from the CLONE Device Server.
This feature is only supported on Devices Servers that contain a 1GHz (or faster) CPU.
To stop the Cloning process manually, from the CLONE Device Server’s main menu select
File > Stop Cloning”.
The Cloning Process halts, and the MAIN Device Server displays “Main Without Clone” and the clone DS displays "Cloning Stopped".
NOTE: This ceases the mirroring of list and status data between the MAIN and CLONE device servers, and disables automatic failover. However, the device servers will continue to generate cloning heart beat across the network connection between them. This has the same effect as setting the CLONE Device Server’s Alternate Server Handle to “0”.
To Restart Cloning
To restart the Cloning process, from the CLONE Device Server’s main menu select File >
Start Cloning.
The Cloning Process starts, and the MAIN Device Server displays “Main With Clone” and the clone DS displays "Clone Of Main".
NOTE: This begins the mirroring process between the device servers, which when complete will restore automatic failover – provided the front panel controls of the Cloning Control panel are correctly set. This has the same effect as setting the CLONE Device Server’s Alternate
Server Handle back to its original value.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 19 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Installation
Installation
The Pre-installed Application
The Automation system comes with all of the necessary software already installed. If, for some reason, the operating system and ADC Device Server v11 software need to be reinstalled, a bootable CD-ROM is supplied for each Device Server (and client PC) in your system. This CD-ROM contains a compressed image of the Device Server’s hard drive at the time the system was delivered. The CD-ROM does not contain your custom build of
Device Server software or any configuration changes you or your Customer Support
Engineer may have made to the system during commissioning.
NOTE: It is essential to back up your Device Server software and configuration files
(ADC100NT.INI, LISTCONF.INI, HANDLES.INI) to another location before attempting to reinstall the operating system. These files are usually located in the “C:\Server” folder on the
Device Server.
IMPORTANT: NetBIOS hotfix for 64 bit OS: The following only affects ADC v11.x running under a 64 bit OS. When running 64 bit Server 2008 or Windows 7, there is an issue where client names are retained after an abnormal disconnect, requiring the name to be changed in order to reconnect. In turn, this means that the customer eventually runs out of logins and must restart the device server. It turns out that this is an OS issue and there is a Microsoft hotfix to correct it; http://support.microsoft.com/kb/2633667/en .
To Reinstall Windows OS (if required)
To reinstall the Windows Operating System on your Device Server, you will need to boot directly from the Windows Installation CD. To do this, ensure the computer's BIOS has been configured to boot from the CD-ROM drive before it attempts to boot from the hard drive:
1. Reboot the computer.
2. Press <Del> when prompted to enter the BIOS setup utility.
3. Select Advanced CMOS Setup and press <Enter>.
4. Press the <down arrow> to highlight 2nd Boot Device, and press <Page Up> or <Page
Down> until CDROM has been selected.
5. Press the <down arrow> to highlight 3rd Boot Device, and press <Page Up> or <Page
Down> until IDE-0 has been selected.
6. Press <ESC>, then <F10>, and <Y> to Save current settings and exit.
7. Make sure the supplied Windows Installation CD is in the CD-ROM drive and allow the computer to reboot.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 20 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Installation
8. When the computer reboots, it will look for a bootable CD-ROM. When it finds one, it will display "Press any key to boot from CD". Press <Enter>.
Default .ini Settings
When the INI file does not exist, the following ini items are assigned a Default value of True
(enabled) for the following Device Server's List Properties.
Recue on Media Changes
Update Cued event on media changes
Only Thread Next AO Event
Update On-Air Time
Auto Ripple Times
Keep List Threaded
Release Tension When Cued
Tension After Up Counter
Play Hard Hits
Contact Start
Update Final UpCount Durations
Confirm the Application Icon Command Line
Before running the ADC Device Server application, you may wish to check that the command line for the application is written correctly.
1. Right-click on the ADC100NT icon on the Device Server’s desktop, and then select
“Properties”.
2. In the window that opens, select the “Shortcut” tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 21 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Installation
3. In the target field, the command line should read C:\Server\adc100nt.exe MAIN. The
“MAIN” in the command line is the application name for this instance of the Device Server application.
Your backup Device Server may be configured to run as backup, so the name designation may be “BACKUP”.
4. Each instance of the Device Server application on the LAN must have a unique application name. The names used are optional. You may rename your Device Server application name to suit your needs.
NOTE: If you change the application name for your Device Server, the command lines for all client applications must be changed accordingly. If not, the client applications will not be able to log into the Device Server.
CAUTION: The path name should not have spaces, otherwise quotation marks are automatically placed around the path. If quotation marks appear around the path, all command line syntax must be placed outside of the quotation marks.
For example,
Correct: C:\ADCServer\adc100nt.exe MAIN
Correct: “C:\ADC Server\adc100nt.exe” MAIN
Incorrect: “C:\ADC Server\adc100nt.exe MAIN”
Incorrect: C:\ADC Server\adc100nt.exe MAIN
IMPORTANT: While up o 16 characters are allowed, it has been discovered that only the
first 10 characters are observed. For each name of main and backup Device Servers that
share the same naming convention, one character must be unique in the first ten characters.
In the following example, while the names are the same to a point, notice that the tenth character is different:
• Main-playout Name: POD100-DSA-SVR01
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 22 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
• Backup-playout Name: POD100-DSB-SVR02
5. When finished, click OK.
Installation
Improving Transfer Speed via NetBIOS Over
TCP/IP
The Database access speed between the File Server and Air Client is slower when running on Windows XP Pro than it is on Windows 2K. The following procedure details how to improve the performance when running on Windows XP Pro.
Perform this procedure on all of the computers that will run Windows XP Pro and communicate using NetBIOS over TCP/IP in the order the information is provided below.
Create a Backup of the computer registry
If you do not know how to create this Backup, consult “How To Use Backup to Back Up Files and Folders on Your Computer in Windows XP”, (Q308422), at: http://support.microsoft.com
.
WARNING: Serious problems might occur if you modify the registry incorrectly. These
problems might require that you reinstall your operating system.
Determine which NIC is set to LANA Number 0
If you do not have LANACFG.EXE, it is available at: http://corporate.windowsupdate.microsoft.com/ .
1. Place LANACFG.EXE into a directory, double click on it, and it will self-install.
2. From the Desktop click Start > Run…, type “cmd” in the Open: field of the Run window, and then click OK.
3. Type C:\>lanacfg showlanapaths and identify which NIC is set to LANA Number 0.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 23 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Determine the IP Address of the NIC that is set to LANA Number 0
Installation
1. From the Desktop click Start > Run…, type “cmd” in the Open: field of the Run window, and then click OK.
2. Type C:\>ipconfig /all
3. Locate the name of the NIC that is set to LANA Number 0 and note the IP Address
Enter the New Registry Entry
1. From the Desktop click Start > Run…, type “regedit” in the Open: field of the Run window, and then click OK.
2. Double click on HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services,
TCP/IP, Parameters, and then Interfaces.
3. Highlight, (one at a time), an item in the Interfaces sub tree.
4. Look on the right side of the screen for the IP Address of the NIC that is set to LANA
Number 0.
5. With the correct item in the Interfaces sub tree highlighted, right click on the right side of the screen, and pop-up named New will appear.
6. Place the cursor on New, select DWORD Value, and type in TcpAckFrequency.
7. Double click on TcpAckFrequency, enter 1 into the “Value data:” window, and click OK.
8. Close the Registry Editor, disable and then re-enable this NIC, or reboot the computer.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 24 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Network Setup
Network Setup
Network Settings
This section assumes a system using XP on a Gig-E network, and that the following have already been performed: LanaCFG, set lana 0 for WINS TCP/IP on the automation NICs for all Clients and Device Servers, and that valid IP addresses and a valid Subnet are set. Make substitutions as needed for parts where your setup differs from those described in this document.
1. (If changing your network to Gig-E all TCP/IP) Open Network Connections menu, rightclick automation NIC and choose Properties.
2. Highlight TCP/IP and choose Properties…
3. Select the Advanced tab.
• Speed & Duplex settings – (Press the Advanced button) Set ALL NICs and all ports on the Switch to 1000/Full Duplex. All ports and all NICs must match, or problems will occur.
**NOTE – if any NICs DO NOT display an option for 1000/Full, then set all NICs and all
Switch ports to “Auto”**
Recommended NIC is Intel-Pro 1000. Avoid consumer-grade NICs and switches.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 25 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Network Setup
4. Select the Power Management tab.
• Power Management – Make sure Power Management NIC options are all
DISABLED, as shown below…
5. On the Internet Protocol (TCP/IP) Properties dialog, select the General tab.
• Default Gateway and DHCP – Make sure these options are left BLANK…
6. On the Local Area Connection Properties dialog, select the General tab.
• NetBEUI Unchecked (disabled) – make sure NetBEUI protocol is disabled
(unchecked) if going to an all-TCP/IP environment
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 26 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Network Setup
7. On the Advanced TCP/IP Settings dialog, select the WINS tab.
• NetBIOS over TCP/IP – Enable NetBIOS over TCP/IP should be selected, under
Properties/Advanced/WINS tab on TCP/IP NIC’s properties on all Clients and on the
Device Server
8. Set M-Node Settings – From CMD Prompt (Start/Run/CMD), check ipconfig /all to ensure you are in M (Mixed node) under node type.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 27 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Network Setup
• If MIXED node is not displayed; Go to
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services \Netbt\ Parameters.
Right Click: DhcpNodeType, choose Modify and enter value "4" and choose Decimal, exit Regedit and reboot PC afterwards.
9. TCP Ack Frequency (Registry Setting) – [for XP or 2K when using all-TCP/IP – to be done on all boxes (except the File Server)]
• Navigate to the registry (Start/Run/regedit). Expand tree as shown above, then choose your NIC based on the IP address, then right-click, New>DWORD Value.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 28 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
• Name it “TCPAckFrequency”
• Right click it, and choose Modify.
Network Setup
• Make the Value Data = 1, and choose Hexadecimal, then OK. You must restart the
PC afterwards. This needs to be done on all Clients and on the Device Server.
Windows XP (and Server 2003)
Considerations
Check to ensure that the following XP/Server 2003 Default Settings are corrected.
Internet Time setting
Make sure this is disabled on all XP and Server 2003 boxes. Go to Start/Control Panel/Date,
Time, Language and Regional Options, then choose the Internet Time tab. Uncheck the
“Automatically Sync…” option.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 29 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Network Setup
Power Saver settings
Make sure these are ALL disabled. Start Control Panel/Performance and
Maintenance/Power Options
Windows Automatic Updates
Make sure this is disabled (under Start/Control Panel/Security Center/Automatic Updates)
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 30 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Network Setup
Windows Firewall
Make sure it is DISABLED (under Start/Control Panel/Security Center/Windows Firewall)
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 31 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Clients
Network Setup
Do NOT use old versions. Do NOT use old INIs. Reboot after installing so old Windows
Registry DLL associations are refreshed.
Air Client – Do NOT use older Air Clients. v3.14.7 is the lowest you should go.
Datagram size and DLLs have been changed and problems (such as increased likelihood of Transmission List corruption) may arise from using mismatched older versions with the newer DS software. Do not copy INIs from non-version 3 Air Clients.
Media Client – Do NOT use older Media Clients. v3.10 is the lowest you should go.
DLLs have changed significantly which result in significantly improved performance.
Using older Media Clients will cause a loss of these improvements, and result in application crashes. Do NOT copy Media Client INIs, as this may introduce conflicting features that will cause significantly bad performance.
With your new MC INIs make sure these settings are changed from default, back to what you need…
SQL
Ensure the ASSEG 32-char fix steps (BELOW) are followed BEFORE you start using Media
Client. This needs to be done when all clients are down.
Steps to resolve Legacy 16-character title in Multi-Segment…
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 32 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Network Setup
1. In Enterprise Manager on MAIN-FS Expand Tree (as shown below) and navigate to
ASDB, then click on “Tables”
2. Then, choose ASSEG (in Right-side pane).
3. Right Click on ASSEG and Choose “Design Table”
4. Within Design Table Window, select the Title Length entry, and correct it to read “32”
5. CLOSE all open Air Clients and Media Clients (all things with a SQL DB connection to
File Server BEFORE you click on SAVE) SAVE changes by clicking the Disk icon.
6. Relaunch all clients.
INIs
DEVICE SERVER – v9 INIs can be used on the newer DS versions, but you will need to send them to Tech Support for analysis and possible adjustments
AIR CLIENT – Avoid copying non-v3 INIs to a v3 Air Client
MEDIA CLIENT – Never copy any pre-v3.10 Media Client INIs to v3.10
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 33 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Network Setup
IMPORTANT Device Server Configuration
Tweaks…
AO Logic
It is important that BOTH AO checkboxes be set. This will return Hard Start Logic functionality to “v9-style” behavior. This is most important at call-letter net affiliate type stations…
AP Logic
There are two changes here…
v11 registers events across Air and Protect differently
The following config adjustments help this function better. Make sure that Disk Port
Comm timeout values are high NONE LOWER THAN 30, and that on a Protect port they are higher than on the Air Side. (As shown above) Do this for all A/P pairs.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 34 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Network Setup
Only Swap one Event in A-P…
Checking this box will return to v9-like AP behavior. The new logic swaps the entire column when the AP button is hit, or a failure is sensed. Many customers prefer the new logic, this is a user-preference item.
Cue With Data Settings
Review Port: Review Ports on Media Lists will not allow for Shuttling, or Cue to, or Goto commands unless this setting is checked. This should ONLY be done on Review Ports
(not to on-air ports), unless otherwise recommended by the vendor.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 35 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Network Setup
Play to Air ports (Cue with Data): Make sure the new “Segment Play Search Path” parameters are set. These may default to all blank, and will cause problems if they are all left as “Invalid”
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 36 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Configuration
Configuration
From the Device Server Display
There are a limited number of configuration settings that can be made from the Device Server display. These are presented in this section.
The bulk of the Device Server Configuration is done using the Configuration Tool. For details
see Configuring the Device Server using the Configuration Manager .
To Configure a Server Handle
Use this procedure to configure the Global Server Number (must be unique on the network) for the main Device Server.
IMPORTANT: For correct connection of devices and clients, configure the Server handle first from the Device Server side. Once done, it can then be changed from the Configuration
Manager Tool.
1. From the Device Server main menu select File > Server Handle. The Server Number dialog is displayed.
2. Use the spin arrows to specify a Global Server Number. (This number must be unique on the network.)
3. When finished select OK.
To Configure an Alternate Handle
In an environment utilizing Cloning, an Alternate Server handle (Global Server Number) must be configured for the backup, or “clone” Device Server
Note: This option is available only when a customer has purchased a Cloning build of the
Device Server.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 37 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuration
1. From the Device Server main menu select File > Alternate Handle The Alternate
Number dialog is displayed.
2. Use the spin arrows to specify a Global Server Number. (This number must be unique on the network.)
3. When finished select OK.
To Configure TCP/IP Socket Listening Port
In an environment utilizing a Remote Air Client, this option is used to configure the Device
Server’s “listen port” (TCP/IP Socket Listen Port). This parameter allows the operator to control the TCP/IP port on which the Device Server receives a connection request from another application.
Use this procedure to configure the TCP/IP for WAN addressing.
1. From the Device Server main menu select File > TCP/IP for WAN addressing. The
TCP/IP Networking Properties dialog is displayed.
2. Use the spin arrows to specify a TCP/IP Socket Listen Port. The Default value for the
Device Server port is 10052. It’s not recommended for the user to change this value.
3. Possible reasons for changing this value are:
• The user has another service running on this port and cannot change the server listen port for this service.
• A firewall prohibits connection to this port and the setting cannot be changed for some reason.
4. When finished select OK.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 38 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configuring Devices using
Configuration Manager
About Device Types
Devices supported by the Automation system generally fall into one of two categories: media devices and non-media devices. Media devices include any devices that can be assigned to a list, have a storage collection of available media, and have the ability to cue and play media. Non-media devices are devices that perform other functions within the automation system. The following descriptions refer to the software objects within the automation system that control the actual devices.
Media Devices
Media devices may be categorized as one of two types within the Automation system: physical media devices and virtual media devices. Media devices have a number of common characteristics including:
• A storage collection of available media
• Assignment to a list (or several lists, in the case of multiple-stream devices)
• Ability to cue media
• Ability to play or record media
• One or more “media heads” (I/O streams)
Physical Media Devices Virtual Media Devices
Video Server Encoder and Decoder Ports
VTRs
Cart Machines
Switch-Only Devices
GMT Requesters
GMT Distributors
Still Stores
Character Generators
Audio Disk Carts
Serial Devices
Video Effect Devices
VChip Encoders
Demo Devices
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 39 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Physical Media Devices: Physical Media Devices are devices that physically exist within the broadcast control room and are controlled though an RS-422 serial or GPI connection. The configuration GUIs for the software objects that the automation uses to control these devices will contain a Serial Port tab where you designate the serial port the Device Server will use to communicate with the device.
Virtual Media Devices: Virtual Media Devices exist only as software objects and perform special functions within the automation system.
Switch-Only devices will switch a designated source to a designated destination on a switcher or router when their device name is placed in the ID column of a Transmission list
GMT Requesters are special GMT components that request missing media to populate a playout device.
GMT Distributors are special GMT components that distribute media from a source device at the request of a Requester.
Demo Devices simulate the behavior of certain physical media devices. Demo Devices are used primarily for testing, diagnostics and demonstration purposes.
Storage Collection of Available Media
All media devices have a storage collection of available media. This storage collection is maintained in the Device Server’s RAM as the application is running. The storage collection for a device may consist of one ID or many IDs. Mass-storage devices, such as video servers and cart machines, may have storage collections consisting of hundreds or thousands of IDs. Single-stream devices, such as VTRs, have storage collections that consist of either one ID (if a tape has been loaded into the VTR), or no IDs (if the VTR is empty).
The storage collections for mass storage devices may be viewed from the Device Storage window in either the Air Client or Media Client application.
Media Head
A media head is a software representation or abstraction of the I/O stream to or from a media device. A single-stream device, such as a VTR, has a single media head. A VTR is capable of playing out only one piece of media at a time. A multi-stream device, such as a cart machine, has as many media heads as there are VTRs available within the cart machine.
Each VTR may produce a separate audio/video stream simultaneously.
A video server encoder or decoder port is abstracted in the software as a two-headed device because of its ability to play out (or record) a continuous stream of audio and video. A decoder port may be thought of as analogous to a cart machine with two VTRs – while one
VTR is playing out, the other has the next media cued. While one of the decoder port’s media heads is playing out, the other media head has the next clip cued.
Switch-Only devices have eight media heads. A Switch-Only device may be configured with eight ID names, each representing a crosspoint on a router or switcher. All eight heads may be cued simultaneously on a list.
Non-Media Devices
Non-media devices behave differently than media devices. Non-media devices:
• Are not assigned to lists
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 40 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Are shared by all lists
• Do not have storage collections
• Cannot cue, play or record
• Do not have “media heads”
Like media devices, non-media devices may be controlled through an RS-422 serial connection. Some of the non-media devices supported by the automation system include:
Routers and switchers are the most common types of non-media devices. Routers and switchers (including master control switchers) are not assigned to lists. Instead, they are shared by all lists through the audio/video routing tables (A/V tables) configured for each device on each list.
Barcode readers: Barcode readers or barcode wands are used to identify tapes by a barcode label.
Special Device Types
A few device types supported by the Automation system do not fall into the categories of either media or non-media devices. They have some of the characteristics of media devices, but are never assigned to a list. They include the following types:
Archives, archive managers and archive systems are controlled though an Ethernet connection, rather than a point-to-point RS-422 serial connection. T
ProxyFTP Devices are software gateways the automation system uses to initiate FTP file transfers between video servers over a wide area network (WAN).
Database Update Redirectors are software devices that propagate changes to database records to events on lists running on multiple Device Servers.
NOTE: All devices, whether they are media devices, non-media devices or the special devices described above, must be assigned to a device channel in the Configured Devices
window of the Configuration Manager.
About Device Control
Devices supported by the Automation system may be controlled by one of several means: a point-to-point RS-422 serial connection, an Ethernet connection on a local area network, or by a GPI trigger.
RS-422 Control
Physical media devices are generally controlled though a point-to-point RS-422 serial connection. Different devices utilize different command protocols for their serial control.
Video server ports on all makes and models of servers are controlled using VDCP (Video
Disk Communication Protocol). VTRs are typically controlled using Sony VTR protocol.
Other devices are controlled using their manufacturer’s native command protocols.
Depending on the requirements of the command protocol, devices may be polled periodically for status updates. Video server ports, for example, are polled every frame for port status and every 8 seconds (approx.) for system status. Sony VTRs are polled every frame for an update of the current timecode position. Other devices are not polled but sent commands only when they are called upon to perform some action.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 41 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
The automation serial boards in the Device Server contain serial communication status LEDs that indicate the current status of the board. On the top edge of each serial board are banks of three LEDs corresponding to the eight RS-422 serial ports on the board (1 bank of eight
LEDS for an 8-port card, 2 banks of eight LEDs for a serial 16 card). These LEDs are only visible by removing the Device Server’s cover.
• The green LED indicates that there is data being transmitted to the device from the
Device Server.
• The yellow LED indicates that there is data being received by the Device Server from the controlled device.
• The red LED indicates that a communications error has occurred. Only a mismatch in the communication parameters configured for the device (Baud rate, parity, stop bits, data bits) will cause this LED to illuminate.
Depending on the types of devices connected to the serial board, the transmit and receive
LEDs will either solidly illuminate, or intermittently illuminate. The communications error LED will illuminate upon the first occurrence of an error and remain illuminated until normal communications are established.
For most devices supported by the Automation system, the communication parameters are not configurable within the Configuration Manager. The devices themselves must be configured to match the automation system’s requirements.
Reference the user notes for a specific device for more information about its communication parameter requirements.
8 Port Serial Card LEDs
On the rear panel of the 8-port serial card, visible from the outside of the Device Server, are three summary status LEDs. These LEDs are a summary of the eight sets of LEDs on the top edge of the board. A communications error on any one of the eight serial ports will cause this LED to illuminate.
8-port serial board (rear)
Tx Rx Rx Error
Summary status LEDs
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 42 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
16 port Serial Card LEDs
Transmit, Receive, and Error indications are available for each of the 16 ports via green, yellow, and red LEDs respectively. Global Transmit and Receive LEDs are visible thru the rear bracket.
16-port serial board (top)
Ethernet Control
Archives and archive systems are controlled through a separate Ethernet connection to the archive manager. The Device Server contains a second network interface, bound to TCP/IP protocol, which may be used to connect the Device Server to the local area network for the archive system.
Reference NOTE: Installation of Device Server v11 recommends TCP/IP on two separate
LAN’s, one for Automation Hardware Control, and one for the SQL Database interaction. It is
recommended to use TCP/IP with a 2nd NIC installed into Clients for the SQL interaction.
Archive system without bridge computer
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 43 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Archive system with bridge computer
Another optional archive control architecture involves the use of a bridge computer. The bridge computer serves as a gateway between the Device Server and the archive system. It contains two network interfaces, one bound to TCP/IP protocol for connection to the automation LAN, and one bound to TCP/IP protocol for connection to the archive system
LAN. The bridge computer runs a separate instance of the Device Server application with a single device configured: the archive device. This architecture separates the functions of the
Device Server’s devices and the archive device, and frees the TCP/IP network interface in the Device Server for other purposes.
The Automation system uses the Video Archive Communication Protocol (VACP) to control archive systems. This command protocol is widely supported by archive system manufacturers.
FTP file transfers between video servers on a wide area network may be controlled through an Ethernet connection as well. The ProxyFTP device may be configured with the IP addresses of any video servers on the WAN and initiate and control file transfers.
Device Servers are shipped with IP default addresses configured for their TCP/IP network interfaces. These IP addresses may be changed at installation time to suit the needs of your particular network.
GPI Control
Devices that cannot be controlled through a serial or Ethernet interface may be controlled using a General Purpose Interface (GPI) trigger. A GPI is a relay contact closure that provides either a high-to-low or a low-to-high transition to trigger devices that accept this type of control. A single Device Server can support up to 32 contact closures (four GPI cards), although the standard Device Server configuration includes two GPI cards. Additional GPI cards may be purchased separately.
GPI triggers are configured in the Configuration Manager Tool as Switch-Only devices.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 44 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
To Start Device Configuration
The Configuration Manager Tool is used to configure the device drivers for devices controlled by a specific Device Server.
1. Right-click on the name of the Device Server. A pop-up menu is displayed.
2. From the pop-up menu select “Configured Devices.” The Configured Devices window opens to display the devices already configured and the available device drivers.
• The left pane displays the available device channels, the Device Channel is not necessarily the same as RS-422 Serial Port to be used.
• The right pane displays the available device drivers.
• The number in parentheses next to the device type in the right pane displays the number of available device drivers for that device type.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 45 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Main Menu Options
The Configured Devices window has a number of drop-down menus available.
File menu
The File menu has the following options:
Option
Save Devices
Select to…
Write the current configuration to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
Save Configuration
Locally
Print Configuration Print the Device Server’s configuration files, if you have a printer attached to the client PC (or a network printer configured).
Caution: The configuration files can be quite large! Be sure to
have plenty of paper in your printer.
Clocking
Save the Device Server’s configuration files to an alternate location.
Only the ADC100NT.INI and LISTCONF.INI files are saved. This allows you to back up your current configuration to an alternate location (recommended). Choosing this option will open an
Explorer window and allow you to choose where to save the files.
Delete
Configure the system reference clock for the Device Server. In the window that opens (left), select the appropriate type of clock input your system will be using (SMPTE timecode, Video Sync, or the
Device Server’s internal PC clock) the correct frame rate (NTSC –
30 fps, or PAL – 25 fps), and if you are using drop-frame or nondrop-frame timecode.
Delete the selected device from its device channel.
Properties
Diagnostics
Close
Open the configuration GUI for the selected device.
Open a modeless diagnostics logging window for the selected
device. For more information see Diagnostics and
NOTE: This option is only available for certain types of devices
(GMT Distributors, Archives, ProxyFTP devices).
Close the Configured Devices window.
Edit menu
The Edit menu has the following options:
Option
Copy
Paste
Select to…
This option is not currently available. (use the keyboard shortcut
CTL+C)
This option is not currently available (use the keyboard shortcut
CTL+V)
View menu
The View menu has the following options:
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 46 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Option Select to…
Large Icons
Details
Display large icons in the left pane of the Configured Devices window.
Displays device details in the left pane of the Configured Devices window.
Device Status
Port Usage
Connections
Open the Device Status window. This window displays the realtime status of devices in use by the automation system.
Open a window that displays the devices in order of serial port number.
Open a window that displays all of the Device Servers and client applications currently logged into this Device Server
GPI Card 1 (2, 3, 4) Open a diagnostic utility for testing the GPI cards in the Device
Server. Opening the appropriate GPI card window and placing a check in a checkbox will close the relay contacts for the corresponding GPI output.
Refresh Refresh the display in the Configured Devices window.
Help menu
The Help menu has the following options:
Option
Contents**
Topic Search…**
Select to…
Display the contents of the help file.
Display a search engine for the help files.
How to Use Help** Display a Windows help file with information about how to use the help file.
About… Launch a dialog displaying version and copyright information of the currently selected Device Server.
**NOTE: These Options are currently unavailable.
To Configure the System Reference Clock
(Clocking)
Use the following procedure to configure the system reference clock for the Device Server.
1. From the ADCNT Configuration screen, right-click on the name of a listed Device Server.
A pop-up menu is displayed.
2. From the pop-up menu select “Configured Devices.” The Configured Devices window opens to display the devices already configured and the available device drivers for that
Device Server.
3. On the Configured Devices window, from the main menu select File > Clocking. The
Clocking dialog is displayed.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 47 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
4. Source: Select the appropriate type of clock input connected to your system: (SMPTE timecode, Video Sync, or the Device Server’s internal PC clock). The Source title will change to reflect the connected input.
Note: If no sources are connected the Source title will always revert to “- PC”.
Note: If running multiple Device Servers and PC Clock is selected as Source, the clocks must be manually synchronized.
IMPORTANT: The Time Code Source used (e.g. timecode generator) must be set to 24 hour format.
(See also About Device Server Clocking .)
5. Rate: Select the correct frame rate (NTSC – 30 fps, or PAL – 25 fps).
6. Drop Frame: If you are using timecode to clock the system, select whether the timecode
source is drop-frame or non-drop-frame timecode. (See also About Drop Frame / Non
• If the timecode source is Drop-Frame (DF), select Drop Frame - ON
• If the timecode source is Non Drop-Frame (NDF), select Drop Frame - OFF.
7. Round DF: Select if the round drop frame parameter if you want to force the play list timing the always be accurate with respect to Time of Day, when using NTSC drop frame
(DF).
• Without Rounded DF checked in NTSC timing mode, the drop frame follows the rule from RS-170A, in the full minute. If an event’s duration is not a full minute, the drop frame is ignored for the segment smaller than a minute.
• With Rounded DF checked in NTSC timing mode, all the event duration segments smaller than 1 minute are accumulated to a full minute and then drop frame is implemented. This makes the timing more accurate
8. Date: (Optional) The current date can be changed while the Device Server application is running. When the date drop down is selected, a calendar view is presented, with the currently set date noted. The correct date can be selected by highlighting it. If necessary, the arrow controls can be used to select the month.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 48 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
About PC Clock Date: When the Device Server application if first launched, the PC clock's date is used to determine the date. However, since the Device Server uses an external reference to maintain its clocking—typically house timecode—the point at which the day is incremented cannot be maintained using the PC clock. Therefore the date is incremented whenever the Device Server's clocking passes through 00:00:00:00. Under certain circumstances, the date may become out of sync with the actual date. This has no effect on the execution of events, but affects certain processes such as AsRuns.
9. When finished click Apply and then click OK.
About Drop Frame / Non Drop Frame Settings
The Drop Frame or Non Drop Frame settings must be correctly set across the system.
If the Drop Frame (DF) option is set to ON, and Drop Frame is received, then DF is shown in BLACK in the Device Server window and in the Client's transmission windows.
If the Drop Frame (DF) option is set to OFF, and Drop Frame is received, then DF is shown in RED in the Device Server window and in the Client's transmission windows.
If the Drop Frame (DF) option is set to ON, and Non Drop Frame is received, then NDF is shown in RED in the Device Server window and in the Client's transmission windows.
If the Drop Frame (DF) option is set to OFF, and Non Drop Frame is received, then NDF is shown in BLACK in the Device Server window and in the Client's transmission windows.
To see NDF in Black, genlock the system with Timecode, select NDF in the configuration,
AND ensure the clock being fed to the Device Server is NDF.
About Device Server Clocking
If the Source option selected in the configuration (TimeCode, SYNC or PC Clock) is available, it is shown in BLACK in the Device Server window and in the Client's transmission windows. The Source title on the Clocking Information dialog will change to reflect the connected input.
If a selected Source option is not available, then the next available option is shown in RED on the Clocking Information dialog, according to the source initially selected. These sequences are described below.
Note: If no sources are connected the Source title will always revert to “- PC”.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 49 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Sequence 1:
If TIMECODE is selected and is connected to the Device Server, it is shown in BLACK. If it is selected and is not connected, then SYNC is shown in RED - if Sync is connected. If SYNC is not connected either, then PC CLOCK is shown in RED.
Selected
Source
1
Timecode
2
Connected to Device
Server
2b
NO
Sync
3
Connected to Device
Server
3b
NO
PC Clock
2a
YES
3a
YES
Selected
Source
(Timecode)
Shown in
BLACK
Source
Shown in
RED
4
Sequence 2:
If SYNC is selected and is connected to the Device Server, it is shown in BLACK. If SYNC is selected and it is not connected, then PC CLOCK is shown in RED.
Selected
Source
1
Sync
2
Connected to Device
Server
2b
NO
PC Clock
3
2a
YES
Selected
Source
(Sync)
Shown in
BLACK
Source
Shown in
RED
To Configure GPI Control
The GPI configuration GUI provides Enhanced GPI Triggering with ADC. The primary aspects of this functionality include:
The GPI inputs extended to encompass all 32 inputs.
The ability to configure the action taken for each input.
The ability to select Single or multiple Lists for each GPI. (i.e. the equivalent of gang rolled functionality).
The default configuration matches the existing fixed functionality.
Important: This GPI configuration is independent of the GPI configuration for Switch Only devices.
IMPORTANT: For this feature to be enabled, ini files generated by versions 11.55 or higher must be utilized. Ini files created by previous versions do not contain the necessary configuration settings for correct operations. Please contact ADC Technical Support if you would like to utilize this feature.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 50 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
GPI Card Status: For information on checking the status and functionality of GPI cards
installed in the Device Server see GPI diagnostics .
To Configure Enhanced GPI Triggering
1. From the Configuration Tool’s main menu select File > GPI Input Configuration. The
GPI Input configuration screen is displayed and provides easy viewing of all GPIs at a glance.
2. On the GPI Input configuration screen configure the following parameters as required:
• Action: Specify the action for a specific GPI: The drop down menu for the Action field offers all Playlist Control Panel options. These include: Run, Ready, Play, Hold, Skip,
Tension Release, Freeze, Roll, Unthread, Protect, Add, Recue, Sub, Cut Next, Roll
Secondary, Play to Next, and Skip to Next.
• List: Select the Lists to which the GPI will issue a command. Single or multiple Lists can be selected (checked) for each GPI. A single GPI can issue a command to multiple lists- with the limitation that only a single command can be selected. This is the equivalent of gang rolled functionality.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 51 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
To configure skipping a commercial break after a GPI
(input)
ADC Device Server functionality allows skipping a commercial break after receiving a contact closure input. The following two GPI Input options are used to configure this action: “Play to
Next” and ’Skip to Next”. These options work together with the "Contact Start" option of a transmission list.
Note: The “Play to Next” and ’Skip to Next” options work together with the "Contact Start" option of a transmission list.
When a transmission list plays an up-count event and a GPI closure is received…
The Up count event rolls to the next event.
This new feature allows rolling out of the commercial break back to the next N event.
For example, in a playlist with the following events:
AU LIVE
A SPOT1
A SPOT2
A SPOT3
AUN LIVE
If a GPI is received any time in between the AU LIVE event, in any of the SPOT1, 2 or 3, the transmission list, skips all the SPOT 1, 2, 3 and mark MISSED, and starts playing the next N event - similar to having a hard started the U LIVE Event, but instead of a fixed time (AO) it is started with a GPI trigger.
In Operation
The event modifier - “N” Time-to-next event type - marks where to jump. This allows the user to define arbitrary points: segmented or non-segments, up-count or not and so on.
Time-to-next event must be in look ahead.
The events that are skipped when receiving a GPI input are marked as MISSED.
Skip-to-next mark all events between current and time-to-next as MISSED. The Current event is skipped.
Play-to-next marks all events between current and time-to-next as MISSED. The Current event will finish playing and then time-to-next event will start playing.
If current event is up-count event type, the Play-to-next signal is processed as Skip-tonext.
If time-to-next event is not cued, the playlist tries to thread and cue it.
If any error occurs (N event is absent or cannot be threaded), it is displayed on client side and the playlist will continue playing events in normal order not skipping any event.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 52 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Note: This functionality applies only to a GPI input. It does not apply to a function available on the Air Client Software/Hardware control panel. That is, this functionality is not available on the Air Client software panel, nor the Air Client hardware panel.
To Configure this functionality
1. From the Configuration Tool’s main menu select File > GPI Input Configuration. The
GPI Input configuration screen is displayed and provides easy viewing of all GPIs at a glance.
2. On the GPI Input configuration screen configure the following parameters as required:
• Action: Specify the action for a specific GPI: The drop down menu for the Action field offers all Playlist Control Panel options. For this enhancement select “Play to Next” or’ Skip top Next”.
Skip-to-next marks all events between current and time-to-next as MISSED. The
Current event is skipped.
Play-to-next marks all events between current and time-to-next as MISSED. The
Current event will finish playing and then time-to-next event will start playing.
If the current event is an up-count event type, the Play-to-next signal is processed as Skip-to-next.
• List: Select the Lists to which the GPI will issue a command. Single or multiple Lists can be selected (checked) for each GPI. A single GPI can issue a command to multiple lists- with the limitation that only a single command can be selected. This is the equivalent of gang rolled functionality.
To Assign a Device to a Device Channel
1. Display Device Drivers: To display the specific device driver, click on the
⊞ symbol next to a device type. This expands the tree to display the specific device drivers for that device that are available in the system. (e.g. VTRs expanded would produce Sony,
Ampex, etc.)
2. Select the specific device in the right pane with the mouse, and then drag-and-drop the device on a device channel in the left pane. The number to the left of the device in parentheses decrements by one to indicate one less device driver is available.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 53 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Once a device has been assigned to a device channel, it may be configured for specific options.
(Option) To Remove a Device from a Device Channel
Use the following procedure to remove a device from a device channel.
1. Select the device you wish to remove.
2. Right-click on the entry and from the popup menu select Remove (or use the keyboard
DEL key). The device is removed from the device channel and is made available for assignments to another channel.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 54 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Video Disk Configuration (General)
The following is an example video disk configuration. Your device may have slightly different options and the selection of configuration tabs may be different for that device. If necessary, refer to the User Notes for your device for complete details on how to configure it.
IMPORTANT NEXIO NOTE: The Nexio/VR device driver is currently under development.
Support for the Nexio/VR device will be addressed in a future release.
DTP Insertion Note: The configuration required for the DTP Insertion video disk differs
radically from all other supported video disks. For details see: Configure a DTP Insertion
To Configure a Video Disk
1. Under Video Disk Servers in the Available pane (right pane), select a device and drag-n-
drop it to the Configured Pane (left pane). For details on assigning a device see: To
Assign a Device to a Device Channel .
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the Video Disk device in the left pane, right-click and from the popup menu select
Properties. The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select the General tab. Available options may differ depending on the device selected.
Configure the following parameters as required:
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 55 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Device Name: The device name identifies the disk port. The default name for standard video disks is DISK. Enter the name by using up to 16 characters. When an event is threaded, an extra character - the head number - is added to the end of the name.
The name is also used to identify the disk port used to execute secondary data events. If a disk port’s name matches the ID of a secondary data event, the event is executed. Such secondary data events include those that delete spots, transfer an archived spot, delete protect spots, or undelete protect spots.
• ID Match Name: The ID match name identifies the disk port in secondary events, where the device name is played in the ID field. The default name is the same name you selected as the device name. Enter the name by using up to four characters.
When an event is threaded, a fifth character - the head number - is added to the name.
The name is also used to identify the disk port used to execute secondary data events. If a disk port’s name matches the ID of a secondary data event, the event is executed. Such secondary data events include those that delete spots, transfer an archived spot, delete protect spots, or undelete protect spots.
• Options.
Stop Disk Play/Record on Init: A stop command is issued to the disk whenever the Device Server is started or the port is re-initialized. When disabled, the
Device Server connects to the video disk port if it can. If it cannot, the port must manually be re-initialized on the Device Server (under System, Diagnostics).
When disabled, it is the operator’s responsibility to check the port status in the
Device Status Window and the IDs in the Device Storage Window and reinitialize if required. Default is enabled (checked).
NOTE: Some sites prefer to DISABLE on ports the play to Air, and also Auto
Record List ports.
Back to Back Play: When performing back to back play of short spots (for example, five second spots), the preroll and postroll of the lists should be kept as short as possible. The postroll time must be compatible with the VTR, switcher and effect minimum postroll times. Also, the ADC Device Server allows a video disk that has started cueing to continue cueing during preroll as long as cueing finishes before playout time. If disabled, the second head status line never threads (staying offline). This option should typically be left enabled. Default is enabled (checked).
Update Event Durations From Disk: The ADC Device Server reads from the video disk the duration of every item in the disk. This duration is displayed at the
Device Storage window. The ADC Device Server shortens the duration of any event that is longer than what is reported from the disk. This feature is not typically needed for normal on-air operations since the automation database has the exact durations. Default is disabled (unchecked).
Report Spot Shorter than Scheduled: Becomes available when “Update Event
Durations From Disk” is selected. Check to enable report.
Reset Storage on Reinit: Check to reset the storage when the device is reinitialized.
Checked: Destroy the old storage collection and recollect storage from disk whenever the disk driver reconnects with the video disk from a lost communication.
Unchecked: Continue to use the old storage collection after the reconnection.
Recommendation: Uncheck if the disk lost communication frequently.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 56 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Disable heart beat checking for device air protection: Enable/Disable heartbeat check.
Checked: The Driver will not check if the device lost heat beat.
Unchecked: The driver will sense the lost heat beat error and try to reset and reconnect with the device.
Recommendation: Uncheck unless the device can’t reply heat beat checking query command from driver.
4. Select the Serial Port tab. Use this tab to connect the driver to the ADC’s serial COM port that the device is physically connected. Click the down arrow button to select from a list of available serial ports.
5. Select the Ports tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 57 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Video Input Port In Disk. (Default: 1, Range: No Port (0) to 127) The video port number in the video disk that the automation serial board port logs into. The video input port number you enter depends on the disk system being used. Input ports are used for recording. Typically, only one video port is assigned to a list. A value of ‘No
Port’ closes the video port and makes it available to another communications port.
This must be configured for a video port number that is available in the video disk for the disk to record. ‘No Port’ in the port number: it cannot record and the status is
OFFLINE. The disk port should only be configured to ‘No Port’ if the port is not to be used for recording, or you want to CLOSE the port so another controller’s communication port can take control of that video port number. Normally this should have the same value as the VIDEO OUTPUT PORT if not zero (No Port).
• Video Output Port In Disk. (Default: 1, Range: No Port (0) to 127) The video output port is typically the same as the input port. The output board is used for playout. This is the video port number in the video disk that the automation serial board port logs into. Typically, only one video port is assigned to a list. A value of 0 closes the video port and makes it available to another communications port.
This is normally a unique number for each video disk to specify which video port to use for playing. This must be configured for a video port number that is available in the video disk for the disk to play. A zero in the port number specifies no port
(disabling play). The status is OFFLINE if configured to zero. The disk port should only be configured to zero if the port is not to be used for playing, or to CLOSE the port so another controller’s communication port can take control of that video port number. Normally, this should have the same value as the VIDEO INPUT PORT if not zero.
NOTE: A single disk port can only play or record at a given time (not both). ADC changes from input to output port and back when required, but will not change until it has finished its current task and is in STANDBY. For example it can be scheduled to record a news feed for an hour, then play that news program the next hour on the
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 58 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
same port providing there is at least 10 seconds (disk dependent) from the time it ends recording to the time it is scheduled to begin play out. If play out must begin sooner, or during recording, then a different disk port of that video disk must be used
to play out the news that is recorded.
• Close Disk Port When Not In Use. The default is disabled. This feature is rarely used. It should only be enabled when the disk port is used by different controllers at different times (for example the ADC/NT and a Turbo product). A television station might use it so the day shift plays out from the disk port and the night shift records new material into the port (however, this is limiting because if a spot needs to be recorded into the disk during the day, the port is busy for playout).
• Disk To Use As Storage Port. Select a disk to be used for storing clips. Typically this will be the same disk being configured. Default is Self.
• Additional Port Of Same Disk. Default: None (not used). This device parameter is only used when you want to assign two video ports from the same video disk to the same play list.
There are only two situations where this is useful: (1) You want to do mixed effects from one piece of material in the disk to the next piece of material in the disk. (2) You want to play spots smaller than Preroll + Postroll + 10 frames + disk cue time. In situation #1 you must have two different video ports from the same disk because you need two streams of simultaneous video do the mix. In situation #2 two ports can allow the next port to get cued and ready simultaneously thus allowing a very short spot to play and the next event will be cued on the other port.
To configure two video disk ports from the same disk to the same list:
• Assign both disk ports to the list as primary ports (air disk ports) not as protect ports.
• In this parameter of each of the two ports, select the name of the disk of the other ports. This allows the list to control both ports, but the first port will think it can play all the material.
When the list asks the first port to cue the events on the list, the first disk port, knowing it has a pointer to an additional disk port, only threads every other event. It then passes the other events to the additional port for threading.
• Use the same procedure to configure two protect disks, each protecting one of the air disk ports. Thus, when loading a playlist with four disk events and pressing program run you will see:
Additional ports of same video disk
EVENT#
1
2
3
4
DEVICE
Disk1:1
Disk2:1
Disk1:2
Disk2:2
STATUS
Cued
Cued
Stop
Stop
PROTECT
DEVICE
Disk 3:1
Disk4:1
Disk3:2
Disk4:2
PROTECT
STATUS
Cued
Cued
Stop
Stop
ID
SPTA
SPTB
SPTC
SPTC
When configured this way, any editing within or before any threaded and cued events, and all events below the edit point, are ejected and rethreaded in the proper order. This assures that playout toggles ports for every other event.
6. Select the Prerolls/Postrolls tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 59 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Instant Prerolls.
The Instant feature is designed for coming out of a live or upcounting event as fast as possible when the next event has a near instant preroll. If you are using a master control switcher, the preroll must not be shorter than the shortest preroll supported by the switcher.
Use Instant Prerolls. This function has a default of zero seconds, four frames.
The values can range from four frames to 59 seconds. Instant Preroll provides instant play/skip capability to the device. When enabled, Instant Play Preroll is activated by pressing the Instant button or Roll Now button on the control panel.
The preroll must be set to at least the minimum switcher preroll or the disk port may start playing before the switcher switches.
The preroll also must be set to at least four frames greater than the Disk Preroll and Number of Frames to Send Play Early. Four frames is the minimum preroll allowed by ADC. If not configured properly, the list may stop, or Roll Now may not work as expected, but take a longer time than desired.
If Instant Preroll is set longer than the List Preroll, instant play is actually a delayed play. ADC operations rely on list preroll settings configured through the
Options menu, in Configure Lists.
• Device Postroll.
Use Postroll. Default: Disabled, zero seconds, four frames. Range: four frames to 59 seconds. When enabled, this settings overrides other configured postroll settings. Device postroll, if enabled, must be set to at least 4 frames.
This feature allows the list to use one postroll for VTRs, cart machines, and other devices, and a different postroll for video disks. The Device Postroll can be longer or shorter than the list postroll. Its main purpose is to clear out the disk
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 60 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager status line quickly after the disk stops playing, so the status line can be loaded with the next event to cue. This allows small spots to be played back to back.
If the Device Postroll was set to a larger value, and the disk had over recorded the ID compared to the play duration, the disk would continue to play for the post roll duration if on air play switched to another device. This would permit mix effects during the post roll of the disk device into the play out from another device.
Seconds. Select a value of up to 59 seconds.
Frames. Select a value of at least 4 frames.
NOTE: The Seconds and Frames values have no effect unless the Use Postroll box
is enabled (checked).
• Prerolls.
Disk Prerolls. This has a default of zero seconds. The values can range from 4 to 300 frames. (Four frames is the minimum preroll allowed.) This feature should not be used unless specified by the disk manufacturer or Automation (refer to device-specific information).
Preroll is sent to the video disk port when initialized or configured. All play and record commands are executed at a given time after receipt of the command
Disk preroll provides the preroll the disk requires for frame-accurate playout. It gives the disk more time to get the required video on air on the correct frame.
Disk preroll must be set to the same value as Number of Frames to Send Play
Early (discussed below).
Frames To Send Play Early. The default is 0 and should not need to be changed unless the disk has a fixed latency of greater than one frame for the play command. This setting determines when (number of frames) the video disk port should receive the play command before playout is performed. A setting of zero sends the play command to the disk port the frame before the command is performed.
The setting should never be greater than four frames less than List Preroll or
Instant Preroll or the disk port will not play and the list will stop. If Disk Prerolls is used, the Frames setting should be the same value unless a frame or two of switcher timing compensation is required.
Frames To Send Record Early. The default is 0 and should not need to be changed unless the disk has a fixed latency of greater than one frame for the play command. This setting determines when (number of frames) the video disk port should receive the record command before recording is performed. A setting of zero sends the record command to the disk port the frame before the command is performed.
The setting should never be greater than four frames less than List Preroll or
Instant Preroll or the disk port will not play and the list will stop. If Disk Prerolls is used, the Frames setting should be the same value unless a frame or two of switcher timing compensation is required.
Note: During a crash record operation only to a Video Disk, Media Client ignores values of “# of frames to record early” (Config Tool > Video Disk Configuration >
Prerolls/Postrolls tab > Frames to Send Record Early), and restores the value after the crash record.
• Never Send DiskPreRoll Command: (Recommend only for Nexio) Enable/Disable sending of Disk preroll command.
Checked: The disk driver never sends the Diskpreroll Command to disk.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 61 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Unchecked: The disk driver sends the Diskpreroll command to the video disk when initialized.
Recommendation: Check only when you know the disk doesn’t support the disk
PreRoll Command.
sQ Server Note: When controlling an ISA system via the Quantel VDCP Interface,
check this parameter as the sQ Server does not require and does not support disk
preroll.
• Always Send Preroll on Open: (Recommend only for Omneon) Enable
(check)/Disable (uncheck) issuing a Preroll after opening a port.
(Default) When Disabled (unchecked), the existing behavior is unchanged. i.e.
The existing Preroll is issued before the port open.
When enabled (checked), a Preroll is issued immediately after every Port Open, regardless of the reason for the open, but before any other commands to the opened port.
Note: It is anticipated that this new behavior is transparent in all cases, as issuing a
Preroll immediately after open should have no other effect.
7. Select the Storage tab.
Configure the following parameters as required:
• Automatically Delete From Disk When Full. The automation system ensures that the specified amount of free disk space is maintained. Material is deleted from the disk automatically, based on a first-entered, last-played formula. Example:
A disk has 1000 spots on it, numbered 1 through 1000. Spot 23 is played, at which point it is assigned a new number of 1001. Spot 65 is then played, at which point it is assigned a new number of 1002. Each time a spot is played, it is incremented using this same sequence. As a result, spots that have been on the disk the longest without ever being played have the lowest numbers, and are deleted first. If material must be deleted on the disk, the lowest number would be deleted first, then the second lowest number, then the third lowest, etc. Default is disabled (unchecked).
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 62 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Spots registered in the Lookahead are never automatically deleted.
• Disk Space to Keep Free (Mins). The default is 10 minutes. The range is from 0 to
32,000 minutes. This parameter attempts to keep the disk with at least the entered number of minutes of disk space free. This prevents trying to record something larger than the available amount of time, then having to delete the unfinished (truncated) item. For playout, the default value is typically used. Set this to the size of the largest
ID you expect to record if Automatically Delete From Disk When Full is enabled. This parameter should be used in time delay and record event applications. It is not recommended to set the value below four minutes (since all space available numbers are estimates due to variable rates of compression on different video images). This parameter has no effect unless Automatically Delete From Disk When Full is enabled.
• Delete IDs After Play. Deletes a played event from the video disk. This is typically only enabled for testing or when recording for a one-time playout. Default is disabled
(unchecked).
For testing, this allows a short list of spots, repeated continuously, to record or cache.
The spots are then continuously deleted. For actual on-air playout, the setting automatically deletes from a disk when it is full. This keeps the disk filled with the most current spots to reduce multiple recording or caching of a spot repeated more than once. This function only deletes a spot if it is completely played out, and was recorded by this port.
• Prevents ‘In-Use’ Clips from Being Deleted: Enable/Disable deletion of In-Use clips.
Checked: (Recommended) Users can’t delete an ID when it is inside the lookahead of a list from any clients.
Unchecked: Users can delete any event from the disk storage collection window of clients.
NOTE: When “Prevents ‘In-Use’ Clips from Being Deleted” is enabled and the “Allow
Delete IDs from Storage Window” is also enabled in the “Storage Options” tab of the
Air Client, attempting to delete in-use clips in the Device Storage Window results in a
confirmation popup.
Clicking OK on the Confirm message will not result in these in-use clips being deleted. This applies to in-use clips that are not Protected and are not in a CUED state.
• Query ID Status When Needed by a List: Enable/Disable suppression of 3x.16 messages related to missing events – both segmented and non-segmented material.
QueryIDs are issued only for those permutations enabled (ID, ID+1, ID+2), and if multiple modifier values are enabled, they are issued in the same order as configured.
Enable/Check (Default) to issue the 3x.16 commands. Depending on the video file server used, its configuration, and operational parameters, these commands may be unnecessary and may cause excessive serial traffic or logging.
Disable/Uncheck to suppress the 3x.16 messages for missing events.
• DemoDisk Storage: (Available for Demo Disk Selections) Demo Disk’s storage size can be changed by 2 parameters: Demodisk Leading Word and Number of IDs. The
ID’s in demodisk are combined by these two parts.
For example, using the leading word of “Demo” and number “99999”, allows 99,999
IDs in demodisk’s storage from Demo00001 to Demo99999.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 63 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
8. Select the Recording tab.
Configure the following parameters as required:
Any combination of record qualifiers may be used, or they all may be disabled. The recording qualifiers are effective on record events and caching, and Secondary Record
Device Events. This is useful in caching to record only IDs that are commercials as they are short and not program material (program material normally has a segment number).
Default is disabled.
• Allow Recording.
Recording of Record Events. Allows recording of record events or other types of recordings. When disabled, the disk port will not record. Recording with segment play enabled is equivalent to performing an insert edit or assemble record, depending on the SOM (if the video disk server supports this function).
Back to Back Recording. For secondary record events, this parameter must be disabled. This option should only be enabled if your video disk server supports this function.
This setting is useful when setting up a disk to perform continuous time delay applications. To set this up, enable this parameter and then place a sequence of continuous IDs on a record list. The video disk records every frame into the proper ID. The record list can be made into a playlist and played out. The play output is exactly the same as what was recorded.
This function affects the play out and recording list function and the disk driver function; no other function is affected. When enabled, it:
- Allows the recording port to support back to back recording between different recording IDs.
- The leading Switch Only Device will allow the back to back play between the different play IDs.
- The back to back recording function records single-file-multi-segment file to single file in video disk and the Air Client updates the database after each segment has finished the record.
- The recording operation to video disk will not stop until the recording of all segments is finished.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 64 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
NOTE: Refer to the documentation on your video disk device to verify it supports back-to-back recording.
Record Only No Playout. When enabled, this port will not play any material.
This was added to the software so a port can be assigned to a playlist for recording, with a separate port assigned for playout. Without enabling this parameter, if one port goes down, the other port will try to do both (record and playout). Since it cannot do both at the same time, the list will not work properly.
Default is disabled.
• Disable Recording With Segments. If enabled, the disk port will not record any event with a segment number in it. Default is disabled (unchecked).
• Record Only Segments. Record only events with non-blank segment fields. If not enabled, the disk port will not record any event with a segment number in it.
• Prevent Recordings Greater Than (Mins). Check to enable, then specify a maximum length (in minutes) for any recording. When this parameter is enabled, the disk port will not record any ID whose duration is greater than the number of minutes specified in parameter.
• Prevent Recordings Less Than (Mins). Check to enable, then specify a minimum length (in minutes) for any recording. When this parameter is enabled, the disk port will not record any ID whose duration is less than the number of minutes specified in parameter.
• Only Record Events with ID in. Check to enable, then specify the event range ’--to--
‘ limits. When enabled, the disk will only record IDs whose first character is between or equal to the limits. Numeric and alphabetic entries (upper and lower case ) are permitted.
For example: If only IDs starting with a ’9’ are to be recorded, enter a ’9’ in both boxes. To record only IDs whose first character of the ID is from ’0’ to ’5’ inclusive, place ’0’ and ’5’ in the two parameters. ’A’ to ’Z’ and ’a’ to ’z’ are permitted, and uppercase letters are sorted before lower case letters, and uppercase letters are sorted after numbers.
The ID qualifier is useful where some IDs are recorded and others not, and the
Duration and Segment qualifiers cannot distinguish between them. The traffic system can designate a certain range of IDs that will be cached or recorded only.
9. Select Qualifiers tab. Use this tab to set playing event qualifiers.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 65 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
Any combination of qualifiers may be used, or they all may be disabled.
• Playing Event Qualifiers.
Event qualifier means playlist events must satisfy the selected qualifier before being allowed to play out through this VDCP port. If they do not pass the qualifier check, the event is not registered to this port, and is not allowed to play.
Primary Event: Select (check) this option, if this VDCP disk port allows primary events to play.
Deselect (uncheck) this option, if a playlist has both Primary and Secondary events, and the user wants to only register Secondary to this VDCP disk port, and register Primary events to other devices, such as VTR.
Secondary event (without Data Event): Select (check) this option, if this VDCP disk port allows secondary events to play.
Deselect (uncheck) this option, if a playlist has both Primary and Secondary events, and the user wants to only register Primary to this VDCP disk port, and register Secondary events to other devices, such as VTR.
• Segment Qualifiers: Segment qualifiers allow playback of IDs with Segment numbers and/or IDs without segment numbers. This configuration allows the operator to define:
If the video disk port is able to play both segmented and non-segmented events
If the video disk port will only play events with segments
If the video disk port will only play events with no value (blank) in the segment column
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 66 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Play only events with segments: (Default: disabled/unchecked) When enabled
(checked) this video disk port will ignore any event that does not have a value in the Segment Column. Enabling this qualifier causes the video disk port to only play events where there is a value found in the Segment Column.
For example, the following image illustrates a playlist with values in the Segment
Column (shown highlighted):
Play only events without segments: (Default: disabled/unchecked) When enabled (checked) the video disk port ignores any event with a value placed in the Segment Column. In effect enabling this qualifier causes the video disk port to only play events where there is no value in the Segment Column,
For example, the following image illustrates a playlist with no values in the
Segment Column (shown highlighted):
Segment Qualifier Enabling Rules
Only one of the Segment qualifiers can be in an enabled (checked) state.
After enabling (checking) one of the qualifiers if the user tries to enable (check) the qualifier that is in a disabled (unchecked) state, this action automatically causes the enabled (checked) qualifier to become disabled (unchecked).
However, after enabling (checking) a qualifier it is possible for the user to disable
(uncheck) this qualifier so that both qualifiers are in a disabled (unchecked) state, thus returning the system to its default configuration.
• Duration Range.
If a duration qualifier is enabled then the disk port will not play any ID whose duration is greater (or less) than the number of minutes specified in parameter.
No Events Greater Than (Mins): Check to enable, then specify number of minutes in the associated number field (use spin arrows to increment / decrement).
No Events Less Than (Mins): Check to enable, then specify number of minutes in the associated number field (use spin arrows to increment / decrement).
• ID Range.
If the ID qualifier is enabled, then the disk will only play ID’s whose first character is between or equal to the ’--to--‘ limits.
This qualifier is useful where some ID’s are to be played and others not, and the
Duration qualifier cannot distinguish between them.
Only Events with ID Between: Check to enable. Then specify range in the associated number field.
-- to --: Alphanumeric entry. specify range.
For example: If only IDs starting with a ’9’ are to be played, enter a ’9’ in both boxes. To play only IDs whose first character of the ID is from ’0’ to ’5’ inclusive, place ’0’ and ’5’ in the two parameters. ’A’ to ’Z’ and ’a’ to ’z’ are permitted, and uppercase letters are sorted before lower case letters, and uppercase letters are sorted after numbers.
10. Select Segments tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 67 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Enable Cue with Data: Enable this function only if your video disk server supports this function.
This is only enabled to play a part of an ID. It is similar to playing segments of a program or show.
When enabled, the disk port uses the event’s SOM (start of message) to play or record individual segments of program material. For example, enable this setting if you want to play a program or news item in several parts. However, the different video disk devices implement this feature in various ways. For further details, refer to the documentation on your video disk device. Default is disabled
(unchecked).
This feature must be enabled to play or record individual segments of program material.
(The HP AMS can only start at the beginning of the file for play and record. The
Profile can start play or insert recording at any time into the file.) If the
SEGMENT field in an event is not blank then the video disk can only play or record that event, if this option is enabled. If you always want to start at the beginning of every ID, or your disk does not support segments, then do not enable this feature.
• Modify Segment IDs (# of Characters). Up to two characters can be added to IDs.
Useful for multi-segment recording, this option causes the ID on a video disk to be appended with either 1 or 2 characters to distinguish the segments.
If you never use more than 9 segments in any ID, select 1 character (which allows up to 9 segments). If you select 2 characters here, a maximum of 99 segments is allowed. Valid numbers are 0, 1, and 2. Default is 0.
Example: If Modify Segment IDs (# of Characters) were set to 2, a 3-segment ID titled “spot” would reside on the video disk as “spot01,” “spot02,” and “spot03.” If the
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 68 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager disk has a maximum of 32 characters allowed for an ID, the ID is truncated on the disk if the ID takes up 30 or more characters (2 characters are lost to allow for the 2 segment characters).
• Segment Play Search path: Use this parameter to specify segmented program ID search through various settings of the Modify ID parameter. For media play out, the first valid setting is used. The list permits each setting to be individually enabled or disabled, and for the order in which they are checked to be defined. Populating the search path with a single entry matching the fixed settings allows operation identical to current behavior.
Select a listed segment then use the associated buttons to arrange:
Up / Down: Use these buttons to position the segment in the list.
Enable: Use this buttons to enable a selected segment.
Disable: Becomes active when Enable is selected. Use this button to disable a selected segment.
Cue: Becomes active when Enable is selected.
Cue with Data: Becomes active when Cue is selected
• Reject Blank SOM: Check to enable rejection of segments with blank SOM.
11. Select Spots tab.
Configure the following parameters as required:
• Reject Blank SOM: Check to enable rejection of single spots with blank SOM.
• Cue Non-Segmented material with Data: Check to enable. This must be enabled to allow proper review of Multi-Segmented material. This is because in the Media Client,
Segments are treated as Single-Spots for Review purpose.
12. Select E to E tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 69 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Send Disk EE Mode Commands. (Default: disabled) These commands are only supported on certain video disks. Do not enable unless you are sure they are supported in your version.
When enabled, ADC NT sends EE commands to the disk when it starts and stops playing.
This effectively makes the video disk a video player and insert switcher if the input to the port is a primary video feed, and the video disk is controlled by a ‘break away’ list.
Once the video disk receives an EE command, it enters an EE controlled mode where it no longer controls the internal switcher. If EE commands are then disabled, the video disk software must be stopped and restarted so it will control the internal switcher automatically again.
• Frames to Send EE On Early. (Default: 2) Enter the number of frames that the EE
ON command should be sent early. This box is ignored unless the Send Disk EE
Mode Commands box is enabled (checked).
• Frames to Send EE Off Early. (Default: 3) Enter the number of frames that the EE
OFF command should be sent early. This box is ignored unless the Send Disk EE
Mode Commands box is enabled (checked).
13. Select Reporting tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 70 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Disk Specific Warnings. Displays diagnostic messages used for software development and debugging. If a specific problem or suspected bug is noticed, turn on this setting. If a disk diagnostic message appears when the problem occurs, the diagnostic code associated with the message should be reported to Automation
Support. Default is disabled (unchecked).
• Items Automatically Deleted or Recorded. This setting should only be used to verify or test that the disk is functioning properly. When enabled, diagnostic messages are only written to the error log at a client computer (if the client is configured to write error log files) when a spot is deleted, recorded or played from this disk port. Default is disabled (unchecked).
14. Select Disk Status tab.
The Disk Status tab is informational only. No user-configurable settings are available in this tab.
Click the Refresh tab to update the displayed information.
IMPORTANT: For some video disks, such as the Nexio, the total clips reported in Config
Tool (Disk Status) may be higher than what is reported in Air Client due to the inclusion of
certain hidden or system files.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 71 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
15. Select Diagnostics tab.
Configure the following parameters as required:
• Diagnostics.
Reinitialize: Click to reinitialize the device/port. Executing this action and confirming will stop any play out or recording in progress, clear the disk status lines, clear all spots in the Device Storage Window, then initialize the disk port.
This should only be done if the disk is not recording or playing on air, and it is felt something is hung up in the software.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 72 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
This may need to be done if a videodisk communications program is brought down, then back up, and it does not signal the ADC controller that it was rebooted.
ReVerify: Click to reverify all ID’s from the video disk. This action removes all
ID’s from the Device Storage Window that are not in any list look ahead, (no ‘*’ in the USED column) then reads all ID’s from the video disk and puts them into the
Device Storage Window.
This should only be used if you suspect the Device Storage Window does not have the correct ID’s in it (they should only be what is in the disk or to be recorded or transferred in to the disk).
Before doing this note the ID count and any suspected ID’s or lack of ID’s, and note if after the ID List is re-read if the ID’s in the Device Storage Window are different.
Using this function reduces the efficiency of the Auto Delete (Device Parameter
Delete When Full). It will still delete as needed, but the history of what spots were most recently used will be lost.
Reverify affects the most recently used information in the following way:
The ID list sort mode is always set to FIFO. If the disk follows VDCP protocol, when selecting to Re-verify IDs against the disk storage, the video disk gives the
IDs following the rule that, oldest items are listed first, newest items are listed last. This maintains the usage frequency sequence.
If the video disk doesn’t follow VDCP, the usage frequency sequence will be lost.
Make Input Port: Specify the port as a port for recording material. This should never be needed as the software automatically changes the port type for record or play out as needed. This option allows you to manually force the port to be an input port, overriding the default configuration.
Make Output Port: Specify the port as a port for playing out material. This should never be needed as the software automatically changes the port type for record or play out as needed. This option allows you to manually force the port to be an output port, overriding the default configuration.
• Port Status.
Off Line / On Line: Manually take the port offline and online. Click the appropriate tab (Off Line or On Line).
• Trace Status: Allows tracing of the VDCP communications. This gives more intelligent filtering of the data logged in order to limit the amount data produced in the log.
16. Apply the Configuration Changes: When changes are made to a device’s configuration, the Apply button on the configuration GUI becomes active. Click the Apply button to immediately apply that configuration change to the system configuration held in random access memory by the Device Server.
NOTE: Apply does not write the configuration change to the Device Server’s configuration files. This can only be done by using the Save Devices option on the
Configured Devices window’s File menu.
17. Save the Configuration: From the Configured Devices window select File> Save
Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
• Attempting to close the Configured Devices window without first saving any configuration changes, results in the Configuration Manager prompting to save the
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 73 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager changes on the Device Server. Accepting this prompt writes the configuration changes to the Device Server’s configuration files as well.
Configure a DTP Insertion Video Disk
The DTP Insertion video disk driver utilizes secondary events to pass low level commands to the DTP and to handle spot insertion. This driver:
Controls the DTP via primary events, with an event for each inserted spot representing the playing and splicing of the clip.
Supports a switch-only like behavior, supporting upcounts, to represent a stream source to which splices would be made.
Supports storage validation in order to register events on a list.
This driver only supports clip cuing and playing, splicing, and storage functions. To access other DTP functions, such as logos and crawls, use the existing DTP driver. It is possible to use both drivers simultaneously to control a single DTP, and to use both drivers on a single list if desired.
To Configure a DTP Insertion Video Disk
Use the following procedure to configure a DTP Insertion Video Disk.
1. Under Video Disk Servers in the Available pane (right pane), select the LEITCH DTP
Insertion device and drag-n-drop it to the Configured Pane (left pane). For details on
assigning a device see: To Assign a Device to a Device Channel .
Once the device has been assigned to a device channel, it may be configured for specific options.
2. Select the device in the left pane, right-click and from the popup menu select Properties.
The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the tabs.
3. Select the General tab. Use this tab to define Driver name, ID Match name and DTP client ID.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 74 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Device Name: Specify the name of the DTP Insertion device
• Client ID: This must be unique in different instances of driver which communicate with a single DTP. It’s used as a cookie in commands sent to the DTP and it exists in responses from the DTP. It allows the system to determine which instance of the driver should process a message from the DTP.
• Frames to Send Splice Early: This parameter is used in pair with the Splice preroll time of the output program. The driver sends the Splice command to the DTP before the Splice preroll time plus this parameter value. By default the value is “0”, so the
Splice is sent before the Splice preroll time only.
4. Select the Socket tab. Use this tab to set Host IP address of DTP, RCS port number and enable logging. The default state for logging is disabled. Log Setting is enabled only for debug purposes or if a customer has any problem using driver.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 75 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
5. Select the Prerolls tab. Use this tab to configure instant preroll and postroll values for the
DTP insertion driver. Instant preroll and postroll values are applied to all driver heads.
Configure the following parameters as required:
• Instant Prerolls.
The Instant feature is designed for coming out of a live or upcounting event as fast as possible when the next event has a near instant preroll. If you are using a master control switcher, the preroll must not be shorter than the shortest preroll supported by the switcher.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 76 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Use Instant Prerolls. This function has a default of zero seconds, four frames.
The values can range from four frames to 59 seconds. Instant Preroll provides instant play/skip capability to the device. When enabled, Instant Play Preroll is activated by pressing the Instant button or Roll Now button on the control panel.
The preroll must be set to at least the minimum switcher preroll or the disk port may start playing before the switcher switches.
The preroll also must be set to at least four frames greater than the Disk Preroll and Number of Frames to Send Play Early. Four frames is the minimum preroll allowed by ADC. If not configured properly, the list may stop, or Roll Now may not work as expected, but take a longer time than desired.
If Instant Preroll is set longer than the List Preroll, instant play is actually a delayed play. ADC operations rely on list preroll settings configured through the
Options menu, in Configure Lists.
• Device Postroll.
Use Postroll. Default: Disabled, zero seconds, four frames. Range: four frames to 59 seconds. When enabled, this settings overrides other configured postroll settings. Device postroll, if enabled, must be set to at least 4 frames.
This feature allows the list to use one postroll for VTRs, cart machines, and other devices, and a different postroll for video disks. The Device Postroll can be longer or shorter than the list postroll. Its main purpose is to clear out the disk status line quickly after the disk stops playing, so the status line can be loaded with the next event to cue. This allows small spots to be played back to back.
If the Device Postroll was set to a larger value, and the disk had over recorded the ID compared to the play duration, the disk would continue to play for the post roll duration if on air play switched to another device. This would permit mix effects during the post roll of the disk device into the play out from another device.
Seconds. Select a value of up to 59 seconds.
Frames. Select a value of at least 4 frames.
NOTE: The Seconds and Frames values have no effect unless the Use Postroll box
is enabled (checked).
6. Select the Streams tab. Use this tab to assign configured output on DTP to any of driver streams.
The process of assigning programs to streams is similar to the process of assigning devices to channels. The left list pane contains all streams and the output programs assigned to them. The right list pane contains all unassigned output programs. Use drag and drop to assign and de-assign output programs.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 77 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
7. Select the AutoReturn tab. This tab is used to set – by stream - the input program which will be spliced after clip insertion.
Requirements: The following requirements must be met for this feature to work:
“Auto Ripple Times” option at “Options” tab of the list properties window must be enabled for correct operation of the Auto-Return feature. The option must be enabled for all lists which will run DTP Insertion events with enabled Auto-Return.
An Input reference, which will be set as default Source (Auto-Return program), must be active.
About points A and C from MRD ({Clip Playing} / {Clip Cued} -> {Clip Cued} /
{Idle} and .{Clip Playing} / {Source Cued} -> {Source Cued} / {Idle}). The recommended minimal interval between the end of the first event (not postroll) and preroll of the second one is 3 seconds. Splice to the second event can fail If the interval is lesser then 3 seconds. The back to back splice is not affected.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 78 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Stream 1 – 8:
Check “Enabled” to enable a stream.
Input Program name: Each driver stream has a combo box populated with available ACTIVE input names. An error message is displayed if an incorrect input name is entered. It is recommended not to type it, but instead choose the input from the combobox to avoid an incorrect input.
Note: Auto-Return settings are saved into ADC100NT.ini file with key
“DTP_StreamARProgram%d”, where %d is the zero based stream number.
8. Select the Diagnostics tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 79 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Perform the following actions as required:
• ReVerify: Click this button to update clip and program collections. It removes unregistered clips and inputs from storage and then re-reads collections again adding any additional clip or program again. The “not removed” registered inputs and clips are not checked for existence in downloaded collections. Remaining the registered clips and inputs ensures that playout is not interrupted by the ReVerify.
• ReInitialize: Click this button to reset the driver state machine and re-establish connection with the DTP. It fully removes clips and programs and re-reads it again.
The driver stops playout on the DTP before re-initialization.
9. Apply the Configuration Changes: When changes are made to a device’s configuration, the Apply button on the configuration GUI becomes active. Click the Apply button to immediately apply that configuration change to the system configuration held in random access memory by the Device Server.
NOTE: Apply does not write the configuration change to the Device Server’s
configuration files. This can only be done by using the Save Devices option on the
Configured Devices window’s File menu.
10. Save the Configuration: From the Configured Devices window select File> Save Devices.
The current configuration is written to the Device Server’s configuration files in the
“C:\Server” folder on the Device Server.
• Attempting to close the Configured Devices window without first saving any configuration changes, results in the Configuration Manager prompting to save the changes on the Device Server. Accepting this prompt writes the configuration changes to the Device Server’s configuration files as well.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 80 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
VTR Configuration (General)
The following is an example video tape recorder (VTR) configuration. Your VTR may have different options and the selection of configuration tabs may be different for that device. If necessary, refer to the User Notes for your device for complete details on how to configure it.
To Configure a VTR
1. Under VTRs in the Available pane (right pane), select a device and drag-n-drop it to the
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the VTR device in the left pane, right-click and from the popup menu select
Properties. The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select General tab.
Configure the following parameters as required.
Note: The parameters displayed depend on the device selected.
• Device Name: Enter a name for the VTR to help you identify the VTR during event transmission. The name can have up to 16 characters. The device name has no relation to the ID of any tape inserted in the VTR.
• Options.
Standbyoff for Tension Release: This parameter forces the software to issue a
Standby Off command to the VTR. In Sony Betacam decks, a tension release
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 81 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager command is used. The setting on this parameter does not affect digital and one inch VTR’s - these VTR’s always receive the Standby Off command when issued. Default is disabled (unchecked).
Eject on Initialization: Enable (checked) or Disable (uncheck) issuing a stop command to the VTR and ejecting the disc whenever the Device Server is started or the port is re-initialized. Default is disabled (unchecked).
Keep Media in VTR: A tape inserted in a VTR is retained by the VTR (not ejected). The tape can then only be manually ejected. This feature allows the
VTR to behave as if it has a storage location to hold a tape - like a cart machine.
Use caution when selecting this parameter for VTRs that are used as record decks for the compiler. Default is disabled (unchecked).
• Edit Compensation:
Edit On / Edit Off: These edit compensations are a frame latency value for how long the VTR takes to respond to either enabling or disabling the edit.
Leave these Edit Compensation values at 2 unless you are experiencing problems or if the decks are used as compiler record decks. If you intend to change these values, contact your Automation representative.
Sync Adjust: This parameter adjusts the sync play value for external VTRs
(Sony and Ampex protocols).The Sync Adjust setting has a default of zero and should never have to be changed. However, if it needs to be changed, the value can be changed from -20 to 20 frames. As required, the operator can change this option to adjust the SOM of the clip to record and play out.
A positive value causes the tape to come up to speed past the SOM by the specified number of frames at the end of preroll.
A negative value causes the tape to come up to speed before the SOM by the specified number of frames at the end of preroll.
• Tape Speed Control Options for Media List:
NOTE: This entry appears on all VTR setup tabs. This option need only be set once.
Since the option is in a separate box, though it shares the same tab page as other
setup options, when a different tab is selected, the option and its setting remains.
When a VTR (or tape machine) starts running, its speed increases from 0 to a stable level. However, this transient time to the stable level is not constant and is tape machine dependent.
When a clip in the tape is to be recorded to a video disk server, it requires that the record command to the disk record port be frame accurate so that the first recorded screen of a clip in the video disk server is also SOM frame.
Because of variant VTR transient times, without software control, a recorded clip can be a few frames off.
Tape Speed Override: If absolute frame accuracy is not required, this option can be used.
When this parameter is enabled, the system changes the speed of the VTR machine to hit the time of playing the SOM frame at the time a record command is sent to video disk server record port.
This method typically results in 80% to 90% frame accurate recording.
Sampling Tape Time Code: For frame accurate recording, check this option. By default, this option is enabled.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 82 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
When this parameter is enabled, instead of controlling VTR speed, the system controls the time to send the record command by sampling time code on the tape. When the sampling value shows that the VTR speed is constant, the system calculates the time of sending out the record command.
This method can result in 100% frame accurate recording.
The option is saved to the mclient.ini file and does not need to be checked again after next launch, or when the next setup tab is selected.
NOTE: This option is also for GMT list.
• Frame Calibration to Record Device: This parameter allows adjusting the timing in the VTR driver to get frame accurate recording. Selecting OK saves this parameter setting to the INI file for future use.
This option is available for selection when Sampling Tape Time Code is enabled.
This option is hidden when Sampling Tape Time Code is enabled.
Example Use:
1) Set the parameter “Frames To Send Record Early” on the disk (destination device) configuration.
2) Select one VTR as the source device and perform autocopy.
3) Check the first recorded frame (this should be the SOM frame), and adjust the
VTR parameter “Frame Calibration To Record Device”.
4) Select another VTR as the source device and perform autocopy.
5) Check the first recorded frame (this should be the SOM frame), and adjust the second VTR parameter.
4. Select the Serial Port tab. (This tab is present when Sony and Panasonic VTR types are being configured).
Use this tab to connect the driver to the ADC’s serial COM port that the device is physically connected.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 83 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Port setting: Click the down arrow button to select from a list of available serial ports.
5. Select VTR Offset tab. (This tab is used to specify the offset parameter for DVC Pro.)
Configure the following parameters as required:
• One (1) for 25 MBPS: (Default 0) use spin arrows to set the offset.
6. Select Diagnostics tab. (This tab appears when VTR type Demo VTR is selected and being configured.)
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 84 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• ID: The device name identifies the VTR port. The default VTR name is VTR1. Enter the name by using up to four characters. When an event is threaded, a fifth character
– the head number - is added to the name.
• Compile ID: The name is also used to identify the disk port used to execute secondary data events. If a disk port’s name matches the ID of a secondary data event, the event is executed. Such secondary data events include those that delete spots, transfer an archived spot, delete protect spots, or undelete protect spots.
• Inject button: Click to inject ID’s to tape.
7. Select VTR Type tab. This tab displays information about the VTR, including the model number, protocol ID, cassette size, analog/digital, and if extended errors are reported.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 85 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Refresh button: Click the Refresh button to update the information display.
8. Select Compile tab. (Extended VTR driver) This tab is used to configure up to 8 preset audio channels for insert-editing during the compile operation.
Configure the following parameters as required:
• Auto Editing: Select the group(s) of preset audio channels for insert-editing during the compile operation.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 86 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
9. Select the Timecode tab (Sony VTR Ext TC device only) Select the Timecode tab.
Select the timecode format to use when retrieving timecode data. Options are LTC or
VITC.
Sony VTR protocol provides several options to retrieve timecode data: TIMER-1, LTC and VITC. While the current Sony VTR driver uses LTC by default, there are conditions, such as jogging the tape, where LTC data is incorrect. Since VITC data is more accurate, it is desired for a driver to be able to query VITC data. However, some devices do not support VITC data query.
This Sony VTR Ext TC VTR driver provides a configuration option to choose between different timecode formats, as required.
10. Select Communications tab. (For Sony XDCAM Deck). Ensure the following parameters are specified:
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 87 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required. Below are recommended settings for the
XDCAM Deck.
• Baud Rate: 38400
• Data Bits: 8
• Stop Bits: 1
• Parity: Odd
11. Select the Deck Offset tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 88 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Recording Offsets.
Short Pre-Roll and Short Post-Roll are frame values used to adjust the length of the clips. The full length of the clip should include the duration of the clip, the short pre-roll, and the short post-roll settings.
The default values of short pre-roll and short post-roll for the deck are 0.
12. Apply the Configuration Changes: When changes are made to a device’s configuration, the Apply button on the configuration GUI becomes active. Click the Apply button to immediately apply that configuration change to the system configuration held in random access memory by the Device Server.
NOTE: Apply does not write the configuration change to the Device Server’s configuration files. This can only be done by using the Save Devices option on the
Configured Devices window’s File menu.
13. Save the Configuration: From the Configured Devices window select File> Save
Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
• Attempting to close the Configured Devices window without first saving any configuration changes, results in the Configuration Manager prompting to save the changes on the Device Server. Accepting this prompt writes the configuration changes to the Device Server’s configuration files as well.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 89 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Cart Machine Configuration (General)
The following is an example cart machine configuration. Your cart machine may have different options and the selection of configuration tabs may be different for that device. If necessary, refer to the User Notes for your device for complete details on how to configure it.
To Configure a Cart Machine
1. Under Cart Machines in the Available pane (right pane), select a device and drag-n-drop
it to the Configured Pane (left pane). For details on assigning a device see: To Assign a
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the Cart Machine device in the left pane, right-click and from the popup menu select Properties. The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select General tab. Available options may differ depending on the device selected. The following example is a general tab from Flexicart.
Configure the following parameters as required:
• Device Name: Enter a name (using up to 16 characters) for the cart machine. This name is used to identify the cart machine during event transmission.
• Options.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 90 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Eject on Initialization: A stop command is issued to the cart machine whenever the Device Server is started or the port is re-initialized. Default is disabled
(unchecked).
Enable VTR 1-6: This parameter allows you to select which VTRs are available for use. In the Enable VTR window, if a VTR is not selected, the VTR is not used by the ADC Device Server (or the cart machine). This is useful when using a cart machine VTR for some other operation or when the device is broken. To start using a deselected VTR, make sure this VTR is selected in the Enable VTR window. Default is 4 VTRs enabled.
Keep Media in VTR: A tape inserted in a VTR is retained by the VTR (not ejected). The tape can then only be manually ejected. This feature allows the
VTR to behave as if it has a storage location to hold a tape - like a cart machine.
• Sync Adjust: This parameter adjusts the sync play value for external VTRs (Sony and Ampex protocols). The Sync Adjust setting has a default of zero and should never have to be changed. However, if it needs to be changed, the value can be changed from -20 to 20 frames. A positive value causes the tape to come up to speed past the SOM by the specified number of frames at the end of preroll. A negative value causes the tape to come up to speed before the SOM by the specified number of frames at the end of preroll.
• Door Error Delay: (for Flexicart): Specify the delay before reporting a Door Open error.
• Sampling VTR Time Code: Use this parameter for selecting TSO method or “Frame
Accurate Recording” method. When it is selected, “Frame Accurate Recording” method is used. Otherwise, TSO method is used. This option is applied to all the
VTRs inside the cart machine. By default, it is unchecked. The selection is also saved to mclient.ini file for next launch
• StandByOff When Tension Release: Check to enable. This parameter forces the software to issue a Standby Off command to the VTR. In Sony Betacam decks, a tension release command is used. The setting on this parameter does not affect digital and one inch VTR’s - these VTR’s always receive the Standby Off command when issued. Default is disabled (unchecked).
4. Select the Serial Port tab. Use this tab to connect the driver to ADC’s serial COM port that the device is physically connected. Click the down arrow button to select from a list of available serial ports.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 91 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
5. Select Editor Parameters tab.
Configure the following parameters as required:
• VTR 1 – 6 button: Click on a desired VTR to edit its compensation properties. The following box appears:
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 92 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Edit On / Edit Off: Leave these Edit Compensation values at 2 unless you are experiencing problems.
If you intend to change these values, contact your Automation representative.
Keep Media in VTR: When checked (enabled) a tape inserted in a VTR is retained by the VTR (not ejected). The tape can then only be manually ejected.
This feature allows the VTR to behave as if it has a storage location to hold a tape - like a cart machine.
Use caution when selecting this parameter for VTRs that are used as record decks for the compiler. Default is disabled (unchecked).
Rewind Attempts Amount: Use this option to set the number of attempts the driver waits for the Rewind status before assuming the VTR has rewound and stopped, and then sending an Eject command to the VTR.
• Four Channel Audio: Enable audio recording on four channels instead of the normal two channels. Default is disabled (unchecked).
6. Select VTR Parameters tab. (This tab is available for Odetics Cart Machines.)
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 93 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• VTR 1 – 6 button: Click on a desired VTR to edit its compensation properties. The
VTR Configuration dialog box appears:
Select General tab.
Configure the following parameters as required:
Standbyoff for Tension Release: This parameter forces the software to issue a
Standby Off command to the VTR. In Sony Betacam decks, a tension release command is used. The setting on this parameter does not affect digital and one inch VTR’s - these VTR’s always receive the Standby Off command when issued. Default is disabled (unchecked).
Edit Compensation: This parameter adjusts the sync play value for external
VTRs (Sony and Ampex protocols). The Sync Adjust setting has a default of zero and should never have to be changed. However, if it needs to be changed, the value can be changed from -20 to 20 frames. A positive value causes the tape to come up to speed past the SOM by the specified number of frames at the end of
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 94 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager preroll. A negative value causes the tape to come up to speed before the SOM by the specified number of frames at the end of preroll.
Leave the Edit Compensation values at 2 unless you are experiencing problems.
If you intend to change these values, contact your Automation Technical Support representative.
Select the Serial Port tab. Use this tab to connect the driver to ADC’s serial
COM port that the device is physically connected. Click the down arrow button to select from a list of available serial ports.
Select VTR Offset tab (Used by DVC Pro) to specify the offset parameter:
Configure the following parameters as required:
One (1) for 25 MBPS: (Default 0) use sin arrows to set the offset.
Select VTR Type tab. This tab displays information about the VTR, including the model number, protocol ID, cassette size, analog/digital, and if extended errors are reported.
Refresh button: Click the Refresh button to update the information display.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 95 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
7. Select Tape Handling tab. Use this tab to specify the Label Length. (This tab is available for Odetics and Marc Smart Cart, Cart Machines.)
8. Select Qualifiers tab. Use this tab to specify what types of material may be played out by the cart machine on each playlist.
The Qualifiers option is particularly important in GMT environments where some of a cart machine’s VTRs are assigned to the playlist and others are assigned to the GMT list for baseband caching to a video server. For example, if two of a cart machine’s four VTRs are assigned to play Events With Segments Only on the playlist, then any missing singlespot clips requested for caching will be played out only by the two VTRs assigned to the
GMT list. If the qualifiers are not set, any missing single-spot clips will be registered with the cart machine for direct playout, instead of being registered with the playlist’s
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 96 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Requester for caching. If the missing clip is not found in the cart machine, the event will remain red on the playlist and be missed.
• Select a playlist and then click the Edit button.
A properties sheet opens with playout qualification parameters: No Events With
Segments, Events With Segments Only, No Events Greater Than xx (Mins.), No
Events Less Than xx (Mins.), Only Events With ID in [an ASCII character range – the first character of the ID].
• The individual VTRs in the cart machine may be assigned to different lists with different qualifiers. One VTR may be assigned to Playlist1 and only allowed to play segmented events, while another VTR assigned to Playlist2 is only allowed to play single-spot tapes. The qualifiers apply to playlists globally – any VTRs assigned to that list will be subject to the same playout qualifications.
9. Select Tools tab.
This tab is used only for demo devices. Since no tape is actually being used with a demo device, the tape ID and title are entered here. With an actual device, this action is unnecessary, as the automation system can read this information off either a barcode or from the database record.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 97 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• ID: Enter the ID of the tape to be inserted or removed.
• Title: Enter the title of the tape to be inserted or removed.
• Bin Location (A1-A40): Select the slot in the cart machine to add the tape to or remove the tape from.
• Insert button: Click to insert a tape.
• Remove button: Click to remove a tape.
10. Select Diagnostics tab.
The Diagnostics tab has several different functions depending on the make and model of cart machine.
For example:
• The Betacart’s Diagnostics tab, contains one button: Reinitialize (device). All
Automation cart machine objects contain this option.
• The Odetics TCS90’s Diagnostics tab, contains two buttons: Reinitialize (device) and
Reverify (storage).
• The SmartCart’s Diagnostics tab, contains three buttons: Reinitialize (device),
Reverify (storage), and Reinitialize (elevator).
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 98 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Reinitialize button: Click to reinitialize the device. Confirm your selection when prompted.
The cart machine is reinitialized. The storage collection for the cart machine is cleared and any tapes in the VTRs are ejected (if Eject On Initialization has been selected on the General tab). All the bins are re-verified by the barcode reader and the automation’s storage collection is rebuilt.
WARNING: This can be a risky and time-consuming procedure. Do not attempt a reinitialization unless the customer can afford to be without a cart machine for an extended period of time. Depending on the size of the cart machine and the number
of bins available, reinitialization could take up to several hours!
• Reverify button: This is a less disruptive procedure that a full reinitialization.
ReVerify allows the cart machine to continue operating while it reverifies the contents of its bins and VTRs. This is a background procedure and the normal loading,
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 99 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager unloading and playout of tapes will continue without interruption. The automation system’s storage collection remains intact, but its data is updated as each bin is reverified. New tapes should not be loaded or unloaded from the cart machine through the I/O door (load/unload bins) until the reverification process has completed.
• Init Elevator button: This performs a hardware reinitialization of the elevator robot mechanism. This should be used when problems are encountered and the operator has had to open the door and physically remove a tape from the robot.
11. Select Manual Mode tab. (This tab is available only for Panasonic SmartCart and all
Odetics cart machines.)
Configure the following parameter as required:
• Manual Elevator Mode: When this mode is enabled (checked), the robot mechanism is placed offline for maintenance and the operator becomes the replacement for the robot.
This must be accomplished with the main door open so that the operator may access the storage bins and VTRs.
Prompting is given to indicate when tapes need to be loaded into VTRs from the cart machine’s library or removed from VTRs and replaced into the tape library.
It is necessary to enable the Pop up Diagnostic Window from the Preferences /
Errors menu on the Air Client being used. This allows the prompting messages to appear on that client only.
Other clients are not affected.
Each pop up window must be closed before the next diagnostic message is displayed. This insures that no messages are missed and that tapes are moved in the order they are needed by the VTRs.
12. Select Robotics Arms tab. This option is only available for the Odetics TCS-2000.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 100 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure to place one or more gripper arms offline. The elevator robot will continue to function, and the automation will not use any gripper arms that are disabled. The TCS-
2000 can function with only one gripper arm enabled, but its speed and efficiency will be greatly reduced.
13. Apply the Configuration Changes: When changes are made to a device’s configuration, the Apply button on the configuration GUI becomes active. Click the Apply button to immediately apply that configuration change to the system configuration held in random access memory by the Device Server.
NOTE: Apply does not write the configuration change to the Device Server’s configuration files. This can only be done by using the Save Devices option on the
Configured Devices window’s File menu.
14. Save the Configuration: From the Configured Devices window select File> Save
Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
• Attempting to close the Configured Devices window without first saving any configuration changes, results in the Configuration Manager prompting to save the changes on the Device Server. Accepting this prompt writes the configuration changes to the Device Server’s configuration files as well.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 101 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
M/C Switcher Configuration (General)
In general, the Automation interface treats all makes and models of switchers as generic devices. The specific driver for a particular brand of switcher will communicate using that brand’s control protocol, but this is transparent to the automation system’s user.
The following is an example Master Control (M/C) switcher configuration. Depending on the specific brand and model of switcher, the selection of configuration tabs may be different for that device, and there may be other configuration options not outlined here. Information regarding these options may be found in the user notes for the specific device.
Switching under automation
The Automation system communicates with switchers via the devices’ native protocol. When a switch command is sent to a switcher, the automation sends a “switching triplet” consisting of the device number, the input number and the output number to the software object controlling the device. This “triplet” is then translated to the switcher’s own command language and the command is passed via the RS-422 serial connection to the device. This translated command may also contain transition information or audio mixer and keyer presets for a master control switcher, or the number of levels to switch for a router.
To Configure an M/C Switcher
1. Under M/C Switchers in the Available pane (right pane), select a device and drag-n-drop
it to the Configured Pane (left pane). For details on assigning a device see: To Assign a
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the M/C Switcher device in the left pane, right-click and from the popup menu select Properties. The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select General tab. Use this tab to enter a specific name for the device, specify the dimensions of the switcher, and compensate for any switcher latency.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 102 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Device Name: Enter a name (using up to 16 characters) for the switcher. This name is used by the automation system to identify the switcher. Systems with multiple switchers should have each switcher assigned a unique name.
• Dimensions.
Input Crosspoints: Specify the input crosspoint on a cascaded switcher to which the device’s setting is connected. The valid range is 0 to 32768. Default is
16.
Output Crosspoints: Specify the output crosspoint on a cascaded switcher to which the device’s setting is connected. The valid range is 0 to 32768. Default is
1.
Note on Utah MC2020: The MC-2020 is a 0-based switcher. Since the ADC software is 1-based, all desired A/V port locations must be entered in the software as “A/V port +1.” This includes all VTR A/V information, as well as all source names in the source name table. Crosspoint values up to 64k are
supported.
• Switcher Latency: This parameter adjusts the latency of the switcher. The adjustment can range from -10 to +10 frames.
If the adjustment is positive, the switcher switches the entered number of frames later.
If the adjustment is negative, the switcher switches the entered number of frames earlier. The default value of zero is usually sufficient.
Adjust latency only if it has been determined that the switcher is indeed switching early or late. Some switchers have a built-in latency of one frame and will always switch one frame late if this latency is not compensated for.
4. Select Serial Port tab. Use this tab to connect the driver to ADC’s serial COM port that the device is physically connected. Click the down arrow button to select from a list of available serial ports.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 103 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
5. Select Communications tab. (For GVG MCS 1600, NVision MCS, Evertz E9625 MCS,
Leitch Opus MCS, PixelPower BrandMaster MCS.) Use this tab to specify Baud Rate,
Data Bits, Stops Bits, and Parity.
6. Select Sources tab. Use this tab to create a table of source names (mnemonics) associated with router or switcher inputs that the automation may use for record events.
The source names table accepts multiple names for the same input number, but does not accept duplicate names for different inputs.
If a record event is placed on a record list, the source name may be entered in the title field. The automation compares this source name to the source names table and switches the designated input to the record device that has registered the event.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 104 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Add button: Click the Add button to enter a source crosspoint name and number.
Crosspoint Name: Enter a mnemonic to help the operator identify the crosspoint.
Number: Enter the physical connection number of the crosspoint.
• Edit Button: To edit an existing entry, select an entry from the crosspoint list display and then click Edit. An edit dialog is displayed populated with the parameters currently specified for the selected entry. Make changes as required, and then click
OK.
• Delete button: To delete an existing entry, select an entry from the crosspoint list display and then click Delete.
7. Select Key Parameters tab. (For TriKey-only)
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 105 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Key Number Field Definition: Choose either “#” or “sSP” field in the playlist as the keyer number. The selection depends on the functionality of other switcher drivers that may be used in conjunction with the Trikkey. If the Trikkey is used as a keyeronly slave device expanding the capability of a master control switcher (i.e. a Saturn), then the convention should follow that of the master. Otherwise, this may be set based on preference of the user.
# field of Event: This field has a range of 1 through 254
sSP field of Event: This field has a range of 0 to 9
• Start Key Number: Specify the first keyer number so that if Trikkey is used as a slave, the keyer number will not be in conflict with the numbering system in the master switcher (which always starts from one). (Default: 7, Minimum: 1).
8. Select Destinations tab. Use this tab to create a table of destination names that the automation primarily uses for secondary crosspoint switch events. The destination names table accepts multiple names for the same output number, but does not accept duplicate names for different outputs.
If a secondary crosspoint switch event is placed on the playlist, the source and destination names may be entered in the title field using the format: source
name:destination name (the colon is required)
The automation compares these names to the source and destination names tables and switch the designated input to the designated output at the appropriate time.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 106 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Add button: Launches the Add Destination Data dialog. Specify the CrossPoint
Name, Number, and then click OK
Crosspoint Name: The Crosspoint Name is a mnemonic to help the operator identify the crosspoint.
Number: The physical connection number of the crosspoint.
• Edit Button: To edit an existing entry, select an entry from the crosspoint list display and then click Edit. An edit dialog is displayed populated with the parameters currently specified for the selected entry. Make changes as required, and then click
OK.
• Delete button: To delete an existing entry, select an entry from the crosspoint list display and then click Delete.
9. Select System Inputs tab. Use this tab to specify the switcher inputs for common sources such as Black, Colorbars, Station ID, and Initial Input. All four inputs designated here may be switched manually from the diagnostic switch panel (see Switching Tab below). In addition, the Black and Station ID inputs are used by the automation if the corresponding list settings, Switch to Black and Station ID on Skip, are enabled on the
List Configuration / Properties / Options tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 107 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• System Inputs: For each parameter specify a number from 0 to 32768 to indicate which crosspoints carry the black, colorbars, station ID and initial input signals.
Default is 0. These options are not used by the automation system unless the corresponding list settings are enabled for Black Input and StationID.
Black Input: When the Transmission List Option “Switch to Black” is selected, and the most recent event on the list was running on a device configured to use this router, then the crosspoint listed here (if non-zero) will be switched to the output crosspoint used by that event, if the list stops because of an error, if the event ends and there is a Hard-Start delay until the next event begins, or if it ends normally and there are no more events on the list. If it is set to 0 then nothing will happen.
Colorbars: This crosspoint is used only when the Colorbars button is pressed on the diagnostics control panel (Configuration Utility or Air Client). If it is set to 0 then the Colorbars button will have no action.
Station ID: When the Transmission List Option “Station ID on Skip” is selected, and the most recent event on the list was running on a device configured to use this router, then this crosspoint will be switched to the output crosspoint used by that event, if an operator invokes Skip on the Air Client’s control panel. When the next event begins to play, the crosspoint is switched to whatever that event requires.
Initial Input: This crosspoint will be switched to all outputs of the router when the
Device Server application is launched. If it is set to 0 then nothing will happen. In most cases it is recommended to leave this function disabled (0).
About Initial Input: The Initial Input source comes into play when communication is first established with the switcher or in the event of a switcher failure.
If the switcher fails to switch for some reason – the switcher returns a NAK (i.e. a
Negative Acknowledgment because the command format is wrong) or no response to a switch command – the automation retries the switch command twice.
If the switcher fails to switch after two retries, the automation attempts to reinitialize the switcher. It sends a command to switch to the designated Initial
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 108 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Input. In most cases, particularly if there are intermittent serial communication problems with the switcher, it may be safer to leave the Initial Input set to zero.
That way, the automation will not attempt to reinitialize the switcher and possibly switch to black (or whatever has been designated as the Initial Input).
10. Select Effect Durations tab. To configure Effect durations in frames.
Configure the following parameters as required:
• Slow: Specify a number from 0 to 999. Default is 60.
• Medium: Specify a number from 0 to 999. Default is 30.
• Fast: Specify a number from 0 to 999. Default is 15.
IMPORTANT: These durations, in frames, must match the effect durations configured in the switcher itself.
11. Select Reporting tab. Use this tab to enable reporting of the condition of the switcher to the error log.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 109 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Enable reporting for: There are three available options on the Reporting tab, depending on the amount of information that is necessary to be logged into the ADC error file when the router is used. The actual log is configured on the Air Client v3 application, but the information supplied to the logging mechanism from the router driver is regulated here.
These parameters allow the switcher to generate an error whenever the switcher does not respond to a communication request. Place a check mark in each box to enable reporting (default is disabled for all).
Errors: Enables the logging of critical failures, such as the device failing to confirm that a transition command was executed, or when communication is lost with the router.
Warnings: Enables the logging of other information reported by the router. The
1200 series routers do not provide such information to automation; so enabling
Warnings will have no effect on the system.
Crosspoint Changes: Enables the logging of each transition with a timestamp from when it occurred.
IMPORTANT: Normally these are left disabled, but can be enabled for diagnostic purposes. If reporting for Crosspoint Changes is enabled, the error log will quickly fill up
with every crosspoint switch command the automation has sent to the switcher.
12. Select Log tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 110 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• AsRun Log: This group enables As Run Logging of Manual Actions on Program,
Keyer and Audio Over Bus with the help of 3 check boxes: Select the type of bus to log: Program Bus, Keyer Bus, Audio Over Bus.
• Program Bus: When selected enables the manual change in PGM bus to be reported as an error or as a warning.
• Keyer Bus: When selected enables the manual change in KEY bus to be reported as an error or as a warning.
• Audio Over Bus: When selected enables the manual change in AUDIO OVER bus to be reported as an error or as a warning.
• Contextual Error Message: Check to enable two additional error messages:
“Manual Intervention of System”
“Return to Automated Control of System”
13. Select Backup tab. Use this tab to designate another switcher as the backup to the main switcher in case of a failure. The router that is configured here will receive all of the transition commands that are sent to the main device. For this reason the Backup router must be wired identically to the Main. There are other methods for driving a second switcher if this limitation cannot be accommodated.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 111 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Backup Switcher: Select from the dropdown list of available backup switchers. Use this parameter when installing a redundant switcher to act as backup if the main switcher fails. In the Configure Backup Switcher window, enter the number of the port that has the backup switcher connected to it (i.e., the device server channel number).
The main and backup switchers do not need to be the same model, but the backup should have dimensions large enough to back up all of the main switcher’s crosspoints. Both switchers must receive the same inputs. During playout, the backup switcher switches whenever the main switcher switches
The default is None (no backup switcher configured).
IMPORTANT: The backup switcher is switched simultaneously with the main switcher. The inputs on the backup switcher must match, in a one-to-one
correspondence, the inputs on the main switcher.
14. Select Audio Control tab. Use this tab to set up specific audio control commands for switchers that support this feature.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 112 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Control Audio Mode: Enable (check) to allow control of Audio Mode.
• Audio Mode:
Stereo/Mono: Enable (check) stereo / mono control for audio recording. Default is disabled (unchecked).
If an event has either Stereo or Mono in the sSP column of the transmission list, the automation will command the switcher to use the appropriate audio mixing.
Enhanced Audio Modes: (For MC2020) Check to enable Audio support for mono/stereo/SAP/Dolby modes.
If an event has either Mono/Stereo/SAP in the sSP column of the transmission list, the automation will command the switcher to use the appropriate audio mixing.
IMPORTANT: Dolby is not currently supported in Air Client and Media Client.
Switcher Audio Crosspoint: Enable (check) for secondary audio routing.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 113 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Default Audio Input: Specify the input for Audio 1 - x. These options are enabled when Switcher Audio Crosspoint is selected.
15. Select Cascade tab. Use this tab to set up Cascade routing.
Cascading (sometimes called “chaining”) allows the user to route audio and video through multiple switchers and routers simultaneously.
Example: a customer has ten VTRs, each with a designated output on their router. They have only one input on their master control switcher that must be shared among all ten
VTRs. Each VTR output on the router may be cascaded to the single input on the master control switcher to switch it to air. This particular arrangement negates the possibility of using transition effects on the master control switcher between two back-to-back VTR events – the switcher cannot transition between events on the same input.
• Click the Add button to enter cascade data for the switcher:
• Configure the following parameters as required, then click OK.
Output Active Line: This setting specifies which of the switcher’s crosspoints the cascaded switcher is connected to. The valid range is 0 to 32768.
Note: If the “Output Active Line” number is the same as “Cascade Crosspoint
Out” number, it is treated as invalid. This only occurs if the Cascade Device is the
same and not if it is a different switcher/router.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 114 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Cascade Device: Select a cascade device from the dropdown list.
Cascade Crosspoint In: The crosspoint on the cascaded switcher to which the
Output Active Line setting (above) is connected. The valid range is 0 to 32768.
Cascade Crosspoint Out: The out crosspoint on the cascaded switcher to which the signal is to be routed. The valid range is 0 to 32768.
16. Select Switching tab. Use this tab to manually switch inputs and outputs for diagnostic purposes.
This utility is not intended as an on-line substitute for the switcher’s own control panels.
The source and destination names tables must be completed before any sources or destinations will appear in the drop-down boxes.
Configure the following parameters as required:
• Black, Colorbars, Station ID, Initial Input buttons: These selections refer to the sources designated on the System Inputs tab above. If a source and destination are selected in the drop-down boxes, clicking the “Switch” button will cause the switch to occur.
17. Select Timing tab. Used by devices that support Max Latency and join in progress functionality. (e.g. IconMaster, NVision MCS.)
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 115 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Max Latency Count: (Default: 20) Specify the time in frames that a device needs to reply to a command. Adjust the ”Max Latency Count” based on the number of secondary events to bring up with the primary event.
• Join in progress: (For IconMaster) Enable (check) the IconMaster driver option to re-join the ADC playlist at its current schedule location after the IconMaster has reported to its serial port that Automation control has been restored from the local mode (hold button on IconMaster Panel). (Default: disabled)
18. Select Command tab. (for BTS Saturn Switcher and GVR Maestro) If required, enable
(check) to preroll a transition.
19. Select Diagnostics tab. (For GVG 100 and PixelPower BrandMaster).
• For GVG 100: If required, click the Reinitialize button to reinitialize the device.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 116 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• For PixelPower BrandMaster: Use this tab to send any command to the
BrandMaster device. Enter a command in the Test Command field and then click
Send.
Sending a Command or Request to the BrandMaster:
Enter the command or the request in the “Test command” field using the following format:
REQ:<Request number> <Parameters (if they are needed)>
CMD:<Command number> <Parameters (if they are needed)>
Examples:
REQ:0D
Automation enable status (AUTO_STAT) request will be sent
REQ:0C
Key status (KEY_STAT) request will be sent
CMD:01 03
Next transition (TX_NEXT) command will be sent
01 03
Next transition (TX_NEXT) command will be sent too
Click “Send” button to send the complete command to Brand Master device.
20. Select Manual Control tab. (For Probel TX520). Use this tab to set keyer 1 thru keyer 4 to Manual or Auto mode. For example, if Manual Control is selected for keyer1,
Automation will not send any commands to turn on/ off the keyer 1.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 117 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
21. Select Imagestore tab. (For Miranda MCS SubDev and IM750 MCS SubDev).
22. Select Transition Attributes tab. (For Pesa MCLite MCS only).
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 118 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Cut Input Name: Select option from dropdown list
• Hold Input Name: Select option from dropdown list
• Wipe Pattern: Select option from dropdown list
• Wipe Border: Select option from dropdown list
23. Select Audio Over tab. (For QMC and Oxtel Presmaster)
Configure the following parameters as required:
• Uses: Choose between the # field and the sSP field to represent the Audio unit
(value of 1 or 2). Default will be the current behavior, i.e. # Field.
Audio Over number and Keyer number can be specified in ‘#’ field or the ‘sSP’ field.
Up to 254 logos can be recalled.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 119 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
# field of Event: This field has a range of 0 to 9
sSP field of Event: This field has a range of 1 through 254
24. Select Keyer Number tab. (For QMC)
Configure the following parameters as required:
• Uses: Choose between the # field and the sSP field to represent the Keyer Number.
Default will be the current behavior, i.e. # Field.
Keyer number can be specified in ‘#’ field or the ‘sSP’ field. Up to 254 logos can be recalled.
# field of Event: This field has a range of 0 to 9
sSP field of Event: This field has a range of 1 through 254
25. Select Extra Keyers tab. (For Oxtel Presmaster only).
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 120 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Fitted: This parameter defines the Intuition mode from unfitted to fitted. Default parameter is unfitted (unchecked).
The Presmaster has two downstream keyers, an optional two extra keyers (when the second Imagestore is fitted) or an optional 8 extra keyers (when an Imagestore
Intuition is fitted).
26. Select Logo Source tab. (For Oxtel Presmaster only.)
Configure the following parameters as required:
• Uses: Select one of the following:
# field of Event: (Default selection) When selected, has logo limit of 254.
Title field of Event: Select to allow the operator to use the title field to enter logo numbers up to 4000.
The format of Title filed for Logo is as follows: "L="<logoNumber> (without quotation marks and brackets)
27. Apply the changes. When finished click Apply, then click OK.
When changes are made to a device’s configuration, the Apply button on the configuration GUI becomes active. Click the Apply button to immediately apply that configuration change to the system configuration held in random access memory by the
Device Server.
NOTE: Apply does not write the configuration change to the Device Server’s configuration files. This can only be done by using the Save Devices option on the
Configured Devices window’s File menu.
28. Save the Configuration: From the Configured Devices window select File> Save
Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
• Attempting to close the Configured Devices window without first saving any configuration changes, results in the Configuration Manager prompting to save the
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 121 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager changes on the Device Server. Accepting this prompt writes the configuration changes to the Device Server’s configuration files as well.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 122 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Router Configuration (General)
In general, the Automation interface treats all makes and models of routers as generic devices. The specific driver for a particular brand of router will communicate using that brand’s control protocol, but this is transparent to the automation system’s user.
The following is an example router configuration. Depending on the specific brand and model of router, the selection of configuration tabs may be different for that device, and there may be other configuration options not outlined here. Information regarding these options may be found in the user notes for the specific device.
Routing under automation
The Automation system communicates with routers via the devices’ native protocol. When a switch command is sent to a router, the automation sends a “switching triplet” consisting of the device number, the input number and the output number to the software object controlling the device. This “triplet” is then translated to the router’s own command language and the command is passed via the RS-422 serial connection to the device. This translated command may also contain transition information or audio mixer and keyer presets for a master control switcher, or the number of levels to switch for a router.
To Configure a Router
1. Under Router Switchers in the Available pane (right pane), select a device and drag-n-
drop it to the Configured Pane (left pane). For details on assigning a device see: To
Assign a Device to a Device Channel .
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the Router device in the left pane, right-click and from the popup menu select
Properties. The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select General tab. Use this tab to enter a specific name for the device, specify the dimensions of the router, and compensate for any router latency.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 123 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Device Name: Enter a name (using up to 16 characters) for the switcher. This name is used by the automation system to identify the switcher. Systems with multiple switchers should have each switcher assigned a unique name.
• Dimensions.
Input Crosspoints: Specify the input crosspoint on a cascaded switcher to which the device’s setting is connected. The valid range is 0 to 32768. Default is
16.
Output Crosspoints: Specify the output crosspoint on a cascaded switcher to which the device’s setting is connected. The valid range is 0 to 32768. Default is
1.
• Switcher Latency: This parameter adjusts the latency of the switcher. The adjustment can range from -10 to +10 frames.
If the adjustment is positive, the switcher switches the entered number of frames later.
If the adjustment is negative, the switcher switches the entered number of frames earlier. The default value of zero is usually sufficient.
Adjust latency only if it has been determined that the router is indeed switching early or late. Some routers have a built-in latency of one frame and will always switch one frame late if this latency is not compensated for.
4. Select Serial Port tab. Use this tab to connect the driver to ADC’s serial COM port that the device is physically connected. Click the down arrow button to select from a list of available serial ports.
Set this to the physical serial port number on the Device Server where the router is connected (start from the first serial card on the left; the ports are numbered top-down).
You need not use the same value as the Channel number for the Serial Port, although it may make troubleshooting easier for you in the future.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 124 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
5. Select Communications tab. (Available for BTS Venus and DiTech) Use this tab to specify Baud Rate, Data Bits, Stops Bits, and Parity.
6. Select Sources tab. Use this tab to create a table of source names (mnemonics) associated with router inputs that the automation may use for record events. The source names table accepts multiple names for the same input number, but does not accept duplicate names for different inputs.
If a record event is placed on a record list, the source name may be entered in the title field. The automation compares this source name to the source names table and switches the designated input to the record device that has registered the event.
This is important if you plan on using the router in conjunction with ADC record events, which use the descriptions to identify the source on the router. Otherwise, it is not necessary to fill in this information (the Transmission List will not use this information for
Playout events).
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 125 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Add button: Click the Add button to enter a source crosspoint name and number.
Crosspoint Name: The Crosspoint Name is a mnemonic to help the operator identify the crosspoint. (up to 8 characters)
Number: The physical connection number of the crosspoint.
• Edit Button: To edit an existing entry, select an entry from the crosspoint list display and then click Edit. An edit dialog is displayed populated with the parameters currently specified for the selected entry. Make changes as required, and then click
OK.
• Delete button: To delete an existing entry, select an entry from the crosspoint list display and then click Delete.
7. Select Destinations tab. Use this tab to create a table of destination names that the automation primarily uses for secondary crosspoint switch events. The destination names table accepts multiple names for the same output number, but does not accept duplicate names for different outputs.
If a secondary crosspoint switch event is placed on the playlist, the source and destination names may be entered in the title field using the format: source
name:destination name (the colon is required). The automation compares these names to the source and destination names tables and switches the designated input to the designated output at the appropriate time.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 126 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Add button: Launches the Add Destination Data dialog. Specify the CrossPoint
Name, Number, and then click OK
Crosspoint Name: The Crosspoint Name is a mnemonic to help the operator identify the crosspoint.
Number: The physical connection number of the crosspoint.
• Edit Button: To edit an existing entry, select an entry from the crosspoint list display and then click Edit. An edit dialog is displayed populated with the parameters currently specified for the selected entry. Make changes as required, and then click
OK.
• Delete button: To delete an existing entry, select an entry from the crosspoint list display and then click Delete.
8. Select System Inputs tab. Use this tab to specify the router or switcher inputs for common sources such as Black, Colorbars, Station ID, and Initial Input.
All four inputs designated here may be switched manually from the diagnostic switch panel (see Switching Tab below). In addition, the Black and Station ID inputs are used by the automation if the corresponding list settings, Switch to Black and Station ID on Skip, are enabled on the List Configuration / Properties / Options tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 127 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• System Inputs: For each entry specify a number from 0 to 32768 to indicate which crosspoints carry the black, colorbars, station ID and initial input signals. Default is 0.
These options are not used by the automation system unless the corresponding list settings are enabled for Black Input and StationID.
Black Input: When the Transmission List Option “Switch to Black” is selected, and the most recent event on the list was running on a device configured to use this router, then the crosspoint listed here (if non-zero) will be switched to the output crosspoint used by that event, if the list stops because of an error, if the event ends and there is a Hard-Start delay until the next event begins, or if it ends normally and there are no more events on the list. If it is set to 0 then nothing will happen.
Colorbars: This crosspoint is used only when the Colorbars button is pressed on the diagnostics control panel (Configuration Utility or Air Client). If it is set to 0 then the Colorbars button will have no action.
Station ID: When the Transmission List Option “Station ID on Skip” is selected, and the most recent event on the list was running on a device configured to use this router, then this crosspoint will be switched to the output crosspoint used by that event, if an operator invokes Skip on the Air Client’s control panel. When the next event begins to play, the crosspoint is switched to whatever that event requires.
Initial Input: This crosspoint will be switched to all outputs of the router when the
Device Server application is launched. If it is set to 0 then nothing will happen. In most cases it is recommended to leave this function disabled (0).
Note: During initialization of the router driver, all destinations are set to the source entered in the “Initial Input”.
About Initial Input: The Initial Input source comes into play when communication is first established with the switcher or in the event of a switcher failure.
If the router fails to switch for some reason – the router returns a NAK (i.e. a
Negative Acknowledgment because the command format is wrong) or no response to a switch command – the automation retries the switch command twice.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 128 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
If the router fails to switch after two retries, the automation attempts to reinitialize the router. It sends a command to switch to the designated Initial Input. In most cases, particularly if there are intermittent serial communication problems with the router, it may be safer to leave the Initial Input set to zero. That way, the automation will not attempt to reinitialize the router and possibly switch to black
(or whatever has been designated as the Initial Input).
9. Select Reporting tab. Use this tab to enable reporting of the condition of the switcher or router to the error log.
Configure the following parameters as required:
• Enable reporting for: There are three available options on the Reporting tab, depending on the amount of information that is necessary to be logged into the ADC error file when the router is used. The actual log is configured on the Air Client v3 application, but the information supplied to the logging mechanism from the router driver is regulated here.
These parameters allow the switcher to generate an error whenever the switcher does not respond to a communication request. Place a check mark in each box to enable reporting (default is disabled for all).
Errors: Enables the logging of critical failures, such as the device failing to confirm that a transition command was executed, or when communication is lost with the router.
Warnings: Enables the logging of other information reported by the router. The
1200 series routers do not provide such information to automation; so enabling
Warnings will have no effect on the system.
Crosspoint Changes: Enables the logging of each transition with a timestamp from when it occurred.
IMPORTANT: Normally these are left disabled, but can be enabled for diagnostic purposes. If reporting for Crosspoint Changes is enabled, the error log will quickly fill up with every crosspoint switch command the automation has sent to the router.
10. Select Log tab. Use this tab to configure manual intervention logging parameters.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 129 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• AsRun Log: This group enables As Run Logging of Manual Actions on Program,
Keyer and Audio Over Bus with the help of 3 check boxes: Select the type of bus to log: Program Bus, Keyer Bus, Audio Over Bus.
• Program Bus: When selected enables the manual change in PGM bus to be reported as an error or as a warning.
• Keyer Bus: When selected enables the manual change in KEY bus to be reported as an error or as a warning.
• Audio Over Bus: When selected enables the manual change in AUDIO OVER bus to be reported as an error or as a warning.
• Contextual Error Message: Check to enable two additional error messages:
“Manual Intervention of System”
“Return to Automated Control of System”
11. Select Backup tab. Use this tab to designate another router as the backup to the main router in case of a failure. The router that is configured here will receive all of the transition commands that are sent to the main device. For this reason the Backup router must be wired identically to the Main. There are other methods for driving a second switcher if this limitation cannot be accommodated.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 130 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Backup Switcher: Select from the dropdown list of available backup switchers. Use this parameter when installing a redundant switcher to act as backup if the main switcher fails. In the Configure Backup Switcher window, enter the number of the port that has the backup switcher connected to it (i.e., the device server channel number).
The main and backup switchers do not need to be the same model, but the backup should have dimensions large enough to back up all of the main switcher’s crosspoints. Both switchers must receive the same inputs. During playout, the backup switcher switches whenever the main switcher switches
The default is None (no backup switcher configured).
IMPORTANT: The backup router is switched simultaneously with the main router.
The inputs on the backup router must match, in a one-to-one correspondence, the
inputs on the main router.
12. Select Cascade tab. Use this tab to set up Cascade routing.
Cascading (sometimes called “chaining”) allows the user to route audio and video through multiple routers and switchers simultaneously.
Example: a customer has ten VTRs, each with a designated output on their router.
They have only one input on their master control switcher that must be shared among all ten VTRs. Each VTR output on the router may be cascaded to the single input on the master control switcher to switch it to air. This particular arrangement negates the possibility of using transition effects on the master control switcher between two back-to-back VTR events – the switcher cannot transition between events on the same input.
Recursive Cascading allows Router sources to be cascaded back into the same router for special purposes.
Example: a customer wishes to route certain analog sources through an analog-todigital converter (ADC) before routing them to a digital record device. The router output for the analog device may be recursively cascaded back into the router input for the ADC. The output of the ADC may then be routed to the digital record device.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 131 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Click the Add button to enter cascade data for the switcher:
• Configure the following parameters as required, then click OK.
Output Active Line: This setting specifies which of the switcher’s crosspoints the cascaded switcher is connected to. The valid range is 0 to 32768. Default is
0.
Note: If the “Output Active Line” number is the same as “Cascade Crosspoint
Out” number, it is treated as invalid. This only occurs if the Cascade Device is the
same and not if it is a different switcher/router.
Cascade Device: Select a cascade device from the dropdown list.
Cascade Crosspoint In: The crosspoint on the cascaded switcher to which the
Output Active Line setting (above) is connected. The valid range is 0 to 32768.
Default is 0.
Cascade Crosspoint Out: The out crosspoint on the cascaded switcher to which the signal is to be routed. The valid range is 0 to 32768. Default is 0.
13. Select Wire tab. (For GVG 10XL and Evertz 1200) Use this tab to configure the driver to operate in Simplex or Full Duplex mode.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 132 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• 2 Wires: If selected, the driver will ignore any input from the device and never report any comm. errors. If RS-485 operation is attempted with multiple routers (not recommended), this option must be used and the return lines from the switcher must be disconnected. The Device Server hardware is not capable of negotiation on an
RS-485 bus.
• 4 Wires: If selected, the driver will look for confirmation from the router that a transition has occurred, and retry (twice) if there is no reply. If there is still no reply after three tries, the driver will stop trying and report an error (if Warnings is selected on the Reporting tab). This is the recommended mode of operation, but only one router can be connected to the driver.
14. Select Address tab. (For Sony DVS and Sony Router). Specify the address (level) of the
Sony switcher/router you want to control.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 133 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameter as required:
• Sony Address: This is the hex address (level) of the Sony DVS switcher you want to control.
Routing switchers are connected using multidrop connections, UA1 (31h fixed) and UA2 must be set for each model as their own addresses. UA2 is specified
using this Select Address tab.
When the host CPU controls switchers, the corresponding bit of the switcher to be controlled is set to '1' and the command is transmitted.
If more than one of UA2's bits are on, the command is executed, but no response is returned. However, Negative Acknowledgement (NAK) is returned if NAK (i.e. a Negative Acknowledgment because the command format is wrong) conditions exist.
• (For Sony Router 16x16, 32x32 and 256x256, and for Sony 4096 router.) By default all levels are disabled and the level switching is done based on the value entered in
“Address” tab.
Note: If any levels are enabled in the “Levels” tab, then the “Address” tab is ignored.
15. Select Protocol tab. (Available for BTS Venus)
Configure the following parameters as required:
• Protocol: Select ASCII or ESSwitch protocol
• Crosspoint base: Specify is the protocol is Zero-based or One-based.
• Add CR/LF: Check to enable adding of a carriage return / line feed.
16. Select Salvo tab. (Available for Probel System 2L & 3L, and DiTech) Use this tab to enable salvo switching.
If a Switcher/Router is not assigned to any list then it is used as a shared by all the lists.
This is important for routers because some of them supports salvo switching as the router does not use pre-roll time and effects while switching, so it can do some switches during one frame. Routers which does not support this function can only do sequenced switching.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 134 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
17. Select Matrix tab. (Available for Probel System 3L) Use this tab to specify the Matrix
Address.
18. Select Levels tab. Use this tab to specify how many levels to switch on a multi-level router.
Note 1: These are global settings for all inputs and outputs on the router. The automation does not have the ability to do input-specific level switching, i.e. the automation cannot be configured to specify that one input should only switch levels 1, 2, 3 and another input should switch levels 1 through 8. The “Levels to Switch” parameter applies to all inputs on the router.
Note 2: Other routers may not have this tab available in the configuration sheet. The
“Levels to Switch” may be configured in the router itself allowing more flexibility in level switching. Refer to the user notes for the specific device and to the vendor’s
documentation for more information.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 135 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
The options available on this tab depend on the device selected. The following example tabs are from the Probel System 2 (left), Datatek (right), and NVision Router (lower left), and Sony Router (lower right).
Configure the following parameters as required,
• Number of Levels: Specify the number of video and audio router levels.
For Example: The System 3 router itself has internal association tables. There is an association table for source and one for destination. These internal association tables allow the System 3 to be set up such that the audio and video can be different for a given table entry. To use the association feature on the list, set the value of “levels” in level tab of device configuration to 0.
• Router Levels: Select the number of router levels.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 136 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
(For Sony Router 16x16, 32x32 and 256x256, and for Sony 4096 router.) This tab is used to support multiple levels for the SONY Router (S-BUS protocol)
256x256 driver. If any of the levels are enabled in the “Levels” tab, then the
“Address” tab is ignored.
• For NVision:
Add button: When selected launches an 'Add Cascade Data' dialog. On this dialog specify Level name, Level number, and select Video, Audio, and/or AFV.
When finished click OK.
Delete button: To delete an entry, select an existing entry from the display list and then click Delete.
Edit button: To edit an entry, select an existing entry from the display list and then click Edit. A populated Cascade Data dialog is launched. Make any required changes then click OK.
19. Select Switching tab. Use this tab to manually switch inputs and outputs for diagnostic purposes.
This utility is not intended as an on-line substitute for the switcher’s own control panels.
The source and destination names tables must be completed before any sources or destinations will appear in the drop-down boxes.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 137 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Black, Colorbars, Station ID, Initial Input buttons: These selections refer to the sources designated on the System Inputs tab above. If a source and destination are selected in the drop-down boxes, clicking the “Switch” button will cause the switch to occur.
20. Select Diagnostics tab. If required, click the Reinitialize button to reinitialize the device.
21. Select Cart Machine tab. (For LMS Router)
Configure the following parameters as required:
• Cart Machine: Select the cart machine.
• Monitor Enabled: Check to enable switcher monitoring
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 138 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
22. Select the “Device Specific” Channel tab. (Example tab screens are shown for M2100 and Icon Master Aux Routers). Use this tab to specify the Auxiliary Router device. The device object will handle any commands issued by the Aux Bus Router.
About the IconMaster Aux Router:
ADCv12 supports Aux Bus control on the IconMaster. The AxBus can be switched manually through the switch panel and through automation.
IMPORTANT: The AuxBus driver must be requested and added to your Device Server
build prior to use.
23. Select Video/Audio Address tab. (For Miranda HD 1616D Router). Use this tab to select video/audio addresses (0 to 15) of individual frames to be switched.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 139 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
24. Apply the Configuration Changes: When changes are made to a device’s configuration, the Apply button on the configuration GUI becomes active. Click the Apply button to immediately apply that configuration change to the system configuration held in random access memory by the Device Server.
NOTE: Apply does not write the configuration change to the Device Server’s configuration files. This can only be done by using the Save Devices option on the
Configured Devices window’s File menu.
25. Save the Configuration: From the Configured Devices window select File> Save
Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
• Attempting to close the Configured Devices window without first saving any configuration changes, results in the Configuration Manager prompting to save the changes on the Device Server. Accepting this prompt writes the configuration changes to the Device Server’s configuration files as well.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 140 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Switch Only Configuration (General)
The Switch Only device parameters configure the ADC Device Server to switch to a switcher crosspoint and/or trigger a GPI (general purpose interface) contact closure. GPI is an option to the standard ADC Device Server v11 system (requires a GPI board to be installed in the
Device Server).
About Switch Only Device
Switch Only devices are used to:
Incorporate material from external sources, such as network and satellite feeds, cameras and presenters;
Trigger events involving devices not supported by RS422 or RS232 protocols, through a
GPI (general purpose interface).
A Switch Only event inserted in a list can be set up to switch a crosspoint, count down a predetermined amount of time and roll the next event. By entering Auto Upcount for the event associated with a Switch Only device, the event counts down to zero and then holds the list while counting up. A live feed can be switched away from by issuing a Play or Skip command to the transmission list. This is done manually, through the control panel.
When a primary event in a list has an ID that matches the ID of the Switch Only device, the event and device become associated (if the Switch Only device is assigned to the list). The event goes through the transmission process like other types of events. The event (and device) goes through preroll, switches at the end of preroll, counts down a duration, rolls the next event and then goes through postroll. You can also Skip the event and roll the next event.
A Switch Only device can be used as a secondary event which is bound to another event. A secondary event can close a GPI relay at a designated time before or after the primary event goes to air. The duration of the closure can be controlled directly by the event. The event can also be used to tag a primary event with a video overlay (such as a station bug) or generate a tone at some predetermined time before entering a commercial break or returning to program material. This type of usage requires an external device that is controlled by a GPI closure.
Many such devices are available on the open market.
There are two types of secondary GPI events that can be put on a list to control physical contact closure – GPI Contact or Back-Timed GPI. The type of GPI you use depends on the timing of the secondary event.
• GPI Contact runs a contact after the primary event runs.
• Back-Timed GPI runs a contact before the primary event runs. Both GPI events are associated with a Switch Only device whose ID matches the ID of the secondary event.
Switch Only events with the same ID may be played back to back as primary events. There are no restrictions as long as these events are both primary events. Since Switch Only events have no SOM, these events are always contiguous and will always play back to back.
When it is necessary for two switch only events of the same ID to be played consecutively in a transmission list, it is necessary to have two of them configured within the same group of 8 and for both to be assigned to the same transmission list.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 141 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Important Note on switch-only events w/ IconMaster AuxBus: Under certain circumstances using automation with back-to-back, single-headed switch only events, the
Iconmaster AuxBus can fail to switch properly. A simple alternative solution is to configure a two-headed switch only device in situations where back-to-back switch only primaries are accompanied by Switcher Crosspoint (sXP) events.
To Configure a Switch Only Device
1. Under Switch Onlys in the Available pane (right pane), select a device and drag-n-drop it
to the Configured Pane (left pane). For details on assigning a device see: To Assign a
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the Switch Only device in the left pane, right-click and from the popup menu select
Properties. The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select General tab.
Configure the following parameters as required:
• Device Name: Enter a name (using up to 16 characters) for the switcher. This name is used by the automation system to identify the switcher. Systems with multiple switchers should have each switcher assigned unique name.
• Switch Only 1-8: Assign unique names for each Switch Only.
4. Select Prerolls/Postrolls tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 142 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Use Instant Prerolls: Enable (check) to provide instant play/skip capability to the device. It allows the device to have its own short preroll for manual intervention in the list. The feature is designed for coming out of a live or upcounting event as fast as possible when the next event has a near-instant preroll. When using a master control switcher, the preroll must not be shorter than the shortest preroll supported by the switcher.
• Seconds / Frames: When Use Instant Prerolls is enabled, values for preroll seconds and frames must be entered. The preroll value must be at least 4 frames. These values do not have any effect if the Use Instant Prerolls box is left unchecked.
• Switch Only: Select a Switch Only device configured in the previous tab. The settings chosen in the Prerolls/Postrolls tab must be repeated for each Switch Only device. Default is disabled for each device.
5. Select GPI Sheet tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 143 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• GPI Card.
No Card: No GPI Card is connected to the device activated by this event
Card One – Four: Indicates which GPI card is connected to the device activated by this event.
• Contact Number.
Bit 1 – 8: Specifies the contact number (i.e., relay number) on the GPI card to which the external device is connected. The contacts are numbered 0 to 7 by the
GPI board and 1 to 8 by the ADC Device Server.
Add 1 to the GPI board number when the contact number is entered. For example, a device wired to pins 2 (COM 2) on the board should be entered as having Contact number 3
• Pulse Width: Specifies the duration of the GPI contact, in frames (i.e., the length of time the contacts are closed), for primary GPI events. The GPI contact closes when the event goes into preroll.
For secondary events, the contact duration is specified by the event itself.
• Pulse Offset: Specifies the contact closure offset (in frames) for the primary/secondary event associated with a Switch Only device. The contact can be closed at any time during preroll.
When the value is set to zero, the contact closure is closed, starting at preroll, for the duration specified for Pulse Width.
When the value is greater than zero, the contact is closed when the number of frames remaining in preroll reaches this value.
The Pulse Offset value is backtimed from the end of preroll, not from the beginning of preroll. The value must not be larger than the preroll used by the list the Switch Only device is attached to, or the instant preroll, if configured.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 144 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Switch Only: Select a Switch Only device. The settings chosen in the GPI tab must be repeated for each Switch Only device. Default is disabled for each device.
6. Apply the Configuration Changes: When changes are made to a device’s configuration, the Apply button on the configuration GUI becomes active. Click the Apply button to immediately apply that configuration change to the system configuration held in random access memory by the Device Server.
NOTE: Apply does not write the configuration change to the Device Server’s configuration files. This can only be done by using the Save Devices option on the
Configured Devices window’s File menu.
7. Save the Configuration: From the Configured Devices window select File> Save
Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
• Attempting to close the Configured Devices window without first saving any configuration changes, results in the Configuration Manager prompting to save the changes on the Device Server. Accepting this prompt writes the configuration changes to the Device Server’s configuration files as well.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 145 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Requestor Configuration (General)
The following is an example requester configuration. Your requester may have slightly different configuration options. If necessary, refer to the User Notes for your device for complete details on how to configure it.
About Requestors
A requester is a software object assigned to a transmission list that forwards the ID of a missing media event to distributors. The distributor responds to the requester and, if the distributor’s source device contains the missing media, forwards the ID to the GMT list. The
GMT list moves the media to the destination device specified in the requester. A requester can request media based on a push model (for preloading of media) or a pull model (for a static or running playlist).
Most system configurations only require one requester per transmission list; however, additional requesters may be added to segregate the types of material, such as commercials and programs that will be requested from distributors.
Systems using air and protect devices require an additional requester per transmission list; one for each device.
About the Content Handler Requestor
The Content Handler requester is in charge of triggering and monitoring Content Handling process execution when IDs are missing within the ADC transmission lists.
Typically, the main purpose of the Content Handler requester is “media retrieval to playout devices”. However, there is no specific limitation of the triggered processes (this could be something different than “media retrieval”).
The Content Handler Requestor can provide:
On-Air time export to Intelligent Media Manager (IMM).
If Cloning, Content Handler Requester will not requesting missing events
If required the system can be configured to "Abort Un-registered Events"!
To Configure a Requestor
1. From the Configuration Tool, under Requestors in the Available pane (right pane), select a device and drag-n-drop it to the Configured Pane (left pane). For details on assigning a
device see: To Assign a Device to a Device Channel .
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the Requestor device in the left pane, right-click and from the popup menu select
Properties. The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
Save Recommendation: On concluding the configuration performed on any tab, it is
recommended you click Apply to apply the changes. While the changes should save if
you do not, clicking Apply ensures changes are always saved.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 146 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
3. Select General tab. This is where the name is set. This tab also determines if the
Requester will automatically resend the request if the Distributor cannot fulfill it the first time. It also is where the parameters are set if this Requester is to be used on a Push
List.
Configure the following parameters as required:
• Device Name: The name of the requester. This name should be descriptive enough so you know what it is used for. The default is REQSTxx where xx is the position of the requester within the server’s device list. This position is also known as the channel number. You may change the device name to any name you wish. There is a
16 character maximum.
• Request Sending Interval (Frame): (Default 100 frames) Specify the request sending interval in frames.
Usually, GMT system needs more than one minute to transfer one clip, but when loading a new play list, it may generate thousands of missing events and all these missing events will come to the requestor. This sudden influx of events may cause a traffic jam on the network layer, and affect server operations.
Request Sending Interval (Frame)’s default value is 100 frames.
For general usage, usually 1 frame is OK.
If GMT needs to transfer hundreds even thousands event daily, the GMT flow control needs to be considered. Usually, 30 frames is a recommend value in a
GMT system without baseband.
In baseband GMT system with Air-Protect feature, because the GMT needs to combine both Air and Protect disk’s recording, the value of Request Sending
Interval (Frame) should not exceed 5 frames.
• Auto-Retry Missing Media. Used to automatically send a re-request for missing
ID’s.
Retry Interval (Mins): Select (check) to enable the auto-retry function.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 147 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Retry frequency: Specify the retry interval in minutes. (Default: 5) The retry frequency is how often in minutes a request will be sent to look for missing material.
Maximum Retry Times: Specify the maximum number if times to retry for missing media. (Default: 10) This is the maximum number of retries within the given allotted time.
It is important to note that once an event is in the auto-retry mode; the only way to manually stop the retry is to delete the request from the transmission list.
Caution: Once an event is in the auto-retry mode; the only way to manually stop the retry is to delete the request from the transmission list, and then reinitialize the
requester.
• Push Requester Parameters. This section is used when this Requester is being used for a Push List.
Play Events: Off-air simulated (or “faked”) playing of the moved event. Used for generating an AsRun log entry.
Register Events When Moved: The requester not only removes the
"REQUESTED" status, but causes the list to turn the event BLUE after the operation. This provides an indicator to the operator.
If both ‘Register Events When Moved’ and ‘Play Events’ are enabled AND you have used an available GMT list to load the push list into (as opposed to a standard transmission list) then not only will each event turn BLUE, it will be marked PLAY and then DONE (each event is run in a “fake” manner so that a DONE status appears and the event is AsRun logged).
For Push Lists, if both ‘Register Events When Moved’ and ‘Play Events’ are enabled, ensure option "Release Tension When Cued" in the List Properties >Options tab is unchecked (the default is checked).
4. Select Qualifiers tab. Use this tab to specify the qualifications that this requester uses to determine if it should make requests for media. These parameters would be used if more than one video server was assigned to a transmission list and each server has specific material ID’s in it. These parameters can also be used to optimize performance.
Specify events with or without segments, events that run less than a specific duration, and qualify events based upon the range of the ID. Usually you will need to set the request qualifiers if you have multiple requesters on a transmission list, and these requesters are requesting media from different sources.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 148 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Program – Spots. Configure this Requester to request only Programs or only Spots.
No Events With Segments: To be recorded, events cannot have segments. If enabled (checked), Multi-segment IDs cannot be requested. Default is disabled.
Events With Segments Only: Events must have segments in order to be recorded. If enabled (checked), single spots will not be requested. Default is disabled.
NOTE: If both of the above boxes are left at their default settings (both disabled), you
can request all material: both single spot IDs and multi segment IDs.
• Duration Range: Restrict the length of clip to be requested by this particular
Requester. The time parameters are only active if the associated box is checked.
No Events Greater Than (Mins): Click to enable, and then specify a maximum number of minutes allowed for an event. Default is 5 minutes.
No Events Less Than (Mins): Click to enable, and then specify a minimum number of minutes allowed for an event. Default is 0 minutes.
• I.D. Range: Restrict a Requester to a particular ID range. The range needs to be clearly definable and should consider that the range is based on an alpha numeric
Search Range that places the numbers 0 through 9 at the top and then capital letters
A to Z, then lower case letters a to z. The range is only active if the option box has been checked.
Only Record Events with ID Between: Check to enable, and then specify range.
Exclusion: No Events with ID Between: To invert the range, and use it to exclude the material in that ID range, click the button labeled “Only Record
Events with ID Between” button. The appearance of the button changes as shown below, and the range specified is now the range to be excluded.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 149 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
_ to _: Specify a range (minimum and maximum) for allowable IDs to be recorded. Any IDs that fall outside the specified range will not be recorded.
5. Select the Priority tab. This tab allows the Requester to send the Distributor a priority of each item it requests. This parameter should be used to indicate how the Distributor should treat each request when it is time to transfer it.
Configure the following parameters as required.
• Weighting: Use this parameter to tell the requester to weight, by time, all requests.
This Weighting value is used to prioritize requests made by this Requester. The
Weighting value is a time value that is added to the time in the GMT List event’s
“Time” column. The requester adds this time to an event’s projected on-air time and the result is the time that the media is expected to be needed. Weighting allows some level of prioritization of requests from different requesters on the same or different transmission lists.
Note: Events with a weighted time stamp are processed after events without a
weighting value added.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 150 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
To prioritize the transfer sequence of requesting events on the GMT List:
Delay the less urgent event transfer priority by adding a "fixed Time weight", such as 6 hours (06:00:00:00") to each event associated with a Requester.
For time critical requesting events, such as one from a on-air playlist, add a "zero weight" to its process time.
In this way, less urgent events will yield their process priority to the critical one.
NOTE: Normally, a Requester associated with a push list to prepare media for tomorrow's playlist will have a weight added to all requesting events, so that they will
not take over the GMT resource for On-air playlist missing events.
• Transfer Priority based on: Set the transfer priority.
On-Air Time: The GMT event transfer sequence for this particular Requester is based on its On-Air time. When this parameter is selected, the earlier On-Air time is scheduled to transfer first. The Requester—and by association the
Distributor—use the time of day in the time field to determine what items are needed first. An item inserted into a transmission list is slotted into the list of things to be transferred based on its On-Air time relative to those items already set to transfer. This slotting is evident to the user on the GMT List.
First-in-First Serve: The GMT event transfer sequence for this particular
Requester is based on the sequence received by this Requester. When this parameter is selected, the requester timestamps the current time on the event for
GMT to prioritize the schedule transfer. Items are transferred in the order the requests were received and, secondarily, what order the Distributor determines it can fulfill the request. If an item is added to the transmission list, then it will go to the bottom of the priority list no matter when it is scheduled to air.
6. Select Routing tab. (For Requesters and Multi-requesters) This tab allows the Requester to be set to do certain types of transfers. Although all Modes can be selected, some of the types should not be used together on one Requester. Some modes, when used together indicate using a double-hop or multi-hop GMT.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 151 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required. A single or any combination of routing modes can be specified.
• Baseband: Real time video signal (either analog or digital). Baseband includes SDI and SPIT modes. Default is enabled. This is used for real-time copies from tape to video server.
• Fibre: JPEG or MPEG compressed data files. Fibre mode is typically used when both the source and destination devices are video disks. Fibre transfers are typically nonrealtime. Default is disabled. A Fibre transfer will be selected when a Fibre channel or
Fibre Hub is used to move material from one device (typically a video disk) to another.
• Wan: Wide Area Network. This routing mode implies the transfer protocol will be
FTP. Source and Destination FTP server can be geometrically separate apart. This type of transfer is used specifically for Wide Area Network GMT.
• Archive: Usually there is a SCSI connection between the archive system and the video disk server. This mode is used when transferring material to and from a digital archive device source (e.g., a StorageTek or Ampex DST) under control of an
Archive Manager (e.g. Avalon, PetaServe, DIVA or Flashnet/SGL). Default is disabled.
Push-to-Archive: Check to enable push media to archive storage operation,
(Activates Take “group-ID” from “ReconcileK” option. See below.) The Pushto-Archive is used in conjunction with the Archive type move when an Archive
Push List is being implemented.
• SOM is required for Baseband: Sometimes, when a media is still ingesting, its metadata is not entered into the ADC database, but a playlist event to use this media is entered into a playlist. In this scenario, if the playout server does not have the ID, a baseband GMT that is requested and scheduled will result in a failed transfer.
This parameter determines whether Baseband GMT moves will take place if there is no database record.
Enable (check) this option to prevent this kind of event to transfer prematurely. This ensures a transfer will not start without metadata "SOM" entered into the event either manually or automatically from the ADC Database. The most typical way to get an
SOM is to create a database record.
Note: This should be checked if your Baseband source device is a Cart Machine or a
VTR.
• Take “group-ID” from “ReconcileK”: Check to enable. (This option is active when
Push-to-Archive is selected.) VDCP protocol allows Archive Manager to organize its storage into "Groups", such as "Spot" group, "Program" Group, etc… This "Group" name can also be specified in the "Archive Device--General Tab" UI.
For a ‘push media to archive storage operation’, the user may allow specification of a
"Group" name for each event different than the one specified in "Archive Device--
General Tab" UI, or different from event to event.
Enable (check) this option to specify the archive "Group" name in the "Reconcile
Key" field. When this option is enabled, by the time each push event reaches the
Archive Device to push to archive, the "Group" name that comes with event determines with which Group in the archive it is categorized.
7. Select Destination tab. (for Requestor) Use this tab to specify where the Requester sends the material (i.e. the destination device that receives the requested material). This
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 152 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager device should be a record port of a video disk server. Other devices are not supported in this release. Use this tab to tell the
Configure the following parameters as required:
• Server: This is the server name that the destination device is physically connected to/resides on. Choose the correct server from the dropdown menu.
• Device: Choose the device name associated with the destination device from the dropdown menu. These are configured devices available on the previously specified
Device Server.
• Fibre Handle: This is the unique fibre address assigned to the destination video disk.
Each video disk on a fibre network must have a unique address. Valid entries are 0 through 99.
Note: By using the up/down buttons, values over 99 can be entered.
The Fibre handle is ONLY set if this Requester is set to use Fibre or Archive routing in the previous tab. The Fibre handle should be the handle of the Destination device.
• FTP Handle: FTP Handle is used only for WAN GMT. For a ProxyFTP device to log into a FTP server, a set of login parameters must be correctly specified. Parameters such as: IP-address, Port-Number (normally set to 21 for FTP), User-Name,
Password, login-Directory, etc… are often required parameters.
When configuring an ADC ProxyFTP device to transfer media from a source to a destination, each FTP server is also assigned a unique FTP-Handle. This FTP
Handle is a two-digit integer automatically assigned to a FTP server as a "Site #".
This FTP-Handle is often referenced as a parameter in the Requester and Distributor to address an FTP server, either for source, or for the destination of an FTP transfer.
8. Select Distribution tab. (For Requesters and Multi-requesters) Use this tab to specify which GMT Distributor that this requester communicates with to acquire material (i.e. the
Distributor that will be asked to fulfill the requests). The chosen distributor may reside on the same device server as the requester, or may be on a different device server. This setting should point to the Distributor that should be queried first.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 153 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Server: Choose the Device Server from the dropdown menu where the distributor object identified in the Device field (below) resides.
• Device: Choose the name of the distributor from the dropdown list that requests the distributor representing the primary source of material from this requester. These are the Distributor objects configured on the Device Server specified above.
9. Select MultiDestination tab. (for MutiRequestor) Use this tab to specify the destination devices (the devices that receive the requested material). These devices should be a record port of a video disk server. Other devices are not supported in this release.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 154 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Add destinations as required:
• Click Add to specify destination.
Configure the following parameters as required:
Server: This is the server name that the destination device is physically connected to. Choose the correct server from the dropdown menu.
Device: Choose the device name associated with the destination device from the dropdown menu.
Fibre Handle: This is the unique fibre address assigned to the destination video disk. Each video disk on a fibre network must have a unique address. Valid entries are 0 through 99.
Note: By using the up/down buttons, values over 99 can be entered.
- If a non zero value is entered into the Media Client for the Fibre Handle parameter on the Single Spot/ MultiSpot/Multi Seg configuration Archive tab, it will override the Fibre handle specified in the Device Server configuration for the
Distributor and all ‘Send To Archive’ and ‘Get From Archive’ operations will use this new handle.
- If the Fibre Handle value is set to 0 on the Media Client for the Fibre Handle parameter on the Single Spot/ MultiSpot/Multi Seg configuration Archive tab, the
Fibre Handle value set in the Distributor configuration is used.
FTP Handle: For a ProxyFTP device to log into a FTP server, a set of login parameters must be correctly specified. Parameters such as: IP-address, Port-
Number (normally set to 21 for FTP), User-Name, Password, login-Directory, etc… are often required parameters.
When configuring an ADC ProxyFTP device to transfer media from a source to a destination, each FTP server is also assigned a unique FTP-Handle. This FTP
Handle is a two-digit integer automatically assigned to a FTP server as a "Site
#". This FTP-Handle is often referenced as a parameter in the Requester and
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 155 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Distributor to address an FTP server, either for source, or for the destination of an FTP transfer.
When finished click OK.
10. Select the Diagnostics tab. Use this tab to view the retry status for the events.
The following parameters can be reviewed:
• Total ID Requested: This is the total number of ids that has been requested.
• Retry Waiting ID Counter: This is the number of ID’s waiting in the buffer for the next retry.
• Retry ID Counter: This is the number of IDs currently being handled by Distributors-based on a Retry--whose status has not been returned by the Distributor.
• 1st Time Requested ID Counter: This is the number of ID’s currently being handled by Distributors—for the first time—whose status has not been returned by the
Distributor.
• Update button: Click to manually update the values in the field listed above at that particular instance. However the values are updated automatically, whenever a value has changed in one of the fields.
• Reinitialize button: Click to l reset all outstanding requests to zero.
11. Select the Content Handler tab. (Used for Content Handler Requester only).
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 156 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
This tab dialog is comprised of the following:
• Content Handler: This parameter displays the assigned number of the Content
Handler.
• Devices pane: This box lists all Content Handler published processes. When a
Content Handler requester device is assigned to a transmission list, missing IDs initiate the execution of the processes that have been selected in the Devices pane.
Content Handler requester is in charge of the processes triggering and monitoring until all of them terminate within the Content Handler engine.
Note: A single process selection is commonly configured.
• Options pane: This box lists all the parameters that must be passed to Content
Handler engine when triggering processes. The expected parameters depend on the process design itself: this is a customer oriented configuration. Some parameters can be dynamically filled in by the Content Handler requester driver taking into account the information of the missing events.
The following list of dynamic values are currently supported:
%EVENT_SOM%: If an option has this value, then the value is dynamically replaced with the Start Of Message information (timecode format) of the missing event.
%EVENT_DUR%: If an option has this value, then the value is dynamically replaced with the Duration information (timecode format) of the missing event.
%EVENT_OAT%: If an option has this value, then the value is dynamically replaced with the On Air Time information (timecode format) of the missing event.
%EVENT_RTA%: If an option has this value, then the value is dynamically replaced with the Remaining Time to Air information (timecode format) of the missing event. Note this only work for values lower than 24 hours.
%EVENT_SEG%: If an option has this value, then the value is dynamically replaced with the Segment information (numeric format) of the missing event.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 157 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
%EVENT_BUFFER%: If an option has this value, then the value is dynamically replaced with all information (recfm80 format coded base64 ) of the missing event.
Configure the following parameters as required:
• Add Options: Click this button to add a new line to the Options pane. Afterward, the user must edit the cell values of the new line (first cell is the option name, second cell is the option value).
EXAMPLE: How to setup CH process execution priority based on the on air time.
Add an option with “REQUEST_PRIORITY=%EVENT_RTA%”.
The “REQUEST_PRIORITY” option property value is automatically filled in with the remaining time to air information of the missing event.
This timecode information is then be used by the Content Handler engine to calculate the execution priority.
• Remove Option: Select a currently specified option and then click this button to remove the selected line from the Options pane.
12. Select the CH Qualifiers tab. (Used for Content Handler Requester only)
Configure the following parameters as required:
• Request secondaries: Check this option to request secondaries. When enabled, the
IDs of missing secondary events will also initiate Content Handler process execution.
• Abort unregistered requests: Check this option to abort any unregistered requests.
When enabled, the missing events that are removed from the lookahead will cancel the process execution within Content Handler engine.
Note: An event can be removed from the lookahead if the size of the lookahead is
reduced or if it is simply deleted from the lookahead.
• List of exclusions: This pane lists the missing IDs that must NOT BE USED to initiate process execution. Specify the list of IDs to exclude, separated by semicolons.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 158 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
13. Apply the Configuration Changes: When changes are made to a device’s configuration, the Apply button on the configuration GUI becomes active. Click the Apply button to immediately apply that configuration change to the system configuration held in random access memory by the Device Server.
NOTE: Apply does not write the configuration change to the Device Server’s
configuration files. This can only be done by using the Save Devices option on the
Configured Devices window’s File menu.
14. Save the Configuration: From the Configured Devices window select File> Save
Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
• Attempting to close the Configured Devices window without first saving any configuration changes, results in the Configuration Manager prompting to save the changes on the Device Server. Accepting this prompt writes the configuration changes to the Device Server’s configuration files as well.
Distributor Configuration (General)
The following is an example distributor configuration. Your distributor may have slightly different configuration options.
About Distributors
A distributor is a software object assigned to specific output connections of a device. A distributor can be assigned to any type of device: baseband, fibre channel or archive. Several distributors can be assigned to some types of devices to handle multiple requests or move several different spots at a time. Most video file servers, for example, are able to move multiple spots simultaneously on a single fibre channel.
When a distributor receives an ID from a requester, it parses duplicate requests, transport and routing limitations and format mismatches.
• If the device contains the media requested by the requester, it forwards the missing media event’s ID to a GMT list.
• If the distributor does not contain the requested media, the event’s ID is passed to the next distributor.
• If no other distributor is available, an error message is passed to the requester.
Errors are displayed in the transmission list window.
To Configure a Distributor
1. From the Configuration Tool, under Distributors in the Available pane (right pane), select a device and drag-n-drop it to the Configured Pane (left pane). For details on assigning a
device see: To Assign a Device to a Device Channel .
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the Distributor device in the left pane, right-click and from the popup menu select
Properties. The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 159 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Save Recommendation: On concluding the configuration performed on any tab, it is
recommended you click Apply to apply the changes. While the changes should save if
you do not, clicking Apply ensures changes are always saved.
3. Select General tab. This is where the name is set.
Configure the following parameters as required:
• Device Name: The name of the distributor. This name should be descriptive enough so you know what it is used for. The default is DISTRxx where xx is the position of the distributor within the server’s device list. This position is also known as the channel number. You may change the device name to any name you wish. There is a
16 character maximum.
4. Select Routing tab. Use this tab to configure routing. Source and destination devices can reside on any device server. This sets how the Distributor will execute the transfer of material.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 160 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Routing: Select one of the available routing options (the default is Baseband). This section allows configuring what type of media transfer this Distributor will perform.
Each type of move is very specific. While a Requester can do multiple types of routing, each Distributor can only do one type.
Baseband: Real time video signal (either analog or digital). Baseband includes
SDI and SPIT modes. Default is enabled.
When baseband mode is selected, the Intermediate Destination becomes active.
Fibre: JPEG or MPEG compressed data files. Fibre mode is typically used when both the source and destination devices are video disks. Fibre transfers are typically non-realtime. Default is disabled.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 161 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
When Fibre mode is selected, the ‘Send Disk Command to” becomes active.
Archive: Usually a SCSI connection between the archive system and the video disk server. This mode is used when the source device is a digital archive device
(e.g., a StorageTek or Ampex DST) under control of an Avalon Archive Manager.
Default is disabled.
WAN: Wide Area Network. This routing mode implies the transfer protocol will be
FTP. Source and Destination FTP server can be geometrically separate apart.
• Intermediate Destination: (Active when Broadband is selected). When configuring a system to do baseband double hop, a fibre distributor needs to be in the search loop. This means that the fibre distributor needs to point to the intermediate destination, thus be on the same device server.
The options in this section differ depending on the type of move selected. For example, if an Archive move was selected, it asks which Archive Device on which
Device Server it will be using. If a baseband type is selected, a section for intermediate destination will appear.
Server: Use the pull-down list and select a server.
Device: Use the pull-down list and select a device.
Fiber Handle: The fibre handle needs to be the same as the intermediate disk.
This is the unique fibre address assigned to the destination device. Each device on a fibre network must have a unique address. Typical valid entries are 0 through 99.
• Single-Hop Archive Transfer Only: This parameter determines if this will be a single hop or double hop transfer.
Checked: If it is a single hop, then the destination the Distributor sends the data to will be its final destination.
Unchecked: If this box is left unchecked, it indicates it is a double hop which means the destination this Distributor sends the material to is an intermediate destination. Double hop transfers occur as follows:
- First, the source baseband device will record to an intermediate disk. The source and intermediate device will reside on the same device server.
- Second, GMT will transfer the recorded media via fiber transfer mode from the intermediate destination to the final destination device– the second hop. The destination device resides on any device server, no longer the same device server as the source device.
In an Air and Protect scenario, there is one play and one record to an intermediate disk. After the transfer to the intermediate disk finishes the baseband distributor determines if the transfer is complete. In order to ensure the transfer is complete, it initializes two follow up fibre transfers. The first transfer is to the air disk and the second is to the protect disk which completes the transfer.
• Send Disk Command to: (Active when Fibre is selected). Since disk vendors govern whether a fibre transfer can go to either the source or destination, the fibre routing mode is configurable. Depending upon what is supportable by the disk, specify to send the commands to either:
Destination device: (Default)
Source device.
• Standard Archive: (Active when Archive is selected)
Server: Choose the correct server from the dropdown menu.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 162 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Device: Choose the device name from the dropdown menu.
Single Hop Archive Transfer only: Check to enable the source baseband device to record directly to destination device.
• Proxy FTP: (Active when WAN is selected)
Server: Choose the correct server from the dropdown menu.
Device: Choose the device name from the dropdown menu.
5. Select Next Ring tab. Use this tab to configure this Distributor to pass requests on to another ring of Distributors. This allows for multiple search paths for material and may be required or may be used to optimize the operation of GMT.
• The device selected with the assigned distributor must reside on the correct server selected as well.
• A Next Ring search path may only be configured on an “entry point” Distributor – that is, the first Distributor in a search path to which a Requester is directly passing requests.
• At present, Automation only supports one level of Next Ring request forwarding.
Next-ring pointers are used to construct multiple distributor-rings to do media searches.
This feature is especially important in a multi-channel facility. In this type of environment, the user wants to achieve three goals simultaneously: a) Share distributors among all play-lists, b) Prioritize the search sequence, and c) Balance the load among all sources.
The next-ring feature allows each request packet from each transmission list to travel the entire ring and return back to its entrance distributor before moving into the next-ring search of low priority devices (such as archive and baseband devices) instead of terminating the search at the first ring. It is only possible to construct two (2) rings.
Configure the following parameters as required:
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 163 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Distributor: This is where the first Distributor in the next search ring is set. This can be set in different ways as each Distributor may be able to pass requests on to enter the search ring at a different location.
Server: This is the server name that the destination device is physically connected to. Choose the correct server from the dropdown menu.
Device: Choose the device name associated with the destination device from the dropdown menu.
6. Select Source tab. Use this tab to specify the device supplying material and also to link to additional distributors. The source device can be a cart machine, a standalone VTR or a play port of a video disk server.
Configure the following parameters as required:
• Server: This is the server name that the destination device is physically connected to. Choose the correct server from the dropdown menu. This parameter specifies which Device Server this Distributor is looking at to get its device for the material it is to transfer. Once the Device Server is selected, the devices configured on that
Device Server are available for selection.
• Device: Choose the device name associated with the destination device from the dropdown menu.
• Fibre Handle: This is the unique fibre address assigned to the destination video disk.
Each video disk on a fibre network must have a unique address. Valid entries are 0 through 99.
Note: By using the up/down buttons, values over 99 can be entered.
Fibre Handle is used only if this Distributor is using Fibre, Archive or WAN routing. A fibre handle is required for all fibre transfers to be executed. A fibre handle is required for Global Delete Distributors, although it may be the fibre handle of any device among the delete targets.
If this is an Archive or WAN Distributor, the fibre handle set here may refer to the destination for Archive and WAN transfers.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 164 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Wait until missing media is available: When enabled (checked), GMT waits for the missing media on the source device specified on the distributor. The missing media is placed on the GMT list and stays red until the media is found. Typically used on a
VTR.
If your Baseband source device is a Cart Machine, you may wish to enable this option.
If your Baseband source device is an external VTR, this option must be enabled.
This forces the Distributor to insert GMT events on the GMT list even if they are missing from of the Cart Machine or if an operator is required to insert the tape into the external VTR. When disabled (unchecked), the missing media is skipped and media searching passes down to the next available distributor (or returns an error to the play list). This gives the operator time to locate and insert the tape.
When disabled the source material is not found in the source machine, nothing is put on the GMT list, and the transfer fails without the operator being allowed to find the source tape.
NOTE: This option is only available with baseband and archive routing. Fibre mode is not supported.
• Next Distributor: Specify an additional distributor for locating material.
This parameter is used when there is more than one place the missing material may be found. By telling this Distributor to pass the request on to another Distributor, you are creating a chain. Without this, the request would fail if the material could not be found in the device listed in this tab.
For example, you may have multiple distributors, each associated with a different cart machine. If a distributor cannot process a request because the requested material is not within its source device (i.e., the ID is not in the cart machine), it can pass the request to the next distributor in the chain which may be able to locate the material.
All linked distributors must reside on the same device server and be assigned to the same GMT list. It is recommended to link the last distributor back to the first distributor to form a closed loop so that any distributor on the linked list can be the initial distributor (as pointed to by a requester in a multi-requester environment).
7. Select Segments tab. Two kinds of multi-segment file name conventions exist in a videodisk and archive system; the Single-File-Multi-Segment (SFMS), or the Multi-File-
Multi-Segment (MFMS). In an SFMS convention, all segments with the same program ID will reference the same file name without a segment number. In an MFMS convention, each segment will have a unique file name using the media ID name with a one or two digit segment number forms this unique file name.
Therefore, there are three ways a multi-segmented program event can be translated into a unique file name in a videodisk or archive system: (1) By using the ID for all segments,
(2) Modifying the last digit of the ID with the segment number, (3) Modifying the last 2 digits of the ID with the segment number. At many facilities, the methods above would be mutually exclusive to prevent confusion within the video server or archive device.
In order to help prevent file name conflicts for multi-segment events, the Segments tab is used to configure the search order for multi-segment IDs and how many digits of its associated segment number will be used to create the filename for a particular media ID segment.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 165 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Max ID Length: Specify the maximum ID length of the segment. Options are 8 or 32.
(Default: 8)
• Number: Specify how many of the last digits are to be used to form an ID name.
Highlight a segment number, and then
Use Up/Down buttons are used to specify the direction and order to be used to search for segmented ID files in a device.
Use Enable/Disable buttons are used to enable or disable searches for the selected number of last digits to form a segmented ID. When enabled, it has a red background.
• Use Distributor Segment setting over Disks: When enabled (checked), the GMT fiber transfer refers to the distributor’s segment setting instead of the destination disk’s setting.
Note: The ‘Wait for missing media until it is available function” is currently not
supported (grayed out) in this mode, because it is unknown which ID should be put in
GMT list to wait.
8. Select Global Delete Targets tab. If this Distributor is to be used to handle delete requests to multiple video servers, this is where it will be configured. Some systems will have the requirement to delete from video servers that cannot be accessed directly from
Media Client. This tab allows for deletion of material from those video disks. Under the
Routing tab, this Distributor MUST be configured to do fibre transfers.
Global Delete Targets can be added or deleted, they cannot be edited. Each target can be set to access any Video Server on any Device Server. Each target MUST have a fibre handle configured as well
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 166 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Add button: Click the Add button to display a dialog box allowing you to enter crosspoints.
NOTES:
(1) The Global Delete target should be a video disk.
(2) The only allowable routing mode is fibre mode.
(3) If Delete Target specifies a VTR, cart machine or archive destination, or if the routing mode is baseband or archive, the Global Delete command is ignored.
9. Select Diagnostics tab. When this tab is selected the real-time internal log is displayed.
The Distributor can also be reinitialized from this tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 167 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Mode: Select one of the diagnostic modes: Event Log, ID Trace, or Buffer Dump
Event Log: An event log is a real-time status display for the Distributor. As requests are processed by the Distributor, the RunState Status pane will update dynamically and display the current status of the operation.
If the diagnostics window has been opened in modeless state, the data written to the RunState Status window will also be written to the text log file.
ID Trace. When selected, the diagnostics window will display an Input ID /
Segment field.
Enter an ID you wish to trace in the Input ID field (and a segment number if this is a multi-segment ID) and click Start Trace.
The current status of the ID is displayed in the RunState Status pane. If the diagnostics window has been opened in modeless state, the status is written to the text log file as well.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 168 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Buffer Dump: When selected, the contents of the Distributor’s buffer can written to the RunState Status pane.
Click the Start Dump button and the Distributor will write the contents of its buffer to the RunState Status pane.
This action does not clear the contents of the Distributor’s buffer – that can only be accomplished by clicking the Reinitialize button. If the diagnostics window has been opened in modeless state, the buffer data will be written to the text log file as well.
• Setup Status: Displays an event log in a real-time for the Distributor.
• RunState Status: Displays contents for a Trace Log or Buffer Dump.
• Start Dump button: Available in Buffer Dump mode. When selected the Distributor writes the contents of its buffer to the RunState Status pane.
This action does not clear the contents of the Distributor’s buffer – that can only be accomplished by clicking the Reinitialize button. If the diagnostics window has been opened in modeless state, the buffer data is written to the text log file as well.
• Reinitialize button: Click Reinitialize to clear the Distributor’s collection of pending requests and reset all of its internal variables to zero. Any pending requests on the
Transmission List will be marked FAILED.
10. Apply the Configuration Changes: When changes are made to a device’s configuration, the Apply button on the configuration GUI becomes active. Click the Apply button to immediately apply that configuration change to the system configuration held in random access memory by the Device Server.
NOTE: Apply does not write the configuration change to the Device Server’s configuration files. This can only be done by using the Save Devices option on the
Configured Devices window’s File menu.
11. Save the Configuration: From the Configured Devices window select File> Save
Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
• Attempting to close the Configured Devices window without first saving any configuration changes, results in the Configuration Manager prompting to save the
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 169 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager changes on the Device Server. Accepting this prompt writes the configuration changes to the Device Server’s configuration files as well.
Proxy Device Configuration (General)
ProxyFTP devices are software gateways the automation system uses to initiate FTP file transfers between video servers over a wide area network (WAN). Like archives, they are not media devices in the sense that they are not assigned to lists, they cannot cue and play, and they are not capable of producing an I/O stream. Instead, ProxyFTP devices interpret commands from the automation system and pass them on to the video server’s file system through an Ethernet connection to the WAN. FTP file transfers using a ProxyFTP device can only be accomplished though the use of GMT components. For more information about
ProxyFTP devices and GMT see section: Global Media Transfer .
The following example is an example Proxy device configuration. Your device may have different options. If necessary, refer to the User Notes for your device for complete details on how to configure it.
To Configure a Proxy Device
1. Under Distributors in the Available pane (right pane), select a device and drag-n-drop it to
the Configured Pane (left pane). For details on assigning a device see: To Assign a
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the Proxy device in the left pane, right-click and from the popup menu select
Properties. The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select the General tab. The options available on this tab depend on the device selected.
For example: The following General tabs show options for PXFTP (left) and Factum
(right) selections.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 170 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following properties are required:
• For PXFTP.
Device Name: (Default: PXFTP)This parameter defines the name of the PXFTP driver into the adc100nt configuration..
Designated FTP Resource Manager: In the ADC system, there is one
"Siteconf.ini" file to store the login parameters of each configured FTP server site. To prevent conflict, the information in this "Siteconf.ini" file is shared among all ProxyFTP devices for "read access", but only one ProxyFTP device is granted
"write access" to create and edit this file.
Enable (check) this option to give this particular ProxyFTP device the right to create, add, delete and modify this "Siteconf.ini" file. If an ProxyFTP device is assigned as FTP Resource Manager, the ProxyFTP device name will be displayed with an associated asterisk "*" mark in the Configuration Device window.
Reinitialize button: Click to reinitialize the ProxyFTP device. When selected a message dialog is displayed to confirm the action:
• For Factum DBS.
Device Name: (Default: FACTUM)This parameter defines the name of the
Factum driver into the adc100nt configuration..
Host Name: (Default: “localhost”) This parameter identifies the default address of the Factum DBS100 System the driver is communicating with. This parameter can take an IP address in either dotted or alphanumerical notations.
In Folder: (Default: C:\IN\) This parameter specifies the folder path, where the input files for the Factum DBS100 device driver will be placed to. The device driver will check this folder 20 times per second and process the input files. After being processed, the field is deleted from the input folder.
Notes:
Always specify the last slash character in the configured path. For example:
“C:\IN\” – correct, “C:\IN” – incorrect.
The driver processes files in ascending order according to their filenames and those files should have the “.xml” extension.
Out Folder: (Default: C:\OUT\)This parameter specifies the folder path, where the output files with the responses from the Factum DBS100device driver will be placed to.
Notes:
Always specify the last slash character in the configured path. For example:
“C:\OUT\” – correct, “C:\OUT” – incorrect.
The output file with the response from the Factum DBS100 server will have the same filename, as the input file name. If a file with such a name already exists in the folder, it will not be rewritten until the previous file is removed.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 171 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Logging: (Default: false (unchecked)) This parameter enables or disables logging of actions performed by the Factum DBS100 driver. It’s recommended to check this control if any troubles occurred while working with the proxy device server (logging may require a lot of disk space for log files).
NOTE: The logging information is stored on a local hard drive, disk “C:\”. The file name is formed according to the following scheme: log_Factum_mm_dd_yy_xxxx.txt, where mm_dd_yy – current date and xxxx – random generated number.
4. Select the Disk Type tab. (Proxy FTP only)
Configure the following properties are required:
• Select the disk type from the listing of available devices.
Generic (or Generic FTP): Select to specify using the industry standard “RFC
959” FTP protocol. When selected, Ext List becomes active.
Omneon: Select to specify using Omneon’s proprietary media format (instead of
.MXF format) for FTP transfers using the Omneon proprietary API.
This functionality requires the use of Omneon’s proprietary DLL module. It is strongly recommended to use a separate bridge computer to hold this ProxyFTP device alone.
Isilon: In this mode FTP Proxy checks the existence of clips with Size command and it will not modify files names.
• Passive Mode: Check to enable.
• Mixed Mode: (For Pinnacle only)
Unchecked (Default). This selection indicates both source and destination are
Pinnacle disks (same as before)
Checked: Make this selection when one of the disks is non-Pinnacle disk (e.g.
NEXIO) running in Pinnacle compatible mode
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 172 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
When checked, WAN GMT tries to identify which disk is Pinnacle and which is non-Pinnacle, based on login greeting message (220 reply code). For Pinnacle disks, the greeting message should contain “Pinnacle Systems”.
When transferring in “Mixed Mode”, WAN GMT issues extra commands to comply with non-Pinnacle disk.
• Ext List: (Default: *). (Active when Generic is selected) Specify file extension(s) for
FTP transfer. The operator may specify “mxf” as the extension for FTP transfer.
The default value “*” means any extension is qualified for the specified media ID.
If multiple file extensions are specified in the FTP transfer, they can be entered into the same extension box, but separated by space.
UPD1 support of “Files Extensions” option. (added for Isilon)
The delimiter for extensions is “,”. Proxy will always process files without extension + files with specified extensions. The logic of transferring is the same as for Generic type: if the destination has any of the source files, the Proxy will not transfer anything.
5. Select the Site List tab. (Proxy FTP only)
Configure the following properties are required:
• Add button: Launches a site management dialog. Use this dialog to specify transfer sites. When finished click OK.
• Edit Button: To edit an existing site entry, select an entry from the site list display and then click Edit. The site management dialog is displayed populated with the parameters currently specified for the selected entry. Make changes as required, and then click OK.
• Delete button: To delete an existing site entry, select an entry from the site list display and then click Delete.
6. Select the Connect tab. (Proxy FTP only)
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 173 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following properties are required:
• Destination: Specify the destination device for the transfer. Use the dropdown arrow to select for a list of available devices.
• Source: Specify the source device of the transfer. Use the dropdown arrow to select for a list of available devices.
• Meta data required for transfer: Enable (check) to include metadata in the transfer.
Note: For the Isilon disk type ensure the “'Metadata required for transfer” option is
Disabled (unchecked). This is because only one file, which has the same name as
event ID, will be transferred.
7. Select the Diagnostics tab. This tab displays diagnostic information for the PXFTP.
(Proxy FTP only)
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 174 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
8. When finished click Apply, then click OK.
9. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 175 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Transcode Configuration (General)
The following is an example Transcode configuration. Your device may have different options. If necessary, refer to the User Notes for your device for complete details on how to configure it.
To Configure a Transcode Device
1. Under Archives in the Available pane (right pane), select a Transcoder device (i.e.
FlipFactory or FPD VAST BitSCREAM) and drag-n-drop it to the Configured Pane (left
pane). For details on assigning a device see: To Assign a Device to a Device Channel .
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the Transcode device in the left pane, right-click and from the popup menu select
Properties. The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select General tab. The options available on this tab depend on the device selected.
For example: The following General Tabs show options for FlipFactory (left) and
BitScream (right) selections.
Configure the following parameters as required:
• For Flip Factory:
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 176 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Device Name: This parameter defines the name of the driver into the adc100nt configuration. (Default: FLIPF).
Host Name: This parameter identifies the Telestream Flip Factory System the driver is communicating with. This parameter can take a name or an IP address.
(Default: localhost).
Port: This parameter identifies the Telestream Flip Factory System the driver is communicating with. This parameter can vary from 0 to 65535. Default parameter is “9000”.
Factory Name: This parameter defines the factory that will be used to transcode the files. This parameter must be configured according to the Telestream Flip
Factory settings. Default parameter is “”.
Priority: This parameter defines the priority to attach to each transcode command. The supported values are from 1 (lowest) to 9 (highest). Default parameter is “5”.
User Name: This parameter defines the user name that will be used to access specified factory for transcoding the files. This parameter must be configured according to the Telestream Flip Factory settings. Default parameter is “”.
Password: This parameter defines the password that will be used for the current user name to access specified factory for transcoding the files. This parameter must be configured according to the Telestream Flip Factory settings. Default parameter is “”.
Polling: This parameter enables or disables polling the Flip Factory server by the
ADC Flip Factory Transcoder driver. The polling period is about 2 seconds. It’s highly recommended to check this control, otherwise the Flip Factory status information will not be monitored while transcoding nothing. Default parameter is false (unchecked).
Timeout (msec): This parameter identifies the Polling period for the Telestream
Flip Factory driver in milliseconds. This parameter can vary from 1000 to 60000.
Default parameter is “2000”.
Logging: This parameter enables or disables logging of actions performed by the Flip Factory Transcoder driver. It’s recommended to check this control if any troubles occurred while working with the Flip Factory server (logging may require a lot of disk space for log files). Default parameter is false (unchecked).
NOTE: The logging information will be stored on a local hard drive, disk “C:\”.
The file name is formed according to the following scheme: log_FF_mm_dd_yy_xxxx.txt, where mm_dd_yy – current date and xxxx – random generated number.
Source FH: This parameter specifies the value for the Fiber Handle to use each time the driver receives the request from distributor. This parameter can vary from 0 to 10000. Default parameter is “0”.
If the parameter is zero the source Fiber handle of the request received is used to find the configuration options within the flipfactory.ini file.
If the parameter is nonzero, then the source Fiber handle value of the request received is ignored and the options from flipfactory.ini are extracted according to the Source FH parameters value.
NOTE: This option may be used when only one distributor points to Flip Factory driver. If two or more distributors are configured to point to the same Flip Factory driver we strongly recommend to set this parameter to “0”, so that for request from different distributors there may be used their own specific setting from the flipfactory.ini file.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 177 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Reinitialize button: Click this button to make the Flip Factory driver re-read the flipfactory.ini file with the configuration.
• For Front Porch Digital (FPD) VAST BitSCREAM:
Device Name: This parameter defines the name of the driver into the adc100nt configuration. (Default: BSCRM).
Host Name: This parameter identifies the BitScream system the driver is communicating with. This parameter can take a name or an IP address. (Default: screamer).
Transcoder ID: (Default: 0, Range: 0 - 9) This parameter defines the transcoder that will be used to transcode the files.
If set to 0, the VAST BitSCREAM system is configured in load balancing mode
(Transcoder automatically selected by the transcoding system).
If set to positive value (greater than 0), the adc100nt driver selects the transcoder to be used and only this one will be used for transcoding.
NOTE: The Transcoder ID is randomly generated and hardcoded by Front Porch
Digital. As per Front Porch Digital, there is no upper limit to this #; they are generated sequentially starting from 1. However, if a transcoder is deleted, it’s transcoder ID will not be re-used. (Actual range: 0- 9999)
Source ID: (Default: 1, Range: 1 - 10000) This parameter defines the source directory (storage) that will be used to get the files to be transcoded. It must match a Source ID (using ftp) declared and configured in the VAST BitSCREAM.
Source Extension: (Default: .mpg) This parameter defines the extension of the source filenames from the Source ID. When the driver is declared, the Default parameter is “.mpg” for the source extension. Then, it can be modified to another value. Ensure that the correct case is used.
Note 1: The driver does not insert the “.” (dot) character automatically between the filename and the extension. The “.” (dot) character must be set in the “Source
Extension” field.
Note 2: A blank field can be configured. In this case, this configuration means that there is no extension for the IDs to be transcoded.
Priority: (Default: 5) This parameter defines the priority to attach to each transcode command. The supported values are from 1 (lowest) to 9 (highest).
4. Select Transcoding Parameters tab. (For FPD VAST BitSCREAM)
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 178 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Destination ID: (Default: 2, Range: 1 - 10000) This parameter identifies the destination device (storage) that will receive the transcoded files. This parameter must match a Destination ID configured in the VAST BitSCREAM.
• Destination Formats: (Default: VOD) Select a destination format: VOD or Others
(non VOD). When “VOD” is selected, “Others” is unchecked and the text area is empty and grayed.
If “VOD” format is selected, the transcoding request manages a single output format (VOD).
If “Others” format is selected, the transcoding request manages single or multiple output formats depending of the content of text area (Description field).
• Description field / Text area: This text area field becomes active when Others format is selected. The Text area can contain several formats separated with a comma. If several formats are specified in the list, then a transcoding request will manage simultaneous output formats per transcoding request.
Example for a Single format request (Windows Media): “WM”.
Example for a Multiple format request (Windows Media & Real Media):
“WM,RM”.
All the supported outputs formats depend on the capabilities of the VAST
BitSCREAM. Ensure the proper labels for the format(s) are configured. Current supported outputs formats and associated codes are:
WM - Windows Media
RM - Real Media
QT - Quick Time
MPGP - MPEG-1/2 program stream
PINN - Pinnacle Video Server
GVG - Grass Valley Group video server
LMPG - Leitch video server with MPEG content
DV25 - DV-25 mbps
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 179 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
OMF - AVID OMF
OMN - Omneon Video Server
5. When finished click Apply, then click OK.
6. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 180 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Archive Configuration (General)
Archives, archive managers and archive systems are controlled though an Ethernet connection, rather than a point-to-point RS-422 serial connection. The Device Server’s second network interface (bound to TCP/IP protocol) connects to a separate network hub or switch that allows it communicate with the archive. Archives are not media devices in the sense that they are not assigned to lists, they cannot cue and play, and they are not capable of producing an I/O stream. Instead, archives stream data into a video server for playout. A video server may also stream data into an archive for storage. Archives are strictly data storage devices and may only be accessed by the automation through GMT components.
The Device Server application does maintain a storage collection for archive devices, which may be viewed from the Device Storage window in either the Air or Media Client application.
For more information about archives and GMT, see section Global Media Transfer .
The following is an example Archive configuration. Your device may have different options. If necessary, refer to the User Notes for your device for complete details on how to configure it.
To Configure an Archive Device
1. Under Archives in the Available pane (right pane), select an Archive device (Standard
Archive) and drag-n-drop it to the Configured Pane (left pane). For details on assigning a
device see: To Assign a Device to a Device Channel .
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the Archive device in the left pane, right-click and from the popup menu select
Properties. The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select General tab.
Configure the following parameters as required:
• Device Name: Change this to the preferred name for the device, up to 5 characters.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 181 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Archive Parameters:
Instance: Number of copies of each spot to put on tape when executing a Copy to Archive command.
Copy From Priority: The priority to attach to each Copy From Archive command. 1 means highest priority; 16 means lowest priority.
Copy To Priority: The priority to attach to each Copy to Archive command. 1 means highest priority; 16 means lowest priority.
Group: The group name to use in a Copy to Archive command.
4. Select Socket tab.
Configure the following parameters as required:
• Socket Information:
Host: Enter the IP host address of the Sun workstation running the Avalon
Archive Manager software.
Port: Enter the IP port number on which the AAM process is running its Louth
VACP interface. This value should be 1025.
5. Select VACP Manager tab. Use this tab to select your Archive Manager from the list of available devices.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 182 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
6. Select Storage tab.
Configure the following parameters as required:
• ID List Options: Select one of the following List ID options. During the Archive
Device’s initial connection to the Archive Manager, the user can choose what kind of storage ID collection is desired. Archive Device uses VACP (Video Archive
Communication Protocol) to request ID and status associated with each ID. These
Archive IDs can be displayed in the Air Client Archive Storage Window for browsing.
When the GMT List queries Archive Device for the existence of an ID, this Archive storage collection is not referenced. Rather, the VACP ID query command is sent directly to the Archive Manager for refresh status.
Request ID Name List and Status: When selected this option instructs the ADC
Archive Device to collect all ID name and its associated status. If the archive storage has a huge amount of IDs stored, this option may take a significant
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 183 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager amount of time to process. This is because some Archive Manager products respond to slower than others VACP ID-Request commands.
Request ID Name List Only: If only ID name is required without detail ID status, this option can be much faster to process for slower Archive Manager products.
No ID List Required: When this option is selected, no ID collection is maintained in the ADC Archive Device. This will not affect archive query, nor it will affect archive media transfer. The only limitation is the user will not be able to browse the Archive Storage Window from the ADC system. However, users can still use the browser tool provided with Archive Manager to browse content of archive storage.
7. Select Diagnostics tab. Use this tab to view diagnostic summary. If required click the
Reinitialize button to reinitialize the device.
8. When finished click Apply, then click OK.
9. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
Video Effect Device Configuration (General)
The following is an example video effect device configuration. Your video effect device may have different options and the selection of configuration tabs may be different for that device.
If necessary, refer to the User Notes for your device for complete details on how to configure it.
To Configure a Video Effect Device
1. Under Video Effect Devices in the Available pane (right pane), select a device (e.g.
Pinnacle DVExtreme) and drag-n-drop it to the Configured Pane (left pane). For details
on assigning a device see: To Assign a Device to a Device Channel .
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 184 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the device in the left pane, right-click and from the popup menu select Properties.
The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select the General tab.
Configure the following parameters as required:
• Device Name: The device name identifies the disk port. Enter the name by using up to 16 characters. When an event is threaded, an extra character - the head number - is added to the end of the name.
• ID Match Name: The ID match name identifies the disk port in secondary events, where the device name is played in the ID field. The default name is the same name you selected as the device name. Enter the name by using up to four characters.
When an event is threaded, a fifth character - the head number - is added to the name.
The name is also used to identify the disk port used to execute secondary data events. If a disk port’s name matches the ID of a secondary data event, the event is executed.
4. Select the Serial Port tab. Use this tab to connect the driver to ADC’s serial COM port that the device is physically connected. Click the down arrow button to select from a list of available serial ports.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 185 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
5. When finished click Apply, then click OK.
6. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 186 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Still Store Device Configuration (General)
The following is an example still store (i.e. still store or logo generator) configuration. Your device may have different options and the selection of configuration tabs may be different for that device. If necessary, refer to the User Notes for your device for complete details on how to configure it.
To Configure a Still Store Device
1. Under Still Stores in the Available pane (right pane), select a device and drag-n-drop it to
the Configured Pane (left pane). For details on assigning a device see: To Assign a
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the device in the left pane, right-click and from the popup menu select Properties.
The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select the General tab. The available options depend on the selected device. (For example, the following General tabs show options for a LogoMotion2, an SVA LGA100, a
Leitch DTP20, an Imagestore750, and an AMP Logo Media.)
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 187 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required and available:
• Device Name: The device name identifies the disk port. Enter the name by using up to 16 characters. When an event is threaded, an extra character - the head number - is added to the end of the name.
The “Device Name” appears in the Device Status and configuration window on the client applications. The default name may be used, but it is recommended to use unique names for easy device identification.
• ID Match Name: The ID match name identifies the disk port in secondary events, where the device name is played in the ID field. The default name is the same name you selected as the device name. Enter the name by using up to four characters.
When an event is threaded, a fifth character - the head number - is added to the name.
This string is placed in the ID field of events that will be played by this device.
The name is also used to identify the disk port used to execute secondary data events. If a disk port’s name matches the ID of a secondary data event, the event is executed. Such secondary data events include those that delete spots, transfer an archived spot, delete protect spots, or undelete protect spots.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 188 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Evertz 9725 LGA – 16 char logo Note: Assign the Evertz 9725 LGA – 16 char logo names to a Transmission List to be schedule to air. The Evertz 9725 LGA – 16 char logo names uses A/V, Secondary A/V, and Secondary Data Events to execute the pre-loading and playout of Logos.
• Options.
Back-time value in frames: This parameter determines when commands should be sent to the device. A non-zero value in this field indicates the number of frames that commands will be sent early (during preroll, before the play counter actually starts).
This value is set at 1 by default, it shouldn’t need to be changed.
However if the timing of the device and DVE commands are off with respect to the switcher, this parameter may be changed to adjust the output timing. This parameter does not change the timing for secondary data commands, only A/V events.
LogoMotion2 Note: This driver allows an “EarlyFrameCount” value as low as -5 frames. An “Early Frame Count” value less than zero means the duration of the event is less than it was scheduled. For example, if “Early frame count” = -3 then the actual duration DUR’ = DUR – 3; where DUR is the scheduled duration.
Playback Card ID: (For LogoMotion and LogoMotion2). Under normal circumstances this parameter should be left at 2.
Enable Internal Keyer: Check to enable.
When enabled (checked), the video is brought up on the output at the On Air
Time of the Event. It is then cleared when the event is done. There is no preview ability when keyer mode is enabled. The Timing value adjusts when the video appears on the output. It is expected the program video will be put into the device so the internal keyer can overlay the Logo on its output.
When disabled (unchecked), the device server brings up the video on the output of the device as soon as the event is cued. In this way the operator can see the correct video on a preview monitor if desired. The output could be feed into a keyer of a master control switcher, or another external keyer. After the event is done, the video is left on the output of the device unless it is needed for another event.
Storage Check: (for ImageStore, Miranda XG). Enable (check) if the logo's ID is available in the device storage.
Disable (uncheck) this option, if the Still Store device does not support the storage check. This lets the list blindly register the event (i.e. turn the event to blue).
Stop Current Play After Initialize: Enable (check) / Disable (uncheck) allowing the device to keep playing the logo(s) if the channel(s) is(are) not scheduled to play.
• Device Type. (For LogoMotion 2) Select one:
SD: Choose this option if device type is Standard Definition. The Standard
Definition has 4 keyers (4 layers).
HD: Choose this option if device type is High Definition. The HD version has only
2 layers.
• DTP Parameters (For Leitch DTP20, mCapture) Specify:
Client ID: Goal of this parameter to distinguish the answers from different clients which work with the same DTP (mCapture) device. If there is only one client, use default value (10) or choose any other value in the range [0..65000]. If there are
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 189 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager several clients, specify different clients ID for each (the real values do not matter.
They just need to be different.)
• AMP Logo Channel: (For AMP Logo Media) From the dropdown, choose the required AMP Logo channel. Channel 1 corresponds to Layers A, B, C, D; channel 2
– E, F, G, H; channel 3 – I, J, K, L; channel 4 – M, N, O, P.
4. Select the Serial Port tab. Use this tab to connect the driver to ADC’s serial COM port that the device is physically connected. Click the down arrow button to select from a list of available serial ports.
5. Select the Communications tab. (Available for LogoMotion 2 and SAV 50DK) Use this tab to configure the following parameters as required: Baud Rate, Data Bits, Stop Bits, and Parity.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 190 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
6. Select the Diagnostics tab. If required, click Reinitialize button to reinitialize the device.
This clears the buffers in the driver and resets the connection to the device. This should only be used for troubleshooting purposes.
7. Select the “Device” Channel tab. (Available on SubDev selections only) Some
Make/Model devices will offer additional functionality through a sub-device. This tab is where the device driver of a primary device is associated with the related sub-device
(SubDev) driver.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 191 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
For Example: The Quartz Logo has an optional DVE sub-device. The following screen shot shows the QuartzQMC Channel tab for a Quartz Logo DVE SubDev selection. In this situation the Quartz QMC device driver is configured, then the Quartz Logo DVE
SubDev driver is configured. The QuartzQMC Channel tab is where the two drivers are associated.
EvertzQmcMCS Note:
• The Logo and DVE sub device driver cannot be used without configuring the QMC
MCS device driver first.
• The “EvertzQMC for DVE&Logo” Subdev must also be assigned to the Transmission
List where the Evertz Switcher is used.
8. Select the Socket tab. (Available for Leitch DTP20 and mCapture devices)
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 192 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Socket Information.
Host: (Default: 127.0.0.1)
Port: (Default: 49227). This default value was defined in the description of the
RCS Protocol. Both drivers – DTP and mCapture use this protocol.
• Log Setting.
Both drivers can create own log file. This file can be created in the folder where DS will be started from or forwarded to another computer.
Enable: (Default: unchecked) Check to enable Log creation.
Forwarding: Enable (check) to forward the created log to another computer.
When this option is checked (enabled) Forwarding Address and Forwarding Port are active.
Disable (uncheck) if the log file can be created in the folder where the Device
Server will be started.
Forwarding Address: When this option is active, specify the IP Address of the computer the log will be forwarded to.
Forwarding Port: When this option is active, specify the Port to use on the computer the log will be forwarded to.
9. TCP/IP Connection tab. (Available for AMP Logo Media devices). The AMP Logo Media is controlled via TCP/IP using Inscriber Automation Interface. The driver handles layer assignments to ensure that maximum 4 layers are used at a time and only one logo is assigned to one layer.
Configure the following parameters as required:
• Host: Specify the IP address of the Host (Default: 127.0.0.1).
• Port: Specify the connection port (Default: 8994).
10. When finished click Apply, then click OK.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 193 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
11. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 194 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Character Generator Device Configuration
(General)
The following is an example character generator device (e.g. Chyron MAXINE, Aston CG) configuration. Your device may have different options and the selection of configuration tabs may be different for that device. If necessary, refer to the User Notes for your device for complete details on how to configure it.
To Configure a Character Generator Device
1. Under Character Generators in the Available pane (right pane), select a device and drag-
n-drop it to the Configured Pane (left pane). For details on assigning a device see: To
Assign a Device to a Device Channel .
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the device in the left pane, right-click and from the popup menu select Properties.
The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select the General tab. Options available may differ depending in the device selected.
For example: The following General tabs show options for a Chyron CODI and a Chyron
Duet2.
Configure the following parameters as required:
• Device Name: The device name identifies the disk port. Enter the name by using up to 16 characters. When an event is threaded, an extra character - the head number - is added to the end of the name.
• ID Match Name: The ID match name identifies the disk port in secondary events, where the device name is played in the ID field. The default name is the same name you selected as the device name. Enter the name by using up to four characters.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 195 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
When an event is threaded, a fifth character - the head number - is added to the name.
The name is also used to identify the disk port used to execute secondary data events. If a disk port’s name matches the ID of a secondary data event, the event is executed.
• Options.
Back-time value in frames: This parameter determines when commands should be sent to the device. A non-zero value in this field indicates the number of frames that commands will be sent early (during preroll, before the play counter actually starts). This value is set at 1 by default, it shouldn’t need to be changed.
Address: Specify the Address of the CG
Enable Internal Keyer: Check to enable internal keyer.
When enabled the Program Out line will overlay the graphics onto external video whenever the list event for the CG is on air. Also, the user has the option of enabling Key Hold which will not turn off the keyer after an event finishes playing and the Key Hold will remain in effect until it is ended by another event.
When disabled the internal keyer is always turned on such that the Program Out and Program Key Out are always enabled as input to a downstream keyer.
Display First Frame of Image When Cued: (For Chyron Duet 2 and Duet LEx)
Enable (check) / Disable (uncheck) allowing the load image command to set the attribute to display the first frame to the frame buffer.
4. Select the Serial Port tab. Use this tab to connect the driver to ADC’s serial COM port that the device is physically connected. Click the down arrow button to select from a list of available serial ports.
5. Select the Communications tab. (Available for Chyron Duet selections) On this tab configure the following parameters as required: Baud Rate, Data Bits, Stop Bits, and
Parity.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 196 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
6. Select the Diagnostics tab. If required, click Reinitialize button to reinitialize the device.
7. When finished click Apply, then click OK.
8. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 197 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Audio Disk Cart Configuration (General)
The following is an example audio disk cart configuration (e.g. Digicart, Sony Mini Disk, etc.).
Your device may have different options and the selection of configuration tabs may be different for that device. If necessary, refer to the User Notes for your device for complete details on how to configure it.
To Configure an Audio Disk Device
1. Under Audio Disk Carts in the Available pane (right pane), select a device and drag-n-
drop it to the Configured Pane (left pane). For details on assigning a device see: To
Assign a Device to a Device Channel .
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the device in the left pane, right-click and from the popup menu select Properties.
The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select the General tab. Options available may differ depending on the device selected.
For example: The following General tabs show options for a Digicart (left), Sony Mini
Disk (right), and Dalet devices (lower left).
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 198 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Device Name: The device name identifies the disk port. Enter the name by using up to 16 characters. When an event is threaded, an extra character - the head number - is added to the end of the name.
This name is used in the ID field of an event that is to be assigned to the device. You can use the default name or assign another name if multiple devices are in the system.
• ID Match Name: The ID match name identifies the disk port in secondary events, where the device name is played in the ID field. The default name is the same name you selected as the device name. Enter the name by using up to four characters.
When an event is threaded, a fifth character - the head number - is added to the name.
The name is also used to identify the disk port used to execute secondary data events. If a disk port’s name matches the ID of a secondary data event, the event is executed.
• Options.
Back-time value in frames: This parameter determines when play commands should be sent to the device. A non-zero value in this field indicates the number of frames that commands will be sent early (during preroll, before the play counter actually starts). This value is set at 1 by default, it shouldn’t need to be changed.
Update Durations from Audio Tracks: Check to enable the update of durations with actual durations from audio tracks.
Stop Before Play: (Digicart Option) If enabled (checked), a STOP command is sent from the Device server to the Digicart before each PLAY command. If a cut is still playing this ensures it will be stopped and the new cut played immediately.
Sort Storage by Title: (Digicart Option) If enabled (checked), the cuts in the device storage window are sorted by cut titles. If disabled (unchecked), the window is sorted by cut number.
Enable Storage Sorted by Title: (Sony Option) If enabled (checked), the cuts in the device storage window are sorted by cut titles. If disabled (unchecked), the window is sorted by cut number.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 199 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Sony MDS Model: (Sony Option) Check to enable if this is a Sony MDS Model.
• Preroll Timings: (Dalet Options)
Send play at Preroll: Click to enable send of a play command at preroll.
Frames to send play early: Specify the number of frames that the play command will be sent early (during preroll, before the play counter actually starts). This value is set at 1 by default, it shouldn’t need to be changed.
4. Select the Serial Port tab. Use this tab to connect the driver to ADC’s serial COM port that the device is physically connected. Click the down arrow button to select from a list of available serial ports.
5. Select the Communications tab. (Available for Dalet selection.) On this tab configure the following parameters as required: Baud Rate, Data Bits, Stop Bits, and Parity.
6. Select the Diagnostics tab. As required:
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 200 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Reinitialize button: Click to reinitialize the device.
• Reverify Storage button: (available for Digicart) Click to reverify device storage.
7. When finished click Apply, then click OK.
8. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 201 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Serial Device Configuration (General)
The following is an example ‘serial device’ configuration. Your ‘serial device’ (such as a David
MultiPlayer, a FAB Subtitler, and an Ayato Remote) may have different options and the selection of configuration tabs may be different for that device. If necessary, refer to the User
Notes for your device for complete details on how to configure it.
To Configure a Serial Device
1. Under Serial Devices in the Available pane (right pane), select a device and drag-n-drop
it to the Configured Pane (left pane). For details on assigning a device see: To Assign a
Once a device has been assigned to a device channel, it may be configured for specific options.
2. In the Configured Pane (left pane), select a ‘Serial device, right-click and from the popup menu select Properties. The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select the General tab. Options available may differ depending on the device selected.
For example: The following General tabs show options for SCCOM (left) and Ayato
(right) serial devices.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 202 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Device Name: The device name identifies the disk port. Enter the name by using up to 16 characters. When an event is threaded, an extra character - the head number - is added to the end of the name.
This name is used in the ID field of an event that is to be assigned to the device. You can use the default name or assign another name if multiple devices are in the system.
• ID Match Name: The ID match name identifies the disk port in secondary events, where the device name is played in the ID field. The default name is the same name you selected as the device name. Enter the name by using up to four characters.
When an event is threaded, a fifth character - the head number - is added to the name.
• Timings / Preroll Timings:
Send play at Preroll: Click to enable send of a play command at preroll.
Frames to send play early: Specify the latency - in frames (positive or negative)
- for sending the Play command (during preroll, before the play counter actually starts). This value is typically set at the default level for the device and shouldn’t need to be changed.
For Example: +4 frames (4 frames after on air time).
Frames to send stop early: Specify the latency - in frames (positive or negative)
- for sending the Stop command. This value is typically set at the default level for the device and shouldn’t need to be changed.
For Example: 0 frames (last frame of clip).
Polling Delay (Frames): Specify the frequency (in frames) of polling the device.
Default: 25 frames.
ID Request Polling Delay (Frames): Frequency (in frames) of the device polling when command is executing (the “Pending” status is received). Default: 25 frames.
• Number of command retries: Specify the number of times to retry a command, if the response was not received during the command timeout.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 203 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Send ID Only: (Valid for Screen Subtitler 24) This option determines the device driver mode used. The status command of the Screen Subtitler device contains ‘ID’ and ‘Title’ fields. Size of the ‘ID’ field is 8 bytes (8 characters), size of the ‘Title’ field is 16 bytes (16 characters). The Screen Subtitler has a mode such that when both fields are using only for ID information the ‘Title’ field is used as a continuation of an
ID.
When this option is enabled (checked), the driver uses the ‘ID’ and ‘Title’ fields of the commands only for ID, so a passed ID can be up to 24 characters.
When option is disabled (unchecked), the behavior of the driver matches the behavior of the SCREEN_SRV2 driver.
Note: Changing this setting does not affect the device operation mode, only driver
mode.
4. Select the Serial Port tab. Use this tab to connect the driver to ADC’s serial COM port that the device is physically connected. Click the down arrow button to select from a list of available serial ports.
5. Select the Communications tab. On this tab configure the following parameters as required: Baud Rate, Data Bits, Stop Bits, and Parity.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 204 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
6. Select the Channel tab. (Available for NDS ESS and IBT VPS devices only.)
Configure the following parameters as required:
Select each Player Channel Number and fill in the channel number for each head of the
NDS ESS device. The NDS ESS device is a 10 headed device. By default the channel number for each head is assigned as 0001 through 0010 for the respective heads.
7. Select the Programs tab. (Available for Albrecht devices only.)
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 205 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Select Insert to insert a program.
The Albrecht VPS device is controlled by Secondary AV events. The title field of these events is used to pass details of the command to send to the device. The title field does not contain the command exactly, but is quite close and there is a simple mapping from the title field to the outgoing command.
Program: The event’s Title field contains the program name as a 4-chr string.
That name must match an entry in the list defined in the Program column of the grid on the Programs tab. Program names MUST be 4-chrs in length. If necessary, pad with spaces.
Code: The 4-chr program name string is not passed to the device. Instead we pass a 1-chr code to represent that program. The code to pass for each program is defined in the Code column of the grid on the programs tab.
Area and Country: The command sent to the device contains 2 more fields,
Area and Country. These fields do not appear in the title field of the event.
Instead they are taken from the Area and Country columns of the grid on the programs tab. Area and Country are 1-chr codes.
• Designate a Special Label: This is a label that can be sent to the device in place of a normal date / time. The special label can be any 10-chr string of the form
AA:AAAA.AA where A is any character and ':' and '.' are literals. The : and . delimiter literals are mandatory. The default string used by the driver is SC:SCSC.SC
• When finished click OK.
The data that appears in the grid on the Programs tab is stored in the [DeviceN] section of the INI file (ADC100NT.INI) as:
ProgX=<Prog><Code><Area><Country>
Example: Prog1=BBC123A
This would appear on the first row of the grid, because it is Prog1. The columns would be:
Program: BBC1
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 206 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Code 2
Area 3
Country A
If the INI file does not contain any ProgX entries, the grid contains:
Program: NOT
Code IN
Area INI
Country FILE
The Special Label is held in the [DeviceN] section of the INI file (ADC100NT.INI) as: Special Label=AA:AAAA.AA
If the special label entry in the INI file is shorter than 10 characters, it is padded with trailing spaces. This means that if the Special Label entry is missing from the
INI file, a string of 10 spaces is used.
If the title field of the Secondary AV event is set to the special label, the special label value is used as the TimeDate field in the command to be sent to the device.
8. Select the Macros tab. (For Serial Comm Device, David MultiPlayer, and Sys Media
PDC)
Configure the following parameters as required:
• Add button: Click the Add button to enter a macro. When finished click OK.
Macro Name: Enter a mnemonic to help the operator identify the macro name.
Macro: Enter the macro commands.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 207 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Edit Button: To edit an existing macro entry, select a macro entry from the list display and then click Edit. An edit dialog is displayed populated with the parameters currently specified for the selected macro. Make changes as required, and then click
OK.
• Delete button: To delete an existing macro entry, select a macro entry from the list display and then click Delete.
9. Select the Diagnostics tab. Options available depend on the serial device:
Configure the following parameters as required:
• Reinitialize button: Click to reinitialize the device.
• Reset Timer # button: Click to reset the timer. Click yes when system prompts to confirm.
10. When finished click Apply, then click OK.
11. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 208 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Advanced Device Configuration (General)
The following is an example ‘advanced device’ configuration. Your ‘advanced device’ may have different options and the selection of configuration tabs may be different for that device.
If necessary, refer to the User Notes for your device for complete details on how to configure it.
To Configure an Advanced Device
1. Under Advanced Devices in the right pane, select a device and drag-n-drop it to the left
pane. For details on assigning a device see: To Assign a Device to a Device Channel .
Once a device has been assigned to a device channel, it may be configured for specific options.
2. In the left pane, select an ‘Advanced’ device, right-click and from the popup menu select
Properties. The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select the General tab.
Configure the following parameters as required:
• Device Name: The device name identifies the disk port. Enter the name by using up to 16 characters. When an event is threaded, an extra character - the head number - is added to the end of the name.
This name is used in the ID field of an event that is to be assigned to the device. You can use the default name or assign another name if multiple devices are in the system.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 209 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• ID Match Name: The ID match name identifies the disk port in secondary events, where the device name is played in the ID field. The default name is the same name you selected as the device name. Enter the name by using up to four characters.
When an event is threaded, a fifth character - the head number - is added to the name.
4. Select the Connection tab.
Configure the following parameters as required:
• Chose the Connection Type: Specify Serial or TCP/IP
• Serial Port: (Active when Serial is selected) Use this entry to connect the driver to
ADC’s serial COM port that the device is physically connected. Click the down arrow button to select from a list of available serial ports.
• TCP Connection: (Active when TCP/IP is selected.) Specify the Host IP address.
And enter the port number to lowest field.
5. Select the Communications tab. Use this tab to select Baud Rate, Data Bits, Stop Bits, and Parity.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 210 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
6. Select the Polling tab. If your device supports polling command, use this tab to set polling. The Device Server uses polling to check whether device is alive.
Configure the following parameters as required:
• Polling Enabled: Check to enable polling.
• Polling Parameters:
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 211 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Interval (Frames): Specify the appropriate polling interval - in frames.
Device TimeOut (frames): Specify the appropriate polling reply timeout - in frames.
Command: Enter the polling command or byte sequence, which will be sent with configured interval. You may enter any characters and use hexadecimal representation. For example, you may use {20} instead of space, {0D0A} instead of carriage return. All hexadecimal values should be wrapped with braces.
• Reply Processing.
Automatic reply processing: Check to enable automatic reply mode. This means that reply processing should be done automatically by driver. This option is useful only if you are using custom device driver.
User defined reply: Check to enable user-defined reply mode. This means that you define the expected reply yourself. In this case reply pane text field below should contain expected sequence of character, which device will send after polling command is received.
Reply pane: Specify the user reply.
7. Select the Macros tab.
Configure the following parameters as required:
• Title pane: Lists titles of macros that already exist.
• Check if Macro exists: Enable (check) or disable (uncheck) checking for existence of specified macro in the PlayList. When enabled, the “TITLE” field of each event is checked whether the Macro Template exists in the Universal Sercom or not. If the specified Macro Template does not exist, the event is red colored.
• Edit button: Edit an existing macro. Select a macro listed on the Title pane, and then click the Edit button. The Extended macro Entry form opens, populated with the definition of the selected macro. Make any changes necessary, and then click OK.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 212 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Delete button: To delete an existing macro entry, select a macro listed on the Title pane, and then click the Delete button.
• Add button: Opens the Extended Macro Entry dialog.
Macro Name: Enter a mnemonic to help the operator identify the macro name.
The “Macro Name” is used in TITLE field of PlayList to identify the Macro
Template, which should be processed.
Number of Parameters: Specify the number of playlist parameters. This parameter sets the flexibility of the Macro Template. It defines how many external parameters will be passed to Macro Template.
TITLE Field format: This field shows the way the Macro should be used in
TITLE field of PlayList. It is the syntax of the Macro Template.
For example: If “TEST_MACRO:file1:scene2” (without quotes) is entered into the “TITLE field” of PlayList: “file1” is the first parameter passed to the Macro
Template, and “scene2” is the second parameter passed to the Macro Template.
Important: For 'Data Event with Data': parameters are passed not in a Title field, but they are entered in a special window in Air Client, when creating an event.
Each line in this window represents one parameter in the macro.
Event States: There are 7 states of the event when commands could be sent to the device.
“Check” state occurs when an event is ‘checked’ (e.g. enters the lookahead) to confirm if the ID’s media is available.
“Cue” state occurs when the media tries to be cued (prepared).
“Preroll” state occurs before the “Play” will be started. Preroll time is configurable parameters of PlayList.
“Play” state occurs when media is playing.
“End” and “Postroll” go just after the “Play”. Postroll time is configurable parameter for the list too.
“Skip” state occurs when operator skips the event (for example, by pressing
“Skip” button in Air Client).
Important: For Universal Sercom Driver v.2 only: 'Data Event' and 'Data Event with Data' are registered with Device Server only if the corresponding macro contains 'play' state, only. If macro includes any other state (Cue, Preroll, End,
Postroll, Skip) - an event is registered, because for this type of events there is only 'play' state.
Select the required tabs (Check, Cue, Preroll, Play, End, Postroll, Skip) and set up the following parameters: (It is not required to use all seven states, but it is possible to fill in all of them.)
Command: When selected the Command pane and the Reply Expected option become available.
Command pane: Specify the macro commands.
Reply Expected: Enable (check) if a reply is expected. When selected, the following options become available:
Automatic Reply Processing: Select to enable automatic reply mode.
This means that reply processing should be done automatically by driver. This option is useful only if using a custom device driver.
User defined reply: Select to enable user reply mode. When selected the Reply pane comes available for entry. This means mode means that you define expected reply yourself. In this case Reply pane text
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 213 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager field should contain expected reply. You may use hexadecimal values wrapped with braces inside the expected reply. The sequence received from the device is compared against the sequence stored in the text box for this state. If they don’t match, an error occurs.
Reply timeout: (in seconds) Specify how long to wait for a reply – in seconds – before timing out the process.
Reply pane: Specify the user reply.
About Hexadecimal Values.
Hexadecimal values may be used in the command or reply text fields both for polling and for macro template.
Hexadecimal values are wrapped in braces and within braces may be separated with spaces. If hexadecimal value contains odd number of digits then single digit becomes zero-leading.
For example,
{1 2} is equal to {01 02}
{123} is equal to {01 23}
{1234} is equal to {12 34}
{12 34} is equal to {12 34}
OK button: Click OK to save the Macro Template and close the Extended Macro
Entry dialog.
Cancel button: Click Cancel to close the dialog without saving.
Apply button: Click Apply to save the Macro Template, but keep the dialog open.
Apply and New button: Click Apply and New to save the Macro Template and open a clear Extended Macro Entry dialog for a new Macro Template creation.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 214 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
8. Select the Initialization tab. (for Pubtronic, Universal SerCom Driver, Kaleido K2,
Fingertext, Softel Pres TX, ) Use this tab to set IP address.
Configure the following parameters as required:
• Command: When selected the Command pane and the Reply Expected option becomes available.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 215 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
• Command pane: Specify the initialization command.
• Reply Expected: Enable (check) if a reply is expected. When selected, the following options become available:
Automatic Reply Processing: Select to enable automatic reply mode. This means that reply processing should be done automatically by driver. This option is useful only if using a custom device driver.
User defined reply: Select to enable user reply mode. When selected the Reply pane comes available for entry. This means mode means that you define expected reply yourself. In this case Reply pane text field should contain expected reply. You may use hexadecimal values wrapped with braces inside the expected reply. The sequence received from the device is compared against the sequence stored in the text box for this state. If they don’t match, an error occurs.
Reply timeout: (in seconds) Specify how long to wait for a reply – in seconds – before timing out the process.
Reply pane: Specify the user reply.
9. Select the Global Timeout Settings tab. On this tab enter the reply timeouts in frames for each listed state, and then press “Apply”. Now new default values will be used in the
Extended Macro Entry.
10. Select the Diagnostics tab. Use this tab to test commands or reinitialize the device.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 216 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Test Command: enter a test command and then click Send.
• Reinitialize button: If required, click to reinitialize the device.
11. Select the Latency Adjustments tab. (For Universal Sercom v2 driver only) Use this tab to set latency adjustments in the timing of play, end and skip commands.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 217 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Use these parameters to adjust the time (in frames) to send play, end, and skip commands earlier than the crossing point, the end time, and the skip time, respectively.
Note: These options can be operated only on primary, secondary A/V events, or any
event that supports duration counter.
• The default values of these parameters are zeros.
• The maximum number of frames that currently supported is 90, and the minimum value is zero. The value 90 was chosen to be consistent with other ADC Automation drivers.
12. Select the Supported Audio Modes tab. (For NEC Audio driver only: vcvda) Use this tab to define supported intervals of Audio modes. With ADC v11.60 and higher the NEC
Audio driver supports additional patterns and provides the ability to recall up to 255 Audio modes for each NEC Encoder.
• To add a New Supported Interval (Hex), specify a supported interval in Hex and then press Add. The new interval is added to the list pane. When supported Audio intervals are defined, the driver checks AM2 (Audio Mode 2), and AM4 (audio Mode
4) macros for use with all supported intervals.
• To delete an existing New Supported Interval (Hex), select/highlight an existing interval in the list pane and then press Delete.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 218 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
13. When finished click Apply, then click OK.
14. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 219 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Barcode Reader Configuration (General)
Barcode readers or barcode wands are used to identify tapes by a barcode label. Generally, they are used in conjunction with cart machines. Barcode readers are shared by all lists, although in special cases they may be assigned to a single list.
The following is an example Barcode Reader configuration. Your Barcode Reader may have different options and the selection of configuration tabs may be different for that device. If necessary, refer to the User Notes for your device for complete details on how to configure it.
To Configure a Barcode Reader
1. Under Barcode Readers in the right pane, select a device and drag-n-drop it to the left
pane. Your display may show different options. For details on assigning a device see: To
Assign a Device to a Device Channel .
Once a device has been assigned to a device channel, it may be configured for specific options.
2. In the left pane, select a Barcode Reader device, right-click and from the popup menu select Properties. The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select the General tab.
Configure the following parameters as required:
• Device Name: Enter a name for the VTR to help you identify the VTR during event transmission. The name can have up to 16 characters. The device name has no relation to the ID of any tape inserted in the VTR.
• Odetics Type Label Length: Use spin arrows to specify the label length.
4. Select Serial Port tab. Use this tab to connect the driver to ADC’s serial COM port that the device is physically connected. Click the down arrow button to select from a list of available serial ports.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 220 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
5. When finished click Apply, then click OK.
6. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 221 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
VChip Encoder Configuration (General)
The following is an example VChip Encoder device configuration. Your device may have different options and the selection of configuration tabs may be different for that device. If necessary, refer to the User Notes for your device for complete details on how to configure it.
To Configure a VChip Encoder Device
1. Under VCHIP Encoders in the Available pane (right pane), select a device and drag-n-
drop it to the Configured pane (left pane). For details on assigning a device see: To
Assign a Device to a Device Channel .
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the device in the left pane, right-click and from the popup menu select Properties.
The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select the General tab.
Configure the following parameters as required:
• Device Name: The device name identifies the disk port. Enter the name by using up to 16 characters. When an event is threaded, an extra character - the head number - is added to the end of the name.
This name is used in the ID field of an event that is assigned to the device. The default name can be used or another name assigned, if multiple devices are in the system.
• ID Match Name: The ID match name identifies the disk port in secondary events, where the device name is played in the ID field. The default name is the same name you selected as the device name. Enter the name by using up to four characters.
When an event is threaded, a fifth character - the head number - is added to the name.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 222 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
The name is also used to identify the disk port used to execute secondary data events. If a disk port’s name matches the ID of a secondary data event, the event is executed.
• Run at Preroll: Check to enable sending play command at preroll. (For Evertz devices this option is typically unchecked.))
4. Select the Serial Port tab. Use this tab to connect the driver to ADC’s serial COM port that the device is physically connected. Click the down arrow button to select from a list of available serial ports.
5. Select the Communications tab. As required, configure the following parameters as required: Baud Rate, Data Bits, Stop Bits, and Parity.
6. Select the Regional tab. Use this tab to set up Rating System, Time Zone, and Day Light
Savings.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 223 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Rating System: From the dropdown select the rating system to be used. The actual codes to be used are dependent on the Country setting of the device.
• Time Zone:
Hours / Minutes: Specify hours and minutes as required for the timezone.
Uses Daylight Savings Time: Check to enable if daylight savings is used.
Send Time Zone Packets: Check to enable if time zone packets are sent.
7. Select the Diagnostics tab. If required, click Reinitialize button to reinitialize the device.
8. When finished click Apply, then click OK.
9. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 224 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Database Update Redirector Support
Configuration (General)
Database Update Redirectors are software devices that propagate changes to database records to events on lists running on multiple Device Servers.
For Example: If an operator changes the database record for ID 1234 at a Media Client logged into Device Server “A”, any instances of ID 1234 on lists running on Device Server “A” is immediately updated with the new information.
If a Database Update Redirector is not configured, any instances of ID 1234 on lists running on Device Servers “B” or “C” (on the same LAN) will not be updated.
If a Database Update Redirector is configured on Device Server “A”, changes to database records will update events on lists running on Device Servers “B” and “C” as well.
All devices, whether they are media devices, non-media devices or special devices (such as
Archives, Proxy FTPs, or Redistributors), must be assigned to a device channel in the
Configured Devices window of the Configuration Manager.
The following is an example Database Update Redirector configuration. If necessary, refer to the User Notes for your device for complete details on how to configure it.
To Configure Database Update Redirector Support
1. Under Database Support in the Available pane (right pane), select a device and drag-n-
drop it to the Configured pane (left pane). For details on assigning a device see: To
Assign a Device to a Device Channel .
Once a device has been assigned to a device channel, it may be configured for specific options.
2. Select the device in the left pane, right-click and from the popup menu select Properties.
The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
3. Select the General tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 225 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Devices using Configuration Manager
Configure the following parameters as required:
• Device Name: The device name identifies the disk port. Enter the name by using up to 16 characters.
4. When finished click Apply, then click OK.
5. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 226 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Configuring NDCP Devices
Configuring NDCP Devices
About NDCP Devices
An NDCP Device is defined as any device that uses NDCP protocol version 1.0 or later as a means to be controlled by a device controller, such as ADC Device Server v11. An NDCP device uses a TCP/IP connection between the device and the controller for communication.
The physical connection is not specified, but the typical connection is 100baseT Ethernet.
A single ADC Device Server can support up to 20 NDCP Devices, which are represented on the left hand column of the configuration form. An NDCP Device may have multiple Ports and
Storage collections.
Examples of NDCP Devices are: An entire Video Disk Server including all of its play and record ports, a VTR, a Cart Machine including all of its VTRs, a CG, a Still Store, an Audio
Cart, etc.
IMPORTANT: Support for NDCP Devices requires a special Device Server build. Contact
Automation support for details.
NDCP Components
In ADC, two discrete components work together to control an NDCP Device.
The NDCP Device Driver
The NDCP Device Driver adds a new layer of configuration to the ADC Device Server. Its function is to process and interpret the NDCP protocol commands to and from the NDCP
Device, manage the TCP/IP connection with the NDCP Device, and manage redundancy through the network layer. A single ADC Device Server can support up to 20 NDCP Devices.
The Virtual Device Driver
The Virtual Device Driver is similar to the other “drivers” in the ADC Device Server, and has similar configuration characteristics. Like other ADC device drivers, the function of the Virtual
Device Driver is to interface with the ADC Transmission List and control the behavior of the
NDCP Device. The major difference between the Virtual Device Driver and the other ADC device drivers is that the Virtual Device Driver does not use RS-422 as its connection to the device. Instead, an NDCP Device Driver is specified in place of the RS-422 port. The NDCP
Device Driver then takes the instructions from the Virtual Device Driver and sends them to the NDCP Device.
The NDCP Device Driver handles communication with all types of NDCP Devices and all types of EBDOs. The Virtual Device Driver, however, is limited to the Play/Record functionality and Storage functionality of an NDCP Device. Other types of Virtual Devices will handle the other EBDO types.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 227 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
To Configure an NDCP Device
Configuring NDCP Devices
1. Ensure that a physical connection is established between the NDCP Device and the
Device Server.
2. Right-click on the name of the Device Server. A pop-up menu is displayed.
3. From the pop-up menu select “Configured NDCP Devices”. The NDCP Configuration
Form opens.
The main configuration form of the NDCP Device Driver contains the Device Tree, OK,
Cancel, and Apply buttons, and three tabs used for configuration.
• The Device Tree represents each of the 20 NDCP Devices configurable on the ADC.
• Apply button: When configuring the NDCP Device Driver, the Apply button may be used to activate any entries or changes made to the configuration. Changes do not take effect until either Apply or OK are clicked.
• OK button: Applies any changes made to the configuration and closes the form.
NOTE: Configurations are not permanently saved in the ADC configuration until Save
NDCP Devices is executed. If this is not done, the configurations will revert to the last saved version when the Device Server is restarted.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 228 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices
• Cancel button: Discards any changes made to the configuration and closes the form.
NOTE: Any changes that were applied using the Apply button will have already taken affect and cannot be cancelled.
4. From the Device Tree select one of the 20 main NDCP Devices for configuration by clicking on its representation in the Tree. The NDCP configuration form shows the main configuration items for that device.
All of the following configurations apply to the NDCP Device that is highlighted in the
Tree.
5. Select the IP tab. Use this tab to configure the TCP/IP properties and logging properties are defined for each NDCP Device.
Configure the following parameters as required:
• NDCP TCP/IP
Items in this box specify properties of the network layer connections between the
ADC Device Server and the NDCP Device.
Primary IP addr or Machine Name: The IP address of the NDCP Device is entered in this edit box. If the physical network supports name resolution, or is using DHCP, the name of the NDCP Device may be entered here instead.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 229 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices
Values: Any valid TCP/IP address or DNS name for the NDCP Device System
Controller.
Primary Port number: The TCP/IP port number that the NDCP Driver will use to communicate with the device is entered here. The recommended port numbers to be used for NDCP include 10010 to 10050. The port number that is selected must match the port number that the NDCP Device uses. If more than one
NDCP Device is controlled through the same IP address, then those devices must use different port numbers. NDCP Devices that are controlled on different
IP addresses need not have different port numbers.
Values: Any valid TCP/IP port number. Recommended values are 10010 to
10050.
Secondary IP addr or Machine Name: The NDCP Driver allows for redundant physical connections between the device and the controller. Typically, this would include two Ethernet cables, two sets of Ethernet switchgear, etc. If there are two connections, the backup IP address or computer name is entered in this edit box. If there are not two physical connections, this configuration should be left blank.
Values: Any valid TCP/IP address or DNS name for the NDCP Device System
Controller, or no entry.
Secondary Port number: If there are two physical connections between the device and the controller, then the backup connection’s port number is entered in this edit box. If there are not two physical connections, this configuration should be left blank.
Values: Any valid TCP/IP port number. Recommended values are 10010 to
10050, or no entry.
Maximum Network Latency expected: This value provides the definition of the network conditions to the NDCP Device Driver. The value is set in terms of frames of video, calculated from the video standard that the ADC is set to use. It should be set as low as the system’s network speed and throughput will permit.
The value is used by the NDCP Device Driver when calculating minimum preroll time and when to declare that a command sent to the device has timed out.
Values: Integer between 0 and 9999. Recommended setting for LAN environment is 15 or 12 (half second), higher for WAN or reduced throughput environments.
WARNING: Setting the Expected Network Latency too low will result in diminished driver performance and possible on-air problems. Make sure
Expected Network Latency matches actual network performance! ADC List
Preroll may be no shorter than (Expected Network Latency)+(Device Preroll)+(4 frames)
• Protocol Logger TCP/IP.
The NDCP Device Driver is capable of tracking all NDCP protocol messages that take place between ADC and the NDCP Device. The Driver also adds functional comments to the NDCP logs, to assist in troubleshooting.
Enable Communication Log: This checkbox, combined with the contents of the
IP addr. Or Machine Name fields, determines if a log is generated and where the data is sent.
To capture the data on a remote computer, enable the checkbox. There must also be a valid IP address and port number of a computer that is able to receive the configured log data. That computer will accept the data, and, using a TCP/IP logging application, capture it.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 230 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices
To completely disable logging, leave the IP addr. Or Machine Name fields blank, and ENABLE the checkbox. This is recommended when there is no remote logging computer available.
The log may also be generated locally on the ADC server by leaving the checkbox disabled, and the IP addr or Machine Name and Port Number fields blank. The ADC server itself will capture the data and log it to a text file.
IP addr or Machine Name: The IP address or DNS name of a computer that will accept the NDCP log data. If there is no logging computer available, this configuration should be left blank.
Port Number: The TCP/IP port number of a computer that will accept the NDCP log data. If there is no logging computer available, this configuration should be left blank.
Values: Any valid TCP/IP port number. Recommended value is 700, or no entry.
Auto Config button: Once a connection is established between the NDCP
Device Driver and the device (IP address and TCP/IP port are entered), the Auto
Config button will gather all the information about the device and automatically setup all of the parameters in the NDCP Device Driver according to the device manufacturer’s recommendations and the device’s capabilities. In most cases, this is all that is required to operate the device. This is the recommended method for configuring the NDCP Device Driver.
• Info and Status button: Launches the NDCP Device Information dialog.
The NDCP Device Driver provides information about the condition of the connected
NDCP Device in several areas. The first area is the System EBDO, which is the entry point for all communication with the NDCP Device. This feature is extremely useful for determining if a connection has been established with the NDCP Device. General information that pertains to the entire device is presented, as shown below.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 231 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices
Information tab: General information about the NDCP Device and the NDCP
Session is presented.
Con ID: Each NDCP session that is established between an NDCP Device and an NDCP Controller is given a unique connection ID. When a session is terminated the connection ID may be reused. This value is negotiated between the NDCP Device Driver and the device; it is not user-configurable. Values: Any integer value from 1-9999.
Device ID: The manufacturer of the device provides an identifier for its own management. The Device ID is not user-configurable. Values: Any string value up to 32 characters.
NDCP Protocol Version: This is the version of NDCP protocol that is being used for the current session between the NDCP Driver and the device. The information is used by the driver to determine what set of NDCP commands the device supports. NDCP Protocol Version is not user-configurable. Values: A string value up to 32 characters, containing the major and minor NDCP protocol versions.
Vendor ID: Each company that manufactures broadcast devices that can communicate using NDCP is assigned a unique Vendor ID by Imagine
Communications. Vendor ID is not user-configurable. Values: Any string value up to 32 characters.
Vendor: The name of the manufacturer of the NDCP Device is displayed here.
Vendor is not user configurable. Values: Any string value up to 128 characters.
Model ID: The model number of the NDCP Device is displayed here. In a future release, the NDCP Driver will be able to configure itself based on this and other data. Model ID is not user-configurable. Values: Any string value up to 32 characters.
Description: The manufacturer of the NDCP Device may add a comment about the device, which is displayed here. Description is not user-configurable. Values:
Any string value up to 128 characters.
Firmware Ver: If the NDCP Device reports any applicable firmware version, it is displayed here. In a future release, the NDCP Driver will be able to configure itself based on this and other data. Firmware Ver is not user-configurable.
Values: Any string value up to 128 characters.
Software Ver: If the NDCP Device reports any applicable software version, it is displayed here. In a future release, the NDCP Driver will be able to configure itself based on this and other data. Firmware Ver is not user-configurable.
Values: Any string value up to 128 characters.
Status tab: The System EBDO status tab presents general information that applies to the entire device.
Remote: Shows the status of the devices controllability. Remote is not userconfigurable. Values: (Y): The NDCP Device may be controlled by ADC. (N): The
NDCP Device may not be controlled by ADC; it is in Local Control.
System Down: Shows the general status of the NDCP Device. System Down is not user-configurable. Values: (Y): The NDCP Device is not working properly, or is initializing. It cannot be controlled by ADC. (N): The NDCP Device is working properly.
TOD: Displays the Time of Day as reported by the NDCP Device at the time the information snapshot was taken by the NDCP Driver. Values: HHHMMSSFF.
There can be up to 32 characters for the time to allow for expansion. Any leading zeros are removed. Ex: 30 seconds is represented as “3000”, not “00003000”.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 232 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices
Refresh button: When the Info and Status button is clicked, the NDCP Device
Driver takes a snapshot view of the device information and status for presentation to the user. The information and status are not updated dynamically, thus the refresh button is available. When clicked, the Refresh button will take a new, updated snapshot of the information and status.
Close button: When finished reviewing click this button to close the Information dialog and return to the configuration.
6. Select the Device tab. Configurations on the Device tab apply to the System EBDO on the NDCP Device, and affect functionality of all the other EBDOs of this NDCP Device.
Configure the following parameters as required. Items in the NDCP group box apply to the entire NDCP Device, including all Storage and Port EBDOs.
• Name: Specify any name for the NDCP Device. The name that is placed here will be used later to identify this NDCP Device in other parts of the system. This is not, however the name that will be displayed to the ADC system operator as the device name on the Transmission List. It is recommended that a name that is meaningful to the system engineering staff be chosen for the NDCP device.
Values: A string value, currently not limited in size. It is recommended that spaces and punctuation characters be avoided.
• Use Deferred Commands: When enabled, Use Deferred Commands will stamp each play or record command issued to the NDCP Device with an expected time of execution. This is recommended for absolute frame accuracy, regardless of any delay that may exist in the TCP/IP network layer.
• Time Offset.
Items in the Time Offset group box relate to how the NDCP Driver will handle any differences between the time code reference provided to the ADC Device Server and the time code reference provided to the NDCP Device.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 233 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices
Get Time from Device: When enabled, Get Time from Device will determine any time zone differences based on the TOD reported by the device. When disabled, any time zone differences are resolved.
NOTE: It is required that both ADC and the NDCP Device are locked to the same timecode provider (like a GPS service), however there may be a time zone offset.
Difference with device time reference (hour): Used to determine any time zone offset in hours between the NDCP Device and ADC when Get Time from
Device is disabled. This parameter is not used when Get Time from Device is enabled.
Values: Integer from –23 to 23.
Example: A value of 3 indicates that the NDCP Device is in a time zone that is three hours EARLIER than ADC.
• Polling time (frames): Polling Time determines the frequency at which the NDCP
Device Driver acquires Status from the NDCP Device’s EBDOs. The unit is frames, which is converted to time based on the video standard (NTSC or PAL) that is set on
ADC. Additionally, the NDCP Device may use the Polling Time value to determine whether the Controller is still alive. If the device does not receive any commands (of any type) from the controller within this interval, the device may close the NDCP session.
The polling rate is a large factor in the amount of TCP/IP network traffic that is generated between the device and the controller. It should be set based on the available bandwidth of the network layer, number of NDCP devices on the network, etc. Generally, 90 frames is a good starting point for the Polling Time in a LAN environment. If a Wide Area Network is in use, the Polling Time may be increased to substantially reduce network traffic.
The Polling Time may also be turned off altogether by setting the value to 0. This is not recommended for normal operation, as ADC will not be able to determine when the device has a problem.
Values: Integer from 0 to 1800 frames. Recommended setting: 90 frames (LAN environment – increased for WAN environment or lower network bandwidth).
• Init Device button: Click to reinitialize the entire NDCP Device at the System EBDO level. The ObReset command is issued to the device, causing a complete reset of the device. There is a warning prompt that must be confirmed before this action is performed.
CAUTION: All play and record streams WILL BE STOPPED when the Init Device
button is used!
7. Select the EBDOs tab. Items on the EBDOs tab are used to configure the number of Port and Storage EBDOs for the NDCP Device.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 234 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices
Configure the following parameters as required:
• Number of EDBOs
The various EBDO types are listed inside the Number of EBDOs group box.
Play/Rec Port: The number of currently configured Port EBDOs is displayed under the Configured column. Click on the number to edit it directly. This should be configured to match the actual number of input and output streams the NDCP
Device has. Values: Integer from 0 to 999.
Storage: The number of currently configured Storage EBDOs is displayed under the Configured column. Click on the number to edit it directly. This should be configured to match the actual number of storages the NDCP Device has.
Values: Integer from 0 to 999.
Transfer: Transfer EBDOs have not been implemented. Entries made in this box have no effect on the system.
Get from Device button: Through the NDCP, the device reports exactly how many EBDOs it has. Get From Device will automatically fill in the appropriate values for Port and Storage EBDOs.
NOTE: A connection must be established with the NDCP device before Get From
Device can be used.
• EBDO IDs.
Each EBDO of an NDCP device, except for the system EBDO, is identified by a name (Object ID, or OBID). The name is assigned by the NDCP device, and the
NDCP Driver must know what the name of an EBDO is before it can be controlled.
EBDOs Tree: The names of the EBDOs are displayed in the EBDOs Tree. The names cannot be edited directly in the tree; use the Delete and Add buttons to edit the list.
Add ID button: Launches the Add OBID dialog.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 235 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices
Specify OBID Name, Type (Port or Storage), and then click OK.
OBID Name: The names of the EBDOs can be any string value up to 32 characters (no punctuation characters, e.g. < > \ ? / ! & “ ‘ etc). Values: String up to 32 characters. Configured to match the OBID names provided by the device.
Example: The following image shows the names of the 4 configured EBDOs. The ports are named 1, 2, and 3. The storage is named 101.
Type: The Type combo box is used to select which type of EBDO this OBID identifies. Values: Port or Storage. Identifies the EBDO type for this OBID.
Delete ID button: Use Delete ID to remove an entry from the EBDOs tree.
NOTE: The EBDOs tree cannot be edited directly. Use the Delete ID and Add ID buttons to edit the tree.
Get IDs from Device button: Through the NDCP, the device reports the exact
OBID names and types for the EBDOs it has. Get From Device will automatically fill in the appropriate values for the OBIDs and Types.
NOTE: A connection must be established with the NDCP device before Get From
Device can be used.
8. When finished click OK and then Apply.
9. From the menu select File> Save NDCP Devices.
10. From the menu select File> Close. This closes the NDCP Configuration Form.
Configuring a Storage EDBO
1. From the Device Tree on the NDCP Configuration Form, select a Storage EBDO. The
NDCP Configuration form changes to show the Storage-specific configurations.
In the following image “Storage EBDO 1”, a child element of Device1, is highlighted.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 236 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices
2. Configure the following parameters as required:
• Storage #: The Storage # box is for display only, corresponding to the Storage
EBDO number that is selected in the Device Tree for a given NDCP device.
• Storage EBDO ID: A Storage EBDO ID must be bound logically within the NDCP
Driver to a Storage EBDO before it can be used. To do this, select the Storage ID from the combo box. Once the change is applied, the combo box will display the
EBDO ID with an asterisk (*). The asterisk indicates that the assignment has been made.
NOTE: Before the Storage EBDO ID can be bound to a Storage EBDO, the Storage
EBDO and the EBDO ID must be created.
• Storage Group: Items in the Storage group box affect the behavior of the storagerelated functions for the selected Storage EBDO.
Get Full List: The user may designate whether the NDCP Driver should obtain the entire list of clips that an NDCP Device has, or to determine on a case-bycase basis (based on the needs of the ADC Transmission List) if the NDCP
Device can play or record a clip.
Enabled: The NDCP Driver will obtain the entire list of clips from the device. This is recommended if the list of clips in the device is small to modest size (<
10,000). It provides faster access and cueing time for the driver, as well as a completely populated Device Storage Window on the Client applications. If the collection of clips is too large, it may adversely affect the performance of ADC and the Get Full List should be disabled in this case.
Disabled: The ADC Device Storage Window will only show clips that are within the Lookahead count of the Transmission List. Each time a clip is introduced to
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 237 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices the Transmission List Lookahead, the NDCP Driver will ask the device if it has that clip.
• Re-Read Ids button: Obtains the entire list of clips from the NDCP Device, and refreshes the Device Storage Window on the Client applications. Re-Read IDs is not typically necessary, as the NDCP Device Driver is continually managing the storage as it changes. It should be used as a troubleshooting measure only.
NOTE: Re-Read Ids will not interrupt on-air playout of the device. This function only
applies if Get Full List is enabled.
• Info and Status button: The NDCP Device Driver provides information about the condition of the connected NDCP Device for each of the EBDO types. The Storage
EBDO Status can be observed.
Refresh button: When the Info and Status button is clicked, the NDCP Device
Driver takes a snapshot view of the device information and status for presentation to the user. The information and status are not updated dynamically, thus the refresh button is available. When clicked, the Refresh button will take a new, updated snapshot of the information and status.
Information tab: There is no displayable Information for the Storage EBDO.
Status tab: Provides information about the Storage of the NDCP Device.
Percentage of Storage used: This is the percentage of the total available storage that has been used, as reported by the device. Percentage of Storage
Used is not user-configurable. Values are: 0% to 100%
Remaining Time: The NDCP device calculates the duration in hours, minutes, seconds, and frames of video that it is able to record, and reports it to the NDCP
Driver. The value is an estimate that may be based on a number of factors, including encoder bit rate, tape length, compression scheme and encoder bit
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 238 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices rate, etc. This value will change as any of the variables are changed. Values are:
HHHMMSSFF. Leading zeros are deleted.
Number of ID: The NDCP Device reports the number of clips it has for this
Storage EBDO, displayed here. Values are: Integer from 0 – 4,000,000,000
New ID’s: The number of clips that have been added to the Storage EBDO since the last time the NDCP Driver asked the device for the entire list of clips. Values are: Integer from 0 – 4,000,000,000
Deleted ID’s: The number of clips that have been deleted from the Storage
EBDO since the last time the NDCP Driver asked the device for the entire list of clips. Values are: Integer from 0 – 4,000,000,000
Modified ID’s: The number of clips that have been modified in the Storage
EBDO since the last time the NDCP Driver asked the device for the entire list of clips. Values are: Integer from 0 – 4,000,000,000
List Update Reset: Set to Y when the device cannot manage the changes to the storage. Values are: (Y): The NDCP Driver will obtain the entire list of clips to refresh the storage. (N): The device can continue to manage the change lists and the NDCP device need not refresh the storage.
3. When finished click Apply, then click OK.
4. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
Configuring a Port EDBO
1. From the Device Tree on the NDCP Configuration Form, select a Port EBDO. The
NDCP Configuration form changes to show the Port-specific configurations.
In the following image “Port EBDO 1”, a child element of Device1, is highlighted.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 239 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
2. Configure the following parameters as required:
Configuring NDCP Devices
• Port #: The Port # box is for display only, corresponding to the Port EBDO number that is selected in the Device Tree for a given NDCP device.
• EBDO ID: A Port EBDO ID must be bound logically within the NDCP Driver to a Port
EBDO before it can be used. To do this, select the Port ID from the combo box. Once the change is applied, the combo box will display the EBDO ID with an asterisk (*).
The asterisk indicates that the assignment has been made.
NOTE: Before the Port EBDO ID can be bound to a Port EBDO, the Port EBDO and
the EBDO ID must be created.
• Port Group Box: Items in the Port group box affect the behavior of the play and record-related functions for the selected Port EBDO.
Heads Group Box: Some NDCP devices are capable of preparing or cueing a number of clips prior to being played or recorded. The configurations in the
Heads group box are specific to the NDCP devices capabilities to cue media in advance.
Maximum value of MaxCuePlay: This value specifies the number of clips that the NDCP Device can cue for playout while the Port EBDO is playing a clip. This value should be set based on the capabilities of the device.
Maximum value of MaxCueRec: This value specifies the number of clips that the NDCP Device can cue for recording while the Port EBDO is recording a clip.
This value should be set based on the capabilities of the device.
Prerolls Group Box: The NDCP device requires some advanced notice before playing or recording a clip. The items in the Prerolls group box determine the minimum amount of frames before play or record that the NDCP Driver is allowed to send the command.
Play Frames: This is the minimum notice that the device needs, in frames of video (calculated from the video standard in use on ADC), prior to playing a clip.
This NDCP Driver sets this value at initialization, or whenever the user changes it. When non-deferred commands (also called immediate commands) are used, the command is sent to the device early by Play Frames. When using deferred commands (with TOD timestamps included), the NDCP Device Driver sends the commands to the device at ADC Transmission List Preroll. Values are: Integer from 0 – 300.
Record Frames: This is the minimum notice that the device needs, in frames of video (calculated from the video standard in use on ADC), prior to recording a clip. This NDCP Driver sets this value at initialization, or whenever the user changes it. When non-deferred commands (also called immediate commands) are used, the command is sent to the device early by Record Frames. When using deferred commands (with TOD timestamps included), the NDCP Device
Driver sends the commands to the device at ADC Transmission List Preroll.
Values are: Integer from 0 – 300.
• Get From Device button: Through the NDCP, the device reports its capabilities for
MaxCuePlay, MaxCueRec, and minimum prerolls. Get From Device will automatically fill in the appropriate values for all of these.
NOTE: A connection must be established with the NDCP Device before Get From
Device can be used.
• Reinit Port button: The Reinit Port button will reset the selected Port EBDO. The
ObReset command is issued to the EBDO, causing a complete reset of that port.
There is a warning prompt that must be confirmed before this action is performed.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 240 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices
CAUTION: The selected play or record stream WILL BE STOPPED when the Reinit
Port button is used!
• Info and Status button: The NDCP Device Driver provides information about the condition of the connected NDCP Device for each of the EBDO types. The Port
EBDO Status can be observed.
Refresh button: When the Info and Status button is clicked, the NDCP Device
Driver takes a snapshot view of the device information and status for presentation to the user. The information and status are not updated dynamically, thus the refresh button is available. When clicked, the Refresh button will take a new, updated snapshot of the information and status.
Information tab: Information about the Port EBDO, as well as general information about the device is presented.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 241 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices
Review the parameters and when finished, select a different tab or click Close:
Port Name: Name of the port as reported by the device is displayed. This is different from the OBID, and is not configurable. Values are: Any string value up to 128 characters.
Model ID: The model number of the NDCP Device is displayed here. In a future release, the NDCP Driver will be able to configure itself based on this and other data. Model ID is not user-configurable. Values are: Any string value up to 32 characters.
Description: The manufacturer of the NDCP Device may add a comment about the device, which is displayed here. Description is not user-configurable. Values are: Any string value up to 128 characters.
Vendor ID: Each company that manufactures broadcast devices that can communicate using NDCP is assigned a unique Vendor ID by Imagine
Communications. Vendor ID is not user-configurable. Values are: Any string value up to 32 characters.
Vendor: The name of the manufacturer of the NDCP Device is displayed here.
Vendor is not user configurable. Values are: Any string value up to 128 characters.
Firmware Ver: If the NDCP Device reports any applicable firmware version, it is displayed here. In a future release, the NDCP Driver will be able to configure itself based on this and other data. Firmware Ver is not user-configurable. Values are: Any string value up to 128 characters.
Software Ver: If the NDCP Device reports any applicable software version, it is displayed here. In a future release, the NDCP Driver will be able to configure itself based on this and other data. Firmware Ver is not user-configurable. Values are: Any string value up to 128 characters.
Frame Rate: The number of frames of video per second that the device plays or records is displayed. The NDCP Device Driver does not currently use this information. Values are: 29.97: NTSC Drop-Frame, 30: NTSC Non-Drop-Frame,
25: PAL
Timecode Mode: The method that the NDCP Device uses to count frames of video is displayed. The NDCP Device Driver does not currently use this information. Values are: (DF): The device drops frame labels to compensate for the difference between the frame rate and real time. (NDF): The device does not drop frame labels.
In Port: Indicates the Port EBDO’s capability to record media. Values are: (Y):
The port is capable of recording media. (N): The port cannot record media.
Out Port: Indicates the Port EBDO’s capability to play media. Values are: (Y):
The port is capable of playing media. (N): The port cannot play media.
Back to Back Play: Indicates the Port EBDO’s capability to play media files without any time in between. Values are: (Y): The port can play media back-toback. (N): The port needs time to cue at the end of a clip, before the next is ready to play.
Back to Back Record: Indicates the Port EBDO’s capability to record media files without any time in between. Values are: (Y): The port can record media back-toback. (N): The port needs time to cue at the end of a clip, before the next is ready to record.
MaxCuePlay: The maximum number of clips the Port EBDO can be ready to play while another clip is playing. Values are: integer from 0 to 9999.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 242 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices
MaxCueRec: The maximum number of clips the Port EBDO can be ready to record while another clip is recording. Values are: integer from 0 to 9999.
Random Mode: Indicates the Port EBDO’s capability to play or record cued clips in any order. Values are: (Y): The port can play or record any of the cued clips on demand. (N): The port must play or record clips in the same order that they are cued (Sequential Mode).
Status tab: The Port EBDO Status tab displays the current status of the selected
Port EBDO.
Review the parameters and when finished, select a different tab or click Close:
Port Down: Indicates if the port is operating properly. Values are: (Y): The port is not functioning properly or is initializing. Clips cannot be played or recorded. (N):
The port is operational.
Port Busy: Indicates if the port is able to receive commands or if it is busy processing other commands. Values are: (Y): The port is currently processing other commands and the NDCP Device Driver cannot send additional commands. (N): The port is able to process additional commands from the NDCP
Device Driver.
IO Mode: Indicates the current functionality of the Port EBDO. Values are: (O):
The port is currently set to play media. (I): The port is currently set to record media.
Current Status: Indicates what the Port EBDO is doing. Values are: (I): Idle. No clips are currently playing or recording. (P): Playing. The port is currently playing a clip. (‘R): Recording. The port is currently recording a clip. (V): VariPlay. The port is currently outputting media, but at a variable speed (e.g. Jog, Shuttle, Still).
To Cue: Indicates the number of clips that the Port EBDO can currently cue for play or record. Values are: Integer from 0 – 9999.
In Preparation: Indicates if the Port EBDO is currently cueing a clip to play or record. Values are: (Y): The Port EBDO is currently cueing a clip. The NDCP
Device Driver may not issue any additional cue commands during this period.
(N): The Port EBDO is not cueing. The NDCP Device Driver may cue a clip to play or record, if the 'ToCue' value is greater than 0.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 243 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring NDCP Devices
Ready: Indicates that the Port EBDO is able to play or record a cued clip. Values are: (Y): The NDCP Device Driver may issue a play or record command. (N): The
NDCP Device Driver may not issue a play or record command.
Current ID: Indicates the Clip Name of the currently playing or recording clip on the Port EBDO. This is blank if the Port EBDO is Idle. Values are: String value up to 32 characters.
Current File Handle: Indicates the Clip File Handle of the currently playing or recording clip on the Port EBDO. The file handle is assigned by the NDCP
Device Driver as a means to track the clip while it is active on the device (cued, playing, or recording). This is blank if the Port EBDO is Idle. Values are: Integer from 1 – 9999.
Current Timecode: Indicates the Timecode value of the media currently playing or recording on the Port EBDO. Values are: HHHMMSSFF.
Play Speed: If the Port EBDO is in VariPlay mode, this indicates the speed at which the port is outputting media. This is blank if the port is not in VariPlay.
Values are: Number to 2 decimal places, from –100.00 to 100.00
Loop Status: Indicates if the Port EBDO will repeat the currently playing or recording clip. Values are: (Y): The current clip will start over when complete, without additional commands from the NDCP Device Driver. (N): The current clip will not start over when complete.
Play Preroll: Indicates the Play Preroll setting that the device is currently using.
Values are: Integer from 0 - 300
Rec Preroll: Indicates the Record Preroll setting that the device is currently using. Values are: Integer from 0 - 300
TOD: Displays the Time of Day as reported by the NDCP Device at the time the information snapshot was taken by the NDCP Driver. Values are: HHHMMSSFF.
There can be up to 32 characters for the time to allow for expansion. Any leading zeros are removed. For example: 30 seconds is represented as “3000”, not
“00003000”.
3. When finished click Apply, then click OK.
4. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 244 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring a Virtual Device
Configuring a Virtual Device
About the Virtual Device Driver
In ADC, the Virtual Device Driver works in conjunction with the NDCP Device driver to control an NDCP Device. A single ADC Device Server can support up to 20 NDCP Devices.
For more information on NDCP Devices and driver see About NDCP Devices .
The Virtual Device Driver is similar to the other “drivers” in ADC Device Server v11, and has similar configuration characteristics. Like other ADC device drivers, the function of the Virtual
Device Driver is to interface with the ADC Transmission List and control the behavior of the
NDCP Device. The major difference between the Virtual Device Driver and the other ADC device drivers is that the Virtual Device Driver does not use RS-422 as its connection to the device. Instead, an NDCP Device Driver is specified in place of the RS-422 port. The NDCP
Device Driver then takes the instructions from the Virtual Device Driver and sends them to the NDCP Device.
The NDCP Device Driver handles communication with all types of NDCP Devices and all types of EBDOs.
The Virtual Device Driver, however, is limited to the Play/Record functionality and
Storage functionality of an NDCP Device.
Other types of Virtual Devices will handle the other EBDO types.
To Configure a Virtual Device Driver
This section describes the configuration and function of each of the parameters in the Virtual
Device Driver.
IMPORTANT: Configuring the Virtual Device requires that the NDCP Device Driver configuration
1. Ensure that a physical connection is established between the NDCP Device and the
Device Server.
2. Right-click on the name of the Device Server. A pop-up menu is displayed.
3. From the pop-up menu select “Configured Devices”. The Configured Devices Form opens.
4. Under NDCP Devices in the Available pane (right pane), select a device (e.g. Multi-Port
Play/Rec Device) and drag-n-drop it to the Configured pane (left pane). For details on
assigning a device see: To Assign a Device to a Device Channel .
Once a device has been assigned to a device channel, it may be configured for specific options.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 245 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring a Virtual Device
5. Select the device in the left pane, right-click and from the popup menu select Properties.
The configuration dialog is displayed for this device. Use the left and right arrows at the upper right to scroll through the other tabs.
6. Drag the Multi-Port Play/Rec Device from the Available column on the left to a Channel on the Configured column to configure it. Double click on the Device Name icon (e.g. V1-
20 icon for Multi-Port Play/Rec Device), and the Virtual Device Configuration form is displayed.
The Multi-Port Play/Rec Device is a multi-steam device, meaning it may control up to a maximum of twenty Port EBDOs from the pool of available configured NDCP Devices.
7. The Device Tree, on the left side of the Virtual Device Configuration form, is where the elements of the device (Storage and Ports) are represented.
Click on the parent element in the Device Tree, the configuration window displays settings that apply to the entire Virtual Device Driver.
NOTE: Items in the Device group box apply to all of the configured streams, as well as
the storage of the Virtual Device Driver.
8. Select the General tab. Items on the General tab are global to the Virtual Device. The name and dimensions of the Virtual Device are established here.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 246 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring a Virtual Device
Configure the following parameters as required:
• Device Name: The Device Name is configurable by the user to identify the Streams and Storage of the Virtual Device in other parts of the system, such as the
Transmission List, the Device Storage window, etc. Values: String up to 16 characters.
• Number of Heads per Stream: A Stream on the Virtual Device Driver represents a media input or output on the physical device, and each of these Streams has a number of Heads associated with it. Throughout the ADC software, device capabilities are compared to that of a VTR. The VTR is represented in ADC as having one Head. Other devices, such as the Video Disk are represented as having two or more Heads. This means it has capabilities similar to two or more VTRs, in the sense that the Disk can play back-to-back with no time between media files required for cueing. The second Head cues while the first Head is playing (like a second VTR fast-forwarding to a cue point while the first VTR plays). The difference between the two VTRs and the Video Disk: the Disk port is one Stream (with internal switching to handle directing the media between the two Heads), and the two VTRs are two discrete Streams, requiring external handling of the switching.
In the Virtual Device Driver configuration, unlike other ADC device drivers, the number of Heads per Stream is configurable. The value applies to each Stream on the Virtual Device.
Consult the device-specific user notes to determine the necessary settings for
Number of Heads per Stream. The value entered in Number of Heads per Stream will depend on the device capabilities, available ADC resources, desired minimum length of the shortest media file, etc. A typical setting for this is the value of (MaxCuePlay +
1). Values: Integer from 1 to 20
NOTE: There is a limit of no more than 20 total Heads per Virtual Device Driver, and the Heads are allocated evenly to the Streams. Thus, be careful not to violate the following formula: (Number of heads per Stream) x (Number of Ports on this device)
<= 20
• Number of Ports on this device: The Virtual Device Driver, unlike most ADC device drivers, is capable of controlling multiple Streams (inputs or outputs) with a single driver. The number of Streams is configurable per Virtual Device. Typically, it is configured to represent the number of Streams that the device itself has, but sometimes there are more Streams on the device than the Virtual Device Driver can control. In this case, additional Virtual Device Drivers may be configured to control the remainder of the Streams.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 247 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring a Virtual Device
Likewise, it is not necessary to configure the number of Streams to the full capacity of the Virtual Device Driver; it is best to use only the required number of Streams.
Consult the device-specific user notes to determine the necessary settings for
Number of Ports on this device. The value entered in Number of Ports on this device will depend on the device capabilities, available ADC resources, etc. Values: Integer from 1 to 20
NOTE: There is a limit of no more than 20 total Heads per Virtual Device Driver, and the Heads are allocated evenly to the Streams. Thus, be careful not to violate the following formula: (Number of heads per Stream) x (Number of Ports on this device)
<= 20
9. Select the Events tab.
The parameters in this section define which types of ADC events the Virtual Device will handle, and which fields of those events provide significant information regarding the availability of the media the event represents.
Primarily, these configurations determine if the driver will assume ownership of an ADC event. For the purposes of this document, “ownership” is defined as registering the media. This is best represented when the event turns from red to blue on the transmission list.
The proper configuration of these settings is specific to the type of device that is being controlled by the Virtual Device Driver. When in doubt, consult the device-specific user notes for the proper configuration of these settings.
• Primary tab
Each type of event that the Virtual Device Driver supports is represented by a tab inside the Events Supported group box. The Primary Tab is the first of such tabs.
Configurations inside this tab apply to all of the ADC’s Primary type events that the
Virtual Device Driver can play or record.
Enabled: The Enabled configuration determines if the Virtual Device will attempt to play this type of event.
Enabled: The driver will attempt to take ownership of an event for playout or recording when the ADC list asks it to, provided it passes the remaining requirements.
Disabled: The driver will ignore all requests to take ownership of an event of this type.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 248 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring a Virtual Device
Enable Match Name in ID field: This configuration controls how the Virtual
Device Driver determines which events it should own, and which field of the event represents the media’s identification. (NDCP: aMId).
Enabled: Only events that contain the Virtual Device’s Match Name in the event’s Material ID field will be considered for play or record (the match name is configurable for each port of the Virtual Device Driver. Match Name is discussed in Section 0 below). The ID that is used to identify the media itself is found in the
Title field of the event.
Disabled: The ID that is used to identify the media is found in the Material ID field of the event. Provided that the ID in the Material ID field passes the Storage
Check (does the device have this ID?), the Virtual Device will take ownership of the event.
NOTE: This configuration has no effect if “Enable” is unchecked – no events are owned in this case.
Omit Storage Check: It is possible for a Virtual Device to take ownership of an event without checking to see if the device has the media in its storage. Some devices do not maintain storage, and therefore are not capable of reporting the contents of the device. An example of this is a character generator.
Enabled: Rather than checking to see if the device has the requested media, the
Virtual Device will assume that it can play or record it, and take ownership of the event if the other requirements are met. This parameter is best used in conjunction with “Enable Match Name in ID Field” above. This way, there is some filtering on which events are owned (the Match Name). If Omit Storage Check is enabled and Match Name is not, the Virtual Device will take ownership of every event that is presented to it.
Disabled: The virtual device will check to see if the device has the media ID before it will take ownership of the event. The field that is checked against the storage depends on the setting of “Enable Match Name in ID Field.” If Match
Name is enabled, the content of the Title field is checked against the storage.
Otherwise, it is the content of the Material ID field that is checked.
NOTE: This configuration has no effect if “Enable” is unchecked – no events are owned in this case.
• Sec AV tab: The configurations inside the Sec AV Tab define how the Virtual Device
Driver will process ADC events of the Secondary Audio/Video type. The configurations are the same as in Sections 0 through 0 above.
• Sec Bt AV tab: The configurations inside the Sec BT AV Tab define how the Virtual
Device Driver will process ADC events of the Secondary Back-Timed Audio/Video type. The configurations are the same as in Sections 0 through 0 above.
• Sec Data tab: The configurations inside the Sec Data Tab define how the Virtual
Device Driver will process ADC events of the Secondary Data type. The configurations are the same as in Sections 0 through 0 above.
10. Init Device button
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 249 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring a Virtual Device
The Init Device button is a diagnostic tool that should only be used when there is a serious problem with the device. When clicked and confirmed, the Init Device button will reset the Virtual Device Driver (configurations are preserved). The user will also be asked if the NDCP Driver and the device itself should also be reset. This additional function is the same as clicking the Init Device button on the NDCP Driver, described in Section 0 above.
CAUTION: All play and record streams WILL BE STOPPED when the Init Device button
is used!
11. When finished click Apply, then click OK.
12. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
Configure Storage EDBOs
The Storage EBDO is where the Virtual Device Driver keeps track of what media the NDCP device has available.
1. To access the properties for the Storage EBDO, click on its representation in the Device
Tree.
2. Configure the following parameters as required:
• NDCP Device Binding Group Box: The Virtual Device Driver must be associated with an NDCP Storage EBDO in order to be used, and the configurations in the
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 250 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring a Virtual Device
NDCP Device Binding box are where the associations are made. The NDCP Storage
EBDO must be configured first (Sections 0, 0, and 0).
NDCP Device #: This list contains all of the configured NDCP Device Drivers on this Device Server. Select the name of the NDCP device that this Virtual Device
Driver will control.
Storage: If the NDCP Device that is selected above has any Storage EBDOs, they will appear in this list. Select the one that the Virtual Device Driver should use to validate its media inquiries against.
NOTE: An NDCP device may have more than one Storage EBDO, but the Virtual
Device Driver only supports one. If a second one is required, an additional Virtual
Device Driver can be used. The Storage of an NDCP Device may be shared among multiple Virtual Devices. Also, it is valid for a Virtual Device Driver to not use the Storage EBDO, but the storage check must be disabled.
Display Storage: Display Storage controls the visibility of the device’s list of media at the automation Client applications.
Enabled: The contents of the Storage EBDO are forwarded over the network to the Client Applications. The client applications can build a “Device Storage
Window” to display the list of media.
Disabled: No list of media is forwarded to the Client Applications. There is no
Device Storage Window associated with this Virtual Device Driver. This is useful if the list of media is very large (10,000 +). Disabling this parameter will save system resources and improve performance.
• Directories Group Box: Within a Storage EBDO, the NDCP provides additional means to subdivide the list of media through the use of directories. When configured, the Virtual Device Driver can specify a directory to use when searching for or recording media.
Use Directories: Use Directories controls the Driver’s ability to add a file path name to the Media ID when searching for or recording media.
Enabled: The Virtual Device Driver will prefix the Media ID with the file path specified in the Default Directory edit box.
Disabled: The Virtual Device Driver uses the Media ID only, with no file path name specified. The NDCP Driver will add its own default directory of Root (/) in this case.
Version 1 Implementation NOTE: Directories are not supported in the first release.
Default Directory: When Use Directories in enabled, the file path specified here will be used when searching for or recording media.
Version 1 Implementation NOTE: Directories are not supported in the first release.
3. When finished click Apply, then click OK.
4. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
Configure Port EDBOs
The Port EBDO is the actual stream of media that will be assigned to the ADC transmission list for playout or recording
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 251 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring a Virtual Device
1. To access the properties for the Port EBDO, click on its representation in the Device
Tree.
2. Select the General tab. Configurations in the General tab pertain to the selected Port
EBDO.
Configure the following parameters as required:
• NDCP Device Binding Group Box: The Virtual Device Driver must be associated with an NDCP Port EBDO in order to be used, and the configurations in the NDCP
Device Binding box are where the associations are made. The NDCP Port EBDO must be configured first.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 252 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring a Virtual Device
NDCP Device #: This list contains all of the configured NDCP Device Drivers on this Device Server. Select the name of the NDCP device that this Virtual Device
Driver will control.
Port: If the NDCP Device that is selected above has any Port EBDOs, they will appear in this list. Select the one that should be represented by the selected Port on the Virtual Device.
NOTE: It is not necessary to associate all of the Virtual Device’s Port EBDOs with an NDCP Device. Additionally, all of the NDCP Device’s Port EBDOs need not be associated with a single Virtual Device. If there are more Port EBDOs on a single NDCP device than the Virtual Device can support, additional Virtual
Devices can be configured to control the remaining Port EBDOs. The same
NDCP Device Port EBDO cannot be shared by two Virtual Device Drivers.
• ID Match Name: The ID Match Name is the identifier that is used by the Virtual
Device when the ADC Transmission List asks it to play media from this stream.
Depending on the configuration of the Events Supported parameters (Section 0), the
Virtual Device may take ownership of an event that contains the ID Match Name in its
ID Field. Values are: String, no spaces, up to 16 characters.
NOTE: The ID Match Name has no effect unless the “Enable Match Name in ID
Field” is enabled.
• Play/Record Mode: The Play/Record capabilities of the Port are defined here. This should be set according to the abilities of the hardware.
Values are:
Play Only, no Record: The Virtual Device will attempt to take ownership of
Primary Play, Secondary A/V, Secondary Backtimed A/V, and Secondary Data
Events only.
Record Only, no Playout: The Virtual Device will attempt to take ownership of
Primary Record and Secondary Record Events only.
Play and Record: The Virtual Device will attempt to take ownership of Primary
Play, Primary Record, Secondary A/V, Secondary Backtimed A/V, Secondary
Data, and Secondary Record Events.
NOTE: Switching modes between Play and Record is handled automatically by the
Virtual Device, but only one type of event (Play or Record) can be cued at a given time. Thus, a Play event cannot be played back-to-back with a Record event, and
vice-versa.
3. Select the Play tab. Configurations on the Play tab affect how the Virtual Device will handle ADC Play type Events that it owns.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 253 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring a Virtual Device
Configure the following parameters as required:
• Enable Segment Play within ID: This configuration affects the Virtual Device’s use of Offset Cueing.
Enabled: When a media file is cued (prepped), an offset is provided in the form of a
Timecode value. This value is extracted from the SOM field of the ADC Event, allowing a single file to be played from any point within itself.
Disabled: No offset is provided when a media file is cued, and by default, the file is cued at the beginning in all cases.
• Update Event Duration from device: This should only be used in the event that there is no automation Database available to get the duration information from.
Durations provided by the device pertain to the entire file, and are generally slightly larger than the intended play time.
Enabled: The Virtual Device Driver will extract the Duration of each instance of media from the device and publish it in the Device Storage.
Disabled: The Virtual Device will not update any durations.
• Alternate Port for Playout: In certain cases, it is necessary to use two streams of a device on a single Transmission List to achieve Mix Effects through a master control switcher.
By configuring an Alternate Port for Playout, the Virtual Device Driver will share ownership of the ADC Events it can play with the Alternate Port, assuring that backto-back Events always originate from different physical sources.
NOTE: Both ports to be used must be assigned to the Transmission List. Of the two
Port EBDOs used, only one of them should have an Alternate Port configured, and it must be the one with the lowest number in the Device Tree. The second port (pointed to by the first) should have No Port configured. The Alternate Port must be a Port
EBDO from the same Virtual Device.
4. Select the Record tab. Configurations on the Record tab affect how the Virtual Device will handle ADC Play type Events that it owns.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 254 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring a Virtual Device
Configure the following parameters as required:
• Enable Back to Back Record: This configuration determines the behavior of the
Virtual Device when two Record Events appear consecutively on the ADC
Transmission List. This parameter should be set based on the capabilities of the device being controlled.
Enabled: The Virtual Device will attempt to record a Record Event immediately upon the completion of the previous Record Event, provided that there is an available head to cue the Event ('ToCue' is not 0).
Disabled: The Virtual Device will withhold cueing and recording a Record Event until the previous Record Event has completed. This requires that there be sufficient time between Record Events for the device to cue.
• Segments Group Box: Configurations in the Segments box apply to events that contain an entry in the Segment field of the ADC Event.
Record Segments: Record Segments is a qualifier for Record Events that have a Segment Number.
Enabled: The Virtual Device will attempt to take ownership of Record Events that contain an entry in the Segment field of the Event.
Disabled: The Virtual Device will not take ownership of a Segmented Record
Event.
Modify Ids for events with Segments: Modify Ids is a method for managing segmented media by means of concatenating an ID and a Segment number. The new value (Material ID + Segment Number) becomes the Media ID and will be the file name of the media. This is used when media is to be segmented into multiple files on the device, instead of a single file using offset cueing.
Values are:
0: ID modification is disabled. There is no segment number attached to the material ID. Example: ID = XYZ, Segment Number = 1. The filename is XYZ.
1: The ID is modified by adding a one-character segment number to the Material
ID. Example: ID = XYZ, Segment Number = 2. The filename is XZY2. There is a limit of 10 segments using this method.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 255 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring a Virtual Device
2: The ID is modified by adding a two-character segment number to the Material
ID. Example: ID = XYZ, Segment Number = 3. The filename is XZY03. There is a limit of 100 segments using this method.
• Recording Qualifiers Group Box: Recording Qualifiers are filters that are applied to an ADC event. If the event passes the additional specifications in the Qualifiers, then the Virtual Device will take ownership of the Event.
Duration less than: Specify a duration in minutes that an Event cannot exceed.
If the event meets or exceeds this duration, the Virtual Device Driver will not take ownership of the Event.
Duration greater than: Specify a duration in minutes that an Event must meet. If the event does not meet or is less than this duration, the Virtual Device Driver will not take ownership of the Event.
Record ID’s whose first character is greater than: Specify a character that an
Event’s first character cannot be less than. If the Event’s first character is less than the one specified, the Virtual Device Driver will not take ownership of the
Event.
NOTE: The characters are assigned a value based on their position in the ASCII table. The order, from least to greatest, is: 0...9, A...Z, a…z.
Record ID’s whose first character is less than: Specify a character that an
Event’s first character cannot be greater than. If the Event’s first character is greater than the one specified, the Virtual Device Driver will not take ownership of the Event.
5. Select the Config tab. The Config tab regulates miscellaneous functionality applicable to this Port.
Configure the following parameters as required:
• Stop Play/Record on Init: This parameter controls the behavior of the Virtual Device
Driver when a connection is first established with the device through the NDCP
Device Driver.
Enabled: When the connection is established between ADC and the device, the
Virtual Device Driver will stop any playing or recording media on this Port, and reset it completely.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 256 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring a Virtual Device
Disabled: When the connection is established between ADC and the device, no action is taken to initialize the device and playout or recording will continue if it was in progress. The user should, however, manually reinitialize the port as soon as possible or the system may not operate properly.
• Send Early Group Box: It is possible to manually adjust the timing of the play and record commands sent to the device, relative to the time reference that is used on
ADC. When adjusted, the Virtual Device Driver will offset the absolute time that the commands are executed by Play Frames or Record Frames. Normally it is not necessary to do this, as both ADC and the device have a stable Timecode reference.
It is useful, however, if there are external delays on the media input or output that delay the media by a known number of frames (such as MPEG noise reduction).
Play Frames: Play Frames adjusts the absolute time that a Play command is sent to the device with respect to the ADC Timecode reference. Values are: -300 to
300 frames.
Example: Play Frames is set to 5. System Type is NTSC DF. Device Preroll is set to 40 frames. An event is scheduled to play at 14:28:30:00. The Play command will be sent to the device no later than when the ADC Timecode reference indicates 14:28:28:15, and the Timestamp on the command will instruct the device to Play at 14:28:29:25, plus any fixed difference between the
ADC Timecode Reference and the device’s Timecode Reference.
NOTE: While the maximum value may be set to 300 frames (10 seconds NTSC and 12 seconds PAL), be careful not to violate this formula: ListPreroll >
((ExpectedNetworkLatency) + (DevicePreroll) + (SendEarly) + (4 frames))
Record Frames: Record Frames adjusts the absolute time that a Record command is sent to the device with respect to the ADC Timecode reference.
Values are: -300 to 300 frames.
NOTE: While the maximum value may be set to 300 frames (10 seconds NTSC and 12 seconds PAL), be careful not to violate this formula: ListPreroll >
((ExpectedNetworkLatency) + (DevicePreroll) + (SendEarly) + (4 frames))
6. Re-Init Port button
Functionality of the Re-Init Port Button is similar to the Re-Init Device button, except that only the selected Port EBDO is reset.
CAUTION: The selected play or record stream WILL BE STOPPED when the Re-Init Port
button is used!
7. When finished click Apply, then click OK.
8. From the Configured Devices window select File> Save Devices. The current configuration is written to the Device Server’s configuration files in the “C:\Server” folder on the Device Server.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 257 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Device Assignments
Configuring Device Assignments
Assigning Devices to Lists
To assign devices to lists for a specific Device Server, perform the following procedures in order presented in this section.
About List Assignments
Generally speaking, once a device has been assigned to a list, it cannot be used by any other lists. To use a media device on another list, it must first be un-assigned from the first list.
Devices with multiple output streams may be assigned to several lists simultaneously. A cart machine with four VTRs, assuming that the cart machine is capable of routing the output from each VTR to a different destination simultaneously, may have its VTRs assigned to different lists for different purposes. A video server with multiple decoder ports will generally have each decoder port assigned to a different list.
Stand-alone VTRs may be left un-assigned and used as “floater” VTRs. This makes the VTR available for use by any list. See the Air Client Operator Guide for more information about using “floater” VTRs.
To Start List Configuration
1. Right-click on the name of the Device Server. A pop-up menu is displayed.
2. From the pop-up menu select “List Configurations.” The List Assignments window is opened.
• The left pane displays the available lists in your system – your system may not have a full 16 lists available.
• The right pane displays the configured media devices available for assignment to a list.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 258 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Device Assignments
Main Menu Options
The List Assignments window has a number of drop-down menus available.
File menu
The File menu has the following options:
Option
Save
Properties
Save
Configuration
Locally
Configuration
Unassign
Select to…
Save the current configuration to the Device Server’s configuration files. It has the same action as the Save Devices option in the Configured Devices window’s File menu.
Save the Device Server’s configuration files to an alternate location. Only the
ADC100NT.INI and LISTCONF.INI files are saved. This allows you to back up your current configuration to an alternate location (recommended).
Choosing this option will open an Explorer window and allow you to choose where to save the files.
Print the Device Server’s configuration files, if you have a printer attached to the client PC (or a network printer configured). Caution: the configuration files can be quite large! Be sure to have plenty of paper in your printer.
Un-assign the selected device from its list and return it to the Available Media pane. This may be accomplished using the keyboard’s DEL key as well.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 259 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Option Select to…
Add
Requester
Remove
Requester
Configuring Device Assignments
Associate a GMT Requester with a specific device. See chapter 7 of this manual for more details about GMT and Requesters.
Remove a GMT Requester from its association with a specific device.
Properties
Audio Video
Preview Audio
Video
Close
Invoke the properties configuration GUI for the selected list.
Invoke the audio/video routing table configuration GUI for the selected list.
Preview audio/video routing table configuration GUI. The routing tables configured here apply globally to all devices used by the system.
Close the List Assignments window.
View menu
The View menu has the following options:
Option
Connections
Refresh
Select to…
Open a window that displays all of the Device Servers and client applications currently logged into this Device Server.
Refresh the display in the List Assignments window.
Help menu
The Help menu has the following options:
Option Select to…
Contents**
Topic
Search…**
Display the contents of the help file.
Display a search engine for the help files.
How to Use
Help**
About…
Display a Windows help file with information about how to use the help file.
Launch a dialog displaying version and copyright information of the currently selected Device Server.
**NOTE: These Options are currently unavailable.
To Assign a Device to a List
1. Select a device in the right pane (Available Media), drag and drop it on to the desired list in the left pane.
• Once a device has been assigned to a list, that device is exclusive to that list, and cannot be shared by another list.
• The only exception to this rule is a video disk with multiple streams. Each stream of a video disk can be assigned to a different list, thereby allowing multiple lists to share the same video disk. Example: The record stream could be assigned to a media list, and the playout stream assigned to the play list.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 260 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Device Assignments
2. Save this assignment: From the List Assignments window main menu select File > Save
Properties. This saves the list configurations to the device server’s configuration files.
Assigning a Protect Device
Stations that have purchased the Air and Protect option for their Automation system, may wish to assign a Protect device to a list to run in parallel with their primary Air playout device.
If the automation system detects a failure in the Air device – for example, a tape or video server decoder port fails to cue – the automation system sends a command to your master control switcher to take the Protect device to air and switch away from the (now failed) Air device. The Air device and the Protect device run in parallel, synchronized to frame-accuracy, so the switch is not apparent on air.
If the Air device fails due to an error not detectable by the automation system, such as a tape head clog or simply bad audio or video, operators may manually switch to the
Protect device using a button on either the Air Client’s software or hardware control panels.
It is recommended that Air and Protect only be used with devices of a similar type. A cart machine may protect another cart machine, or a decoder port on one video server may protect a decoder port on another video server. A video server with multiple decoder ports sharing a common storage array may have decoders on the same device protecting one
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 261 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Device Assignments another, but is recommended that the Air decoder and Protect decoder be on separate I/O nodes.
NOTE: Both the Air and Protect devices must have exactly the same media available in
storage.
To Assign a Protect Device to a List
1. Select the Protect device from the right pane.
2. Drag and drop it on the Air device in the left pane.
• Take care not to drop it on the list. This will assign this device to the list as a Protect device for the Air device.
• The word “Protect” in parentheses indicates that this device is now protecting the Air device above it.
Configuring GPI Control
Devices that cannot be controlled through a serial or Ethernet interface may be controlled using a General Purpose Interface (GPI) trigger. A GPI is a relay contact closure that provides either a high-to-low or a low-to-high transition to trigger devices that accept this type of control. A single Device Server can support up to 32 contact closures (four GPI cards),
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 262 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Device Assignments although the standard Device Server configuration includes two GPI cards. Additional GPI cards may be purchased separately.
GPI triggers are configured in the Configuration Manager Tool as Switch-Only devices.
To Configure a GPI Trigger
1. After assigning a Switch-Only device to a device channel, double-click the entry in the
Configured pane (Left pane) to open the configuration GUI.
2. Select the GPISheet tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 263 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Device Assignments
3. On the GPISheet tab configure the following entries as required:
• Switch Only: In this drop-down box, select which of the eight Switch-Only device media heads you wish to associate with the GPI trigger. The eight media heads correspond to the eight names configured on the General tab.
• GPI Card: Select which of the Device Server’s GPI cards contains the relay contact you wish to associate with this Switch-Only device.
• Contact Number: Select which of the eight contacts (bits) on the selected GPI card you wish to associate with this Switch-Only device.
• Pulse Width: For Primary GPI events, specify the length of the contact closure (in frames). See the Air Client Operator Guide for an explanation of Primary and
Secondary GPI events.
• Pulse Offset: For Primary GPI events, specify any back-timed offset from the zero crossing for this contact closure (in frames). With a zero offset configured, Primary
GPI events will trigger at the list pre-roll time.
NOTE: Refer to the device manufacturer’s manual for information regarding GPI triggering requirements.
4. When finished click Apply, then click OK.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 264 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Configuring List Types
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 Automation 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]>
<output directory>
[-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
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 265 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types 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.
Examples:
C:\WINCMMS\WinCMMS.exe A:\ E:\Playlist
This example will translate traffic logs 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
AsRun logs back into traffic reconciliation logs, combine AsRun 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 .
•
•
•
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 266 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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 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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 267 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Configuring Transmission List/Playlist
Options
About Transmission Lists / Playlists
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
• An unregistered event is modified and the media is now available
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
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 268 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
• 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.
Record Lists and GMT Push Lists
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”.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 269 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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
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.
3. Select the Parameters tab. This tab contains general configuration options for
Transmission Lists. Some options are commonly used and enabled by default.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 270 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Configure the following options as required:
• Name: Enter a name for this Transmission List. List names are limited to 16 characters.
• Options:
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).
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.
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.
Recue On Media Changes: (Default: enabled) When enabled, this option causes events to automatically recue if the event’s SOM (start-of-message time) is changed.
Update Cued Event on Media Change: When this parameter is enabled
(checked), all of the database derived metadata for any cued events is updated.
If ‘Recue on Media Changes’ parameter is enabled, then this parameter is also enabled.
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
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 271 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
get out of sync. To avoid this ensure ‘Recue on Media Changes is also
set.
If this parameter is disabled, ‘Recue on Media Changes’ must also be disabled and no updates will be applied to cued events.
If Auto Ripple is enabled, the start time of the event following the an updated event is also updated.
Manual Subtitler Mode Enabled: As required enable (check) / disable
(uncheck) Manual Subtitler Mode Enabled.
When disabled (default), the Subtitler (e.g. Screen, Cavena, etc.) works in automatic mode.
When enabled, the Subtitler (e.g. Screen, Cavena, etc.) works in manual mode.
Following each change in operational mode, subtitler devices have to be unassigned and then reassigned to the playlist. It is important to note that the same operational mode selection applies to all subtitling devices assigned to a given playlist.
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
0
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:
Enable Recue On Media Changes: Check to enable.
“Update Cue Event on Media Change: Check to enable.
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 +
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 272 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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:
When the termination event is an O (hard start) event the Time To
Next display includes the running short value.
Zero duration up counters do not stop the rippling.
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.
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.
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.
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).
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.
If this parameter is enabled, then ‘Update Cued Event on Media
Change’ must also be enabled.
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.
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
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 273 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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:
Enable Recue On Media Changes: Check to enable.
“Update Cue Event on Media Change: Check to enable.
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
0
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:
Enable Recue On Media Changes: Check to enable.
“Update Cue Event on Media Change: Check to enable.
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)
• 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
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 274 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
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 re-tensioned 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.
NOTE: All of the options on this tab may also be configured in the Air Client application.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 275 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Enable (check)/ Disable (uncheck) and configure the following as required:
• Options:
Switch To Black: 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.
Play Hard Hits: 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.
Contact Start: 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.
Auto A-B Routing: 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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 276 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Play ID Title Mismatches: 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.
Skip Bad Events: 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: 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.
Release Tension When Cued: Enabling this option causes the system to send a
“standby off” command to any VTRs when they have cued a tape. The tape is re-tensioned at the standby on time.
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: Enabling this option causes the on-air time for events to update to the actual time the event rolled. AsRun logs for the list are updated as well.
When disabled, the AsRun logs reflect the time-of-day that appeared on the
Transmission list, rather than the actual time the event rolled.
Auto Ripple Times: 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.
Tension After Up Counter: 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: 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.
When disabled, the list must be threaded manually before it can execute a Play command.
Keep List Threaded: 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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 277 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
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.
5. Select the Lookahead tab. This tab contains the configuration options for this
Transmission list’s lookahead.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 278 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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 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).
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 279 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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 AsRun logs created by the Air Client application.
• By default, not all secondary event types are logged to the AsRun log. Checking the appropriate checkbox on this tab will enable logging of that secondary event type.
• If this Transmission list is to be used as a record list and you require a log of what has been recorded, an AsRun log may be created that includes primary record events. Check the Log Record Events checkbox to enable this.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 280 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
• Secondary Events to Log:
Enable (check)/ Disable (uncheck) the secondary events to log in the AsRun log.
When all check-boxes are selected (checked), all secondary events associated with a primary are included in the AsRun log.
For Example: BREAK is disabled and others are enabled – all secondary events except BREAK secondary event are included in the AsRun log.
For descriptions of all listed Secondary Events see, Appendix C: Secondary Events .
• 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 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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 281 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
Medium: Valid numbers are 0 to 999 frames. Default is 30 frames.
Fast: Valid numbers are 0 to 999 frames. Default is 15 frames.
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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 282 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
• 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.
8. Select the Linking tab. List linking is an option that may be purchased separately for your
Automation system. List linking allows one Transmission list to act as a master list for linked lists. The linked lists roll events simultaneously with the master list. The options on this tab enable list linking.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 283 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Configure the following options to enable list linking as required:
• List is Master: (Default: disabled) For linked lists where the sectional lists must be complete (i.e., have all spots that are on the primary list, with the exceptions).
• List is Keyed Master: (Default: disabled) Use this option when the sectional lists are sparse and the exceptions have keys to control them when they run.
• To link a list, select a list from the Available column, then click the Add to <– button to move it to the Linked column. List is Master and List is Keyed Master have no effect if no list is selected as a linked list.
Reference NOTE: Reference the LinkList user notes for more information.
9. Select the Compiler tab. The Compiler function is an option that may be purchased separately for your Automation system.
IMPORTANT: This option is only available if the optional compiler function has been
purchased.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 284 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Configure the following options as required:
• Skip Missing Material: (Default: disabled) The compiler leaves space for events in a pod that are not currently available to be compiled. It then continues to compile the pod around the missing material. If you enable this option and then later change the duration of any of the missing items of material you will have to recompile the remainder of the pod after the event whose duration changed.
• Log Errors: (Default: disabled) Check this box to cause all compile errors to be recorded into a logfile.
• Time Parameters:
SOM: (Default: 00:01:00:00) Specify a Start Of Message (SOM) value for the compile tape.
Tape Length: (Default: 01:30:00:00) This is the duration of the compile tape.
Break Gap: (Default: 00:30:00:00) The distance between the end of black on one pod and the start of black on the next pod.
Black In: (Default: 00:00:00:00) The amount of pre-black to record on the tape before recording the first compiled event.
Black Out: (Default: 00:00:00:00) The amount of post-black to record on the tape after recording the last event in a compiled pod.
10. Select the Device Owned tab. Use this tab to define the relationship between the list and the specific switcher.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 285 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
11. 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:
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 286 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
• List Behavior: From the available options, choose the “list behavior” to use in case of manual intervention.
12. Select the Skip Secondary tab.
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.
13. Select the List Redundancy tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 287 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 288 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Checked: Enable Auto Swap Function.
Configuring List Types
Unchecked: (Recommended) Disable Auto Swap Function.
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.
• 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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 289 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
14. When finished click OK, and then Apply.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 290 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Configuring Media List Options
Configuring List Types
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.
1. To access the Media List options configuration GUI, select a Media List 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.
3. Select the Parameters tab. This tab contains general configuration options for Media
Lists. Some options are commonly used and enabled by default.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 291 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Configure the following options as required:
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:
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).
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.
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.
Recue On Media Changes: (Default: enabled) When enabled, this option causes events to automatically recue if the event’s SOM (start-of-message time) is changed.
Update Cued Event on Media Change: When this parameter is enabled
(checked), all of the database derived metadata for any cued events is updated.
If ‘Recue on Media Changes’ parameter is enabled, then this parameter is also enabled.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 292 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
If this parameter is disabled, ‘Recue on Media Changes’ must also be disabled and no updates will be applied to cued events.
If Auto Ripple is enabled, the start time of the event following the an updated event is also updated.
Manual Subtitler Mode Enabled: As required enable (check) / disable
(uncheck) Manual Subtitler Mode Enabled.
When disabled (default), the Subtitler (e.g. Screen, Cavena, etc.) works in automatic mode.
When enabled, the Subtitler (e.g. Screen, Cavena, etc.) works in manual mode.
Following each change in operational mode, subtitler devices have to be unassigned and then reassigned to the playlist. It is important to note that the same operational mode selection applies to all subtitling devices assigned to a given playlist.
Block Recue Following an Upcount: <<IMPORTANT: While this configuration
option is currently shown as available for Media List types, it should not be
used.>> Enable (check) this option for the recue behavior to never allow recue following an upcount event. (See also ‘Always Allow Recue Following an
Upcount’.)
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:
When the termination event is an O (hard start) event the Time To
Next display includes the running short value.
Zero duration up counters do not stop the rippling.
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.
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.
Auto Restart When Cued: (Default: disabled) When enabled, this option causes events to automatically restart, without manual intervention, if the media has been recued.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 293 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
When this option is disabled, the automation system marks the event as missing and does not automatically cue the event when located.
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).
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.
If this parameter is enabled, then ‘Update Cued Event on Media
Change’ must also be enabled.
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.
Always Allow Recue Following an Upcount: <<IMPORTANT: While this
configuration option is currently shown as available for Media List types, it should
not be used.>> Enable (check) this option for the recue behavior to always allow recue following an upcount event. (See also ‘Block Recue Following an
Upcount’.)
• 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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 294 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
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 re-tensioned 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 Media lists.
NOTE: All of the options on this tab may be configured in the Air Client application also.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 295 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Enable (check)/ Disable (uncheck) and configure the following as required:
• Options:
Switch To Black: 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.
Play Hard Hits: 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.
Contact Start: 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.
Auto A-B Routing: 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.
Play ID Title Mismatches: 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
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 296 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types 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.
Skip Bad Events: 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: 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.
Release Tension When Cued: Enabling this option causes the system to send a
“standby off” command to any VTRs when they have cued a tape. The tape is re-tensioned at the standby on time.
Timed List: 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: Enabling this option causes the on-air time for events to update to the actual time the event rolled. AsRun logs for the list are updated as well.
When disabled, the AsRun logs reflect the time-of-day that appeared on the
Transmission list, rather than the actual time the event rolled.
Auto Ripple Times: 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.
Tension After Up Counter: 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: 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.
When disabled, the list must be threaded manually before it can execute a Play command.
Keep List Threaded: 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).
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 297 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
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.
5. Select the Events to Log tab. This tab contains configuration options for the AsRun logs created by the Air Client application.
• By default, not all secondary event types are logged to the AsRun log. Checking the appropriate checkbox on this tab will enable logging of that secondary event type.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 298 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Enable (check)/ Disable (uncheck) the following as required:
• Secondary Events to Log:
Enable (check)/ Disable (uncheck) the secondary events to log in the AsRun log.
When all check-boxes are selected (checked), all secondary events associated with a primary are included in the AsRun log.
For Example: BREAK is disabled and others are enabled – all secondary events except BREAK secondary event are included in the AsRun log.
For descriptions of all listed Secondary Events see, Appendix C: Secondary Events .
• Log Record Events: (Default: disabled) Check to enable logging of record events on normal completion.
6. Select the Skip Secondary tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 299 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference 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.
7. When finished click OK, and then Apply.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 300 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Configuring GMT List Options
Configuring List Types
GMT lists are modified Transmission lists used exclusively by the Global Media Transfer technology. They are not designed for use as Transmission lists. GMT uses the media devices assigned to the GMT lists for automated transfer of media from wherever it exists within the system to where it needs to be to play out. Generally, only GMT Distributors and certain baseband media devices are assigned to a GMT list. GMT lists do not require operator intervention, although events on a GMT list may be dragged and dropped to a new position to alter its transfer priority. The A/V routing tables for baseband devices assigned to
GMT lists may be configured as they are for Transmission lists to allow automatic routing of
A/V streams.
NOTE: For more information about GMT lists see
To Configure GMT 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 GMT List options configuration GUI, select a GMT List 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.
3. Select the Parameters tab. This tab contains general configuration options for GMT
Lists. Some options are commonly used and enabled by default.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 301 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Configure the following options as required:
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:
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).
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.
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.
Recue On Media Changes: (Default: enabled) When enabled, this option causes events to automatically recue if the event’s SOM (start-of-message time) is changed.
Update Cued Event on Media Change: When this parameter is enabled
(checked), all of the database derived metadata for any cued events is updated.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 302 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
If ‘Recue on Media Changes’ parameter is enabled, then this parameter is also enabled.
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.
If this parameter is disabled, ‘Recue on Media Changes’ must also be disabled and no updates will be applied to cued events.
If Auto Ripple is enabled, the start time of the event following the an updated event is also updated.
Manual Subtitler Mode Enabled: As required enable (check) / disable
(uncheck) Manual Subtitler Mode Enabled.
When disabled (default), the Subtitler (e.g. Screen, Cavena, etc.) works in automatic mode.
When enabled, the Subtitler (e.g. Screen, Cavena, etc.) works in manual mode.
Following each change in operational mode, subtitler devices have to be unassigned and then reassigned to the playlist. It is important to note that the same operational mode selection applies to all subtitling devices assigned to a given playlist.
Block Recue Following an Upcount: <<IMPORTANT: While this configuration
option is currently shown as available for GMT List types, it should not be
used.>> Enable (check) this option for the recue behavior to never allow recue following an upcount event. (See also ‘Always Allow Recue Following an
Upcount’.)
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:
When the termination event is an O (hard start) event the Time To
Next display includes the running short value.
Zero duration up counters do not stop the rippling.
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.
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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 303 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
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).
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.
If this parameter is enabled, then ‘Update Cued Event on Media
Change’ must also be enabled.
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.
Always Allow Recue Following an Upcount: <<IMPORTANT: While this
configuration option is currently shown as available for GMT List types, it should
not be used.>> Enable (check) this option for the recue behavior to always allow recue following an upcount event. (See also ‘Block Recue Following an
Upcount’.)
• 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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 304 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
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 re-tensioned 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 GMT lists.
NOTE: All of the options on this tab may be configured in the Air Client application also.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 305 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Enable (check)/ Disable (uncheck) and configure the following as required:
• Options:
Switch To Black: 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.
Play Hard Hits: 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.
Contact Start: 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.
Auto A-B Routing: 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.
Play ID Title Mismatches: 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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 306 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Skip Bad Events: 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: 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.
Release Tension When Cued: Enabling this option causes the system to send a
“standby off” command to any VTRs when they have cued a tape. The tape is re-tensioned at the standby on time.
Timed List: 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: Enabling this option causes the on-air time for events to update to the actual time the event rolled. AsRun logs for the list are updated as well.
When disabled, the AsRun logs reflect the time-of-day that appeared on the
Transmission list, rather than the actual time the event rolled.
Auto Ripple Times: 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.
Tension After Up Counter: 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: 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.
When disabled, the list must be threaded manually before it can execute a Play command.
Keep List Threaded: 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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 307 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
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.
5. Select the Events to Log tab. This tab contains configuration options for the AsRun logs created by the Air Client application.
• By default, not all secondary event types are logged to the AsRun log. Checking the appropriate checkbox on this tab will enable logging of that secondary event type.
• If this Transmission list is to be used as a record list and you require a log of what has been recorded, an AsRun log may be created that includes primary record events. Check the Log Record Events checkbox to enable this.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 308 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Enable (check)/ Disable (uncheck) the following as required:
• Secondary Events to Log:
Enable (check)/ Disable (uncheck) the secondary events to log in the AsRun log.
When all check-boxes are selected (checked), all secondary events associated with a primary are included in the AsRun log.
For Example: BREAK is disabled and others are enabled – all secondary events except BREAK secondary event are included in the AsRun log.
For descriptions of all listed Secondary Events see, Appendix C: Secondary Events .
• Log Record Events: (Default: disabled) Check to enable logging of record events on normal completion.
6. Select the GMT tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 309 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Configure the following options to enable list linking as required:
• Skip Events Not Cued: This option is used for baseband transfer. When selected if the source event does not cue then the source and destination events are automatically marked missed and eventually removed from the GMT list. If the option is not selected then the events remain on the list allowing the operator to intervene in the GMT list and correct the source event so that it can be re-cued.
• Allow Event Paste From Another GMT List: Enable (check) / Disable (uncheck) pasting from another GMT list. (Default: Disabled (unchecked)).
Enabling (checking) this parameter allows the user to share GMT List load as described below.
In some situations, the user may want a GMT List to share the work of baseband transfers of another GMT List of the same device server.
For example: A Cart Machine port can be shared between two GMT Lists. Each
GMT list has its own encoders on the same video disk. Event build on one GMT
List may not get Cued for transfer because all encoders of this particular GMT
List are busy. If the other GMT list has a spare encoder port that can share the baseband media transfer, the user may Cut-and-Paste these events from one busy GMT List to the GMT List that has an available encoder port. The waiting events immediately Cue and start transfer.
CAUTION: Event build on a GMT List is done by distributors owned by the GMT
List. The transfer of an event on a GMT List often has hidden fields that do not show in the GMT list display window used for editing. Attempting to edit an event on a GMT List can be dangerous. It is not recommended, unless the user really
knows what they are doing.
7. Select the Skip Secondary tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 310 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference 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.
8. When finished click OK, and then Apply.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 311 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Configuring Compile List Options
Configuring List Types
Compile lists are used by the optional compiler function. The compiler allows operators to create compile reels or “spot reels” from play list files. Play list files, after some modification, may be loaded into the Compiler window and run in a similar way to a Transmission list. Only the source and destination devices for the compiler need be assigned to the Compile list.
NOTE: For more information about using the Compiler reference the “Auto Compile
Configuration and Operations Guide”.
To Configure Compile List Options
A number of options may configured to control the behavior of Compile Lists. These options are accessed from the Configuration Manager’s List Assignments window.
1. To access the Compile List options configuration GUI, select a Compile List 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.
3. Select the Parameters tab. This tab contains general configuration options for Compile
Lists. Some options are commonly used and enabled by default.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 312 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Configure the following options as required:
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:
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).
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.
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.
Recue On Media Changes: (Default: enabled) When enabled, this option causes events to automatically recue if the event’s SOM (start-of-message time) is changed.
Update Cued Event on Media Change: When this parameter is enabled
(checked), all of the database derived metadata for any cued events is updated.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 313 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
If ‘Recue on Media Changes’ parameter is enabled, then this parameter is also enabled.
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.
If this parameter is disabled, ‘Recue on Media Changes’ must also be disabled and no updates will be applied to cued events.
If Auto Ripple is enabled, the start time of the event following the an updated event is also updated.
Manual Subtitler Mode Enabled: As required enable (check) / disable
(uncheck) Manual Subtitler Mode Enabled.
When disabled (default), the Subtitler (e.g. Screen, Cavena, etc.) works in automatic mode.
When enabled, the Subtitler (e.g. Screen, Cavena, etc.) works in manual mode.
Following each change in operational mode, subtitler devices have to be unassigned and then reassigned to the playlist. It is important to note that the same operational mode selection applies to all subtitling devices assigned to a given playlist.
Block Recue Following an Upcount: <<IMPORTANT: While this configuration
option is currently shown as available for Compile List types, it should not be
used.>> Enable (check) this option for the recue behavior to never allow recue following an upcount event. (See also ‘Always Allow Recue Following an
Upcount’.)
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:
When the termination event is an O (hard start) event the Time To
Next display includes the running short value.
Zero duration up counters do not stop the rippling.
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.
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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 314 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
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).
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.
If this parameter is enabled, then ‘Update Cued Event on Media
Change’ must also be enabled.
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.
Always Allow Recue Following an Upcount: <<IMPORTANT: While this
configuration option is currently shown as available for Compile List types, it
should not be used.>> Enable (check) this option for the recue behavior to always allow recue following an upcount event. (See also ‘Block Recue Following an Upcount’.)
• 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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 315 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
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 re-tensioned 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 Compile lists.
NOTE: All of the options on this tab may be configured in the Air Client application also.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 316 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Enable (check)/ Disable (uncheck) and configure the following as required:
• Options:
Switch To Black: 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.
Play Hard Hits: 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.
Contact Start: 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.
Auto A-B Routing: 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.
Play ID Title Mismatches: 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
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 317 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types appear on the Transmission list. Enabling this option allows the LMS to register mismatched events.
Skip Bad Events: 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: 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.
Release Tension When Cued: Enabling this option causes the system to send a
“standby off” command to any VTRs when they have cued a tape. The tape is re-tensioned at the standby on time.
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: Enabling this option causes the on-air time for events to update to the actual time the event rolled. AsRun logs for the list are updated as well.
When disabled, the AsRun logs reflect the time-of-day that appeared on the
Transmission list, rather than the actual time the event rolled.
Auto Ripple Times: 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.
Tension After Up Counter: 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: 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.
When disabled, the list must be threaded manually before it can execute a Play command.
Keep List Threaded: 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’.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 318 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
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.
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 option is grayed out.) 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.
5. Select the Lookahead tab. This tab contains the configuration options for this
Transmission list’s lookahead.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 319 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Configure the following options as required:
• 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 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.
• 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 AsRun logs created by the Air Client application.
• By default, not all secondary event types are logged to the AsRun log. Checking the appropriate checkbox on this tab will enable logging of that secondary event type.
• If this Transmission list is to be used as a record list and you require a log of what has been recorded, an AsRun log may be created that includes primary record events. Check the Log Record Events checkbox to enable this.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 320 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Enable (check)/ Disable (uncheck) the following as required:
• Secondary Events to Log:
Enable (check)/ Disable (uncheck) the secondary events to log in the AsRun log.
When all check-boxes are selected (checked), all secondary events associated with a primary are included in the AsRun log.
For Example: BREAK is disabled and others are enabled – all secondary events except BREAK secondary event are included in the AsRun log.
For descriptions of all listed Secondary Events see, Appendix C: Secondary Events .
• Log Record Events: (Default: disabled) Check to enable logging of record events on normal completion.
7. Select the Compiler tab. The Compiler function is an option that may be purchased separately for your Automation system.
IMPORTANT: This option is only available if the optional compiler function has been
purchased.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 321 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring List Types
Configure the following options as required:
• Skip Missing Material: (Default: disabled) The compiler leaves space for events in a pod that are not currently available to be compiled. It then continues to compile the pod around the missing material. If you enable this option and then later change the duration of any of the missing items of material you will have to recompile the remainder of the pod after the event whose duration changed.
• Log Errors: (Default: disabled) Check this box to cause all compile errors to be recorded into a logfile.
• Time Parameters:
SOM: Specify a Start Of Message (SOM) value for the compile tape. Default is
00:01:00:00.
Tape Length: This is the duration of the compile tape. Default is 01:30:00:00.
Break Gap: The distance between the end of black on one pod and the start of black on the next pod. Default is 00:30:00:00.
Black In: The amount of pre-black to record on the tape before recording the first compiled event. Default is 00:00:00:00.
Black Out: The amount of post-black to record on the tape after recording the last event in a compiled pod. Default is 00:00:00:00.
8. Select the Skip Secondary tab.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 322 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference 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.
9. When finished click OK, and then Apply.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 323 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Audio / Video Routing Tables
Configuring Audio / Video Routing
Tables
About AV Routing Tables
One of the key features of the Automation system is its ability to automatically route audio and video streams for events on Transmission lists. Every media device assigned to a
Transmission list may have an associated audio/video routing path specified.
The A/V path is list-specific, so a device that is assigned to different lists for different purposes may have a different A/V path specified for each list.
The A/V routing tables also contain alternate A/V paths for devices, and a Protect A/V path for use with Air and Protect.
The Audio/Video routing tables must be correctly configured for the automation to correctly route audio and video for devices. Each playlist (or media list or GMT list) may have designated routing paths for all devices in the system, including devices that may not be currently assigned to that list.
To Configure A/V Routing
1. To access the A/V routing tables, open the List Assignments window in the Configuration
Manager Tool, and select a Transmission list (PlayList).
2. Right-click on the entry and then from the pop-up menu select Audio Video.
3. On the Audio Video tab configure the following as required:
• Device: The Device drop-down list contains a list of all media devices configured in the automation system. Choose the device for which you wish to configure the A/V routing path for this Transmission list.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 324 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Audio / Video Routing Tables
• Media Head: The Media Head list will display all available media heads for the selected device. Single-stream devices, such as VTRs or video server ports, will display a single media head. A Multi-stream device, such as a cart machine, will display multiple media heads. The A/V routing path for each media head may be configured separately.
• Edit Output and Edit Input buttons: The Edit Input and Edit Output buttons refer to the input to, or output from, the media device.
4. Edit the input to, or output from, the media device.
Select the appropriate button. An easy way to remember which button to click is this:
• If the device you are configuring is a playout device (an output device), click the Edit
Output button.
• If the device is a record device (an input device), click the Edit Input button.
• If the device is to be used as both a playout and record device (such as a VTR), both the input A/V path and output A/V path may be configured.
5. The Crosspoints dialog that opens is the configuration GUI for this device’s A/V routing table for this Transmission list.
Output Crosspoints
Dialog
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 325 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Audio / Video Routing Tables
Input Crosspoints Dialog
Configure the following as required:
• Device: The Device drop-down list refers to the router or switcher device on which the crosspoint will be switched. Select the router or switcher device to which to send commands when this media device rolls an event on the Transmission list.
• Input Cross Point: The Input Cross Point field indicates the input on the router or switcher for this media device. For playout devices, this is the input on the router or switcher that receives audio and video from the device. For record devices, this is the input on the router or switcher that is the source for the recording.
• Output Cross Point: The Output Cross Point field indicates the output on the router or switcher for this media device. For playout devices, this is the destination on the router or switcher to which the A/V stream from the device will be routed. For record devices, this is the output on the switcher or router that feeds the A/V inputs to the record device.
The A path is the default A/V routing path for this device on this Transmission list.
The B and C paths are alternate A/V routing paths for this device on this
Transmission list. The alternate routing paths are invoked by placing a “B” or “C” in the event’s Ch (channel) column in the Transmission list.
• Protect: The Protect path is used in an Air and Protect environment. When configured, this is the A/V routing path for this device when it is acting as a protect device. The output crosspoint is typically configured to feed a control room monitor.
In the event of a failure of the Air device, the system will switch the Protect device to air, invoking it’s A path, and invoke the (now failed) Air device’s Protect A/V path, switching its output to a monitor. The Protect A/V path for the Protect device must be similarly configured to switch its output to a monitor under normal circumstances.
6. When finished click OK.
To Configure Preview A/V Routing
Use this procedure to review/ configure the preview audio/video output for devices.
The preview audio/video configuration applies to a device regardless of which list it is running on. This means that there is only one preview audio/video configuration for device.
1. To access the A/V routing tables, open the List Assignments window in the Configuration
Manager Tool, and select a Transmission list (PlayList).
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 326 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Audio / Video Routing Tables
2. From the main menu select File > Preview Audio Video. The Preview Audio Video dialog is displayed.
3. On the Preview Audio Video tab you can review and/or edit the configuration as required:
4. Click the Edit Output button.
5. The Preview Audio Video Crosspoints dialog opens. This is the configuration GUI for this device’s preview A/V routing table for this Transmission list.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 327 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Configuring Audio / Video Routing Tables
6. Configure the preview A/V routing table as required:
• Device: The Device drop-down list refers to the router or switcher device on which the crosspoint will be switched. Select the router or switcher device to which to send commands when this media device rolls an event on the Transmission list.
• Input Cross Point: The Input Cross Point field indicates the input on the router or switcher for this media device. For playout devices, this is the input on the router or switcher that receives audio and video from the device. For record devices, this is the input on the router or switcher that is the source for the recording.
• Output Cross Point: The Output Cross Point field indicates the output on the router or switcher for this media device. For playout devices, this is the destination on the router or switcher to which the A/V stream from the device will be routed. For record devices, this is the output on the switcher or router that feeds the A/V inputs to the record device.
The A path is the default A/V routing path for this device on this Transmission list.
The B and C paths are alternate A/V routing paths for this device on this
Transmission list. The alternate routing paths are invoked by placing a “B” or “C” in the event’s Ch (channel) column in the Transmission list.
• Protect: The Protect path is used in an Air and Protect environment. When configured, this is the A/V routing path for this device when it is acting as a protect device. The output crosspoint is typically configured to feed a control room monitor.
In the event of a failure of the Air device, the system will switch the Protect device to air, invoking it’s A path, and invoke the (now failed) Air device’s Protect A/V path, switching its output to a monitor. The Protect A/V path for the Protect device must be similarly configured to switch its output to a monitor under normal circumstances.
7. When finished click OK.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 328 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Global Media Transfer
Global Media Transfer
Overview
Global Media Transfer (GMT) automatically copies media among the devices controlled by the automation system, as it is needed for playout on a Transmission list. If a video server assigned to a Transmission list does not have a piece of media available in its storage collection, GMT will attempt to find the material in other media devices and copy it to the playout video server. This process occurs in the background and requires little or no operator intervention.
Purchase Note: GMT is a for-purchase option to ADC systems. Contact your Automation
Sales representative for details.
Reference Note: For more information reference the ADC GMT Configuration and
Operations Guide document.
GMT Transfer Modes
GMT supports four transfer modes or mechanisms for copying media: fibrechannel transfers, baseband transfers, archive transfers and wide-area network FTP transfers.
Fibrechannel transfers – Media may be copied among video servers linked by a fibrechannel connection. Fibrechannel transfers are data transfers of compressed MPEG or JPEG files and occur faster than real time. Fibrechannel transfers may occur between devices controlled by multiple Device Servers.
Archive transfers – Media may be copied to or from an archive device either by the normal background GMT process, or manually through the Media Client application.
Archive transfers are data transfers of compressed MPEG or JPEG files and occur faster than real time. Archive transfers may be “single-hop” or “double-hop” transfers. Singlehop transfers copy the media from the archive directly to the requesting playout video server. Double-hop transfers copy the media from the archive to an intermediate video server, and then execute a fibrechannel transfer from the intermediate video server to the requesting playout video server. Archive transfers may occur between devices controlled by multiple Device Servers.
Baseband transfers – Media may be copied from a baseband source device, such as a cart machine, VTR or a video server’s decoder port, to a video server’s encoder port.
Baseband transfers are real-time transfers. Audio and video are automatically routed from the source device to the destination device according to the A/V routing tables configured for the GMT list. Baseband transfers may be “single-hop” or “double-hop” transfers. Single-hop transfers copy the media from the source device directly to the requesting playout video server. Double-hop transfers copy the media from the source device to an intermediate video server, and then execute a fibrechannel transfer from the
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 329 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Global Media Transfer intermediate video server to the requesting playout video server. Baseband transfers may only occur between devices controlled by a single Device Server. Only the fibrechannel “hop” of double-hop baseband transfers may occur between devices controlled by multiple Device Servers.
WAN FTP transfers – Media may be copied among video servers using the video server’s native FTP transfer mechanism. This may be accomplished on a local-area or wide-area network. FTP transfers are data transfers of compressed MPEG or JPEG files and may occur faster than real time, depending on the bandwidth available on the widearea network. Only the local video server, designated as the site manager, need be controlled by a Device Server.
GMT Components
GMT consists of three fundamental components: Requesters, Distributors and GMT lists.
Requesters – are virtual media devices assigned to a Transmission list and associated with destination devices (playout video servers). Media that is not available in the
Requester’s destination device is requested from a Distributor (or Distributors) associated with source devices. Requests are made when events enter the lookahead of a
Transmission list and cannot be registered with any of the physical media devices assigned to that list.
Distributors – are virtual media devices assigned to a GMT list and associated with source devices. These source devices may be video server ports, cart machines, VTRs, archives or ProxyFTP devices. Distributors create and run events on the GMT list to accomplish the transfer of media to the requesting destination device. A single distributor can only support a single transfer mode, depending on the type of its associated source device, but may be “pointed to” or linked with other Distributors supporting other transfer modes. By “chaining” Distributors in this manner, search paths may be created to pass requests through a number of Distributors of different types. The first Distributor whose source device contains the requested media will execute a transfer - of that Distributor’s type - to the Requester’s destination device.
GMT Lists – are modified Transmission lists used exclusively by GMT. Distributors assigned to the GMT list will create events to execute transfers of one type or another.
Non-real-time transfers (fibrechannel, archive and WAN FTP) are executed by events registered and run by the Distributors. Baseband transfers are created by Distributors but run by the physical media devices assigned to the GMT list.
(OPTION) Push Lists are simply Transmission Lists used for a specific purpose other than on-air playout. Push Lists are used to “push” media from a source device to a destination device ahead of time. Under normal circumstances, Requesters request missing media at roughly the same rate as events enter the lookahead of the requesting
Transmission List. GMT is driven by the Transmission List and will fulfill requests for missing media as events undergo the registration process.
A Push List allows GMT to move (“push”) media in advance of the Transmission List.
The traffic department may create a “push list” log consisting of spots needed for air tomorrow. The log file may then be translated into a playlist file by the Traffic Translator and loaded into the Push List.
A Simple GMT System
The illustration below shows a simple fibrechannel GMT system.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 330 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Global Media Transfer
A Requester assigned to the Transmission List queries the destination device for availability of media. If an ID on the Transmission List cannot be registered by the destination device (because the ID does not exist in the destination device), the
Requester passes a request to the Distributor.
The Distributor is assigned to the GMT List and is in communication with a source device.
If the Distributor, after querying its source device, finds that the media is available, it will create an event on the GMT List that will initiate a Fibrechannel transfer.
The Distributor will run the event on the GMT List and the media will be copied from the source device to the destination device. Once the copy process has begun, the source device will inform the system that the media is now available for registration on the
Transmission List and playout.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 331 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Cloning
Cloning
Introduction to ADC Cloning
The ADC Device Server v11 application runs on a Device Server chassis consisting of a personal computer installed with automation cards, connectors, network cards, and other peripherals. The operating systems can be Windows 2000 and Windows XP. Via 422 serial port connectors, the ADC Device Server communicates with and controls up to 68 broadcasting devices. In case of hardware failure, the automation stops functioning.
Purchase Note: Cloning is a for-purchase option to Device Server. Contact your Automation
Sales representative for details.
Reference Note: For more information on Cloning operations reference the ADC Cloning
User Guide_Complete v8 document. For details on setting up the Cloning panel see the ADC
Hardware Control Panels Reference, Cloning panel section.
For some mission critical TV channels, it is desirable to have a back up ADC Device Server to take over automation control when the main device server fails. For this purpose, in hardware, a relay is used to switch the connection between one of the device servers and the broadcasting devices. The device server pair are called A and B. When A is switched to communicate with the broadcasting devices, for instance, it is called the “Main” device server, and B is called “Clone” device server, and vice versa. The relay has an affiliated cloning control panel for user settings, as illustrated below:
In software, a cloning feature is added to the ADC Device Server application when the
USECLONING compiler directive is defined. The feature has two basic functions.
One is to copy the device status, device storage, list contents, list status, and other state machines from the main device server application to the clone device server application.
The other is to dynamically maintain the synchronization by means of feedback close control looping.
With both hardware and software implementations, a seamless cloning with transparent switching between A and B device servers is achieved.
NOTE: The cloning feature software is only contained inside the device server application.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 332 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
IMPORTANT: Cloning and List Redundancy are considered mutually exclusive functionalities.
Cloning
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 333 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
List Redundancy
List Redundancy
About List Redundancy
List Redundancy is an option of ADC Device Server v11 that is designed to add extra security to the automated broadcast system playout. Since this feature is only useful for the play out, the feature is only applied to transmission lists and not to media lists, GMT lists and so on…
Purchase Note: List Redundancy is a for-purchase option to Device Server. Contact your
Automation Sales representative for details.
Reference Note: For more information reference the ADC List Redundancy Control Client
Reference document.
IMPORTANT: Cloning and List Redundancy are considered mutually exclusive functionalities.
The List Redundancy Process
List Redundancy uses two Transmission Lists running the same programs in parallel, and independently, from distinct but similar devices (mostly videodisks) - if a problem occurs on one of the redundant lists, due to a device error for instance, the other redundant lists will keep on playing.
These lists can run on two Device Servers (MAIN & BACKUP) simultaneously. To achieve this, both lists must have the same event content, e.g. the lists are mirrored, and must be synchronized to play out events in a synchronous way. The List Redundancy gives a control on the Mirroring and on the Synchronization to the operator.
In order to have both redundant lists mirrored and synchronized, one redundant list has to provide all needed information to the other. So, the list providing information is called the
‘Master List’ and the list receiving information is called the ‘Slave List’. Editing the Air Client connected to the Master List will automatically make the same edits to the Slave list.
Same program: The List Redundancy guaranties that the Master List is mirrored into the
Slave List, and so that both lists have the same content.
Same running point: The List Redundancy guaranties that Master List and Slave List are synchronized, and so that programs are running the same way.
Overall control: The List Redundancy gives operators the ability to manually control the above functions.
The following graphic illustrates the List Redundancy process.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 334 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
List Redundancy Process
List Redundancy
Insert
1
Device Server A
MASTER
LIST
2
Insert
Freeze
Play List
Device Server B
MASTER
LIST
Freeze Play
DEVICE
1
An operator inserts an event into the Master List.
2
The command is echoed to the related Slave List, if the list content or state has changed.
3
The Slave List refreshes its content.
3
Device Server C
SLAVE
LIST
SLAVE
LIST
DEVICE
DEVICE
DEVICE
Functions
The List Redundancy provides following major functions:
Master List / Slave List: For a given transmission channel, Master and Slave Lists can use their own controlled devices to do play out, they can also share some of devices
(normally assigned to the Master List).
The Slave List handles the missing media, and keeps the synchronicity with the Master
List when the Master List is malfunctioning, and allows the operator to use the Slave List to control program play out.
Note: If an operator attempts to use the Control Panel to edit or control a slave playlist, a
warning/error message is displayed indicating the “operation can't be applied to slave
list.”
List Mirroring: The List Mirroring guaranties that both redundant transmission lists have the same content.
List Synchronization: The List Synchronization guaranties that both redundant transmission lists have the same running point.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 335 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Diagnostics and Troubleshooting
Diagnostics and Troubleshooting
Troubleshooting techniques
Once the automation system has been installed and commissioned, there should be very little regular maintenance or troubleshooting necessary to insure continued operation.
Occasionally, if upgrades or changes are made to the system, problems can arise which require some investigation.
The automation system provides a number of troubleshooting tools, both as stand-alone applications and built into the Configuration Manager, to aid in troubleshooting problems with the system.
Generally, to diagnose and troubleshoot a problem, it is first necessary to isolate the problem.
Is the problem with a component of the automation? Is the problem with the Device Server or one of the client applications? If the problem is with the Device Server, is it a specific component (physical device or device driver) that is the cause of the problem? Were any changes made to the system prior to the appearance of the problem? What did the operator do that preceded the appearance of the problem?
If all else fails, call Automation Technical Support. For customers who have a current service and support agreement with Imagine Communications, technical support is available 24 hours a day, 7 days a week. A call to technical support during business hours (6AM to 5PM
Pacific Time) insures that you will speak to an Automation Technical Support representative.
A call after business hours will be referred to a technical support representative on-call. If the problem is not critical (i.e. it does not affect on-air operations or revenue stream), it is best to postpone a call until business hours. By doing so, it will insure that the full resources of
Automation Technical support will be at your disposal.
Device Server Debugging Logs
To enable the device server debugging logs, You use the key combination of Control + Shift
+ Alt + Function. Each function key enable/disable a specific log: <Ctrl> + <Shift> + <Alt> +
<Fn>
F2 = Enable cloning log
F4 = B: Background performance Log. It log how many times background come in each frame. Usually we don't leave it on in a long time period.
F5 = LR: List Redundancy log.
F6 = HAD: logs background timing and network timing.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 336 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
F7 = DSK: Video disk log
F8 = API: API log
Diagnostics and Troubleshooting
F9 = TLE: more detail API log, usually we don't leave it on in a long time period. And
GMT log
F10 = LST: List log.
Configuration Manager tools
The Configuration Manager application provides a number of troubleshooting tools to diagnose problems with the automation system. All of them may be accessed from the
Configured Devices window within the Configuration Manager.
Device Status window
The Device Status window may be accessed from the Configuration Manager or from the Air or Media Client applications. The Device Status window displays the current status of all of the devices configured in the automation system, and is updated dynamically by the Device
Server. Of particular note is the status column. It will display a status message for each device in the list.
1. In the Configured Devices window, select View > Device Status.
Different devices will display different statuses:
Normal status: The normal status for an idle video server port is STANDBY. Both heads of a decoder port should display a STANDBY status. Encoder ports normally display a
STANDBY status for head 1 and an OFFLINE status for head 2.
• VTRs, both stand-alone and those within a cart machine, if there is no tape loaded, normally display a status of UNTHRD (unthreaded).
• Other devices may display a status of STANDBY or may not display any status at all.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 337 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Diagnostics and Troubleshooting
• If the device is currently being used to play out media, a status of PLAY, REW,
FFWD, JOG or STOP is normal.
OFFLINE status: An OFFLINE status for a video server decoder port is usually caused by an incorrect configuration in the Device Server. Re-check the video server port device driver configuration and reinitialize the device if necessary. An OFFLINE status for head
2 of a video server encoder port is normal.
BUSY status: Occasionally a video server port may display a status of BUSY. This means that the video server is currently performing some background operation and is not able to respond to commands from the automation system. The BUSY status is typically displayed for only a few seconds before it changes back to a STANDBY status.
If the video server port remains in a BUSY state for an extended period of time, the port may have “hung” and may require reinitialization.
NO DEV status: If a device displays a status of NO DEV, this means that there is no communication between the automation system and the device. A NO DEV status is typically caused by a faulty serial cable, or a serial cable that has been incorrectly pinned.
Refer to the user notes for the device in question for the correct serial cable pinouts.
Some devices require an RS232 to RS422 converter to connect the device to the automation system. This requirement, and the pinouts of the serial cables, will be noted in the user notes. If the serial cable is found to have been correctly made, then the device itself has stopped communicating with the automation system and may have failed.
No Comm status: A status of No Comm indicates that a serial port on the Device Server has not yet been assigned for this device. Check the device configuration and assign a serial communications port for the device.
Unknown status: If a device displays a status of Unknown, it is typically caused by a mismatch in the communication parameters for the serial port. Most device drivers in the automation system do not allow changes in the communication parameters (Baud rate, stop bits, data bits, parity). Check the communication parameters for the device’s serial port and ensure that they match the Device Server’s requirements. Again, this information may be found in the user notes for the device in question.
GPI diagnostics
The status and functionality of GPI cards installed in the Device Server may be checked from the Configuration Manager as well.
1. In the Configured Devices window, select View > GPI Card 1, 2, 3 or 4.
2. Clicking on one of the GPI Card menu items will open a diagnostic utility.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 338 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Diagnostics and Troubleshooting
3. Placing a check mark in the appropriate check box will close the GPI contacts for the selected GPI card and relay. An ohmmeter connected to the NO or NC and COMMON pins on the GPI breakout panel may be used to check whether the relay is open or closed.
Real-time diagnostic traces
The Configuration Manager provides a means of capturing and displaying the data traffic to and from certain devices on a dynamic real-time basis. Devices that currently support this diagnostic feature include GMT Distributors, archive devices and ProxyFTP devices. The diagnostic windows for these devices may be opened in one of two states: modal and modeless. Select the device in question in the list of devices in the Configured Devices window. Right-click and select Properties. This opens the configuration GUI for the device.
Click on the Diagnostics tab within the GUI. This displays the diagnostics window in modal state; only one modal-state diagnostic window may be displayed at a time.
Alternately, select the device in question in the Configured Devices window, right-click and select Diagnostics. This will open the diagnostics window for the device in modeless state.
Several devices may be monitored simultaneously in modeless state, and the Configured
Devices window may be minimized to reduce desktop clutter.
If a diagnostics window is opened in modeless state, a text log file will be created on the PC running the Configuration Manager in the C:\CONFIG\LOG folder. This log file may be emailed to Automation Technical support for assistance in diagnosing problems with your system.
Distributor diagnostics
The Distributor Diagnostics tab allows for a diagnostic file to be created. When this
Distributor is opened on the diagnostic tab, a log file is created. As long as this window is open, the log file is being kept. The problem is that with this window open, you cannot access any other part of the config tool. Therefore, there is an alternate way of turning on this log file.
1. To check the current status of a GMT Distributor, its diagnostics window may be opened in either modal or modeless state. From the Configuration Tool, in the Configured devices pane (Left pane) Right click on the Distributor and from the popup select Diagnostics.
The Distributor Modeless Diagnostics window is displayed.
Three options are available for tracing the status of a Distributor: Event Log, ID Trace and
Buffer Dump.
Note: The Multiple Modeless Distributor Diagnostic window can be opened
simultaneously. This allow an operator to trace an event ID across multiple Distributors.
2. Select Event Log: An event log is a real-time status display for the Distributor. As requests are processed by the Distributor, the RunState Status pane will update dynamically and display the current status of the operation.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 339 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Diagnostics and Troubleshooting
This logs all internal ID events that occur in a Distributor. This event log provides information about how many events are holding in a Distributor and where they are internally. If the selected Distributor is currently transferring media, its ID name and its running states are recorded in the Run State Status. The user can check out what running state for an ID was last in if the Distributor doesn’t work.
• If the diagnostics window has been opened in modeless state, the data written to the
RunState Status window will also be written to the text log file.
• A Reinitialize button is also available in Event Log mode. Clicking Reinitialize will clear the Distributor’s collection of pending requests and reset all of its internal variables to zero. Any pending requests on the Transmission List will be marked
FAILED.
3. Select ID Trace. When selected, the diagnostics window displays an Input ID / Segment field. This logs a specified ID event and shows how it goes through a Distributor internally. It provides useful information for engineers to diagnose a troubled event and identify what states an ID has gone through within the Distributor.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 340 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Diagnostics and Troubleshooting
• Enter an ID you wish to trace in the Input ID field (and a segment number if this is a multi-segment ID) and click Start Trace.
• The current status of the ID will be displayed in the RunState Status pane. If the diagnostics window has been opened in modeless state, the status will be written to the text log file as well.
4. Select Buffer Dump. This is used to dump out all event IDs that are currently holding in the internal buffer of a Distributor. If a Distributor is not working correctly, and it still holds some IDs within its internal buffer, this may prevent the same ID to be sent in. The user can use this function to dump out these IDs and analyze what caused this problem.
• Click the Start Dump button and the Distributor will write the contents of its buffer to the RunState Status pane.
• This action does not clear the contents of the Distributor’s buffer – that can only be accomplished by clicking the Reinitialize button. If the diagnostics window has been opened in modeless state, the buffer data will be written to the text log file as well.
5. When finished click Close.
Diagnostic log file
The diagnostic function generates log files as long as the Diagnostic tab sheet is displayed on the screen. This file is created on the same computer that is running the ADC100NT
Configuration Manager program. It is created under a “\log” sub-directory in the same directory, which contains ADCNTCFG.exe. The log file name has the following general structure:
Device name + Channel number + 'Diagnostics'+ Current Date + '.Log'
For example, a diagnostic log file with the following file name will be created for DISTR20, which is occupied channel 20:
DISTR20 - Channel 20 - Diagnostics 2002-07-29.log
Please contact your Automation Tech Support Representative for assistance in reading this log!!
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 341 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Archive diagnostics
Diagnostics and Troubleshooting
Archive devices’ configuration GUIs have a modal or modeless diagnostics window available as well.
1. Select the archive device in the Configured Devices pane (left pane).
2. Right-click and from the popup menu select Diagnostics. This opens the archive device’s diagnostics window in modeless state.
• The diagnostics window displays the current real-time status of the archive device and log all communication between the Device Server and the archive manager.
• If the diagnostics window is opened in modeless state, the contents of the diagnostics window are written to a text log file in the C:\CONFIG\LOG folder of the
Configuration Manager PC.
3. When finished click Close.
ProxyFTP diagnostics
ProxyFTP devices’ configuration GUIs have a modal or modeless diagnostics window available as well.
1. Select the ProxyFTP device in the Configured Devices pane (left pane).
2. Right-click and from the popup menu select Diagnostics. This opens the ProxyFTP device’s diagnostics window in modeless state.
• The diagnostics window displays the current real-time status of the ProxyFTP device and log all communication between the Device Server and the video server managing FTP transfers.
• If the diagnostics window is opened in modeless state, the contents of the diagnostics window are written to a text log file in the C:\CONFIG\LOG folder of the
Configuration Manager PC.
3. When finished click Close.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 342 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
VDCP diagnostics
Diagnostics and Troubleshooting
Tracing the port of a VDCP object through the Configuration Tool provides a simpler method of diagnostic tracing. Rather than using the Diagmon trace program used to generate traces, and the Trace Viewer to open them, the Configuration Tool has an additional control in its diagnostic mode to allow tracing of the VDCP communications. This gives more intelligent filtering of the data logged in order to limit the amount data produced in the log. VDCP devices’ configuration GUIs have a modal or modeless diagnostics window available as well.
Diagnostics tab
1. Select the VDCP device in the Configured Devices pane (left pane).
2. From the Configuration Manager main menu select File > Properties
3. Scroll right to select the Diagnostics tab.
4. When finished click Cancel.
Diagnostics Window
1. Select the VDCP device in the Configured Devices pane (left pane).
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 343 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Diagnostics and Troubleshooting
2. Right-click and from the popup menu select Diagnostics. This opens the device’s diagnostics window in modeless state.
• The diagnostics window displays the current real-time status of the VDCP device and log all communication between the Device Server and the video server.
• If the diagnostics window is opened in modeless state, the contents of the diagnostics window are written to a text log file in the C:\CONFIG\LOG folder of the
Configuration Manager PC.
3. When finished click Close.
Diagnostic Monitor
The Diagnostic Monitor is a client application available from Automation Solutions technical support. It will capture the data traffic to and from the Device Server on a specific serial port or multiple serial ports. When troubleshooting communications difficulties with a device, the
Diagnostic Monitor is an invaluable tool for examining the data stream.
Each build of Device Server software contains a special session-layer login for the Diagnostic
Monitor. The Diagnostic Monitor may only log into a single Device Server at a time.
The Diagnostic Monitor consists of three files:
DIAGMON.EXE
APILIB32.DLL
NBIOS32.DLL
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 344 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
To Set up Diagnostic Monitoring
Diagnostics and Troubleshooting
1. Copy the three files into a folder on the Configuration Manager PC and create a desktop shortcut to the executable file. The Configuration Manager does not need to be running to run the Diagnostic Monitor.
2. Right-click on the desktop icon and select Properties. Select the Shortcut tab. In the
Target field, place the cursor at the end of the path to the executable file, type a space, then type an application name for the Diagnostics Monitor. The name may be anything you wish (most people use DIAGMON). Type another space, then type the application name of the Device Server you wish the Diagnostic Monitor to log into (MAIN, MAIN_DS,
BACKUP_DS, etc.). Click OK.
3. Start the Diagnostic Monitor by double-clicking the desktop icon.
4. From the Trace menu, select Ports. In the window that opens, select the Device Server serial port from which you wish to capture the data trace, then click Enable (ON/OFF).
Multiple serial ports may be selected by holding down the CTRL key while clicking, but the trace files generated will contain data from all the serial ports selected. It is recommended that you capture the data traffic on a single serial port at a time.
• Once a serial port has been selected, the Diagnostic Monitor will begin writing the data to a trace file. The naming convention for the trace files is mmddyy_nnnnnn.TRC, where nnnnnn represents a number from 000000 to 999999.
By default, the trace files are stored in the same folder as the Diagnostic Monitor executable.
• The Diagnostic Monitor will write to the current trace file until it reaches 1MB, at which point the Diagnostic Monitor will close the current trace file and begin writing to a new trace file. As long as the Diagnostic Monitor application is running, data will be written to trace files.
• NOTE: if the Diagnostic Monitor is left running unattended for a long period of time, it will eventually fill up the client PC’s hard drive with trace files. Automation Support can provide another application called TraceFind (see below) to help manage the trace files generated by the Diagnostic Monitor.
5. To view the trace files that have been captured by the Diagnostic Monitor, Automation
Technical Support can provide another application called TraceView (see below). The trace files are not ASCII text files and may only be viewed with TraceView.
6. TraceView cannot open a file to which the Diagnostic Monitor is currently writing. To force the Diagnostic Monitor to close the current trace file and open a new one, from the
File menu select Force New File.
For more information about the Diagnostic Monitor application, refer to the user notes for the
Diagnostic Monitor.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 345 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
TraceView
Diagnostics and Troubleshooting
To view the trace files generated by the Diagnostic Monitor, Automation Technical Support can provide an application called TraceView. TraceView is a stand-alone application and is not required to log into the Device Server. It may be run on a PC completely separate from the automation system.
TraceView consists of a single file, TRACVIEW4.0.EXE, which may be copied into a folder on any PC. Create a desktop shortcut to the executable and double-click the icon to run the program.
TraceView also allows you to save the trace files as text files.
The trace files captured by the Diagnostic Monitor may be emailed to Automation
Technical support to aid in the troubleshooting and resolution of a problem.
NOTE 1: The Traceview tool supports the Logomotion protocol. Recently, Field engineers have needed the Leitch Logomotion translated the communication byte stream into human readable form.
NOTE 2: Please refer to the user notes for TraceView for more information.
To view a trace file
1. To view a trace file, select the File menu, and then select one of the viewing options.
TraceView can parse the trace files in a number of different formats. The choices are:
• ASCII text
• Sony VTR protocol
• Sony Cart Machine protocol
• GVG M2100 switcher protocol
• VDCP (for video servers)
• Sony M1000 switcher protocol
2. TraceView will open an Explorer window allowing you to find the trace find you wish to view. TraceView will open a new window displaying the data trace.
Example Data Trace
Below is a portion of a data trace captured by the Diagnostic Monitor from a Sony VTR.
From left to right, the first column displays the serial port from which the data trace was taken
– in this case, serial port 1. The next column displays either an O> or an I< indicating whether this is data going out from the Device Server or coming into the Device Server. The next column displays the time stamp for the data trace. The number in parentheses in the next column displays the number of bytes in the command. The next column displays the raw hexadecimal data, and the last column displays the command interpreted in the selected protocol.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 346 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
1 O> 14:33:15.15 ( 4) 61 20 09 8A
1 I<
Diagnostics and Troubleshooting
Sense Status
14:33:15.16 ( 12) 79 20 00 A0 07 00 00 00 00 00 00 40 VTR Status
1
1
1
1
1
1
1
1
1
1
O> 14:33:15.16 ( 4)
I< 14:33:15.17 ( 7)
61 0C 01 6E
74 04 42 57 00 00 11
Get Timecode
Timecode 00:00:57:02
O> 14:33:15.17 ( 4)
I< 14:33:15.18 ( 12)
61 20 09 8A
79 20 00 A0 07 00 00 00 00 00 00 40
Sense Status
VTR Status
O> 14:33:15.18 ( 4)
I< 14:33:15.19 ( 7)
O> 14:33:15.19 ( 3)
I< 14:33:15.20 ( 3)
61 0C 01 6E
20 01 21
10 01 11
74 04 42 57 00 00 11
Get Timecode
Timecode 00:00:57:02
Play
Ack
O> 14:33:15.20 ( 4)
< 14:33:15.21 ( 12)
61 20 09 8A
79 20 00 81 04 00 00 00 00 00 00 1E
Sense Status
VTR Status
TraceFind
TraceFind is a stand-alone application available from Automation Technical support to aid in the management of trace files generated by the Diagnostic Monitor. The Diagnostic Monitor captures trace files up to 1MB in size. When a trace file reaches 1MB, the Diagnostic Monitor closes the trace file and opens a new one. If the Diagnostic Monitor is left running unattended for a long period of time, there is a chance that it could fill the client PC’s hard drive with trace files. This makes it inconvenient to use the Diagnostic Monitor to diagnose an intermittent problem.
The TraceFind application automatically manages the trace files generated by the Diagnostic
Monitor.
1. Copy the program, TRCFIND.EXE, to folder on any PC (preferably the same PC where the Diagnostic Monitor is installed).
2. Create a desktop shortcut to the executable and run the program by double-clicking on the desktop icon.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 347 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Diagnostics and Troubleshooting
TraceFind allows you to:
• Look for specified hexadecimal strings within captured trace files
• Automatically delete trace files older than a specified age
• Automatically delete trace files when a specified amount of disk space has been used
• Log TraceFind’s activities to a text log file
• Log the trace data extracted from the trace files to a separate trace file
• Either run the application manually or on a regularly-scheduled basis
NOTE: Please refer to the user notes for TraceAnalyzer for more information.
Application and exception errors
The Device Server and Configuration Manager applications contain built-in error handling routines that will generate an exception error log file in the unlikely event of a software crash.
By default, these log files are written to the same folder that contains the executable program that generated the error. The exception error logs are not text files and cannot be viewed in a text editor. It is strongly recommended that you email the exception error logs to Automation
Technical Support as soon as possible after a software crash.
Automation Technical Support
Before making any configuration changes to your system, or if you are having problems with your system, it is strongly recommended that you contact Automation Technical Support.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 348 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Diagnostics and Troubleshooting
Automation Technical support is available 24 hours a day, 7 days a week to customers who have a current service and support agreement with Imagine Communications. To insure that you receive the best technical support possible, please have the following information readily available (if applicable) before placing a call:
Software version numbers – the version number of your software may be found by clicking the Help / About menu in any of the Automation system’s software programs.
Device Server and client configuration files – technical support can diagnose many problems by examining the configuration files for (INI files) your Device Server or client applications. These may be emailed to technical support.
Diagnostic trace files – if you are using the Diagnostic Monitor application, or are using the diagnostic features for GMT Distributors, archive devices or ProxyFTP devices, technical support can diagnose many problems by examining the trace files and data trace logs. These may be emailed to technical support.
AsRun logs – AsRun logs can provide technical support with additional information about how the automation system is running. These may be emailed to technical support.
Playlist files – technical support can often diagnose problems by examining your playlist files. They may also be compared to the associated AsRun logs. These may be emailed to technical support.
Exception error logs – as noted above, the Device Server and Configuration Manager applications have built-in exception error handling routines and will generate an exception error log file in the event of a software crash. These may be emailed to technical support and may be used to pinpoint the source of the exception error.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 349 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix A: Supported Devices
Appendix A: Supported Devices
This section lists devices supported by ADC applications. Since product development is ongoing, this list is subject to change.
Archive Management:
Avalon Archive Management
Front Porch Digital
MassTech Group
SGL
Audio Carts:
360 Systems
Barcode Printers:
Brother
Divide Research
Intermec
Intermec
Cart Machines:
Grass Valley Group
Odetics
Odetics
Odetics
Odetics
Odetics
Panasonic
Sony
Sony
Sony
Digital Processing :
Imagine
Communications
Imagine
DivArchive (DiVa)
MassStore
FlashNet
Digicart & Digicart E
P-Touch PTPC Model
With Epson 1520 printer
PM4i, 4420
Easycoder 601XP
Procart
TCS-45
TCS-90
TCS-90A
TCS-90LEM
TCS-90M
Smart Cart
LMS Family
Flexicart
XDCART (PDJ-A640)
NetVX
Digital Turnaround Processor
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 350 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Communications
Tandberg
Telestream
Graphic Devices:
E5780 Series
FlipFactory
Avid
Chyron
Chyron
Evertz
DekoCast via Triple-I control
Duet 2Channel SD/HD / LEX
Hyper-X
Appendix A: Supported Devices
9625LGA/LG, 9725LGA/LG, HD9625LG,
HD9725LGA/LG
Icon Station Imagine
Communications
Imagine
Communications
Inscriber
G7 ;G5 XT ;G5 ;G3 ;G1
TitleOne XT ; TitleOne
(*)
Imagine
Communications
Miranda
Icon Logo, LogoMotion, LogoMotion II
Miranda
ORAD
Pixel Power
Quantel
SAV
VizRT
Intuition, Imagestore, Imagestore 2, Imagestore 750
Vertigo XG
3DPlay / Maestro
Collage / Graphite / Clarity
SQ Server
LGA 100 / LGA 200 / LG 50
Viz Multichannel Playout (VDCP or CII)
VizRT Viz Trio (VDCP or CII)
Master Control Switchers:
Evertz
Evertz (Quartz)
Grass Valley Group
Grass Valley Group
9625 DSK-LGA
QMC w/QMG Graphics
GVG-100
Maestro, No DVE or Logo
Grass Valley Group
Grass Valley Group
Imagine
Communications
Imagine
Communications
Miranda
M-2100
Saturn
IconMaster w/IconLogo
Opus
PresMaster w/ IS2 and Intuition, PresStation
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 351 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Nvision - Miranda NV5128-MC w/ Logo recall
Pixel Power
Pro-Bel
BrandMaster
TX-220, TX-520
Pro-Bel
Ross
Snell & Wilcox
Thomson
Masterpiece (TX-520 Control)
310/316 AVM7900/DVM8900
Trikkey Triple Keyer
Artel MCS9920
MC2020, MC-500 w/501/502 tub Utah Scientific
News Systems:
Associated Press
Avid
Chyron
Octopus
PSIP Generators:
ENPS iNews
CAMIO
Octopus Newsroom
PSIP Pro
GuideBuilder
DTV Innovations
Triveni Digital
Routers:
Evertz (Quartz)
Evertz (Quartz)
Grass Valley Group
Grass Valley Group
Grass Valley Group
Grass Valley Group
Grass Valley Group
Grass Valley Group
Grass Valley Group
Q1600/Q3200
SC-1000 Controller & Xenon
20-Ten
7000
Acappella
AccuSwitch (w/ CM4000)
Concerto w/ Encore Controller
Horizon
Trinix
Grass Valley Group
Grass Valley Group
Imagine
Communications
Imagine
Communications
Imagine
Communications
Triton HD
Venus (w/ VM3000 & 4000)
Integrator / Integrator Gold
Panacea
Platinum
Appendix A: Supported Devices
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 352 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
Imagine
Communications
XPlus
Miranda
Miranda
NTW-HD16x16
HD0808 / HD1616
Network Electronics
Nvision – Miranda
Nvision - Miranda
Pesa
Vikinx a.k.a Proline
Appendix A: Supported Devices
NV 1055/NV4055, Series 5000 thru 8000
NV9000 Router Controller
2400/6600E
Pesa
ProBel
Sierra
Sony
Sony
Utah Scientific
Tiger/Jaguar/Cougar w/ 3500 Plus Controller
Standard, Systems 2 & 3
Yosemite
DVSV 16 x 16 or larger
HDS-X (3600, 3700 & 5800)
AVS Series
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 353 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix B: Error Messages
Appendix B: Error Messages
Device Server Errors
Following is a list of Errors that can be generated by ADC Device Server v11. Please note that the Time of Day the error occurred, the list name, as well as the Device Name precede errors. The quickest method to find your error in this document is to do a Find using only the text of the specific error message less the Time of Day, list name and if displayed, Device
Name.
NOTE: This section does not cover all possible errors. Contact Automation Support for assistance with any error: listed or not listed.
AIR COPY REMOVED FROM EVENT - The primary copy of the media was removed or ejected, and the backup (Protect) copy became the primary copy. The media was not on-air.
ANOTATION CAUSED SHORT PROGRAM
ANOTATION MEDIA WAS EJECTED - The secondary record event was deleted. No record.
ARM NOT INDEXED - The arm of the TCS90 cart. Machine is not properly indexed (not initialized or problem).
ARM OFF LINE: <Error Code> - One or more cassette handler component not indexed.
AUDIO DATA ERROR LEVEL NO GOOD - ID: <ID> <Time Code> - In a Digital Sony deck the VTR protocol returned back an Audio Data error. The SOM of the error code will indicate where on the tape the error occurred.
AUDIO READ AFTER WRITE NO GOOD - ID: <ID> <Time Code> - In a Digital Sony deck the VTR protocol returned back an Audio Raw Verify error. The SOM of the error code will indicate where on the tape the error occurred.
AUDIOOVER NUMBER SWITCHED ON/OFF MANUALLY - Manual Intervention occurred on
Audio Over.
AUDIOOVER NUMBER SWITCHED ON/OFF MANUALLY - Manual Intervention occurred on
Audio Over.
AXIS OFF LINE - The arm cannot move in the axis (not initialized or problem).
BAD BARCODE READ ON BIN: <Bin Number> - The barcode reader in the cart machine has detected a label on the tape, but cannot properly read it.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 354 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix B: Error Messages
BARCODE READ LOST - An unknown error occurred in a cart machine when trying to read the barcode label on a tape.
BARCODE READER ERROR - An error occurred with the barcode reader.
BIN: <Bin Number> IN USE BY VTR <Error Code> - BIN assigned to multiple tape.
CACHING FAILURE-CHECK EVENT:<ID> List <Error Code> - Impossible to make a cache request. The ID of the media seems bad.
CART COMMAND MALFUNCTION - C<ErrorCode> COMMAND FORMAT ERROR - Bad format of the command sent to the cart machine.
CART COMMAND MALFUNCTION - C<ErrorCode> ILLEGAL COMMAND ID - Unknown command ID.
CART COMMAND MALFUNCTION - C<ErrorCode> MARC BUFFER FULL - Cart machine buffer is full. Impossible to run the command.
CART COMMAND MALFUNCTION - C<ErrorCode> MARC BUSY - The cart machine is busy, the command will not run.
CART COMMAND MALFUNCTION - C<ErrorCode> MARC BUSY - The cart machine is busy.
CART COMMAND MALFUNCTION - INVALID PARAMETER - Cart command contained invalid parameters.
CART COMMAND MALFUNCTION - INVALID PARAMETER <ErrorCode> - Bad command parameters sent to the cart machine.
CART COMMAND MALFUNCTION - INVALID PARAMETER <ErrorCode> - Bad command parameters sent to the cart machine.
CART COMMAND MALFUNCTION - INVALID PARAMETER <ErrorCode> - Bad command parameters sent to the cart machine.
CART ERROR ON BARCODE READER COMMAND - Problem with a barcode reader command.
CART ERROR ON MISCELLANEOUS COMMAND - Message for every kind of errors
(MISCELLANEOUS).
CART ERROR ON ROBOT COMMAND - Problem with a robot command.
CART ERROR ON VTR COMMAND - Problem with a VTR command.
CART JARRED - Attempted a movement command while the emergence stop switch is activated.
CART MALFUNCTION - <IDC_Format_OdeticCart> - General problem in the odetics carts.
CART OTHER MALFUNCTION - M<ErrorCode> NO TIMECODE - There is no timecode reference in the cart machine.
CART OTHER MALFUNCTION - M<ErrorCode> TIMECODE ERROR - Timecode error with the cart machine.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 355 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix B: Error Messages
CART ROBOT MALFUNCTION - BAD BARCODE READ ON BIN: <ErrorCode> - The barcode reader in the cart machine has detected a label on the tape, but cannot properly read it.
CART ROBOT MALFUNCTION - R<ErrorCode> Abnormal End - The command wan abnormally finished.
CART ROBOT MALFUNCTION - R<ErrorCode> Abnormal End - The command was abnormally finished.
CART ROBOT MALFUNCTION - R<ErrorCode> DEVICE OFF LINE - Device connected but offline.
CART ROBOT MALFUNCTION - R<ErrorCode> DEVICE RETURNED NAK, MINOR ERROR
- The robot responded with a NAK, instead of an ACK.
CART ROBOT MALFUNCTION - R<ErrorCode> DEVICE RETURNED NAK, MINOR ERROR
- The robot responded with a NAK, instead of an ACK.
CART ROBOT MALFUNCTION - R<ErrorCode> DEVICE RETURNED NAK, MINOR ERROR
- The robot responded with a NAK, instead of an ACK.
CART ROBOT MALFUNCTION - R<ErrorCode> DEVICE RETURNED NAK, MINOR ERROR
- The robot responded with a NAK, instead of an ACK.
CART ROBOT MALFUNCTION - R<ErrorCode> DOOR IS OPEN - The door of the robot is open.
CART ROBOT MALFUNCTION - R<ErrorCode> EJECT TIMEOUT - Eject command didn't run on time in a robot.
CART ROBOT MALFUNCTION - R<ErrorCode> EJECT TIMEOUT - Eject command didn't run on time in a robot.
CART ROBOT MALFUNCTION - R<ErrorCode> UNINITIALIZED - Robot not initialized.
CART ROBOT MALFUNCTION - R<ErrorCode> UNINITIALIZED - Robot not initialized.
CART ROBOT MALFUNCTION - R<ErrorCode> Unknown Robot Error - The robot returned an unknown problem.
CART VTR MALFUNCTION - V<ErrorCode> CAN NOT CANCEL - Impossible to cancel the
VTR command.
CART VTR MALFUNCTION - V<ErrorCode> COMMAND CANCEL - Cancel of a VTR command.
CART VTR MALFUNCTION - V<ErrorCode> COMMAND CANCEL - Cancel of a VTR command.
CART VTR MALFUNCTION - V<ErrorCode> COMMAND CANCEL - VTR command was cancelled.
CART VTR MALFUNCTION - V<ErrorCode> COMMUNICATION ERROR - Communication error between the VTR and the Device server.
CART VTR MALFUNCTION - V<ErrorCode> COMMUNICATION ERROR - Communication error from a VTR in the cart machine.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 356 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix B: Error Messages
CART VTR MALFUNCTION - V<ErrorCode> COMMUNICATION ERROR - Communication error from a VTR in the cart machine.
CART VTR MALFUNCTION - V<ErrorCode> COMMUNICATION ERROR - Communication error from a VTR in the cart machine.
CART VTR MALFUNCTION - V<ErrorCode> DEVICE OFF LINE - Device connected but offline.
CART VTR MALFUNCTION - V<ErrorCode> DEVICE OFF LINE - VTR connected but offline.
CART VTR MALFUNCTION - V<ErrorCode> DEVICE OFF LINE - VTR from a VTR in the cart machine is off line.
CART VTR MALFUNCTION - V<ErrorCode> DEVICE WENT INTO LOCAL - The remote control from the VTR in the cart machine is not able.
CART VTR MALFUNCTION - V<ErrorCode> HARDWARE ERROR - Hardware error for a
VTR in the cart machine.
CART VTR MALFUNCTION - V<ErrorCode> HARDWARE ERROR - Hardware error for the cart machine.
CART VTR MALFUNCTION - V<ErrorCode> MARC BUSY - The cart machine is busy, the
VTR command is not running.
CART VTR MALFUNCTION - V<ErrorCode> MARC SOFTWARE ERROR - VTR Cart machine software problem.
CART VTR MALFUNCTION - V<ErrorCode> MARC SOFTWARE ERROR - VTR Cart machine software problem.
CART VTR MALFUNCTION - V<ErrorCode> NO RESPONSE - No answer from a VTR in the cart machine.
CART VTR MALFUNCTION - V<ErrorCode> NO VTR - There is no VTR connected.
CART VTR MALFUNCTION - V<ErrorCode> REC INHIBIT - Recording impossible with a
VTR in the cart machine.
CART VTR MALFUNCTION - V<ErrorCode> SERVO TROUBLE - Servo problem.
CART VTR MALFUNCTION - V<ErrorCode> TAPE TROUBLE - Problem with a tape in a
VTR.
CART VTR MALFUNCTION - V<ErrorCode> UNDEFINED COMMAND - Undefined command sent to a VTR in the cart machine.
CASSETTE STUCK IN ELEVATOR - POSSIBLE VTR PROBLEM - The door on the cart machine is open.
CHC SLIDER NOT RETRACTED - Attempted a load port command before previous stall condition cleared.
COMMAND TIMED OUT, RECEIVED NO REPLY - Command got no reply.
COMMUNICATIONS LOST WITH CART - A Cart Machine stopped communicating over the
RS422 connection.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 357 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix B: Error Messages
COMMUNICATIONS LOST WITH DEVICE - The communication between the device server and the video server is lost.
COMMUNICATIONS LOST WITH DEVICE <Error Code> - A device stopped communicating over the RS422 connection.
COMMUNICATIONS RESTORED WITH DEVICE - The communication between the device server and the video server is restored.
COMPILE MEDIA NOT IN POSITION TO PLAY - Rollover between compile reels failed.
DEVICE - DIAGNOSTIC CODE:<Error Code> ID: <ID> - Error code return for a media in the video disk.
DEVICE - DIAGNOSTIC CODE:<Error Code> ID: <ID> - Specific error from the odetics cart.
The errors have to be checked in the protocol of the device.
DEVICE - DIAGNOSTIC CODE:<Error Code> ID: <ID> - Used by video disk , do not use in diagnostic. The errors have to been checked in the protocol of the device.
DEVICE DELETED SPOT: <ID> - Spot deleted from the device. Impossible to play it.
DEVICE ERROR <Device Name> - INTERNAL ERROR - RESULT BUFFER OVERRUN -
The buffer of the video server is full. The command won't be run.
DEVICE ERROR <Device Name> SWITCHPRESET - VID CROSSPOINT: <VideoInput> <->
AUD CROSSPOINT: <AudioInput> - From SwitchPreset.
DEVICE ERROR - PORT NOT VALID - Problem with a port of the video disk.
DEVICE ERROR - REPORTED FROM DEVICE: <Error Code> - Error code return for the video disk.
DEVICE ERROR - REPORTED FROM DEVICE: <ErrorCode> - Used by video disk , do not use in diagnostic. The errors have to been checked in the protocol of the device.
DEVICE NAME NOT VALID - The major device specified by the system resource event could not be found.
DEVICE NOT CUED IN TIME, HOLDING TIME:<ID> List <Error Code> - Media not cued in time in the video disk.
DEVICE NOT CUED IN TIME, HOLDING TIME:<ID> List <Error Code> - Media not cued in time.
DEVICE NOT IN EDIT ON - After a command to go into edit on mode, the device indicates that it is not in edit on mode.
DEVICE PLAY/RECORD STATUS LATE: <ID> - Problem with the time delay of the device.
DEVICE RECORDED SPOT: <ID> - Spot recorded in the device. Can be played.
DEVICE RETURNED ACK - Received unexpected ack.
DEVICE RETURNED NAK, MINOR ERROR <Error Code> - A device returned either a NAK through the protocol or a problem with communications existed.
DEVICE RETURNED UNEXPECTED NAK, MINOR ERROR <Error Code> - Received unexpected nak.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 358 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix B: Error Messages
DEVICE SENT CUE CMD: <ID> - ID in copy queue is not in spot collection.
DEVICE SENT PROTECT CMD: <ID> - Record media, spot marked for cache.
DEVICE SERVER LOST BACKGROUND: <Error Code> - Event pointer nil when unregistered.
DEVICE SERVER REFERENCE VIDEO LOST
DEVICE SERVER TIMECODE LOST
DEVICE TIMEOUT -RETRYING COMMAND: <Error Code> - A timeout occurred when waiting for the response of a device.
DEVICE WENT INTO LOCAL - The device is no longer under automation control.
Communications exist, but the device will not respond to commands.
DIAGNOSITIC STATUS ERROR <Error Code> - In a Digital Sony deck the VTR protocol returned the diagnostic status bit set in the extended status. The minor error code has the actual error code as defined by the Sony VTR Protocol.
DISK ERROR - AUDIO OVERLOAD - Problem with the configuration of the audio in the video server.
DISK ERROR - COMMAND NOT SUPPORTED - The video file server received a command not yet implemented.
DISK ERROR - COMMAND WHILE BUSY - The video server had an error while is busy.
DISK ERROR - CUE NOT DONE - The media was not cued on the right timecode.
DISK ERROR - DISK IS FULL, RECORD FAILED - The video disk server is full. No recording.
DISK ERROR - ID ALREADY EXISTS: <ID> - ID already exist in the video server. Message for a record.
DISK ERROR - ID DELETE PROTECTED: <ID> - ID protected, do not delete from the video server.
DISK ERROR - ID NOT FOUND: <ID> - The media in the video server is not in the device storage.
DISK ERROR - ID STILL PLAYING: <ID> - Impossible to stop the media during a play.
DISK ERROR - ID STILL RECORDING: <ID> - Impossible to stop the media during a record.
DISK ERROR - ID TRANSFERRED: <ID> - Impossible to play an ID from the video server it was already transferred.
DISK ERROR - ILLEGAL VALUE - Bad value sent to the video server in a command.
DISK ERROR - INVALID ID: <ID> - The format of the ID is not correct.
DISK ERROR - INVALID PORT - Configuration conflict with port.
DISK ERROR - NO AUDIO INPUT - There's no input audio flow in the video server.
DISK ERROR - NO REFERENCE INPUT - The video file server has had the reference video removed.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 359 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix B: Error Messages
DISK ERROR - NO VIDEO INPUT - No video input in the video disk.
DISK ERROR - NO VIDEO PORT OPEN - There's no port configured for the playout.
DISK ERROR - NOT IN CUED STATE - The state of the media in the device server is not already cued.
DISK ERROR - PORT NOT ACTIVE - The port of the video server is not active. The command won't be run.
DISK ERROR - PORT NOT IDLE - The port of the video server is not well reinitialized.
DISK ERROR - PORT PLAYING OR ACTIVE - The port is already used for a command.
Impossible to use it for a new one.
DISK ERROR - SYSTEM ERROR - General problem in the video server.
DISK ERROR - VIDEO PORT DOWN - The playout port is down.
DISK ERROR - WRONG PORT TYPE - Wrong port assignment in the video server.
DISK ERROR-CUE OR OPERATION FAILED: <ID> - Impossible to cue an event in the video server. This message is used for another command.
DISK NAK - COMMUNICATIONS CHECKSUM ERROR - Time out between the device server and the video server. Problem with the checksum of the video server answer.
DISK NAK - COMMUNICATIONS FRAMING ERROR - Time out between the device server and the video server. Problem with the format of the video server answer.
DISK NAK - COMMUNICATIONS OVER FLOW - Time out between the device server and the video server. Problem with the format of the video server answer.
DISK NAK - COMMUNICATIONS PARITY ERROR - Time out between the device server and the video server. Problem with the parity bit of the video server answer.
DISK NAK - COMMUNICATIONS TIME OUT - Time out between the device server and the video server. No response from the video server.
DISK NAK - COMMUNICATIONS UNDEFINED ERROR - Undefined error from the video server.
DOOR OPEN TIMEOUT - The door stayed open too long.
DOS Server network error, obsolete error
DUPLICATE TAPE: <ID> In BIN: <Bin Number> - There at least two identical ID in the bins of the cart Machine.
ELEVATOR OFF LINE - The robotic elevator is in an offline state.
ELEVATOR REPLY TIMEOUT - The elevator of the cart machine didn't move on time.
EMERGENCY STOP ACTIVE - Manual intervention has removed the device from service.
ERROR - DEVICE ACCESS ERROR - Access denied in the device.
ERROR - DEVICE OUT OF MEMORY - The memory of the device is full.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 360 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix B: Error Messages
ERROR - DISK CACHE RECORDER FAILED ID: <ID> - Problem with the recording during the cache.
ERROR - DISK FAILED PLAY ID: <ID> - Problem to play a media from the video server.
ERROR - DISK FAILED RECORD ID: <ID> - Problem to record a media to the video server.
ERROR - LOST DISK REPLY(S) - Problem with the disk of the video server.
ERROR - RESENT LAST COMMAND - A command have not been executed and lost from the memory of the video server.
ERROR - UNKNOWN RESPONSE - The answer from the video server is wrong.
EVENT NOT PLAYED
EVENT NOT PLAYED
EVENT NOT PLAYED
EVENT NOT PLAYED
EVENT NOT PLAYED - INVALID OFFSET ON SECONDARY - A secondary GPI event that was to be run twice on the same primary event had an overlapping start time on the subsequent GPI event.
EVENT NOT PLAYED - SECONDARY MEDIA MISSING - GMT Error. A GMT transfer failed because the secondary events were not valid, such as in a baseband transfer.
EVENT SKIPPED - ABNORMAL END - An event encountered an end of media condition such as end of tape or end of recorded clip. The media stopped playing and the next event was run. (If a Protect copy exists this message is not generated)
EVENT UNABLE TO CUE - NO SOM - The Start of Message in the event is invalid for the material. Cannot cue the material to the specified location
EVENT UNABLE TO RECORD, REC INHIBIT ON - The device has recording disabled.
Typically, a VTR with the rec inhibit tab set
FETCH OR INSERT TO EMPTY OR FULL LOCATION - Try to insert in full bin or try to take a tape from an empty bin.
GMT MEDIA TRANSFER FAILED, TIME = - A failure was reported back to the list for a media transfer by a requestor. The media was not transferred.
GMT-ABORT EVENT DUE TO ARCHIVE OR DISK TIME OUT - Abort event due to the archive manager or the video file server timeout.
GMT-BASEBAND DEVICE I/O FAILURE - A problem occurred during the baseband transfer.
GMT-EVENT ABORTED DURING RUNNING STATE - The running GMT event aborted during execution.
GMT-EVENT ID NOT FOUND IN SOURCE DEVICE - Event ID not found in the source device.
GMT-FOUND BUFFER FULL DURING GLOBAL DELETE - A buffer overflow error occurred during a global delete.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 361 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix B: Error Messages
GMT-FOUND UNKNOWN/UNIMPLEMENTED DISK COMMAND - Found unknown / unimplemented VDCP command during transfer.
GMT-ID ALREADY EXISTED IN DESTINATION DEVICE - The media already exists in the device storage of the destination device.
GMT-LIST EVENT CUT OR RAN SHORT - An event on the GMT list was cut.
GMT-LISTED ID NOT FOUND IN DISTRIBUTOR COLLECTION - The media wasn't found by the distributor.
GMT-MISSING DISK HANDLE WHILE NEEDED - There is no disk handle parameter available for the activity.
GMT-NO FIBER DISTRIBUTOR TO DO THE MOV AFTER BB TRANSFER - No fibre distributor available to do the move after the baseband transfer has occurred.
GMT-NO FIBER DISTRIBUTOR TO DO THE MOV AFTER CFA - There is no fibre distributor to do a copy after the move from archive has occurred.
GMT-NO GLOBAL DELETE TARGETS CONFIGURED - No global delete targets are configured in the distributor.
GMT-REQUEST SUCCESS - The request succeeded.
GMT-REQUESTOR LOST COMMUNICATION WITH DISTRIBUTOR - The requestor lost communications with the distributor.
GMT-TRANSFER SUCCESS - Distributor transfer media in Fiber/Archive/WAN routing mode is successful.
GMT-VACP ERR COMM FAIL - VACP response from archive manager. Problem of communication.
GMT-VACP ERR ID EXISTS - VACP response from archive manager. The ID is already existing.
GMT-VACP ERR ID NOT FOUND - VACP response from archive manager. The ID was not in a device storage. The archive manager cannot find the specified ID.
GMT-VACP ERR INIT - VACP response from archive manager. Problem at the initialization.
GMT-VACP ERR INSUFF MEMORY - VACP response from archive manager. Problem of memory.
GMT-VACP ERR INSUFF SVCS - Insufficient services.
GMT-VACP ERR MACRO FAIL - The Archive manager reports (CFA/CTA) macro command is failed.
GMT-VACP ERR OP COMPLETED - Inverse of Incomplete Operation.
GMT-VACP ERR OPPERATION ABORTED - VACP response from archive manager. The command was aborted because of an unspecified error.
GMT-VACP ERR PARM INVALID - VACP response from archive manager. Bad parameters in the command.
GMT-VACP ERR PARTITION SMALL - The partition is too small to hold the material.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 362 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix B: Error Messages
GMT-VACP ERR PORT_BUSY - VACP response from archive manager. The port is busy.
Impossible to run the command.
GMT-VACP ERR RW FAILURE - VACP response from archive manager. Problem on read write mode.
GMT-VACP ERR SETUSERID - VACP Client is using wrong user ID to do the login.
GMT-VACP ERR TAPE UNAVAIL - VACP response from archive manager. No available tape to perform the operation.
GMT-VACP ERR TIMEOUT - VACP response from archive manager. Time out on a command.
GMT-VACP ERR UNKNOWN Command Received - VACP response from archive manager.
The command is not a valid one.
GMT-VACP NAK_ERR_CHECKSUM - VACP response from archive manager. The checksum indicates an error in transmission.
GMT-VACP NAK_ERR_FRAMING - VACP response from archive manager. A framing error was detected in the message.
GMT-VACP NAK_ERR_ID_CONFLICT - VACP response from archive manager. The ID being sent to the archive already exists.
GMT-VACP NAK_ERR_ILLEGAL_VALUE - VACP response from archive manager. The response is a NAK, as a result of an illegal value being sent.
GMT-VACP NAK_ERR_OVERRUN - VACP response from archive manager. An over run condition was detected in the message.
GMT-VACP NAK_ERR_PARITY - VACP response from archive manager. A parity error was detected in the message.
GMT-VACP NAK_ERR_UNDEFINED - VACP response from archive manager. The response is a NAK, of undefined error type.
GMT-VACP NAK_ERR_UNSUPPORTED - VACP response from archive manager. The command is not supported by the archive manager.
GMT-VACP SUCCESS - VACP response from archive manager. Clip moved successfully.
GMT-VDCP Archive disk handle not configured - VDCP archive disk handle not configured.
GMT-VDCP_SUCCESS - VDCP response from archive manager. The command ran with success.
HARD ERROR - A Sony Protocol VTR returned back the Hard Error bit enabled indicating some physical problem with the VTR or Tape.
HARDWARE TROUBLE BUZZER ALARM - In a Digital Sony deck the VTR protocol returned the buzzer bit set in the extended status.
HEAD STILL IN PLAY - The system resource event attempted to assign a device that was in play. The assignment did not take place.
HUB OFF LINE - Attempted a load port command with no load port installed. Attempted a transfer command with no transfer mechanism installed.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 363 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix B: Error Messages
ID DOES NOT MATCH, MACRO LSB <Error Code> - ID doesn't match.
INCORRECT SIZE AT LOCATION - Insert command attempted to an incorrect size location.
INTERNAL ERROR - BAD COMMAND GENERATED - The format of the command is wrong.
INVALID EVENT COMMAND - The system resource event was not valid and could not be decoded by the list.
INVALID HEAD NUMBER - The minor device head specified by the system resource event was not a valid head number.
KEYER NUMBER SWITCHED ON/OFF MANUALLY - Manual Intervention occurred on
Keyer.
KEYER NUMBER SWITCHED ON/OFF MANUALLY - Manual Intervention occurred on
Keyer.
LIST WILL STOP ON NEXT EVENT - Manual intervention occurred, List will stop on next event, id field is empty.
LOAD PORT FULL - CANNOT UNLOAD VTR - Load port is full in the Procart.
LOAD PORT INDEX, OPEN, CLOSED ARM IN FRONT ?? - Load port problem, it can be a bad reinitialization, or the load port is open or the arm is blocked just in front.
LOAD PORT NOT INDEXED - Bad load port initialization.
LOAD PORT STALL NOT CLEARED - Tape were not put out of the load port.
MACRO BUSY ERROR - A Sony Cart machine returned back a status of Macro Busy on a macro command. This error condition should never occur in a Sony Cart Machine.
MACRO DISTURBED - A Sony Cart machine returned back via the protocol that a Macro
Command was either terminated or disturbed.
MACRO NOT FOUND, MACRO LSB <Error Code> - Couldn't find macro.
MAIN ROBOT - General robot problem.
MAIN ROBOT, CLAW 1 - Problem with the gripper 1 of the robot.
MAIN ROBOT, CLAW 2 - Problem with the gripper 2 of the robot.
MAIN ROBOT, X AXIS - Problem with the X Axis arm robot.
MAIN ROBOT, Y AXIS - Problem with the Y Axis arm robot.
MANUAL INTERVENTION OF SYSTEM - Indicates Manual Intervention on the switcher.
MASTER MEDIA FAILURE - DURING PREROLL - A failure of the primary media occurred during pre-roll of the media. No switching to a protect copy could occur at this time.
MASTER MEDIA FAILURE - PROTECT COPY NOT PLAYING - A failure of the primary media occurred but the backup media was unable to be switched into the on-air video stream.
MASTER MEDIA FAILURE - PROTECT COPY SWITCHED - A failure of the primary media caused the backup media (Protect) to be switched into the on-air video stream.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 364 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference
MECHANICAL INTERFERENCE - Mechanical interference.
Appendix B: Error Messages
MEDIA DEVICE NOT PROPERLY INITIALIZED - The media wasn't initialized properly.
MEDIA MISSING - NOT FOUND - The event was unable to play because the ID was not found in any device
MEDIA NOT THREADED - The event was unable to play because the media was not threaded into a device.
MEDIA UNABLE TO CUE - ID: <ID> - Device is unable to cue.
MODE SET TO DISABLE MOVEMENT WHEN DOOR OPEN - In the Procart cart machine you can enable or not a sound indicating that the door in the Procart cart machine is open and that you have to close it.
MOVE WITH LIGHT CURTAIN ACTIVE - While moving the robotics, an interruption of the light curtain was detected.
MULTIPLE GRIPPER ERRORS
MULTIPLE GRIPPER ERRORS, ARM <Error Code> PLACED OUT OF SERVICE - Gripper is out of service.
NAK RETURNED FROM SWITCHER - The switcher responded with a NAK, instead of an
ACK.
NO ANOTATION EVENTS TO RECORD - The secondary record event was not inserted. No record.
NO CASSETTE IN GRIPPER - Procart cart machine. No tape in the gripper.
NO MORE BINS TO STORE MEDIA - The bins in the cart machine are all full. There is no more room for tapes in the cart machine.
NO VTR AT LOCATION - There is no VTR installed at the physical location.
NOT CUED IN TIME - The event was unable to play because it was unable to cue.
ON AIR EVENT PACKED - LIST WILL STOP - The on-air event was playing, and the packing of the list forced the deletion of the event.
ON AIR EVENT WAS CUT - The on-air event was playing, and it was deleted from the playlist
ON AIR EVENT WAS EJECTED - Media was ejected during playout
ON AIR EVENT WAS RECUED - The event began to play, but the operator intervened by invoking the recue command.
OUTPORT IS FULL - PLEASE EMPTY IT - The I/O port of the cart machine is full. It must be emptied so that the current ejection process continues.
PGM CROSSPOINT NUMBER AUDIO SWITCHED MANUALLY - Manual Intervention occurred on Audio crosspoint number.
PGM CROSSPOINT NUMBER AUDIO SWITCHED MANUALLY - Manual Intervention occurred on Audio crosspoint number.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 365 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix B: Error Messages
PGM CROSSPOINT NUMBER VIDEO SWITCHED MANUALLY - Manual Intervention occurred on video crosspoint number.
PGM CROSSPOINT NUMBER VIDEO SWITCHED MANUALLY - Manual Intervention occurred on video crosspoint number.
PLAY ISSUED - MEDIA IN LOCAL - The device received the play command, but the returned status indicates that it did not go into play mode.
PLAYOUT TIMES OVERLAP - Events overlapped in the transmission list.
PRESETEFFECT BEGIN VID CROSSPOINT: <VideoInput> <-> AUD CROSSPOINT:
<AudioInput> - Beginning of PresetEffect.
PRESETEFFECT END VID CROSSPOINT: <VideoInput> <-> AUD CROSSPOINT:
<AudioInput> - End of PresetEffect.
PROGRAM/INTERFACE ERROR - SYSTEM ALARM - In a Digital Sony deck the VTR protocol returned the system alarm bit set in the extended status.
PROTECT COPY NOT USABLE – REMOVED - The protect copy of the media was removed or ejected, but the primary copy was not. The media was not on-air.
PROTECT MEDIA NOT PLAYED - NOT CUED - The secondary event was unable to play because the media was not cued in time.
PROTECT NAME NOT VALID - The major device to be used as a protect device, specified by the system resource event could not be found.
PUT TAPE FROM VTR: <Error Code> INTO BIN: <Bin Number> - Problem with an unthread tape for a VTR to a bin in the odetics cart.
PUT TAPE: <ID> FROM BIN: <Bin Number> INTO VTR: <Error Code> - Problem with a threading tape in a VTR of an odetics cart.
RECORD ENDED PREMATURELY - The event for a record operation terminated abnormally.
RECORD EVENT WAS CUT - The record event was recording, and it was deleted from the record list.
RECORD NOT STARTED - Event failed to start.
Reference Timecode missing. Shifting from timecode to reference video for clocking input
REFERENCE VIDEO MISSING - The VTR has lost the reference video signal.
Reference Video missing. Shifting to PC Clock for clocking input. (Timecode also missing)
REMOVE TAPE FROM VTR, INSERT VIA I/O PORT - Somebody put a tape manually into a
VTR instead of the load port.
REMOVE TAPES FROM VTRS, INSERT VIA I/O PORT - Somebody put tapes manually into a VTR instead of the load port.
RESEAT CASSETTE IN BIN: <Bin Number> AND INIT ROBOT - Put the tape in its bin and reinintialize the robot.
RETURN TO AUTOMATED CONTROL OF SYSTEM - Indicates the switcher is back to the list control.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 366 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix B: Error Messages
ROBOT WARNING number V<ErrorCode> VTR number <ID> - Problem with a VTR from the
MARC cart machine.
SERIAL CONTROL WENT INTO AUTOMATION - The device is now under automation control. This is the reverse of AUTO_ENABLE_OFF.
SERIAL CONTROL WENT INTO LOCAL - The device is no longer under automation control.
Communications exist, but the device will not respond to commands.
SETKEYON END VID CROSSPOINT: <VideoInput> <-> AUD CROSSPOINT: <AudioInput> -
End of DoSetKeyOn.
SETMIXON END VID CROSSPOINT: <VideoInput> <-> AUD CROSSPOINT: <AudioInput> -
End of DoSetMixOn.
SKIP ISSUED - The event began to play, but the operator intervened by invoking the skip command.
STANDBYON ISSUED - MEDIA IN LOCAL - The device received the standby command, but the returned status indicates that it did not go into standby mode
SWITCHER COMMAND QUEUE FULL <Error Number> - From PutQueue, when queue is full.
SWITCHER DID NOT RESPOND TO REQUEST - The switcher is no longer communicating.
SYSTEM ERROR: NO DATAGRAM NCBS
TAKE WAS SENT VID CROSSPOINT: <VideoInput> <-> AUD CROSSPOINT: <AudioInput>
- From Background, just after sending take.
TAPE TROUBLE - A Sony Protocol VTR returned back the Tape Trouble bit enabled indicating some problem with the tape.
TARGETING OR DOOR OPEN - Procart cart machine. The door is either open or the tape could be put in the VTR.
THREAD FAILURE - DOOR OPEN OR SYSTEM DOWN - <Error Code> - The threading of a tape into the cart VTR has failed. The elevator may have become jammed or the VTR jammed.
TRANSITION - INPUT CROSSPOINT: <CrosspointInput> <-> OUTPUT CROSSPOINT:
<CrosspointOutput> - From transition or/and control panel.
TRANSPORT MECHANISM MUST BE EMPTIED MANUALLY - Gripper has to be emptied manually.
TROUBLE IN DEVICE SERVO - In a Digital Sony deck the VTR protocol returned the servo alarm bit set in the extended status.
TROUBLE WITH OUTPORT - PLEASE CHECK - On those cart machines that have an I/O port, attempting to put a tape into the I/O port failed because of a hardware problem with the
I/O port.
UNABLE TO ASSIGN HEAD - Using the system resource assignment event, the device that was to be assigned to the list could not be assigned.
UNABLE TO RELEASE HEAD - Using the system resource assignment event, the device that was to be released from the list could not be released.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 367 of 410
ADC Device Server v11.61.4
Installation, Configuration, and Operations Reference Appendix B: Error Messages
UNKNOWN MARC ERROR - Unknown MARC cart machine problem.
UNKNOWN RESPONSE FROM CART <Error Code> - Undefined problem from the LMS cart machine.
UNKNOWN THREAD ERROR - <Error Code> - A Sony Cart returned an unknown Macro completion code when the threading of a tape into a VTR failed.
USERBITS NOT VALID, DEVICE NOT SET TO EJECT - A VTR was set to keep the tape even if an eject was issued, but the userbit associated with the tape was not valid.
VENUS NOT LOCKED TO TIMECODE - Venus doesn't get any timecode.
VIDEO DATA ERROR LEVEL NO GOOD - ID: <ID> <Time Code> - In a Digital Sony deck the VTR protocol returned back an Video Data error. The SOM of the error code will indicate where on the tape the error occurred.
VIDEO READ AFTER WRITE NO GOOD - ID: <ID> <Time Code> - In a Digital Sony deck the VTR protocol returned back an Video Raw Verify error. The SOM of the error code will indicate where on the tape the error occurred.
VTR COMMAND TIMEOUT - The VTR command wasn't made on time.
VTR EJECT FAILURE - CHECK FOR JAM - <Error Code> - The VTR did not eject the tape when requested.
VTR ERROR number<Bin Number> - Problem with a tape between the VTR and the bin of the cart.
VTR PROBLEM - CHECK FOR JAM - <Error Code> - A VTR in a cart machine had a failure and is off-line.
VTR STATUS : <Bin Number> - <Bin Number> - Status of the VTR returned to the device server.
WARNING-SPOT SHORTER THAN SCHEDULED: <ID> - The spot in the video server is too short to play well the next event.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 368 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
SQL Server Database Error Messages
ADC 100 applications have migrated to SQL Server. This section provides a reference to database errors that may be encountered.
Error Message Number
Each error message displayed by SQL Server has an associated error message number that uniquely identifies the type of error.
Error Severity
The error severity levels provide a quick reference for you about the nature of the error. The severity levels range from 0 to 25.
Severity
Level
Description
0 to 10
11 to 16
17
20
Severity level 17 indicates that SQL Server has run out of a configurable resource, such as locks. Severity error 17 can be corrected by the DBA, and in some cases, by the database owner.
Severity level 18 messages indicate nonfatal internal software problems. 18
IMPORTANT: Severity errors 19 through 25 are fatal errors and can only be used via
RAISERROR by members of the fixed database role sysadmin with the with log option required. Severity 0 - 18 can be used by all users. When a fatal error occurs (20 - 25), the running process that generated the error is terminated (nonfatal errors continue processing).
For error severity levels 20 and greater, the client connection to SQL Server is terminated.
19 Severity level 19 indicates that a non-configurable resource limit has been exceeded.
Severity level 20 indicates a problem with a statement issued by the current process.
21
22
Messages with a severity level of 0 to 10 are informational messages and not actual errors.
Severity levels 11 to 16 are generated as a result of user problems and can be fixed by the user. For example, the error message returned in the invalid update query, used earlier, had a severity level of 16.
Severity level 21 indicates that SQL Server has encountered a problem that affects all the processes in a database.
Severity level 22 means a table or index has been damaged. To try to determine the extent of the problem, stop and restart SQL Server. If the problem is in the cache and not on the disk, the restart corrects the problem.
Otherwise, use DBCC to determine the extent of the damage and the required action to take.
23
24
25
Severity level 23 indicates a suspect database. To determine the extent of the damage and the proper action to take, use the DBCC commands.
Severity level 24 indicates a hardware problem.
Severity level 25 indicates some type of system error.
State Number
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 369 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
The error state number is an integer value between 1 and 127; it represents information about the source that issued the error (such as the error can be called from more than one place).
For SQL Server Error Definitions
1. From the Windows start menu, select the SQL Server program group and then select
Books Online. The SQL Server Books Online dialog box appears.
2. From the SQL Server Books Online dialog box, click the Search Tab.
3. The Search tab enables you to quickly search Books Online for specific information. In the Query combo box, type the error message number: 208. In the Topic Area To Search frame, select the Title Only check box.
4. To run the search, click the List Topics button. The query runs, searching for 208 in the title of any of the book topics. If one or more items are found, they are displayed in a
Query Results frame in the SQL Server Books Online dialog box.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 370 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
5. To view the document(s) found in the search, double-click the item or select the item and click the Display button.
6. The detailed information for the error message number, including a detailed explanation and the action to take, is displayed in the document.
You can even print the document
When getting multiple documents back for an error message query, select the document title Error Error_Number. For example, the document title Error 208 displays detailed information on error 208. After you have displayed the error number document, read through the document for an explanation of the error and then follow the directions in the
Action section of the document to correct the error.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 371 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e
BTrieve Database Errors
A p p e n d i x B : E r r o r M e s s a g e s
ADC 100 applications have migrated to SQL Server. The following BTrieve error list is
provided for backward compatibility of this document.
1: The operation parameter is invalid.
The specified Btrieve operation does not exist or is not valid for this version of the
MicroKernel.
2: The application encountered an I/O error.
An error occurred while reading from or writing to the disk. One of the following has occurred:
The file is damaged, and you must recover it. Refer to the User's Guide for more information about recovering a file.
There is a large pre-image file inside a transaction, and there is not enough disk space for a write to the pre-image file.
For pre-v6.0 data files, there is one pre-image file for multiple data files. For example, if you name the data files CUSTOMER.ONE and CUSTOMER.TWO, both files have preimage files named CUSTOMER.PRE.
For pre-v6.0 data files that are larger than 768 MB, there is a conflict among locking mechanisms. The file has not been corrupted. Your application can retry the operation until the conflict is resolved (when the competing application releases the lock your application requires).
A pre-v6.0 Btrieve engine attempted to open a v6.x or later MicroKernel file.
3: The file is not open.
The operation cannot execute because the file is not open. The application must perform a successful Open operation before the MicroKernel can process any other operations. The
MicroKernel also returns this status code if the application passed an invalid position block for the file, or if the application passed a position block with a client ID other than the client ID used to open the file.
4: The application cannot find the key value.
The MicroKernel cannot find the specified key value in the index path. When you receive this status code on an Update or Delete operation, it usually means that the file is damaged, and you must recreate it. Also, pre-v6.x server engines return this status code if two separate files have different ACSs, but those ACSs have the same name. Never use the same name for different ACSs, regardless of the version you are using.
5: The record has a key field containing a duplicate key value.
The MicroKernel cannot add or update a record because the record has a key field that contains a duplicate key value for an index that does not allow duplicate values. The
MicroKernel also returns this status code when it cannot create an index that does not allow duplicate key values because a duplicate key value already exists.
6: The key number parameter is invalid.
The value stored in the key number parameter is not valid for the file being accessed. The key number must correspond to one of the keys defined for the file. Valid key numbers are 0 through 118.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 372 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e
7: The key number has changed.
A p p e n d i x B : E r r o r M e s s a g e s
The key number parameter changed before a Get Next, Get Next Extended, Get Previous, or
Get Previous Extended operation. The operation requires the same key number parameter as the previous operation, because the MicroKernel uses positioning information relative to the previous key number.
In a related situation, the MicroKernel returns this status code when an application performs a
Delete or Update operation immediately following a Get operation. If the application changes the value of the key number in the Delete or Update operation (from the value used with the preceding Get operation), the MicroKernel deletes or updates the record as requested and does not return this status code, at least not at this point. However, the MicroKernel does return this status code on the very first Get Next, Get Next Extended, Get Previous, or Get
Previous Extended operation performed after the deletion or update, even if that Get operation uses the same key value the application passed to the Delete or Update operation.
If you need to change key numbers between consecutive Get Next, Get Next Extended, Get
Previous, or Get Previous Extended operations (or in Delete or Update operations as described in the preceding paragraph), use a Get Position operation followed by a Get
Direct/Record operation to reestablish positioning for the new index path.
8: The current positioning is invalid.
You must establish the current position in order to update or delete a record. Perform a Get or Step operation to establish the current position. The MicroKernel also returns this status code if the application passed an invalid position block for the file.
9: The operation encountered the end-of-file.
The MicroKernel returns this status code in one of the following situations:
The operation encountered an end-of-file boundary or tried to read past a file boundary
(end-of-file or start-of-file).
In a Get Next Extended, Get Previous Extended, Step Next Extended, or Step Previous
Extended operation, the number of records satisfying the filtering condition is less than the number of specified records to be returned, and the reject count or filter limit has not been reached.
When reading a file in ascending order according to an index path, the MicroKernel has already returned the last record in that index path. When reading a file in descending order according to an index path, the MicroKernel has already returned the first record in the index path.
When using the Get By Percentage operation, either the value supplied for the percentage is too high-it exceeds 10,000 decimal (0x2710)-or the file contains no records.
10: The key field is not modifiable.
During an Update operation, the application attempted to modify a key field that is defined as non-modifiable.
11: The specified filename is invalid.
This status code indicates either that the specified filename does not conform to file naming conventions, or that the pathname is invalid. Make sure the filename or pathname is valid for the environment. This status code can also have the following meanings in client/server versions of the MicroKernel:
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 373 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
The application attempted to open a file that has .^^^ as its extension. This extension is reserved for the MicroKernel to use during continuous operation. (Only server engines can use continuous operation.)
The data buffer for a Begin or End continuous operation is not set up correctly.
12: The MicroKernel cannot find the specified file.
Check the key buffer parameter to make sure the pathname is terminated with a blank or a binary zero. Also, ensure that the file exists. When accessing a file on a server, ensure that you have FILE SCAN rights to the directory in which the file resides.
13: The MicroKernel could not open the extension file for an extended file.
The MicroKernel could not open the extension file for an extended file that the application tried to open. For v7.0 and later MicroKernels, an extended file can consist of a base file and up to 15 extension files. Extension files must remain in the same volume and directory as their base files.
The MicroKernel returns this status code if you delete, move, or rename the extension files.
For pre-v6.0 MicroKernels, extension files must be loaded on the logical disk drive specified when the extension was created. Both the primary file and its extension file must be on-line to access an extended file.
14: The MicroKernel cannot create or open the preimage file.
The MicroKernel uses pre-image files only for pre-v6.0 data files.
The MicroKernel returns this status code in one of the following situations:
The MicroKernel cannot create a new pre-image file because the disk directory is full.
The MicroKernel must be able to create a pre-image file.
The MicroKernel cannot open the pre-image file to restore file integrity. If the pre-image file is erased or damaged, the MicroKernel cannot restore the file's integrity. Refer to the
User's Guide for more information about recovering damaged files.
The workstation MicroKernel cannot assign a handle to the pre-image file because the
MicroKernel was not started by a user with access rights to the pre-image file.
The file structure of a pre-image file created by a v6.0 or later MicroKernel is different from the file structure of a pre-image file created by a v5.x MicroKernel. If you have an extraneous .PRE file in v5.x format and you are using a v6.0 or later MicroKernel, the
MicroKernel returns this status code when you try to open the data file to which the .PRE file belongs.
15: The application encountered an I/O error during preimaging.
The MicroKernel uses pre-image files only for pre-v6.0 data files.
This status code indicates that either the disk is full or the pre-image file is damaged.
If you receive this status code, proceed as follows:
If the pre-image file is damaged, the integrity of the data file cannot be ensured. Refer to the User's Guide for more information about recovering damaged files.
If the disk is full, erase any unnecessary files.
16: The application encountered an expansion error.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 374 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e
This status code is obsolete in MicroKernel versions 6.0 and later.
A p p e n d i x B : E r r o r M e s s a g e s
The MicroKernel returns this status code when it encounters an error while writing the directory structure to disk prior to creating the expanded file partition. Either the MicroKernel cannot close the file, or a new page was added to the file and the MicroKernel cannot close and reopen the file to update the directory structure. Check for a disk hardware failure.
17: The application encountered a close error.
This status code is obsolete in MicroKernel versions 6.0 and later.
The MicroKernel returns this status code when it encounters an error while writing the directory structure to disk prior to closing the file. Either the MicroKernel cannot close the file, or a new page was added to the file, and the MicroKernel cannot close and reopen the file to update the directory structure. Check for a disk hardware failure. The MicroKernel also returns this status code if the application passed an invalid position block for the file.
18: The disk is full.
The MicroKernel can return this status code in the following situations:
The disk is full, and the MicroKernel cannot expand the file to accommodate additional records. Erase any unnecessary files. If using a pre-v6.0 MicroKernel, you can possibly end the file to gain additional disk space.
There is not enough space to append a new page to the data file.
The pre-image file is out of disk space. If your files are in pre-v6.0 format and you are in a transaction, the pre-image file size increases for the duration of the transaction. If you receive this status code, either reduce the number of operations in the transaction, or obtain more disk space.
For files located on a NetWare server, the NetWare owner name for the file is no longer valid, and your application tried to insert or update records in the file, thus causing the file to expand. In this case, the MicroKernel returns this status code when it needs to add a page to the file, regardless of how much disk space is available. To check for an owner name, use the NetWare utility NDIR. To add an owner name, use either FILER (a
NetWare text utility) or the NetWare Administrator graphical utility.
In some environments, you can restrict the amount of disk space available to each user.
This status code indicates that the application attempted to expand a data file beyond the amount of disk space allocated to the file's owner.
You tried to read or modify a file which was not closed properly after a disk full error.
Make sure that every application that used the file at the time of the disk full error closed the file successfully.
19: The application encountered an unrecoverable error.
To ensure file integrity, recover the file as described in the User's Guide.
20: The MicroKernel or Btrieve Requester is inactive.
In the DOS and NetWare environments, you must load the MicroKernel and, if applicable, the
Btrieve Requester before generating any requests. Also for NetWare, ensure that the appropriate communications modules are loaded at the server.
If you are running an application in a client/server environment and also need to access files located on a local drive, ensure that you enable both Local and Server access and that the local MicroKernel is available.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 375 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
By default in the Windows and Windows NT environments, the Setup utility enables the Local
Engine Usage option. To access a client/server MicroKernel engine but not a workstation engine, turn the Local option off and turn the Server option on. To access both workstation and client/server MicroKernels, enable both the Server option and the Local option.
Also, in the Windows environment, ensure that the Btrieve for Windows DLLs and
MicroKernel executable are in your path or in the top level of your Windows directory. In the
Windows NT server environment, you must start the MicroKernel before generating any requests. Ensure that the Windows NT DLLs are in your path. Also ensure that the appropriate communications modules are loaded at the server.
In the OS/2 environment, ensure that the necessary DLLs are in your LIBPATH directory.
21: The key buffer parameter is too short.
The key buffer parameter is not long enough to accommodate the key field for the requested index path. Verify that the length of the key buffer equals the defined length of the key specified in the key number parameter.
22: The data buffer parameter is too short.
The data buffer parameter specified by the application was not large enough to accommodate either the minimum length of the record for an Insert or Update operation, or the entire record length for a Get or Step operation. Also, the data buffer may not be large enough to accommodate the length of data required for operations such as Create, Create
Index, Stat, Get By Percentage, Find Percentage, or Version.
For Get or Step operations, the MicroKernel returns as much data as it can and this
status code, indicating that it cannot return the entire record.
For an Insert operation, the MicroKernel does not insert the record if the data buffer is
shorter than the fixed-length portion of the record.
For an Update operation, if the data buffer is too short to contain the fixed-length portion
of a record, the MicroKernel does not update the record.
For the Create, Stat, and Create Index operations, the data buffer is not long enough to
contain all the file specifications, the key specifications, and (if specified) the ACS
definition.
For the Get by Percentage or Find Percentage operation, the data buffer length is less
than 4 bytes.
For the Version operation, the data buffer length is less than 5 bytes.
This status code can also indicate a corrupt file if the file allows variable-length records and you
receive this status code on a Get or Step operation. In such a corrupt file, you can receive Status
Code 54 when you use Get or Step operations to read other records. Recover the file according
to the instructions in the User's Guide.
23: The position block parameter is not 128 bytes long.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 376 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
This status code is obsolete in Btrieve language interface versions 6.0 and later.
The position block parameter must be exactly 128 bytes long.
24: The page size or data buffer size is invalid.
The MicroKernel returns this status code in one of the following situations:
The page size you specified when creating a file is invalid. The page size must be a multiple of 512 bytes and cannot exceed 4096 bytes.
During a Create operation, the page size is the first file specification the MicroKernel checks. A Status Code 24 at this point can indicate an invalid data buffer parameter.
In pre-v6.1 MicroKernels, the Open operation can return this status code. In this case, the
MicroKernel cannot open the file because the file's page size exceeds the Largest Page Size configuration option. To successfully open the file, you must increase the value of the Largest
Page Size configuration option and then reload the MicroKernel. The v6.1 or later
MicroKernel does not return this status code from the Open operation.
25: The application cannot create the specified file.
The MicroKernel can return this status code if an application attempts to create a data file, but the disk directory or the disk itself is full. If the application is creating a file over an existing file, the MicroKernel returns this status code when the existing file is open or when the operating system prevents the operation for some other reason (for example, because the file is flagged transactional in NetWare).
Sometimes pre-v6.0 MicroKernels can return this status code if the HOLD parameter in
NET.CFG or SHELL.CFG is set to ON and the application attempts to create a data file on a network drive.
(The HOLD parameter is set to OFF by default.) Creating the file on a local drive is successful regardless of the value of the HOLD parameter.
26: The number of keys specified is invalid.
The number of keys specified for the page size is invalid. The number of key segments must be within the following limits:
Page Size 512 1024 1536 2048 2560 3072 3584 4096
Max. No. Key Segments 8 23 24 54 54 54 54 119
If the MicroKernel is configured to create files in v5.x format, the maximum number of key segments is 8 for files using 512 byte page sizes; the maximum number of key segments for all other v5.x files is 24.
27: The key position is invalid.
The specified key field position is less than 1 or exceeds the defined record length for the file.
Either the key position is greater than the record length or the key position plus the key length exceeds the record length.
28: The record length is invalid.
The specified record length (plus overhead for duplicates, record usage count, variable record pointers, key pointers, and blank truncation information) must be less than or equal to the page size minus 6 bytes, and greater than or equal to 6 bytes.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 377 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e
29: The key length is invalid.
A p p e n d i x B : E r r o r M e s s a g e s
The specified key length must be greater than 0 but cannot exceed 255 bytes. The length of a key segment must agree with its key type if the key type implies a length (for example, an integer key must have a length evenly divisible by two). Each key page in the file must be large enough to hold at least eight keys. If the page size is too small to accommodate eight occurrences of the specified key length (plus overhead), either increase the file's page size, or decrease the key length.
30: The file specified is not a MicroKernel file.
Either the MicroKernel did not create the file, or a pre-v3.x MicroKernel created it. You can also receive this status code from earlier versions of Btrieve when you open a file created by a later version, if the file has a format incompatible with the earlier version. This status code can also indicate that the first page of the file is damaged. Use a backup copy of your data file. If you receive this status code and you suspect that the header page of the source file is damaged, recover the file as described in the User's Guide.
31: The file is already extended.
This status code is obsolete in MicroKernel versions 6.0 and later.
The MicroKernel returns this status code if an application tries to extend a file that has already been extended; you can only extend a file once.
32: The file cannot be extended.
The MicroKernel returns this status code when it must create an extension file to accommodate a file which is growing larger than the operating system's file size limit, but the
MicroKernel encounters an error from the operating system when it tries to create and open the new extension file. Possible causes for receiving this status code include the following: the directory is full, the disk is full, or the MicroKernel has not been granted sufficient rights by the operating system.
33: The MicroKernel cannot unload.
In the DOS environment, the MicroKernel returns this status code for one of the following two reasons:
You attempted to unload the MicroKernel when you have loaded another terminate and stay resident (TSR) program after you loaded the MicroKernel. Unload the other TSR before unloading the MicroKernel.
You attempted to unload the MicroKernel from a 32-bit application that uses the BSTUB interface with the DOS/4G extender.
34: The specified extension name is invalid.
This status code is obsolete in MicroKernel versions 6.0 and later.
The MicroKernel returns this status code if an application specified an invalid filename for the extended partition. Check the validity of the filename.
35: The application encountered a directory error.
Either a Get Directory operation specified a drive that does not exist, or a Set Directory operation specified an invalid pathname. Check the validity of both the drive and the pathname.
36: The application encountered a transaction error.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 378 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
Version 7.0 and later MicroKernels return this status code if Scalable SQL defines too many transaction nesting levels. The v7.0 MicroKernel allows each transaction a total of 255 internal nesting levels. However, Scalable SQL v4.0 uses some of these levels internally to enforce atomicity on INSERT, UPDATE, and DELETE statements. Therefore, a session can effectively define no more than 253 savepoints to be active at one time. This limit may be further reduced by triggers that contain additional INSERT, UPDATE, and DELETE statements. If your operation reaches this limit, you must reduce the number of savepoints or the number of atomic statements contained within it.
Version 6.x MicroKernels return this status code if the MicroKernel tried to perform a Begin
Transaction operation, but it was not configured to allow transactions. Use the Setup utility to specify a higher value for the Number of Transactions configuration setting. Next, stop and then restart the MicroKernel so that your changes take effect.
On a workstation that is running both a workstation MicroKernel and a Btrieve Requester accessing a client/server MicroKernel, ensure that both the workstation MicroKernel and the client/server MicroKernel are configured for transactions.
In a client/server environment, all servers running MicroKernels to which the workstation is attached must be configured for transactions, even if the files involved in the transaction are only located on one of the servers.
37: Another transaction is active.
The application issued a Begin Transaction (19 or 1019) operation while another transaction was active by the same user or task; the active transaction can be nested or non-nested.
38: The MicroKernel encountered a transaction control file I/O error.
This status code is obsolete in MicroKernel versions 7.0 and later.
The MicroKernel returns this status code if an error occurs when the MicroKernel tries to write to the transaction control file. Possible causes for receiving this status code are that the disk is full, the disk is write protected, the transaction control file (BTRIEVE.TRN) that is created when you load the MicroKernel has been deleted, or the transaction control file is flagged read-only or is corrupt.
39: A Begin Transaction operation must precede an End/Abort Transaction operation.
The application issued an End Transaction (20), End Nested Transaction (2020), Abort
Transaction (21), or Abort Nested Transaction (2021) operation without a corresponding
Begin Transaction (19 or 1019) or Begin Nested Transaction (2019 or 3019) operation. Make sure that each End or Abort Transaction operation in your program is executed only after a successful Begin Transaction operation.
40: The file access request exceeds the maximum number of files allowed.
This status code is obsolete in MicroKernel versions 6.0 and later.
The application tried to access more than the maximum number of files allowed within a transaction. You set the maximum number of different files that you can access during a logical transaction when you configure the MicroKernel.
41: The MicroKernel does not allow the attempted operation.
The MicroKernel returns this status code for one of the following reasons:
The application tried to perform an operation that is not allowed at this time. The
MicroKernel does not allow some operations under certain operating conditions. For
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 379 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s example, the MicroKernel returns this status code if the application attempts to perform a
Step operation on a key-only file.
If using a server engine, the key number parameter of a continuous operation
MicroKernel call is not valid.
Also, the MicroKernel prohibits certain operations during transactions because they have too great an effect on the file or on performance. These operations include Set Owner, Clear
Owner, Create Index, Drop Index, and Close (for files updated during the transaction).
42: A file previously opened in Accelerated mode was not closed.
This status code is obsolete in MicroKernel versions 6.0 and later.
The MicroKernel returns this status code for one of the following reasons:
Either the application tried to open a v5.x data file that was previously accessed in
Accelerated mode by a v5.x MicroKernel and never successfully closed, or the application tried to open a file for which a v6.0 or later MicroKernel encountered an unrecoverable error during a Set or Clear Owner operation. The file's integrity cannot be ensured. Refer to the User's Guide for information about recovering damaged files.
Your application tried to open a file in MicroKernel v5.x format using a v5.x MicroKernel; however, that same file was previously accessed by a v6.0 or later MicroKernel, which failed to close the file successfully and left a pre-image file on the disk. Version 5.x
MicroKernels cannot read pre-image files created in v6.0 or later format.
43: The specified record address is invalid.
The MicroKernel returns this status code for one of the following reasons:
The record address specified for a Get Direct operation is invalid. Either the address is outside the file's boundaries, or it is not on a record boundary within or on a data page, or the record at the specified address has been deleted. For a Get Direct operation, specify the 4-byte address obtained by a Get Position operation.
If the records' file is in v5.x format, this status code can indicate a file access conflict. For example, task 1 has a file locked in an exclusive transaction. Task 2 is reading records from the same file and tries to update a record that the transaction inserted. If task 2 reads the record and then task 1 aborts the transaction, task 2 receives this status code when issuing the Update operation.
For a Find Percentage operation that is seeking a percentage based on a record's physical location within the file, the specified record address is invalid.
The file may be corrupt, and you must recover it. Refer to the User's Guide for information about recovering damaged files.
44: The specified key path is invalid.
The application tried to use the Get Direct/Record operation to establish positioning on an index path for a key whose value is null in the corresponding record. The MicroKernel cannot establish positioning based on a null key value. Pre-v6.x MicroKernels return Status Code 82 in this situation; therefore, write your application to check for both of these status codes.
45: The specified key flags are invalid.
The key flags specification on a Create operation is inconsistent. If a key has multiple segments, the duplicate, modifiable, and null attributes should be the same for each segment in the key. Also, you cannot use the null or manual key attributes in a key-only file. The
MicroKernel also returns this status code if the application attempted to specify a different
ACS for two or more segments of a segmented key.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 380 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e
46: Access to the requested file is denied.
A p p e n d i x B : E r r o r M e s s a g e s
The MicroKernel returns this status code for one of the following reasons:
The application opened a file in Read-only mode and tried to perform a write operation on that file.
The application attempted to perform a write operation on a file that is flagged read-only by the operating system.
When the application opened the file, it did not correctly specify the owner name required for updates.
(Workstation Only) If a user or task opens a file that another user has opened using a server MicroKernel, the MicroKernel returns this status code if the workstation user attempts to write to the file.
47: The number of files opened exceeds the maximum allowed.
This status code is obsolete in MicroKernel versions 6.0 and later.
Pre-v6.0 workstation MicroKernels return this status code when the number of files opened in
Accelerated mode exceeded the number of buffers available in the MicroKernel's cache.
When a file is opened in Accelerated mode, the MicroKernel reserves one of its cache buffers for the file. It always reserves five empty buffers for index manipulation. Reconfigure Btrieve with both a smaller /P configuration option (to allocate more buffers) and a larger /M option.
48: The alternate collating sequence definition is invalid.
The MicroKernel returns this status code for one of the following reasons:
The first byte of an ACS definition (the identification byte) does not contain the hexadecimal value AC (for user-defined ACSs) or AD (for locale-specific ACSs). Make sure that the first byte contains the appropriate value.
You are running a pre-v6.0 MicroKernel, and you attempted to add an index with a localespecific ACS to a file in v5.x format. Pre-v6.0 files do not support locale-specific ACSs.
You are running the v6.0 or later MicroKernel with the Create File Version option set to v5.x, and you attempted to create a file that contains a key with a locale-specific ACS.
Pre-v6.0 files do not support locale-specific ACSs.
49: The extended key type is invalid.
The MicroKernel returns this status code for one of the following reasons:
You tried to create a file or an index with an invalid extended key type, or you are trying to assign an ACS to a BINARY key or key segment. You can assign an ACS only to a
STRING, LSTRING, or ZSTRING key type.
You defined an index requiring an ACS, but no ACS definition exists (either in the file or in the key definition passed in the data buffer).
You attempted to create a key segment with both the Case Insensitivity and the Alternate
Collating Sequence flags set, and the MicroKernel is configured to create files in v5.x format. This combination is invalid for v5.x files.
You attempted to create a file that contains multiple ACSs, but you are running a pre-v6.1
MicroKernel. Only v6.1 and later MicroKernels support multiple ACSs.
You are running the v6.x or later MicroKernel with the Create File Version option set to v5.x, and you attempted to create a file with a NUMERICSA or NUMERICSTS key. Prev6.0 files do not support these key types.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 381 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
You set the default file creation format to v6.x, but you are using one of the new Scalable
SQL v4.0 data types, such as CURRENCY.
50: The file owner is already set.
The application tried to perform a Set Owner operation on a file that already has an owner.
Use the Clear Owner operation to remove the previous owner before specifying a new one.
51: The owner name is invalid.
The MicroKernel returns this status code for one of the following reasons:
If the application received this status code from a Set Owner operation, the owner names specified in the key buffer and data buffer do not match.
If this status code occurred during an Open operation or a DROP TABLE statement, the application attempted to open a file that has an owner name assigned to it. The application must specify the correct owner name in the data buffer. Ensure that the owner name is null-terminated in the data buffer and that the data buffer length is set long enough to include the owner name plus the null terminator.
If an application received this status code when removing a file from continuous operation mode, then the client ID of the calling application differs from the client ID of the application that originally put the file into continuous operation mode. (Version 7.0 and later MicroKernels return Status Code 88 in this instance.)
52: An error occurred while writing to the cache.
This status code is obsolete in MicroKernel versions 6.0 and later.
While trying to make a cache buffer available, the MicroKernel attempted to write data to a disk from a file that was previously opened in Accelerated mode. The operating system returned an I/O error during the write. This generally indicates a hardware memory problem.
Unload and reload Btrieve before you continue.
53: The language interface version is invalid.
An application tried to access a file containing variable-length records with a language interface from Btrieve v3.15 or earlier. To access files with variable-length records, you must use a v4.x or later interface. The MicroKernel can also return this status code when an application calls BTRVID using a pre-v6.0 MicroKernel with the DOS interface. Pre-v6.0
MicroKernels do not support BTRVID.
54: The variable-length portion of the record is corrupt.
During a Get or Step operation, the MicroKernel could not read all or part of the variablelength portion of a record. The MicroKernel returns as much data as possible to the application. This status code usually indicates that one or more pages used to store variablelength records are corrupt. Check the data buffer length the MicroKernel returns to see how much of the record was returned. Recover the damaged file as described in the User's Guide.
55: The application specified an invalid attribute for an AUTOINCREMENT key.
The application tried to specify either the segmented or duplicate attribute for an
AUTOINCREMENT key type. An AUTOINCREMENT key can be part of a segmented key only if the key number of the AUTOINCREMENT key is less than the key number of the segmented key. An AUTOINCREMENT key cannot allow duplicates.
56: An index is incomplete.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 382 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
An index can be damaged if a Create Index operation (31) or a Drop Index operation (32) is interrupted before it runs to completion. Perform a Drop Index operation to completely remove the damaged index from the file, then rebuild the index with the Create Index operation, if desired.
57: An expanded memory error occurred.
This status code is obsolete in MicroKernel versions 6.0 and later.
Btrieve for DOS returns this status code if it receives an error from the Expanded Memory
Manager. This status code usually means that the MicroKernel was unable to save or restore the memory mapping register context, indicating an incompatibility with another application that uses expanded memory.
58: The compression buffer length is too short.
The application tried to read or write a record that is longer than the value specified for the size of the compression buffer. Reconfigure the MicroKernel using the Setup utility, specifying a higher value for the Largest Compressed Record Size option.
59: The specified file already exists.
This status code is returned for the Create operation if the application specified -1 in the key number parameter and the name of an existing file in the key buffer parameter. To overwrite the existing file, remove the -1 from the key number parameter. To preserve the existing file, alter the filename specified in the key buffer parameter.
60: The specified reject count has been reached.
The MicroKernel rejected the number of records specified by the reject count before a Get
Next Extended, Get Previous Extended, Step Next Extended, or Step Previous Extended operation found the requested number of records that satisfy the filtering condition. Check the first two bytes returned in the data buffer for the number of records that were retrieved.
61: The work space is too small.
The Get Next Extended, Get Previous Extended, Step Next Extended, and Step Previous
Extended operations use a buffer as work space. This status code indicates that the work space (set by default to 16 KB) is not large enough to hold the filtering data buffer structure and the largest record to be received. When using v6.15.2 and later MicroKernels, you receive Status Code 0 if the work space is large enough to hold the filter/extraction expression and enough of the record to include all of the fields to be filtered or extracted.
62: The descriptor is incorrect.
The descriptor (data buffer structure), which is passed for a Get Next Extended, Get Previous
Extended, Step Next Extended, or Step Previous Extended operation, is incorrect. The descriptor length (the first two bytes of the data buffer) on the extended operation call must be the exact length of the descriptor. This requirement does not apply to the data buffer length option, which can still be declared longer than necessary.
On a Stat Extended operation, the signature field in the data buffer is not set to 0x74537845, the subfunction field is not set to 0x00000001, or the namespace field is not set to
0x00000000.
On a Get Direct/Chunk or Update Chunk operation, the descriptor structure in the data buffer is incorrect, or it is inconsistent (either internally or with respect to the data buffer length).
63: The data buffer parameter specified on an Insert Extended operation is invalid.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 383 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
An Insert Extended operation provided an invalid buffer. Either the buffer length is less than 5 bytes, or the number of records specified is 0. Correct the buffer length or the number of records.
64: The filter limit has been reached.
During a Get Next Extended, Get Previous Extended, Step Next Extended, or Step Previous
Extended operation, a rejected record was reached; no other record can satisfy the given filtering condition, going in the direction that the operation specified. This is applicable only if the first segment of the key that the key number specified is also used as the first term of the filtering field.
65: The field offset is incorrect.
The field offset in the extractor of a Get Next Extended, Get Previous Extended, Step Next
Extended, or Step Previous Extended operation is invalid based on the length of the retrieved record. Make sure that the field offset is a valid value (from 0 through the record length minus
1).
66: The maximum number of open databases has been exceeded.
The MicroKernel tried to open files bound to too many Scalable SQL databases. Use the
Setup utility to configure a higher value for the Maximum Databases option. Refer to the
Scalable SQL Database Design Guide for more information about bound files.
67: The MicroKernel cannot open the SQL data dictionary files.
The MicroKernel returns this status code for one of the following reasons:
An application attempted to use a data file that is bound to a Scalable SQL database, but the MicroKernel could not open one of the Scalable SQL data dictionary files (FILE.DDF or, if the file has RI definitions, RELATE.DDF) or the configuration file (DBNAMES.CFG).
You attempted to create a file with the Replace option, and a bound Scalable SQL data file with the same name and location already exists. However, the MicroKernel could not open the Scalable SQL data dictionary file FILE.DDF, or the configuration file
(DBNAMES.CFG).
If the data file has RI definitions, the DBNAMES.CFG file must be in the location you specified using the Setup utility; you determine the location of DBNAMES.CFG by using the
Database Names Directory option for the MicroKernel. Also, ensure that FILE.DDF and
RELATE.DDF (if the file has RI definitions) are in the locations specified by the database's configuration.
Refer to the Scalable SQL Database Design Guide for more information about RI.
68: The MicroKernel cannot perform the RI Delete Cascade operation.
The MicroKernel cannot enforce the Delete Cascade rule on a file under RI control because the record that the application attempted to delete has more than 16 levels of descendants.
Delete records from the lower levels, and then try again to delete the record that the application was attempting to delete initially. Refer to the Scalable SQL Database Design
Guide for more information about RI.
69: The Delete operation specified a file that is damaged.
The application encountered an error while the MicroKernel was attempting to enforce the
Delete Cascade rule in response to a Delete operation. This status code indicates that the related file has been damaged and must be recreated. Refer to the User's Guide for more information about recovering damaged files.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 384 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
Refer to the Scalable SQL Database Design Guide for more information about RI and the
Delete Cascade rule.
71: There is a violation of the RI definitions.
If you have attempted an Insert operation on a file under RI control, you can receive this status code if a foreign key value in the record to be inserted does not have a corresponding primary key in the referenced file. If you are performing an Update operation, there are two possible causes for this status code:
You attempted to change the value of a primary key.
You attempted to change the value of a foreign key to a value that does not exist for the defined primary key.
If you attempted a Delete operation, the restrict rule is enforced, and a primary key value in the record you are trying to delete references a foreign key in the referenced file. Refer to the
Scalable SQL Database Design Guide for more information about RI.
72: The MicroKernel cannot open the RI referenced file.
The referenced file cannot be found at the location specified by FILE.DDF and
DBNAMES.CFG.
Be sure that the referenced file is in one of the data file locations that the DBNAMES.CFG file specifies for the named database.
If the DBNAMES.CFG file is defined on a server, verify that the file location does not contain a drive letter.
If the DBNAMES.CFG file is defined for a workstation engine, make sure that the drive letters are the same (and map to the same locations) as specified in DBNAMES.CFG.
Refer to the Scalable SQL Database Design Guide for more information about RI.
73: The RI definition is out of sync.
The MicroKernel returns this status code for one of the following reasons:
You tried to open a data file that is bound to a Scalable SQL database, and the database to which the file is bound was not found in the DBNAMES.CFG file.
You tried to open a data file with RI definitions that is bound to a Scalable SQL database, and the table to which the file is bound was not found in the database's FILE.DDF file, or the table's location and filename does not match the file's location and filename as configured in the DBNAMES.CFG or FILE.DDF file.
You attempted to modify a bound file, and the RI definition for that file disagrees with the definition in the RELATE.DDF file.
You can also receive this status code on an Insert or Delete operation, or on an Update operation that would change a foreign key, if the file related to this file is out of sync (an attempt to open or modify the related file would have returned this same status code).
You attempted to create a file with the Replace option, and a bound Scalable SQL data file with the same name and location already exists. However, the MicroKernel detected that the existing bound file was out of sync (that is, an attempt to open the existing file would have returned this same status code).
Check the RI constraints on your database. For information about how to do this, refer to the
Scalable SQL User's Guide.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 385 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e
74: The MicroKernel aborted the transaction.
A p p e n d i x B : E r r o r M e s s a g e s
This status code is obsolete in MicroKernel versions 6.0 and later.
This is an informative status code. A NetWare-based MicroKernel replaced an End
Transaction operation with an Abort Transaction operation after detecting an error for a
Transaction Tracking System (TTS) file inside the transaction. The MicroKernel then executed the Abort Transaction operation.
75: The server routing list is too small.
If you use SET BRQPARMS=/S:1 with the Btrieve for OS/2 Requester, this status code occurs after you try to open a file or get the version number of Btrieve for NetWare. Set the /S value to 2 or higher. Do not set /S so that it defaults to 1.
76: There is a conflict on the referenced file.
An application attempted to perform an Update, Insert, or Delete operation on an RIcontrolled file that references another file. The application cannot open the referenced file for
RI checking because it is already open in Exclusive mode. Wait until the referenced file is closed or is opened in a mode other than Exclusive, and then retry the operation. Refer to the
Scalable SQL Database Design Guide for more information about RI.
77: The application encountered a wait error.
This status code is obsolete in MicroKernel versions 7.0 and later.
This is an informative status code. You must retry the operation yourself; the MicroKernel does not automatically retry the operation. A client/server MicroKernel returns this status code in one of the following situations:
The application specified a wait lock bias for an operation, but another user has locked the requested resource.
The application is currently processing a wait transaction and tried to access a file that another user has locked.
When you are using the Btrieve Requester to access the MicroKernel, the Requester waits and retries if a requested resource is locked. When a server-based application is accessing the MicroKernel and the requested resource is locked, a wait is also required. In this case, the MicroKernel is expected to perform the wait. Because this would occupy the MicroKernel and lock out other users who might be trying to release the requested resource, the
MicroKernel does not perform the wait. Instead, it returns this status code, and the serverbased application must retry later.
78: The MicroKernel detected a deadlock condition.
The application should clear all resources (for example, by aborting or ending the transaction or releasing all record locks) before proceeding. This breaks the deadlock, allowing other applications to access the resources for which they are waiting.
79: A programming error occurred.
This status code is obsolete in MicroKernel versions 7.0 and later.
Although very rare, it is possible to receive this status code when there is a malfunction that the MicroKernel cannot specifically detect or from which the MicroKernel cannot recover.
Retry the operation. If the error persists, there may be system corruption; try to clear the system by rebooting, and then try the operation again.
80: The MicroKernel encountered a record-level conflict.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 386 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
The MicroKernel did not perform the Update or Delete operation because of a record-level conflict. For example, station A reads a record, station B reads the same record and updates it, and then station A attempts to update the record. The application should reread the record prior to resending an Update or Delete operation. Alternatively, the application can employ record locks to avoid conflicts.
In key-only files, you receive this status code if the record is moved in the file's b-tree after being read and before being updated or deleted. A record can move as a result of other records being inserted, updated, or deleted.
In pre-v6.0 workstation MicroKernels, a page-level conflict also produces this status code.
For example, station A reads a record, station B reads and updates a different record on the same data page, and then station A attempts to update the record it read. (You also receive this status code with v6.0 and later MicroKernels if the files are in v5.x format.)
In pre-v6.0 workstation MicroKernels, a conflict can also occur if station A reads a record, station B reads a different record and updates it, causing duplicate pointers to be updated on record A, and then station A tries to update the record.
81: The MicroKernel encountered a lock error.
The MicroKernel returns this status code in one of the following situations:
The application tried to unlock a record that is locked with a multiple record lock, but the record position stored in the data buffer does not correspond to any record locked in the associated file.
The application tried to unlock a single-record lock with a multiple-record lock or viceversa.
(Workstation Only) You tried to open a v6.0 or later file in Read-only mode on a NetWare drive on which you only have Read and Filescan rights. The MicroKernel cannot create the .LCK file. You must obtain Create and Write rights or redirect the .LCK files to a directory on which you have Create and Write rights.
(Workstation Only) You tried to open a file in MEFS mode on a local drive, and the DOS
SHARE.EXE program is not loaded. Either load SHARE.EXE or open the file in SEFS mode.
(Workstation Only) You manipulated a file (you opened and then locked all or part of the file) in MEFS mode on a local drive, and the DOS SHARE.EXE program ran out of locks.
Reload the SHARE program and specify a higher value for the /L and /F options.
(Workstation Only) You redirected the lock file to a local drive with the /I option, and the
DOS SHARE.EXE program is not loaded.
(Workstation Only) You are running in MEFS mode, and you ran out of operating system file handles when the MicroKernel attempted to allocate a file handle to the .LCK file.
Refer to your operating system documentation for instructions about configuring your operating system to allow more file handles.
In pre-v7.x MicroKernels, the lock table is full. Decrease the number of locks that the application uses, or use the Setup utility to specify a higher value for the Number of
Locks option.
82: The MicroKernel lost positioning.
When performing a Get Next or Get Previous operation on a key with duplicates, the application tried to retrieve a record that was deleted or whose key value was modified by
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 387 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s another application. Use a Get Equal or a Get Direct/Record operation to re-establish positioning. (See Status Code 44 on page 46 for a related positioning problem.)
83: The MicroKernel attempted to update or delete a record that was read outside the transaction.
This status code is obsolete in MicroKernel versions 7.0 and later.
The MicroKernel returns this status code if the application tried to update or delete a record within a transaction, but it did not read the record within the transaction. The application must read the record within the transaction before attempting to modify the data.
84: The record or page is locked.
The application tried to apply a no-wait lock on a record that is currently locked by another application, or the application tried to access a file in a no-wait transaction while another application holds one or more active record locks in that file. This status code can also occur if the application tried to update or delete a record locked by another application.
The application can use either of the following recovery methods:
Retry the operation until it is successful. This can be the simplest and quickest solution for a network with light to moderate use.
Use the wait option (+100/+300) instead of the no-wait option (in versions that support the wait option).
The MicroKernel can return this status code on an Insert, Update, or Delete operation when it attempts to lock an index page to insert or delete a key value. Have your application check for this status code and retry the operation if the status code is returned.
85: The file is locked.
The MicroKernel returns this status code in one of the following situations:
The workstation MicroKernel has a file open, and another workstation that has the
Requester loaded tries to open the same file via the server MicroKernel. The server
MicroKernel cannot open the file because it cannot obtain exclusive access. The workstation that has the Requester loaded receives this status code.
In a workstation engine environment, the MicroKernel can return this status code on an
Open, Insert, Update, or Delete operation for a file under heavy usage by multiple users or tasks. The MicroKernel must momentarily have exclusive access to the file during these operations, and it retries the operation several times before returning this status code. In this case, the application can reissue the operation. In addition, you can reconfigure the workstation MicroKernel with a lower Operation Bundle Limit and Initiation
Time Limit to reduce the amount of time the MicroKernel keeps a lock on the file.
In a workstation environment, a v6.15 or later MicroKernel has a pending modification
(insert, update, or delete) as an incomplete system transaction in a file that has been opened in MEFS mode. If multiple users or tasks attempt to access (Get/Step) or modify
(insert, update, or delete) the shared file, the MicroKernel returns this status code. An access operation can receive this status code only if the writing phase of the system transaction has started.
• Reconfiguring the MicroKernel with a lower Operation Bundle Limit and Initiation
Time Limit reduces the occurrences of file contention that produce this status code.
Refer to the User's Guide for more information about how to do this.
• If you are a developer and want more information about system transactions, refer to the Programmer's Guide.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 388 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
While one user has a file locked in an exclusive transaction, another user attempts to lock all or part of that file.
When opened by a server MicroKernel, a file is in transition into continuous operation mode. Retrying eventually works.
When opened by a server MicroKernel, two data files have the same filename but different extensions (for example, INVOICE.HDR and INVOICE.DET). One file is open and in continuous operation mode, causing the MicroKernel to generate a delta file (for example, INVOICE.^^^). The MicroKernel returns this status code when you attempt to open the second file.
86: The file table is full.
Using the Setup utility, specify a higher value for the Open Files configuration option.
87: The handle table is full.
Either you have attempted to open more handles than the MicroKernel is configured to support, or the MicroKernel attempted to open more files than the operating system allows.
To configure the MicroKernel to allow more handles, use the Setup utility and increase the value of the Handles option.
To configure your operating system to allow more handles, refer to your operating system documentation. It is helpful to know the following details regarding the MicroKernel's requirements for handles from the operating system. When the same file is opened multiple times, the MicroKernel uses only one operating system handle. However, if the file is in v6.x or later format and the file is shared via MEFS mode, the MicroKernel opens a second handle for the associated .LCK file.
If the file is in v5.x format, the MicroKernel might request a second handle, for the .PRE file.
Also, if the file (in any format) is placed in continuous operation mode, the MicroKernel requests another handle for the delta file. If the file is extended, the MicroKernel requests n operating system handle for each of the extension files.
88: The application encountered an incompatible mode error.
The MicroKernel returns this status code in one of the following situations:
If an application opens a file in Exclusive mode, all other applications receive this status code when they try to open the same file in any mode.
If an application opens a file in any mode other than Exclusive, all other applications receive this status code when they try to open the same file in Exclusive mode.
(Workstation Only) If a user or task opens a file in MEFS mode, all other users or tasks using the same MicroKernel receive this status code when they try to open the same file in SEFS mode.
(Workstation Only) Similarly, if a user or task opens a file in SEFS mode, all other users or tasks using the same MicroKernel receive this status code when they try to open the same file in MEFS mode.
(Workstation Only) If a user or task opens a file in Accelerated mode and MEFS is enabled, all other remote users or tasks receive this status code when they try to open the same file in any mode. All other local users or tasks receive this status code when they try to open the same file in any mode other than Accelerated.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 389 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
If another workstation has the Requester loaded and has the file open, applications running v6.15 or later MicroKernels receive this status code when they try to open the same file in SEFS mode.
Using the MicroKernel's continuous operation mode, this status code can also indicate one of the following situations:
You attempted to remove a file from continuous operation, but the file is not in continuous operation mode.
You attempted to remove a file from continuous operation, but a different client placed the file into continuous operation.
You attempted to include two files in continuous operation that have the same name but different extensions.
You attempted to include a file in continuous operation, but the file is already in continuous operation.
89: A name error occurred.
This status code is obsolete in MicroKernel versions 5.0 and later.
BSERVER was loaded before you specified the short name to which the device was redirected. You must specify all short names that you want to share with the NET SHARE command before you start BSERVER.
90: The redirected device table is full.
This status code is obsolete in MicroKernel versions 6.0 and later.
The DOS Requester's redirection table or server routing table is full. This occurs if you attach to additional servers or map additional drives after loading the Requester. Reload the
Requester, specifying a larger value for either the Number of File Servers (/S) option or the
Number of Mapped Drives (/R) option. This status code also occurs if you detach from a server and attach to a different server. Once a workstation has attached to a server, the
Requester does not remove its name from the server routing table.
91: The application encountered a server error.
The MicroKernel returns this status code in one of the following situations:
The Requester cannot establish a session with the server. Either the client/server
MicroKernel is not loaded or the server is not active.
The SPX drivers are not installed or are outdated.
The value for the Number of Sessions configuration option is too low. Use the Setup utility to specify a higher value for this option.
An application specified a path for a file and did not include the volume name in the path.
The Btrieve Message Router has not been loaded, and the following situation has occurred: an application that uses both the Btrieve Message Router and the MicroKernel to make remote calls (and which therefore includes the server and volume name when performing an Open operation) has attempted to open a remote file. Because the Btrieve
Message Router does not interpret the server name, the MicroKernel attempts to do so but cannot.
A communication or network addressing problem exists in your network environment, so the MicroKernel requests never reach their destination server address. Ensure that your
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 390 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s workstation and server network components are up to date and certified for your network environment.
92: The transaction table is full.
This status code is obsolete in MicroKernel versions 7.0 and later.
The MicroKernel returns this status code if the application exceeded the maximum number of active transactions. Use the Setup utility to specify a higher value for the Number of
Transactions configuration option.
93: The record lock types are incompatible.
The application tried to mix single-record locks (+100/+200) and multiple-record locks
(+300/+400) in the same file at the same time. You must release all locks of one type before you can execute a lock of the other type.
94: The application encountered a permission error.
The MicroKernel returns this status code in one of the following situations:
The application tried to open or create a file in a directory without the proper privileges.
The MicroKernel does not override the network privileges assigned to users.
The designated server is in the server routing table, but your particular workstation is not logged into that server.
Both the server-based and workstation MicroKernels (pre-v6.15) are trying to access the same file at the same time.
A NetWare application tried to access a file using NetWare Runtime support with the given username. Specifically, one of the following situations exists regarding the supplied username:
The user is not a valid user on the NetWare Runtime server.
The user does not have the appropriate rights to access the file.
The username is ADMIN or SUPERVISOR. For security reasons, the MicroKernel does not enable you to use ADMIN or SUPERVISOR as a username when enabling NetWare
Runtime support.
When using the 32-bit requesters from a Windows NT or Windows 95 workstation to a
NetWare server, you must use the same username for logging in to both the workstation and the NetWare server. You cannot be logged in to NetWare as SUPERVISOR or
ADMINISTRATOR.
95: The session is no longer valid.
The server MicroKernel returns this status code for one of the following reasons:
The previously established session is no longer active due to an error at the workstation, at the server, or on the network. Verify that the workstation is still attached to the server, and then unload and reload the Btrieve Requester.
The server MicroKernel has reached the maximum number of SPX sessions. Use the
Monitor utility to check this statistic. Use the Setup utility to specify a higher value for the
Number of Sessions configuration option.
This status code could indicate a time delay problem if the workstation does not receive a response back from the server in an appropriate timeframe or after an appropriate
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 391 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s number of retries. Refer to your network configuration documentation for information about increasing timeout and retry parameters. This is often necessary in a WAN environment or a LAN configuration with heavy network traffic.
• If you continue to receive this status code after increasing the network timeout parameters, this status code usually indicates a problem with network communications.
• Verify that you have up to date network cards and drivers; for example, incompatible
LAN card drivers can also cause this status code to occur. Consult your LAN administrator for network communication troubleshooting.
96: A communications environment error occurred.
The MicroKernel returns this status code for one of the following reasons:
The user count limit has been exceeded. Either close a session or upgrade your user count. For more information about purchasing and installing additive user counts, refer to the User's Guide.
You tried to attach to the MicroKernel on a server, but the SPX connection table or the
MicroKernel's client table is full. Use the Setup utility to specify a higher value for the
Number of Remote Sessions configuration option.
An application that calls the MicroKernel can return this status code for the following reasons:
• Not all of the clients have been properly reset.
• You loaded the MicroKernel with a value that is too small for its Active Clients setting.
Use the Setup utility to increase the Active Clients configuration option.
You are using a limited user count version of the MicroKernel, and it has reached the maximum number of users.
The DBNAMES.CFG file contains a named database definition specifying a data location on a different server.
In the Windows environment, the v6.15 and later MicroKernel returns this status code if you try to run a Btrieve-based application, but the client table is full. Use the Setup utility to specify a higher value for the Active Clients configuration option.
97: The data buffer is too small.
The application either tried to read or write a record that is longer than the current allowed settings for the MicroKernel or the Btrieve Requester, as follows:
For an Update, Insert, or Create operation, the application receives this status code if the data buffer length it specifies for the record exceeds the message buffer length.
For a Get, Step, or Stat operation, the application receives this status code if the message buffer is shorter than the length of the data the MicroKernel would return, regardless of the data buffer length specified in the application.
For a Get Chunk or Update Chunk operation, the total size of the retrieved or updated chunk exceeds the message buffer length.
For information about configuring the message buffer size, refer to the User's Guide. To avoid receiving this status code, perform one or both of the following steps:
Increase the size of the message buffer by using the Setup utility to specify a higher value for the Communications Buffer Size option.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 392 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
Reload the Btrieve Requester and specify a higher value for the message buffer size.
98: The MicroKernel detected an internal transaction error.
This status code is obsolete in MicroKernel versions 6.0 and later.
A NetWare-based MicroKernel detected an error while executing the operation on a NetWare
Transaction Tracking System (TTS) file. The application can perform only an Abort
Transaction operation at this point.
99: The Btrieve Requester is unable to access the NetWare Runtime server.
The Btrieve Requester returns this status code when you enable NetWare Runtime server support and the Requester either detects no existing connection or cannot find a valid login username. SUPERVISOR and ADMIN are not valid usernames, even if supplied with the correct password. If the Requester cannot find a login username other than SUPERVISOR or
ADMIN, there is no valid name to pass.
100: No cache buffers are available.
This status code, returned by v6.0 and later MicroKernels, indicates that the MicroKernel has used all the cache buffers it allocated at load time. Use the Setup utility to increase the value for the Cache Allocation configuration option.
101: Insufficient operating system memory is available.
This status code, returned by v6.0 and later client/server MicroKernels, indicates that there is not enough operating system memory available to perform the requested operation. To fix this problem, perform one or more of the following:
Use the Setup utility to decrease the value for the Cache Allocation configuration option.
Add memory to the server.
For more information about the configuration options, see Status Code 1002, a similar status code that the Windows-based MicroKernel returns in the same situation.
102: Insufficient stack space is available.
This status code, returned as a run-time error by v6.0 and later MicroKernels, indicates that the MicroKernel has run out of stack space. To increase the amount of stack space available to your application, relink the application, setting the stack size to a higher value. The
MicroKernel returns this status code only to Windows-based applications that call
WBTRCALL.DLL, or applications that call the Btrieve API on the local server.
103: The chunk offset is too big.
The MicroKernel returns this status code in one of the following situations:
An Get Direct/Chunk operation specified an offset beyond the end of the record, either explicitly or using the next-in-record bias to the subfunction value. Unless the MicroKernel returns this status code while processing the first chunk, the operation was partially successful. Check the data buffer length parameter immediately after the call to see how much data was retrieved (and therefore how many chunks).
An Update Chunk operation specified an offset that is more than one byte beyond the end of the record. This status code indicates that the MicroKernel has made no changes to the record.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 393 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
An Update Chunk operation with an Append subfunction causes a record length to exceed its operating system file size limit. The MicroKernel has made no changes to the record.
104: The MicroKernel does not recognize the locale.
In v6.0 or later MicroKernels, the Create or Create Index operation returns this status code to indicate that the operating system was not able to return a collation table for the country ID and code page specified. Ensure that the application specified the locale's country ID and code page correctly and that the operating system is configured to support the country ID and code page.
105: The file cannot be created with Variable-tail Allocation Tables (VATs).
Version 6.0 and later MicroKernels return this status code when an application tries to create a file with Variable-tail Allocation Tables (VATs) but without variable-length records (a precondition for files to use VATs). This status code applies to key-only files as well as to regular data files.
106: The MicroKernel cannot perform a Get Next Chunk operation.
Version 6.0 and later MicroKernels return this status code when an application calls the Get
Direct/Chunk operation to retrieve a chunk from a record and uses the next-in-record bias on the descriptor subfunction, but after the application establishes its positioning in the record
(and prior to this call), the target record is deleted.
107: The application attempted to perform a chunk operation on a pre-v6.0 file.
Version 6.0 and later MicroKernels return this status code when an application tries to use either a Get Direct/Chunk operation or an Update Chunk operation on a file in pre-v6.0 format.
109: An unknown error was encountered either creating or accessing a semaphore.
OS/2 and Windows NT workstation MicroKernels return this status code when trying to perform an operation using incompatible versions of the DLLs. Shut down the MicroKernel and make sure that you are using the most recent versions of the DLLs.
110: The MicroKernel cannot access the archival logging configuration file.
The archival logging configuration file (BLOG.CFG) contains entries for the data files on the drive for which you want to perform archival logging. The MicroKernel returns this status code for the following reasons:
The MicroKernel cannot find the BLOG.CFG file. Ensure that the file is in the \BLOG directory in a real root directory of the physical drive that contains data files you want to log. (That is, do not use a mapped root directory.) If your files are on multiple volumes, you must create a \BLOG directory on each volume.
The MicroKernel cannot open the BLOG.CFG file. Either the file is locked or it does not exist.
The MicroKernel cannot read the BLOG.CFG file. Either the file does not use the correct format or it is corrupt. Refer to the User's Guide for information about the format of the
BLOG.CFG file.
111: The specified filename was not found in the archival logging configuration file.
The MicroKernel cannot find the specified file in the BLOG.CFG file. The file must be specified in the BLOG.CFG file on the same physical drive.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 394 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e
112: The specified file is in use by another client.
A p p e n d i x B : E r r o r M e s s a g e s
Before the MicroKernel can perform a roll forward, the file must be in the same state it was in when it was last backed up. If another client changes the file, you must restore the file again before rolling forward.
113: The MicroKernel cannot find the archival log for the specified file.
The MicroKernel cannot find the archival log file associated with the specified file. By default, the MicroKernel names the archival log file the same as the logged file, but with a .LOG extension. However, you can specify a different filename for the archival log file in the
BLOG.CFG file. Ensure that the BLOG.CFG file indicates the correct filename for the archival log and ensure that the archival log file exists.
114: The archival log for the specified file is invalid.
The archival log associated with the specified file is not a valid archival log file. By default, the
MicroKernel names the archival log file the same as the logged file, but with a .LOG extension. However, you can specify a different filename for the archival log file in the
BLOG.CFG file. Ensure that the BLOG.CFG file indicates the correct filename for the archival log and ensure that the archival log file exists.
115: The MicroKernel cannot access the archival logging dump file.
The MicroKernel cannot access the archival logging dump file for one of the following reasons:
The filename indicated for dumping entries in an archival log is not a valid filename. Be sure this filename does not contain a volume specification. The dump file is created on the same volume as the log file.
The caller does not have access rights to the dump file.
The MicroKernel cannot open the file because another user has opened the file using an exclusive operating system lock.
130: The MicroKernel ran out of system locks.
This status code is obsolete in MicroKernel versions 6.15 and later.
This status code can indicate a temporary condition in which no system locks are currently available. The following are example cases:
A single client is performing a very large transaction, in which thousands of records are being modified.
Many clients are performing large transactions concurrently. A client can receive this status code whether or not it is in a transaction. In some cases, a client can simply retry the failed operation. If other clients have released system locks in the interim, the retried operation may succeed. If a client in a transaction receives this status code, end or abort the transaction. If the transaction is very large, consider breaking it into multiple, smaller transactions. You can also use the Setup utility to lower the number of system locks devoted to explicit locking. To do so, lower the values assigned to the Number of Locks and/or Number of Sessions configuration options.
132: The file has reached its size limit.
The MicroKernel returns this status code in one of the following situations:
An operation attempted to allocate more than 16,777,216 pages to a data file.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 395 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
A data file has remained in continuous operation for a lengthy period of time, causing its delta file to exceed the operating system limit.
A pre-v6.5 data file has reached the operating system file size limit.
133: More than 5 concurrent users attempted to access the same data file.
In the Scalable SQL or Btrieve Developer Kit for a workstation environment, you attempted to access a data file with more than five MicroKernels at the same time. The Scalable SQL
Developer Kit and the Btrieve Developer Kit for workstation environments limit the number of concurrent users of a file to five engines.
134: The MicroKernel cannot read the International Sorting Rule.
The MicroKernel returns this status code for one of the following reasons:
The ISR is not found in the LOCALE.CFG file.
The LOCALE.CFG file is missing or corrupt.
The MicroKernel cannot read the ISR from the LOCALE.CFG file.
136: The MicroKernel cannot find the specified Alternate Collating Sequence in the file.
The MicroKernel returns this status code in the following situations:
You tried to create an index that uses an ACS, but the MicroKernel cannot locate an ACS with the specified name in the file.
You called a Step Next Extended, Get Next Extended, Step Previous Extended, or Get
Previous Extended operation and specified an ACS name, but the MicroKernel cannot locate an ACS with the specified name in the file.
139: The MicroKernel has detected an unacceptable value in the key number.
Certain Btrieve operations either use, or reserve the use of, the key number parameter as a subfunction number, rather than as a means to specify a file's index to be used with the operation (as is done, for example, in the Get Equal operation). This status code is returned if an application does not specify a valid subfunction number (via the key number parameter) to one of these operations. For information about acceptable values for the operation's key number parameter, consult the section in the Btrieve Programmer's Guide that documents the operation that returned this status code.
140: The savepoint ID is invalid.
The application supplied an invalid savepoint ID in a nested transaction operation. Ensure that you specify valid savepoint IDs.
143: The MicroKernel cannot allow unauthorized access to files in a secure Scalable SQL database.
You attempted to open a data file bound to a Scalable SQL database that has security enabled.
The MicroKernel does not allow access to such files, except through Scalable SQL.
The MicroKernel also returns this status code if you are not using Scalable SQL and all of the following are true:
You attempt to create a file with the Replace option.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 396 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x B : E r r o r M e s s a g e s
A bound Scalable SQL data file with the same name and location already exists.
The database to which the existing file is bound has security enabled.
147: The log segment is missing.
The MicroKernel cannot find a log segment that is necessary for rolling at least one file forward.
148: A roll forward error occurred.
The MicroKernel encountered an error while rolling a file forward. Depending on the operating system, the MicroKernel reports an error message as follows:
The NetWare MicroKernel displays the message on the server's system console and writes the message to SYS:SYSTEM\SYS$LOG.ERR.
The Windows 95 and Windows NT workstation MicroKernel and the OS/2 MicroKernel displays the message in the console message window and writes the message in the file
MKDEMSG.LOG, which is located in the home directory.
The Windows NT server MicroKernel does not display a message, but writes the message in MKDEMSG.LOG in the home directory.
149: You must use Scalable SQL to make changes to this file.
You attempted to write to a data file for which triggers are defined, and you are not using
Scalable SQL. You can only make changes to files that contain triggers if you are using
Scalable SQL.
151: The nesting level is too deep.
You have exceeded the number of nesting levels that the MicroKernel allows. The
MicroKernel's nesting level limit is 4,095. Specify fewer nesting levels. If you are using
Scalable SQL and you specified fewer than 4,095 nesting levels, you may have specified more nesting levels than your system memory can hold.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 397 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x C : S e c o n d a r y E v e n t s
Appendix C: Secondary Events
About Secondary Events
Secondary events are associated with the primary event above it in the play list. Multiple secondary events can be assigned to a primary event and are played concurrently. A secondary event’s time is used as an offset in relation to the primary event’s time.
Secondary Switching Parameter (sSP)
The secondary switching parameter contains values depending on the event type. For primary and secondary Audio/Video events, the value is the audio modes, mono and stereo.
By default, the audio mode is stereo. The value is initially set in a media prep product, such as Media Client, for the Audio Format database field. It can be modified in Air Client by clicking an event and entering S or M in the sSP field in Revise mode (ALT + R).
For secondary key and secondary audio over events, the value ranges from 1 to 9. The number corresponds to a keyer or mixer channel number on the master control switcher.
Secondary Audio/Video (sAV)
The secondary Audio/Video Audio Over event is used to add another A/V audio source over the primary audio/video source. The A/V audio over source may replace the primary A/V audio source or be mixed with it.
A secondary Audio/Video Audio Over event plays material, in addition to the primary event on air, for use in effects such as keys, audio overs and mixes.
When inserting a new secondary audio/video event in a play list, play (P) and thread (T), but not auto (A), are entered into the Type field. Switching is not used for this event. The event can be used to produce the audio/video over for a key/audio over input to a master control switcher or as an audio/video breakaway.
To switch the switcher
An A/V event may be run to switch the switcher. To do this, enter an A, instead of a P or T, in the Type field. The secondary event will begin with an audio-follow video transition.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 398 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x C : S e c o n d a r y E v e n t s
Back Timed Secondary Audio/Video (bAV)
The Back Timed A/V (backtimed secondary audio/video) event is the same as a Secondary
Audio/Video, except the secondary’s on-air time is the amount of time before the primary event begins. (i.e. The offset is measured backwards in time from the start of the associated primary event.)
In the event Type field, these events are inserted with types P and T (but not A). No switching is done on these events, unless this is changed. These events can be used as a key/audio over inputs to a master control switcher.
It is possible to associate a switching event with a back timed event. To do this, change the
Type field to A. This event starts with an audio-follow-video transition.
NOTE: Backtimed events cannot be run after up-counting events.
GPI Contact (sGPI)
A GPI contact closure secondary event controls the contact closure on a GPI card and is used to insert a GPI contact closure secondary event to the list. The Device Server must have the optional GPI card.
For each event, an on time (offset) and duration value must be entered.
An offset indicates how long after the start of the primary event the contact closure should occur.
The duration value sets the duration of the pulse or length of closure of the contact.
The offset is entered in the event’s on-air field and duration in the DUR field. The GPI closure may be longer than the associated primary event.
GPI Contact dialog
In following parameter configuration dialog is on the Air Client:
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 399 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e
Back Timed GPI (bGPI)
A p p e n d i x C : S e c o n d a r y E v e n t s
A Backtimed GPI is similar to a standard GPI event, except that the offset is measured backwards in time from the start of the associated primary event. For example, a backtimed
GPI event with an offset of 5 seconds fires the GPI contact 5 seconds before the start of the associated primary event.
A backtimed GPI event cannot be attached to an event following a primary upcount event. In this case, the system would not be able to calculate when to begin the GPI event.
Back Timed GPI dialog
In following parameter configuration dialog is on the Air Client:
Keyer On/Off (sKEY)
A Keyer On/Off event allows events to have an offset from the beginning of the event to be specified. Define a secondary Keyer event in which a hole is cut in the associated primary event’s video output and is filled with the output of the Keyer source.
The task performed by the key depends on the capabilities of the device you are using. This function will only be performed if the primary event’s A/V Switching data is configured to use a Master Control Switcher.
Key Event dialog
In following parameter configuration dialog is on the Air Client:
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 400 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x C : S e c o n d a r y E v e n t s
Modifier. This parameter specifies how the key source is outlined. The options are normal, shadow, drop shadow and border.
Source. The key fill’s source. When self is selected, the fill input both cuts and fills the hole.
When external is selected, the key input cuts the hole and fill input fills it in. When chroma is selected, the key is determined by the colors of the background video.
Matte. When selected, fill input is replaced by a matte source. The matte source color is determined by the mixer controls.
Key Hold. When selected, this option will keep the keyer on through subsequent primary transitions.
On Time. This will determine the start time of the keyer event. This option determines how long after the start of the primary event the key is overlaid. The value must be greater than
1.5 seconds or the key will arrive late.
NOTE: This secondary event behaves identically to the Transition Audio Over and
Transition Keyer secondary events when the value for the On Time field is blank or
00:00:00.00.
Duration. Determines the length of time the key is overlaid. Do not specify a keyer event to turn off during the next event’s preroll, as mixers are not equipped to carry out both actions concurrently. In order to have the key last as long as the primary event, make the duration field blank.
The duration of the keyer event can either be blank, or specified as equal or greater than to:
• the duration of the primary minus the secondary's (normal) offset
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 401 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x C : S e c o n d a r y E v e n t s
• 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.
A/V Keyer On/Off
The secondary Audio/Video Keyer event is used to add an A/V Keyer source over the primary audio/video source. The A/V Keyer source may replace the primary audio/video source or be mixed with it.
Transition Keyer
A transition keyer secondary event is similar to Keyer On/Off, except that the keyer is brought up at the start of its associated primary event with the same transition type as that of the primary. This type of secondary event has a configuration dialog box similar to Keyer On/Off; however, for the transition key, the value of the offset cannot be set. It is possible to define a transition key event so it lasts as long as the primary event. To do this, make the duration field blank. If the key hold option is on, the key is held over the transition in the same way as an ordinary secondary keyer event.
Transition Keyer dialog
In following parameter configuration dialog is on the Air Client:
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 402 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x C : S e c o n d a r y E v e n t s
To define a transition key event to last as long as the primary event, make the duration field blank. If the key hold option is on, the key is held over the transition in the same way as an ordinary secondary keyer event.
Audio Over On/Off (sAOV)
The Audio Over secondary event is used to add another audio source over the primary audio/video source. The audio over source may replace the primary audio source or be mixed with it.
To have the secondary audio event end at the same time as its primary event, make the duration field blank.
Audio Over dialog
In following parameter configuration dialog is on the Air Client:
Audio Over. The number of the audio input line on the mixer.
Ratio. The ratio of over audio source to primary source audio, ranging from 0 (all primary sources) to 99 (all audio over source).
Speed and Effect. The Speed option determines the speed of the transition effect. You may also set which type of effect will run between events by using the icons located next to the time fields. Transition effect options are cut, mix, wipe, fade fade, cut fade and fade cut.
On Time. This determines the start position of the event and how long after the start of the primary event the audio is overlaid. The value must be greater than 1.5 seconds or the event arrives late; however, you may use the Transition Audio Over to restart the audio when the primary event beings.
NOTE: This secondary event behaves identically to the Transition Audio Over and
Transition Keyer secondary events when the value for the On Time field is blank or
00:00:00.00.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 403 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x C : S e c o n d a r y E v e n t s
Duration. Determines the length of time the event is overlaid. The event is only performed if the primary event’s A/V Data is configured to use a Master Control Switcher.
Transition Audio Over (sTAO)
The secondary Transition Audio Over allows you to specify a secondary audio event to coincide with the primary event in the same manner as a transition keyer event, as described in Keyer On/Off.
This event has a set of options that are identical to the audio over on/off secondary event, except that the ontime option is missing (the ontime for a transition audio over event is set to
0).
To have the secondary audio event end at the same time as its primary event, make the duration field blank.
Transition Audio Over dialog
In following parameter configuration dialog is on the Air Client:
Break
A break may be inserted at a point on the list where you would like the list to stop running.
Events will play out normally up to this event.
The first event after the Break event cues up as usual, but does not play and the program switches to black. To restart a list after a break, click Play on the control panel. This list may also begin if a GPI contact input is used or if preroll is initiated on a hard start event that is next on the list.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 404 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e
Comment (****)
A p p e n d i x C : S e c o n d a r y E v e n t s
Use this secondary event to enter notes into the play list. Comments are ignored during transmission. Any text may be inserted into the title field of a comment.
Compile ID (cmID)
This type of event is used to label a compilation list with an ID. The tape ID of the compile tape should be entered into the ID field.
Data Event (sDAT)
This type of secondary event is associated with a device but does not generate any video output. Instead, the action specified by the event is performed at the time the event would be put on air, had the event been associated with a video device.
For video disk servers, a data event is used to control and automate the deletion of spots from the server. The use of this event with video disk servers requires an accurate scheduler or traffic program. If the events are not used carefully, spots may be accidentally deleted in the video disk server. Secondary data events are Secondary Events used to command serial devices requiring a simple command that does not need to run a countdown on the time of an event.
This type of secondary event attaches to a primary event that plays at the time the command is sent to the device to execute the data event command. The primary event can be any primary event for any device.
• The command is sent to the device whose device ID matches the event ID. As an example, the commands for the video disk server are entered in the secondary event’s title.
• The command, Delete From Disk, is entered as DEL:XXXXXXXX:YY. X’s represent the spot ID and Y’s represent the optional port value.
• The command, Get From Archive, is entered as GFA:XXXXXXXX:YY.
• The command, Delete From Archive, is entered as DFA:XXXXXXXX:YY.
NOTE: This secondary event may work differently based on the device being used.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 405 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e
Barter Spot (sBAR)
A p p e n d i x C : S e c o n d a r y E v e n t s
Barter spot events are associated with a primary event and are logged to the asrun log when the primary event runs to completion and is logged. Barter spot events are treated as comments by the automation system and are not played.
Barter spot is used for reconciliation with traffic systems. A barter spot is a source of audio/video that is part of another audio/video source. It is not played as separate audio/video, but is treated as a comment that is passed to the asrun log and to the reconciliation process.
This event is attached to the primary event. When the primary event finishes running it is logged to the asrun log.
These events appear in the text asrun log as Barter in the status field. In the enterprise traffic log for example, they appear as BTR in the program type field. The appearance of the spots in the logs does not positively indicate the spots have run. If the primary event runs, the spots are logged; however, the spots may not have actually been on the primary material.
Record Switcher (sRSW)
Record switcher is a secondary event that performs extra switching for inputs. During a recording, this switches to the secondary event’s source.
The name of the source to switch to is entered in the title field. This name must also be in the source name table for the switcher that is supplying the video to the record device.
The event is only performed if the primary event’s device has the A/V data parameters configured to specify the switcher number that has the matching name in its source name table.
Switcher Crosspoint (sXP)
This is a secondary event that performs extra switching for outputs. While an event plays, this function switches to the secondary event’s source:destination. This type of secondary event allows the control of multiple crosspoints during one primary event.
The name of the new source:destination is entered in the title field. Use the format
SRC,DEST where SRC is the name of the source and DEST, the destination. You may enter a maximum of 16 characters for the title and the name you enter must also be defined in the switcher’s device parameter field for Source Name and/or Destination Name for the switcher that is controlling the output for the primary event.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 406 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e A p p e n d i x C : S e c o n d a r y E v e n t s
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.
Switcher Audio Crosspoint (AUD-XPT)
This is a secondary event – similar to a switcher crosspoint event - that performs extra switching for audio outputs. While an event plays, this function switches to the secondary event’s audio source:destination. This type of secondary event allows the control of multiple audio crosspoints during one primary event.
When selected for logging, the logging is done at zero crossing of the primary event.
When “Switcher Audio Crosspoint” is selected in the configuration, and the “Control Audio
Mode” option is selected in the configuration:
• The Secondary Switching Parameter (sSP) field is neglected.
• A new secondary event “Switcher Audio Crosspoint” is used for the audio routing
(shuffling).
• If a “Switcher Audio Crosspoint” secondary event is not attached to the primary, default values are applied for routing as per the configuration.
Format of Title field:
x1 x2 x3 x4
x1 to x4 are input values for output 1 to 4
X1 to x4 = 1 to 4.
• If any of the input (x1 to x4) is not valid, it is replaced by its default (Configuration) value.
• If 2 or more “Switcher Audio Crosspoint” secondary events are found (resulting from an editing mistake), only the first one is taken into consideration.
NOTE: Audio routing is done on the device specified in the ID field, if valid. If ID field is not valid then audio routing is done on the primary event to which the secondary Switcher Audio
Crosspoint is attached.
When the next event is preset, its corresponding cross point is normalized to the default as specified in the configuration, provided the next event audio crosspoint is not the same as the current event.
Secondary Record (sREC)
This type of secondary event allows for the automatic recording and segmenting of live program material for immediate playback to air. Unlike most record events, this event is used in a list that combines record and playback activities. A secondary record event is attached to each primary event that is being recorded.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 407 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e
Break Sync (sSYN)
A p p e n d i x C : S e c o n d a r y E v e n t s
Break sync contains an estimated time of day a pod will run, a deviation time and a time for a window of opportunity for the operator to react to the event.
This event is normally be used on a list that contains only pods/breaks of commercials. The pods are:
• Separated by either an upcount event or by this Break sync event.
• Triggered to run by an external contact closure (GPI) or by clicking Play on the control panel.
In normal operation, a contact closure/play button is detected and the next pod on the list is played. The break sync event is marked DONE immediately. The pod plays out until either an upcount event, break sync event or the end of the list is encountered.
If the next pod has not played by the time of day specified on its break sync event, plus its deviation, the automation sends out a user notification to all automation clients. The event then waits for the opportunity time for a client to respond to the notification.
If no response is received at the end of this time, the automation marks each event in the pod and the break sync event as being missed. It stops marking events as missed when it encounters an upcounting event or break sync event.
If the list was running an upcount event, that event is skipped and the next upcount event runs. During the time the automation is waiting when the break sync occurs, the user notification is sent to all clients. One or more clients are enabled to detect the user notification.
The enabled clients display a dialog box prompting the operator to click OK to Delete Pod and Keep Pod. The dialog box is displayed only during the waiting time and will automatically close if the operator does not respond. This is the equivalent to clicking OK to Delete Pod since the list on the server will time out and mark the pod missed.
If the operator clicks Keep Pod, a message is sent back to the server causing the server to mark the break sync event as done, but leaves the pod intact waiting for the contact closure/play button. There is no other user notification for this pod.
If the contact closure/play button does not occur, the time of day for the break sync event for the next pod may occur. To eliminate a potential problem, the next break sync event is used to mark the previous pod missed. This occurs automatically at the time of day of the next break sync event minus its deviation time. When this occurs, all events before this event are marked missed.
If the automation had been running an upcount event, then this upcounter and the next up-counter before this break sync event are terminated before this event runs.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 408 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e
Secondary System
A p p e n d i x C : S e c o n d a r y E v e n t s
This event allows the traffic system to schedule device (resource) assignment during the execution of a transmission list. Like all secondary events, this type of event is attached to a primary event.
When this event type is run, it is able to move un-assigned device heads to the list that is running this event or release device heads in order to make them available to another list. It is up to the traffic department to schedule the assignment and release of heads so that two lists will not conflict in their usage of these heads. This event is programmed by filling in the time, ID and title fields of the event with control information. The time field controls the time when the event will run offset from the primary event.
Event IDs
The following event IDs act as commands to the list:
Assign. Will assign the device and head(s) specified in the title field to the transmission list the event is located in. The title format is: DEVICENAME,X,Y
Where DEVICENAME is the device name (5 characters) that is assigned to the device, X is the head number assigned to the list and ,Y is the number of other heads to be assigned.
Release. Will remove the device and head(s) specified in the event title field from the transmission list the event is located in and return it back to the system as an unowned device head. The title format is identical to the above described.
Protect. Performs a protect assignment on the device and head(s) to the device specified in the type field.
The title format is: PROTECTNAME, DEVICENAME,X,Y
Where PROTECTNAME is the name of the device that is to be protected.
DEVICENAME is the device name (5 characters) that is assigned to the device, X is the head number assigned to the list, and Y is the number of other heads to be assigned.
You must first have assigned the primary device heads to the list before assigning the protect heads. A space character may be substituted for the comma in any of the title field commands.
Backtimed System (bSYS)
This secondary event works in the same manner as secondary system except that this event type runs prior to the primary event by the time specified in the Time field.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 409 of 410
A D C D e v i c e S e r v e r v 1 1 . 6 1 . 4
I n s t a l l a t i o n , C o n f i g u r a t i o n , a n d O p e r a t i o n s R e f e r e n c e
System Event
A p p e n d i x C : S e c o n d a r y E v e n t s
This secondary event allows the traffic system to schedule device (resource) assignments during the execution of a transmission list. Like all secondary events, this type of event is attached to a primary event. When this event type is run, it is able to move unowned device heads to the list running this event or release device heads in order to make them available to another list. It is up to the traffic department to schedule the assignment and release of heads so that two lists will not conflict in their usage of these heads.
External (vDT)
Use an External secondary event to send commands or other information to a device through a device server. This event acts as a secondary A/V event with the capability of sending commands or other information to a specific device on the device server.
Data Event with Data (sDAT)
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.
© 2014 Imagine Communications Corp. Proprietary and Confidential 22-April-2014 | Page 410 of 410
Download
Offentligt link opdateret
Det offentlige link til din chat er blevet opdateret. You may view and manage your chat links after registration here.
Dokument offentligt link
Annonce
