Professional Documents
Culture Documents
User’s Guide
Your use of the software and operation manual means you agree to become bound by the
terms of this license agreement. If you do not agree to the terms of this agreement, do not
use the software and promptly return the entire package, along with any other product
materials, to the place where you obtained it for a full refund.
1. License
Harris hereby grants to you the right to use the Software only on a single CPU at a
time, at a single location. You may make one copy of the Software in machine
readable form, solely for backup purposes. The enclosed Software and any written
materials (the «Reference Guide») from Harris are licensed, not sold, to you for use
only upon the terms of this Agreement. Harris serves any rights not expressly granted
to you under this Agreement. You own the magnetic or other physical medium on
which the software is originally or subsequently recorded or fixed, but Harris retains
ownership of the Software recorded on the original disk and all subsequent copies of
the Software, regardless of the form or media on which the original and other copies
may exist.
2. Proprietary Rights
The Software and the Reference Guide contain trade secrets. You may not decompile,
reverse engineer, disassemble or otherwise reduce the Software to a human
perceivable form. The Software and the Reference Guide are copyrighted. You must
reproduce on each copy Harris’s copyright notice and any other proprietary legends
that were on the original copies supplied by Harris. You may not modify, adapt,
translate, rent, lease, loan, resell distribute, network, or create derivative works based
upon the Software or any part thereof. Unauthorized copying of the Software,
including Software that has been modified, merged or included with other Software,
or of the Reference Guide is expressly forbidden. You may be held legally
responsible for any infringement that is caused or encouraged by your failure to abide
by the terms of this Agreement.
3. Transfers
You may not electronically transfer the Software from one CPU to another over a
network. You may not distribute or otherwise transfer copies of the Software or the
Reference Guide to others, even if you are transferring the hardware on or with which
the Software is used. Nothing in this paragraph 3 shall impair any rights you may
otherwise have against Harris for any rights granted by Harris under this Agreement.
4. Termination
You may use the Software until this Agreement terminates. You may terminate this
Agreement at any time by destroying the Software and all copies thereof. This
Agreement terminates automatically without notice from Harris if you fail to comply
with any provision of this Agreement. Upon termination, you must destroy the
Software and any copies thereof.
5.1 Media
Harris warrants to the original Licensee that the disk(s) on which the Software is
recorded is free from defects in materials and workmanship under normal use and
service for a period of ninety (90) days from the date of delivery as evidenced by a
copy of the receipt. Harris entire liability and your exclusive remedy as to the disk(s)
shall be, at Harris option, either (a) return of the purchase price or (b) replacement of
the disk that does not meet the foregoing limited warranty and which is returned to
Harris with a copy of the receipt. Any replacement disk will be warranted for the
remainder of the original warranty period. Harris shall have no responsibility to
replace the disk or hardware, or refund the purchase price, if the disk failed due to
accident, abuse, or misapplication.
5.2 Operation
The limited warranty is the only warranty given by Harris in connection with the
Software and the Reference Guide delivered pursuant to this Agreement. EXCEPT
AS PROVIDED IN SECTIONS 5.1 AND 5.2. THE SOFTWARE AND THE
USER’S MANUAL (INCLUDING ANY INSTRUCTIONS FOR USE) ARE
PROVIDED «AS IS» WITHOUT WARRANTY OF ANY KIND. HARRIS DOES
NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATION
REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE
OR USER’S MANUAL IN TERMS OF CORRECTNESS, ACCURACY,
RELIABILITY, CURRENTNESS, OR OTHERWISE. WITH REGARD TO THE
SOFTWARE AND THE USER’S MANUAL, HARRIS DISCLAIMS ALL
WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE OR
ANY WARRANTIES ARISING OUT OF A COURSE OF DEALING. NO ORAL
OR WRITTEN INFORMATION OR ADVICE GIVEN BY HARRIS, ITS
DEALERS, DISTRIBUTORS, AGENTS, OR EMPLOYEES SHALL CREATE A
WARRANTY OR IN ANY WAY INCREASE THE SCOPE OF THIS
WARRANTY, AND YOU MAY NOT RELY ON ANY SUCH INFORMATION
OR ADVICE. EXCEPT AS SET FORTH IN SECTION 5.2. IF THE SOFTWARE
OR USER’S MANUAL IS DEFECTIVE YOU, AND NOT HARRIS OR ITS
DEALERS, DISTRIBUTORS, AGENTS, OR EMPLOYEES, ASSUME THE
ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR, OR
CORRECTION. THE PRICE CHARGED BY HARRIS FOR THE SOFTWARE
AND USER’S MANUAL DOES NOT INCLUDE ANY CONSIDERATION FOR
ASSUMPTION BY HARRIS OF ANY RISK OF ANY DAMAGES INCURRED
BY YOU WITH RESPECT TO THE SOFTWARE OR THE USER’S MANUAL.
THE ENTIRE RISK ARISING OUT OF YOUR USE OF THE SOFTWARE IS
ASSUMED BY YOU. ACCORDINGLY, AND NOTWITHSTANDING THE
7 Miscellaneous
This Agreement is a complete and exclusive statement of the Agreement between us
and supersedes any proposal or prior Agreement, oral or written and any other prior
or subsequent communications between us relating to the subject matter of this
Agreement. This Agreement shall be construed, interpreted and governed by the laws
of the State of California, excluding its conflict of laws provisions to the extent such
provisions would apply the law of another jurisdiction.
COPYRIGHT
This manual is copyright © 1999 by Harris Corporation. ADC-100 software is copyright
© 1990-1999 by Harris Corporation. All rights reserved.
TRADEMARKS
All brand names and product names used in this book are trademarks, registered
trademarks, or trade names of their respective holders.
The information contained in this document has been checked and is believed to be
reliable. However, Harris assumes no responsibility for errors or omissions, and reserves
the right to make changes to the product described herein and the documentation without
prior notice.
1 Installation
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Installing the NT Device Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Checkkey.exe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
2 Configuration Manager
Configuring the Device Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
File Menu (Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
View Menu (Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Server Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Configuring Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Logically Configuring Your Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Deleting Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Configuring Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Configuring a Protect Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Play List Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Parameters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Lookahead Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Events to Log Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Mix/Wipe Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Linking Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Media List Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Parameters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Events to Log Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
GMT List Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Parameters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
4 VTR Configuration
VTR Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Diagnostics Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
8 Requester Configuration
Requester Device Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Qualifiers Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Routing Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Destination Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Distributor Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
9 Distributor Configuration
Distributor Device Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Routing Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Source Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Global Delete Targets Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
List of Figures
2-1 Configured Devices (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2-2 Configured Devices (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2-3 Device Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
2-4 List Assignments (1 of 2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2-5 List Assignments (2 of 2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2-6 Configuring a Protect Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2-7 Configuring a Protect Disk (wrong) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
List of tables
1-1 Updated NT Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
3-1 Additional ports of same video disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Overview
This chapter presents an introduction to the Harris ADC Device Server and how it
works within the automation system. Also included in this overview is a brief
description of the various chapters of this manual. Topics covered in this chapter
include:
Introduction. This chapter, giving an overview of the ADC Device Server and its
features. Also included is a brief description of optional Harris products.
Chapter 1, “Installation” on page 1-1, provides instructions for installing the ADC
Device Server and its client-side configuration software.
Chapter 5, “Cart Machine Configuration” on page 5-1, describes the various configuration
options for a typical cart machine.
Chapter 6, “M/C Switcher Configuration” on page 6-1, describes the various configuration
options for a typical master control switcher.
Appendix A, “Supported Devices” on page A-1, contains a list of all currently supported
devices. This list is continually updated, so be sure to check Harris’ website at
www.harris.com for updates to the list of supported devices.
Automation allows the control room to function at peak efficiency, minimizing operator errors
through such features as automating the process of transferring traffic’s lists so the operator
does not have to re-enter the same data from traffic’s logs. The master control operator also
can perform several tasks at the same time, since the automation system performs many tasks
that formerly were done manually.
The basic ADC Device Server system has a device server which is configured for at least one
transmission list. The file server is located on a separate, dedicated computer. The client (user)
computers connect to the Device Server and file server computers through a local area
network (LAN) that uses a client-server configuration.
System configurations can range from a simple server connected to a switcher and three or
four VTRs to a large system that manages video disk servers, several cart machines, many
VTRs and a wide variety of other devices.
◆ The station’s Traffic department typically generates a dub list (new material to prepare for on-
air playout). Using the Harris Media Client (available separately), this list can be transformed
into a label list for barcode labels and the tape details directly entered into the Harris database,
as well as a dub list for spots to be entered into a video disk server.
◆ Traffic produces a schedule of the items to be played out during a specific time period. The
automation system accepts the schedules from traffic through a traffic system interface, con-
verts the schedules to playlists and stores the lists at the file server computer. Play lists can
also be created and edited directly from the client workstations.
To prepare a list for playout, the play list is loaded into the ADC Device Server transmission
window and becomes a transmission list. ADC Device Server activities are driven by
transmission lists. There are two major types of transmission lists – play and compile lists.
Play lists are used for both playout and record events, although separate lists are used for each
of these activities. Compile lists are used to take interstitial material and record it together on a
separate tape to be played out by a single VTR. Compilation reduces the number of VTRs
needed to play out the interstitial material to air.
◆ While a play list is running, each event performs a specific task such as play, record, which
includes threading and switching. After the event airs, the actual start time and duration of
the event are written in the As-Run log (file). This log is typically returned to Traffic where
changes in the original schedule can be compared and billing and recordkeeping updated.
System Components
The basic automation system is comprised of the following components:
The backup device server is a computer which is identical to the main device server. If the
main device server fails, the backup device server takes over the tasks handled by the main
device server. The backup device server is configured the same way as the main device server.
If the main device server fails, the device connections can be manually transferred to the
backup device server. The transfer is accomplished by an RS-422 switching device.
The client workstations (and the control panels) are where users interact with the ADC Device
Server. A typical automation system comprises enough Air Client workstations to support
several users. At an Air Client workstation, a user creates and edits playlists. Users that have
the proper access rights can also control the transmission lists from the Air Client.
File Server
The file server stores the database and play list files. Through the use of a client, commands
are sent to the file server. The file server then reports back to the client, at which time the client
sends commands to the device server for execution.
The file server does not run any software. Its sole function is to free the device server to
exclusively control devices. The device server reads the play list from the file server (via a
network hub), then executes the play list.
Additional Options
Available options include:
◆ Traffic interface
◆ Redundant device and database server (cloning)
◆ Redundant Device Server switch box
◆ ID/Title Mismatch software
◆ Air Protect
◆ Compilation
◆ Auto-record
◆ GMT
◆ Customization of other features
Physically, the ADC Device Server is either a 20-slot or 10-slot, rack mount PC. The device
server is installed with ADC Device Server software (which is different than what is installed
at the client computers). The server contains four-port serial boards (where the devices
connect), GPI boards, timecode reader board, reference video board and a network board. A
20-slot server installed with four-port serial boards can control a maximum of 64 devices and
provide 16 channels simultaneously. If more capacity is needed, additional device servers can
be added to the system.
The ADC Device Server is configured remotely from any client on the Harris automation
system containing the Remote Configuration Tool. The Configuration Tool contains common
Windows usability features, such as drag and drop and a point-and-click graphical interface.
The system is highly flexible and can be configured for most broadcast operations and
equipment. The ADC Device Server controls most types and models of broadcast devices,
including cart machines, video disk servers, external VTRs, still stores, character generators,
routers, switchers, distributors and master control switchers. The ADC Device Server can also
incorporate existing broadcast applications into the Harris system.
One of the ADC Device Server’s major strengths is its powerful software. The software
interfaces with and controls the broadcast devices (instead of hardware interface boxes). The
software can be easily modified to incorporate new models or types of devices.
Automation system components (including the ADC Device Server) are connected through a
local area network (LAN), in a client-server configuration. The ADC Device Server integrates
the on-air playout system by using station reference video to maintain timing, by using station
timecode to keep to the on air schedule and by controlling virtually any serially-controlled
device (including satellite receivers), and any GPI (General Purpose Interface) controlled
device. The Master Control operator can control the on air playout from a Harris control panel
(similar to a Master Control Switcher Panel). The system can also be started automatically by
time of day, as well as remotely by GPI.
Features
Features provided by the Harris ADC Device Server include:
◆ Software-based System. Most automation systems use the SMPTE standard E/S
Bus to communicate and control broadcast devices. These systems use hardware
interface boxes between the E/S Bus and the devices. Modification or
customization of a system typically involves changes to the hardware, which can
be a difficult process. The ADC Device Server instead uses software tools (objects)
to communicate with broadcast devices in lieu of hardware interface boxes. With
the ADC Device Server, modification to the system is simpler and throughput is
faster.
◆ Object Oriented Programming. The ADC Device Server software is written using
a modern programming technique called object oriented programming (OOP).
With OOP, broadcast devices are treated as software modules or objects. Each
object can be easily modified and extended to support other makes and models of
devices within the same family. Development of custom software modules is
faster and more affordable.
◆ Real Time Control. The ADC Device Server provides frame accurate control.
◆ Future Proof. The Harris system is extendable to new devices, new applications
(for example, HDTV) and current applications (such as multichannel output,
video disk servers and compiling). The system is designed to fully support future
needs and requirements.
◆ Harris Application Programming Interface (API). Harris’ Application
Programming Interface (API) is software that creates a bridge between external
applications and the ADC Device Server. It allows external applications, such as a
newsroom system, or custom modules to seamlessly link to the devices. The API
allows system integrators or customers to develop applications that work directly
with the ADC Device Server.
◆ Client/Server Architecture. The ADC Device Server utilizes a versatile
implementation of client/server architecture. With this architecture, the workload
Broadcast Devices
The ADC Device Server is designed to interface to most devices commonly found in broadcast
operations. Such devices include:
◆ cart machines
◆ video disk servers
◆ external VTRs (VTRs not in cart machines)
◆ routing switchers
◆ master control switchers
◆ still stores
◆ character generators
◆ audio carts
◆ external encoders and decoders
◆ subtitling systems
◆ satellite systems
RS422 connections are used between the Device Server and the broadcast devices.
Some broadcast devices do not interface to RS422. These devices can be controlled through
GPI-type connections with relay contacts.
Play lists can be created locally at the Air Client workstations or from traffic schedules. Play
lists are stored at 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 list is loaded into the transmission
window and becomes a transmission list.
The ADC Device Server supports multiple transmission lists. Each list can contain 2,500
events by default (this number can be expanded to a larger number if necessary. Contact
Harris.).
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 can be made up of several appended playlists.
During configuration of the devices, each transmission list (transmission window) is assigned
specific broadcast devices. Devices are assigned to lists as resources. During playout of the
transmission list, the devices assigned to the list are available to run the events in the list. Each
transmission list controls a separate channel. This feature allows for simultaneous multi-
channel operations. In addition, cart machine VTRs can be assigned to two or more
transmission lists for two (or more) channel operations controlled by the one cart machine. Or,
the cart machine VTRs can be assigned different tasks. For example, two VTRs might be used
for playout, one for record, and one for compile. Video disk servers with multiple ports can be
shared between transmission lists.
The ADC Device Server plays each event in the list sequentialy until the operator intervenes
or specific types of events, such as live events or time-triggered events, are encountered. An
event runs according to where the event is located in the list or what time (if any) is entered for
the event. If changes to the list are needed during playout, the user can directly edit an event
in the list. (The only limitation on the time is the ability of the device to ready the material for
air; e.g., sufficient time is allowed for cueing and pre-roll of the edited event).
Playout can be controlled by the control panel (software or hardware). Using the control panel
buttons, it is possible to skip events, hold up the events past their EOM (end of message time),
and recue events and then restart them. An on-air event can also be edited by either adding or
subtracting a second to the event’s duration.
Automated Recording
An optional ADC Device Server record function provides for automated recording of material.
A recording can be set up for a specific date and time and set duration.
A record list is similar to a play list but just contains record events. Also like the playlist, the
record list is loaded into a transmission window to run the events in the list.
A secondary record event, also an ADC Device Server option, is available for recordings
scheduled for immediate play out. The secondary record event feature uses a playlist that has
both record and play events. This feature can store program segment information (for future
replay of a live event).
The ADC Device Server can use any VTR or video disk in the system for a recording. For long
VTR recordings that require several tapes or to create duplicate copies of a show, several VTRs
can be assigned. This also allows multiple recordings to take place simulultaneously using the
same list.
The ADC Device Server controls input audio and video switching when the recording begins.
Recordings can be made from program output or from external feeds, such as satellite.
GMT
(Optional feature) Global Media Transfer (GMT) is Harris Automation's system for controlling
media movement within a broadcast facility. GMT works in conjunction with the on-air
automation system. Each transmission list may ask GMT to find media that cannot be found
in the devices assigned to the list. GMT finds and moves the media to a destination device
(usually a video disk server) assigned to the transmission list. The transmission list then airs
this media. The main tasks of GMT are:
Compilation
A group of spots or other interstitial material can be prerecorded together on a separate tape
(i.e., compiled) and then played out as a single item (rather than playing out each separately).
Each separate item of original material is logged in the asrun file as a separate entry.
With the compile feature, fewer tapes are required for playout of spots. The material is
recorded on the tape in playout order. The problems associated with locating and cueing
different spots placed on the same tape are avoided. Also, the quality of the playout material
can be checked when the spots are being recorded/compiled.
The ADC Device Server consists of a server and a client, each with communication
software that allows the server and client to “talk” to each other. The software on each
must be configured in order to communicate properly. See “Configuration Manager”
on page 2-1 for details on how to configure the server and client.
System Requirements
The following are the minimum requirements to run Harris’ ADC Device Server
software.
NT DRIVERS
VERSION 1.01
1. Run Windows Explorer, then double click on the setup.exe file on the floppy. If using
a CD-ROM, the CD is self-starting.
2. Proceed through the various screens, at the end of which you will be prompted to
restart the computer. Select Finish to restart the computer. Make certain the floppy is
still in the drive when you select Restart. Remove the floppy after the system finishes
rebooting.
3. After restarting, select Start > Programs > Administrative Tools > Event Viewer to verify
which Harris NT driver services have been started. You should see a service for
TimeCode, HarrisSer, HarrisGPI, and VREFSync.
4. Select Start > Programs > Administrative Tools > Windows NT Diagnostics, then the Resources tab
can be used to check the IRQ and I/O settings used by these boards.
5. Make sure that the VREFSync driver is using interrupt 3 and that no other device is using this
interrupt. Make sure that TimeCode driver is using interrupt 5 and that no other device is
using this interrupt.
6. Selec the I/O Port button to display the input/output port usage:
7. Confirm that you see the HarrisSer for each four port serial card configured in the system.
Checkkey.exe
After installation is complete, a program file CHECKKEY.EXE is installed in the \SERVER
directory. Run this program to verify that it finds the VSYNC hardware.
The first box should have a check mark in it and all the other boxes should be blank. If any
other situation is present, the hardware has been misconfigured. Contact your Harris
representative for further assistance.
NOTE: The Device Server software is installed on the device server. The Device
Server should be used exclusively as a device server, not running any
other applications. Harris’ software is designed to use all possible
resources on the device server, and performance deterioration will result
if the device server is used to run additional software.
You will either have the server software on two floppy diskettes, or on an electronically-
delivered file titled server.exe. This is a self-extracting executable file containing all the files
necessary to install the server software.
NOTE: If you already have the files on two floppy diskettes, skip to step 6.
1. Copy the server.exe file to a temporary directory. This file is a self-extracting zip file.
2. Open a command prompt and cd into the directory containing the server.exe file.
3. Type server.exe -d to extract the file. The file extracts into two subdirectories, titled “Disk1”
and “Disk2.”
4. Copy the “Disk1” files onto a floppy diskette and label it “ADC NT Server Disk #1.”
5. Copy the “Disk2” files onto a floppy diskette and label it “ADC NT Server Disk #2.”
6. Go to the device server and insert Disk #1 into its floppy drive.
7. Open a command prompt and type a:setup.exe to begin the installation.
8. InstallShield proceeds to install the software onto the server. Follow the onscreen instructions
to complete the installation. The opening screen resembles the following:
9. Click Next to continue. One of the subsequent screens is worth mentioning here:
This screen does NOT appear if you are reinstalling the software. Only upon the first
installation on your server does this screen appear. If you wish to RENAME your server after
installation, you must make the change via the command line parameter. See “Command Line
Parameters” on page 1-7 for details on how to change the server name by changing the
command line parameter.
10. After installation is complete, store the installation floppies in a safe place.
1. Copy the config.exe file to a temporary directory. This file is a self-extracting zip file.
2. Copy the extracted files onto a floppy diskette and label it “ADC NT Configuration.”
3. Insert the floppy disk into the client’s floppy drive.
4. Open a command prompt and type a:setup.exe to begin the installation.
5. InstallShield proceeds to install the software onto the client. Follow the onscreen instructions
to complete the installation.
6. Enter a password when the following screen appears during installation:
Make sure to remember the password you enter. You will be required to re-type the same
password on the next screen to confirm your password choice. If you forget the password or if
it becomes compromised (i.e., the proper password no longer works), you must re-install the
configuration utility.
CAUTION! After installation is complete, store the floppy disks in a safe place. If
you installed from a temporary directory on your hard drive, make
sure to delete the temporary directory. If these files are left on the
computer, anyone can override the password by simply reinstalling
the configuration software and entering a new password.
This password may be changed at any time from within the configuration utility. See
“Changing the Password” on page 2-23 for details on how to change the password.
Proceed to “Configuration Manager” on page 2-1 to configure the client for use.
C:\CONFIG\ADCNTCFG.exe NTCONFIG
The NTCONFIG parameter indicates the name of the client running the configuration utility.
This name must be unique on the Harris network. If the configuration utility is installed on
more than one client, each client must have a unique name.
The device server installation also creates a desktop shortcut containing a command line
parameter. Example:
C:\SERVER\adc100nt.exe MAIN
The MAIN parameter is the default name given to the device server. This name must be
unique on the Harris network. We recommend you change this name to something different,
to ensure that no two servers have the same name.
NOTE: This section applies only if you are upgrading from Harris’ ADC100 DOS Server
to the ADC Device Server. If you are a new user, skip this section.
1. When copying the .ini files from a DOS ADC100 server to an ADC Device Server, copy the
files ADC100.INI to LISTCONF.INI and ADC100NT.INI. From a command prompt, type:
copy ADC100.INI LISTCONF.INI
copy ADC100.INI ADC100NT.INI
The legacy DOS .ini files do not contain the serial port configurations. In the ADC Device
Server, each serial device can be assigned to use any valid serial port. The advantage to this is
that if a serial card or port is suspected to be bad, the device can use another port without
having to reconfigure the device or any associated switching.
Make sure to configure each serial port after the server is brought up.
2. The ADC Device Server supports extended device names. A device name may now be 16
characters long. This allows device names in large systems to be more informative (you can
still use 5 character names if you wish). To use the extended device names, enter them into the
device name field of the properties for the device being configured.
In order for the Air Client to use extended device names, the Air Client must be run with a
command line switch of /NT:
3. On the ADC Device Server, list names (play lists, media lists, GMT lists, and compile lists) can
be set for each list. These names can be used in the Air Client without having to configure the
list names for each Air Client. In order for the Air Client to use them the Air Client must be
run with a /NT command line switch. Using the /NT command line switch causes the Air
Client to read the list name from the ADC Device Server. Using list names on the Air Client
does not disable the listname property for configuration. As a result, do not use list names on
the Air Client if you are using the /NT option. This way, the Air Client inherits the list name
from the device server.
ACLNT32 clientname main backup /NT
4. You must configure your switchers before setting up any audio/video (A/V) information in
any of the devices. This includes naming the switcher and entering a crosspoint name for each
usable source and destination.
5. The audio/video information is now configured under the list configurations (i.e., the A/V
paths for a device are configured on each list that might use the device). This is because the
information pertains to the switching for that list. The A/V information is still stored in the
device part of the ini files.
6. The audio/video information for the preview channel is now stored as list number 17. In the
DOS Server, the preview channel was always stored in the device under the last list plus one
(if the server had 6 lists the preview, A/V information was stored as list 7). If you ever added a
list to the server the preview A/V information had to be reconfigured. This is not true in the
NT version.
When converting a DOS .ini file to an NT .ini file, you must reconfigure the preview A/V
information or edit the ADC100NT.INI file to change the preview A/V information for each
device.
7. The ADC Device Server only runs on the Harris 4-Port Serial Cards.
8. The SONY LMS object does not have the router built in anymore. Instead, a new device under
routers exits.
◆ Configure the LMS device first.
◆ Configure the LMS Router under Router/Switchers.
◆ Invoke the Properties form for the LMS Router and select the Cart Machine page.
Configure the LMS Router to use the correct cart machine. The Enable Switcher
Monitor only applies to Beta Carts that have the monitoring built in.
9. The Help > About Server menu on the Device Configuration and List Configuration screens
display the server name and version number of the server software. To display the version
number of the Configuration Manager, use the Help > About menu option (in the first screen of
the configuration program).
10. Sometimes if the NT Server generates a runtime error and you restart it, it may still be
running. If this appears to happen, invoke the Task Manager and see if a copy of
ADC100NT.EXE is already running. If it is, terminate that process before running
ADC100NT.EXE again.
11. There is no manual VTR mode in any of the Odetics cart machines under NT. The architecture
of these machines under NT prohibits this function.
12. The Standard Video Disk drivers and Profile drivers treat the two heads as one video stream
under NT. When assigning the STREAM to a list, both heads are moved as one pair. When
configuring Audio/Video this is also done on the STREAM so that you only have to configure
the STREAM once (but both heads will be automatically configured).
13. Some devices have not been ported to NT. These devices had been replaced in DOS with
newer device drivers. Only the newer device drivers are available under NT.
The ADC Device Server is configured remotely from a client on the Harris automation
network running the server configuration software. We call the remote client utility
the Configuration Manager throughout this manual.
NOTE: The Server Handle can be configured remotely from the configuration
Manager if you desire.
The remainder of the configuration options are found in the Configuration Manager (discussed
next).
NOTE: The remaining options are found in the configuration software, installed on a
client. The configuration software should NOT be installed on the device server,
as performance degradation will result.
Configuration Manager
NOTE: If using more than one Configuration Manager to configure the server,
make sure that only one is running at a time.
The Configuration Manager is an integral part of the Harris ADC Device Server, running on any
client on the Harris Automation network. Do not run the Configuration Manager on the
device server. Running the Configuration Manager on a client benefits the mission-critical
device server by freeing up valuable CPU time for the server.
Server Handle
Right-click on the highlighted server, then select File > Server Handle from the menu. If you
entered a server handle in the server, you do not need to repeat it again here.
Configuring Devices
Right click on the configured device, then choose Configured Devices. The following screen
appears:
1. Click the plus sign (+) to the left of Video Disk Servers to expand the list.
2. Click on the device to be configured to highlight it.
3. Drag the highlighted item over to the left side, and drop it anywhere on the Channel 1 line.
The device is now configured as Channel 1:
Note that the number of Video Disk Servers available on the right side has decreased from 4 to
3, since one of the 4 available servers in our example has now been configured.
4. Right-click on the configured device in the left column, then choose Properties. A dialog box
with multiple configuration options appears. Use the left and right arrows in the upper right
corner to scroll through the other tabs (some devices can have 10 or more tabs).
5. You may want to rename the device. For example, the above Demo Video Disk has a default
name of “DDsk.” If this is to be used as an air disk, you could rename “DDsk” to “Air.” This is
done by typing in a new Device Name in the General tab. Right-click on the device and select
Properties to access this tab.
NOTE: The above example is generic and meant for demonstration purposes only. The
steps to access the configuration options are the same, regardless of the device;
however, the individual options and tabs will vary depending on the device and
make/model. Refer to the User Notes for your device for complete details on how
to configure it.
Repeat steps 1-4 above for all devices to be configured. Once your devices are configured, they
are ready to be added to lists.
We recommend that you configure VTRs and video disks first, then other physical (real)
devices and lastly cart machines. Virtual devices such as requesters and distributors should be
configured in unused channels, after all physical ports.
Deleting Devices
To delete a configured device, do the following:
NOTE: If you delete a configured cart machine, the cart machine ejects tapes from VTRs
and returns the tapes to their locations in the bins. As a result, a slight delay in
deleting the cart machine may occur. The server eventually removes the device
from its list of configured devices, with no further operator intervention required.
Configuring Lists
After devices have been configured, they may be assigned to a list. A list of available devices
appears, based on what devices were configured earlier. See “Configuring Devices” on page 2-
3 for details on how to configure devices.
Play list. Sends commands from play list data files to air devices. Assign devices to Play
List for on-air playout.
Media list. Sends commands generated by Media Client to media preparation devices, such
as VTRs, video disks, and cart machines. Assigning devices to Media List makes the device
available exclusively to Media Client.
GMT list. Executes commands to and from GMT components. Only GMT components
should be assigned to GMT List, as they will be unavailable to other lists.
Compile list. Use a compile list to combine several spots onto one tape. This reduces the
number of devices required during playout. Without compilation, each spot is recorded
onto a separate tape and each tape requires a separate playout device.
1. Right click on the server, then select List Configurations (selecting File, List Configurations also
accesses the same dialog box, similar to the following:)
Note the names “Air” and “Protect” appear as available media. This is because we renamed
“Ddsk” to “Air” and another demo video disk to “Protect” for demonstration purposes.
2. Drag “Air” from the right side onto PlayList 1 on the left side, then drop it onto PlayList 1.
Your screen should resemble the following:
3. The first video disk has now been assigned to PlayList 1. Repeat this procedure for all
configured devices. 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.
The protect device automatically replaces the air device in the event that the air device loses its
connection with the server.
If the operator notices a problem with the air device (such as poor picture quality) and wishes
to manually switch to the protect device, this can be done by using Harris Automation’s Air
Client. See the Air Client User’s Guide for details on how to manually switch to the protect
device.
To configure a protect device, do the following (our example uses two video disks; one as an
air disk and one as a protect disk):
Make sure you have configured at least two video disks. See Figure 2-2 on page 2-4 for details
on how to configure a device.
1. Access the List Assignments dialog box again (highlight the server, then select File > List
Configurations or right-click, then select List Configurations).
2. Drag a second video disk from the Available Media (on the right side) directly onto the first
video disk. In our example, the resulting display looks like this:
The second disk is automatically configured as an air protect disk. The resulting display is
similar to the following:
Note the word Protect in parentheses listed after the second video disk. This indicates that the
protect disk was successfully configured onto the playlist.
If you accidentally dropped the second video disk on PlayList 1 instead of Air (the video disk
assigned to PlayList 1), it will appear like this:
In Figure 2-7, the second video disk is not a protect disk (notice the word Protect does not
appear in parentheses). To undo this, right-click on the second disk, then choose Unsassign.
This action unassigns the second disk and moves it back to Available Media on the right side.
To verify that the protect disk is correctly configured, make sure it appears indented under the
air disk, and not flush left with the air disk. Examine Figures 2-6 (right) and 2-7 (wrong) to see
the difference.
Options
Rewind Spots: After a spot plays, the automation system rewinds the tape before ejecting it
from the VTR. 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). Default is
enabled.
Rewind to First Program Segment: After a program plays, the automation system rewinds
the tape to the first segment before ejecting it from the VTR. The tape is rewound to the
SOM of the first segment minus the preroll. Default is disabled.
Rewind Compile Material: After the final spot on a compile tape plays, the automation
system rewinds the tape before ejecting it from the VTR. The tape is rewound to the first
commercial break (or “pod”) minus the preroll. Default is disabled.
Extended Time to Next: The Time to Next functionality has been enhanced on a transmission
play list. Default is enabled.
◆ When the termination event is an O (hard start) event the Time To Next display
includes the running short value.
◆ Zero duration up counters no longer stop the rippling.
◆ When in an up counter, if an O event exists as the termination event, the Time To
Next computation computes without any long or short value. It displays exactly
how long until the hard timed start begins.
Thread Limited: A new list configuration, Thread Limited is available for controlling
threading on a list. By enabling the Thread Limited option, non-threaded but blue
(registered) events count toward the total thread time as if they were threaded. Default is
disabled.
Auto Restart When Cued: Allows a missing event to automatically start when cued. If
disabled, the automation system marks the event as missing and does not automatically
cue the event when located. Default is disabled.
Time Parameters
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.
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.
StandbyOn Seconds: 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.
Options Tab
Options
Switch to Black: Switches to black on the output channel whenever the lists stops. Default is
enabled.
Play Hard Hits: Enables a hard start event to be started by an operator pressing the play
button on the Control Panel. When disabled, an operator is unable to start a hard start
event unless they clear the hard start type. Default is disabled.
COntact Start: Enables the Transmission list to be started by a GPI (General Purpose
Interface) contact. The GPI contact is equivalent to selecting Play on the Control Panel.
Playlists 1 through 16 correspond to contacts 1 to 8 of Card One/Two, respectively.
Default is disabled.
Play ID Title Mismatches: (Optional feature) Allows mismatched events to play. Default is
enabled.
Skip Bad Events: Enables the list to skip bad events. A “bad” event is an event that is
unable to play, such as unavailable media or an event that causes an error during
transmission (due to a tape jam or tape running short, etc.). If consecutive bad events are
encountered, only the first bad event is skipped. In order to skip the following events you
must use the Play button in the Control Panel. If this option is disabled, the list stops
running when a bad event is encountered. To restart the list if this occurs, cut the bad
event from the list and press Play. Default is enabled.
Station ID On Skip: When this option is enabled and a Skip command is issued, the system
automatically switches to the Logo input (the Logo input is configured in the Device Server
through the switcher’s device parameters. Default is disabled.
Release Tension When Cued: Places tape events into tension release when they are cued. The
events are readied at the Standby On time before they are due to roll. Default is disabled.
Timed List: Enables the list to play Hard Start events at their specified start times. Default
is enabled.
Update On-Air Time: Aafter each event plays, the system updates the event’s time to the
actual time that the event was transmitted. This information is also written to the As-Run
Log (if logging is enabled). Default is enabled.
Auto Ripple Times: The system recalculates the projected start times for the events in the list
dynamically during playout (up to the first hard start event encountered) and updates the
event times accordingly. The calculation assumes that the Duration field for up-counting
events is accurately set. Default is disabled.
Tension After Up Counter: The next Standby On time (in seconds) worth of events that
follow an up-count event are tensioned on. If this option is disabled, the events are tension
released and the next event may only be tensioned on manually by pressing Ready in the
Control Panel. Default is disabled.
Thread After Break: Controls whether or not events are threaded following a break. If this
parameter is disabled, no events are threaded after the break. The events must then be
individually threaded once the list reaches the break, or the Program Run button must be
pressed after the break event is reached. Default is enabled.
Keep List Threaded: This option keeps as many devices threaded as possible, at all times. 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.
When disabled, events are cued only within the thread times. Default is disabled.
Done Count
The number of completed events that display in the Transmission List window on the Air
Client. The valid range is from 1 to 20 events. Default is 4 events.
Thread Time
The amount of time a cart machine loads and threads a tape in a VTR prior to its
scheduled on-air time. The valid range is from 0 to 23:59:59:29 (23 hours, 59 minutes, 59
seconds, and 29 frames). Default is 2 minutes. If the Keep List Threaded box is enabled, that
setting overrides the Thread Time setting here.
Lookahead Tab
Hours: Specify a time duration, in hours, for the lookahead window to check. The
valid range is 0 to 23 hours. Default is 4 hours. This option has no effect unless the
Duration Based Lookahead box is enabled.
Minutes: Specify a time duration, in minutes, for the lookahead window to check. The
valid range is 0 to 59 minutes. Default is 0. This option has no effect unless the
Duration Based Lookahead box is enabled.
Enable Toggle Lookahead: Check this box to enable. This setting has no effect unless the
Duration Based Lookahead box is enabled (above). EnablingDefault is disabled.
Toggle Hours: Set an alternate time for toggling back and forth from the default setting
chosen above. Use the F8 key to toggle back and forth between the default time setting
and the alternate time chosen here. The valid range is from 0 to 23 hours. Default is 4
hours.
Toggle Minutes: Set an alternate time for toggling back and forth from the default
setting chosen above. Use the F8 key to toggle back and forth between the default time
setting and the alternate time chosen here. The valid range is from 0 to 59 minutes.
Default is 0.
Toggle to Alternate Time: Select this option to cause 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 to Full List: Select this option to cause the F8 key to toggle between the Duration
Based Lookahead setting and the full list.
Count Lookahead
Look Ahead: Select how many events the lookahead should check. Default is 50 events. If
Duration Based Lookahead (above) is enabled, that setting overrides the setting here in Count
Lookahead. Otherwise, this setting is used. Default is 50 events.
NOTE: For a detailed explanation of the following options, please see the Air Client user’s
guide. Following is a brief description of each of the following options:
Back Timed GPI: 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. Default is enabled.
Sec. Audio/Video: Secondary Audio/Video event; plays material, in addition to the primary
event on air, for use in effects such as keys, audio overs and mixes. Default is enabled.
Back Timed Sec. Audio/Video: Same as Sec. Audio/Video except the secondary’s on-air time is
the amount of time before the primary event begins. 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. Default is enabled.
Keyer On/Off: 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. Default is disabled.
Transition Key: Similar to Keyer On/Off (above), except that the keyer is brought up at the
start of its associated primary event with the same transition type. 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. Default is disabled.
Audio Over On/Off: 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. Default is disabled.
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
(above). 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). In order to have the secondary audio event end at the same
time as its primary event, make the duration field blank. Default is disabled.
Data Event: This type of secondary event is associated with a device but does not generate
any video output. Instead, the action specified by the event is performed at the time the
event would be put on air, 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 used to command serial
devices requiring a simple command that does not need to run a countdown on the time
of an event. Default is enabled.
Barter Spot: 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. Default is disabled.
Record Switcher: 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. Default is disabled.
Switcher Cross Point: 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. Default is disabled.
Secondary Record: 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. Default is
enabled.
Break Sync: Break sync contains an estimated time of day a pod will run, a deviation time
and a time for a window of opportunity for the operator to react to the event.
This event is normally used on a list that contains only pods/breaks of commericals. The
pods are separated by either an upcount event or by this Break sync event. The pods are
triggered to run by an external contact closure (GPI) or by clicking Play on the control
panel. In normal 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.
Default is enabled.
Comment: Use this secondary event to enter notes into the playlist. Comments are ignored
during transmission. Any text may be inserted into the title field of a comment. Default is
disabled.
System 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. Default is
enabled.
Back Timed System 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. Default
is enabled.
Mix/Wipe Tab
A Wipe effect requires a Wipe number. Each brand of Master Control Switcher may have
its 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 Air 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. Default is
disabled.
NOTE: The effect duration settings must match the switcher’s settings on certain
switchers. Refer to your switcher’s user manual.
Linking Tab
List is Keyed Master: Use this option when the secitonal lists are sparse and the exceptions
have keys to control them when they run. Default is disabled.
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.
Options Tab
See the Play List “Options Tab” on page 2-12.
Options Tab
See the Play List “Options Tab” on page 2-12.
Options Tab
See the Play List “Options Tab” on page 2-12.
Lookahead Tab
See “Count Lookahead” on page 2-15 under the Play List Lookahead tab.
Compiler Tab
Options
Skip Missing Material: 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. Default is disabled.
Log Errors: Check this box to cause all compile errors to be recorded into a logfile. Default
is disabled.
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.
NOTE: The password displays as a series of asterisks on the screen for security purposes.
The password is stored in encrypted form in the system registry.
The following example is a generic video disk. Your video disk may have slightly
different options. If necessary, refer to the User Notes for your device for complete
details on how to configure it.
Right-click on the configured device (see Figure 2-2 on page 2-4 and Figure 2-5 on
page 2-7), then choose Properties. A dialog box with multiple tabs appears. Use the left
and right arrows at the upper right to scroll through the other tabs. Each tab is
discussed in order here:
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 re-initialize if required. Default is enabled (checked).
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 Harris database has the exact durations. Default is disabled
(unchecked).
Ports Tab
Port Usage
Video Input Port In Disk. The video port number in the video disk that the Harris 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 0 closes the video port and makes it available to another
communications port. The valid range is from 0 to 16. Default is 1.
This must be configured for a video port number that is available in the video disk for the
disk to record. A zero in the port number specifies no port, and it cannot record. The
status will be OFFLINE if configured to zero. The disk port should only be configured to
zero 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
Video Output Port In Disk. 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 Harris 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.
The valid range is 0 to 16. Default is 1.
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). The ADC-100
NT 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 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
Disk Port Is Air Protected. Applies only to ports that use the air protect feature. This should
only be enabled on the Air disk port, not the Protect disk port. When enabled, the disk
port generates an error 10 frames after the disk does not respond that it is playing or the
disk stops communicating (which causes the air protect software to switch to the protect
disk). When disabled, disks have a 35 frame time out before an error will be generated.
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-100/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:
1. Assign both disk ports to the list as primary ports (air disk ports) not as protect ports.
2. 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:
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.
Prerolls/Postrolls Tab
Instant Prerolls
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 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 (described below). Four frames is the minimum preroll allowed
by the ADC-100. If not configured properly, the list may stop. If Instant Preroll is set
longer than the List Preroll, instant play is actually a delayed play. The ADC-100/NT
operations rely on list preroll settings configured through the Options menu, in Configure
Lists.
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.
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.
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 zero frames to
300 frames. This feature should not be used unless specified by the disk manufacturer or
Harris (refer to device-specific information). Four frames is the minimum preroll allowed.
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/record
command before playout or recording is performed. A setting of zero sends the play or
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.
Storage Tab
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).
Spots that are registered in the Lookahead are also 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.
Recording Tab
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.
Refer to the documentation on your disk to verify if your disk supports back-to-back
recording. 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.
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.
Prevent Recordings Greater Than (Mins). Specify a maximum length (in minutes) for any
recording.
Prevent Recordings Less Than (Mins). Specify a minimum length (in minutes) for any
recording.
Only Record Events with ID in. The disk will only record IDs whose first character is
between or equal to the limits. 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. Note that ’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. 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.
Segments Tab
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. 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 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).
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.
Archive Tab
Archive Configuration
Disk Has Archive. Default is enabled. It is recommended to keep this parameter enabled
even if a disk does not have an archive. Archives require ADC-100 to check if a disk can
get an ID from an archive. If a communication error has occurred such that an ID in the
disk is not known by the ADC-100, it checks with the disk if needed (if disabled, it
depends on the disk keeping the Device Storage Window to be up-to-date at all times).
When enabled, there can be a much larger communication load between ADC-100 and the
disk if many red events are in the play list, but the ADC-100 can handle virtually any load.
This feature is normally only disabled for testing and troubleshooting to reduce
communications, as the system can generally handle the load and automatically detects if
an archive is present.
Backup Play From Archive. Enable this parameter if the disk port supports this function
(most video disks do not support this function). When the parameter is enabled, and if the
disk uses an archive system as the source for spots, the disk plays a spot directly from the
archive if it is cued for playout before the spot is transferred from archive to the playout
disk. This occurs only if an event is placed on the playlist seconds before it is to go on air.
Normally, every spot is transferred from archive to the playout disk when the spot reaches
the lookahead area of the list (which usually happens hours before playout). Default is
disabled (unchecked).
E to E Tab
E to E Options
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. Enter the number of frames that the EE ON command should
be sent early. Default is 2. This box is ignored unless the Send Disk EE Mode Commands box
is enabled (checked).
Frames to Send EE Off Early. Enter the number of frames that the EE OFF command should
be sent early. Default is 3. This box is ignored unless the Send Disk EE Mode Commands box
is enabled (checked).
Reporting Tab
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).
Local Fibre Channel Handle. Default: zero - not used. Assign the same number that has been
assigned as the Content Servers Fibre Channel Handle, below.
The Content Server function allows program, or spot, material to be shared between
multiple video disks connected by a Fibre Channel Network. This function may be used
for Air and Protect operations, as well as standard operations. The Content Server acts as
a source device for all configured playout/protect disks located on the Fibre Channel by
ensuring that all material(required for playout) located on it is transferred to the
destination disks in order to ensure redundancy of material across multiple disks. This
function may also serve as a source library of material for distribution to one or more
downstream video disks to provide multiple air channel
Content Servers Fibre Channel Handle. Enter the same number that has been assigned as the
Content Server (source disk).
Disk To Use as Communications Port. Set this to match the ADC NT port number that the
copy commands will be sent to (Example: for a Profile, this value should be left at 0 (or
Self in the NT Server), which causes the copy command to be sent to itself.
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.
Diagnostics Tab
Diagnostics
Reinitialize.
ReVerify.
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
Manually take the port offline and online. Click the appropriate tab (Off Line or On Line).
The following example is a generic video tape recorder (VTR). Your VTR may have
slightly different options. If necessary, refer to the User Notes for your device for
complete details on how to configure it.
Right-click on the configured device (see Figure 2-2 on page 2-4 and Figure 2-5 on
page 2-7), then choose Properties. A dialog box with multiple tabs appears. Use the left
and right arrows at the upper right to scroll through the other tabs. Each tab is
discussed in order here:
VTR Parameters
General Tab
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 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: A stop command is issued to the VTR 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.
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 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.
The Edit Compensation values should be left at 2 unless you are experiencing problems. If
you intend to change these values, contact your Harris representative.
Diagnostics Tab
Inject Tape
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.
VTR Type
This tab displays information about the VTR, including the model number, protocol ID,
cassette size, analog/digital, and whether or not extended errors are reported.
Refresh
The following example is a generic cart machine. Your cart machine may have slightly
different options. If necessary, refer to the User Notes for your device for complete
details on how to configure it.
Right-click on the configured device (see Figure 2-2 on page 2-4 and Figure 2-5 on
page 2-7), then choose Properties. A dialog box with multiple tabs appears. Use the left
and right arrows at the upper right to scroll through the other tabs. Each tab is
discussed in order here:
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
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.
Edit Compensation
VTR 1-6: Click on a desired VTR to edit its compensation properties. The following box
appears:
The Edit Compensation values should be left at 2 unless you are experiencing problems. If
you intend to change these values, contact your Harris representative.
Four Channel Audio: Enable audio recording on four channels instead of the normal two
channels. Default is disabled (unchecked).
Options
Auto Change SOM and Duration: The SOM and Duration are automatically changed to
reflect the database record. The following box appears:
Delimiter Position: Set a delimiter position from between 0 and 20 spaces. This number
depends on the number of characters allowed in the ID field of the Sony barcode label.
Default is 5.
Tools Tab
NOTE: 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.
Bin Location (A1-A40): Select the slot in the cart machine to add the tape to or remove the
tape from.
Diagnostics Tab
Reinitialize Device
Click the Reinitialize button to reinitialize the device. Confirm your selection when
prompted.
The following example is a generic Master Control (M/C) switcher. Your switcher
may have slightly different options. If necessary, refer to the User Notes for your
device for complete details on how to configure it.
Right-click on the configured device (see Figure 2-2 on page 2-4 and Figure 2-5 on
page 2-7), then choose Properties. A dialog box with multiple tabs appears. Use the left
and right arrows at the upper right to scroll through the other tabs. Each tab is
discussed in order here:
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.
Latency
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.
Sources Tab
Crosspoint Name
Click the Add button to enter a source crosspoint name and number:
The Crosspoint Name is a mnemonic to help the operator identify the crosspoint. The
Number is the physical connection number of the crosspoint.
Destinations Tab
Crosspoint Name
Click the Add button to enter a destination crosspoint name and number:
System Inputs
Use the following parameters to indicate which crosspoints carry the black, colorbars, station
ID and initial input signals.
Black Input, Colorbars, StationID, Initial Input : Specify a number from 0 to 32768. Default is
0. These options are not used by the automation system unless the corresponding list
settings are enabled for Black Input and StationID. See Switch to Black and Station ID on Skip
under the “Options Tab” on page 2-12.
Reporting Tab
Backup Tab
Backup Switcher
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
Miscellaneous Tab
Audio Mode
Stereo/Mono Control: Select either stereo or mono for audio recording. Default is disabled
(unchecked).
Cascade Tab
Click the Add button to enter cascade data for the switcher:
Cascade Data
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.
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.
Switch Only devices are used in the ADC Device Server for a variety of purposes. The
first is to enable an event to be put into the transmission list which will switch a
crosspoint on a switcher and then count down some predetermined time and roll the
next event. By enabling the AUTO UPCOUNT on an event which is associated with a
switch only device, the event will count down to zero and then hold the list while
counting up. This allows a user to switch to a live or other feed, and count time until
a PLAY or SKIP is issued to the transmission list.
A switch only can be configured with a physical relay such that it can be used to
control a contact closure driven device. There are a variety of ways to use the physical
relay. The first way is to use a switch only with a relay, as a primary event on the list.
On these kinds of events the contact closure occurs at preroll time. This allows a
device such as a parallel-connected VTR to be started at preroll by the list.
Another way to use a switch only with a relay closure is as a secondary event. A
secondary event causes the relay to close at a designated time either before or after the
primary event starts running. The duration of the closure can be controlled directly by
the event. This can be used to tag a primary event with a video overlay, such as station
bug. This can also be used to generate a tone at some predetermined time before
entering a commercial break or returning to program material.
The following example is a generic switch-only device. Your switch-only device may
have slightly different configuration options. If necessary, refer to the User Notes for
complete details on how to configure it.
Right-click on the configured device (see Figure 2-2 on page 2-4 and Figure 2-5 on
page 2-7), then choose Properties. A dialog box with multiple tabs appears. Each tab is
discussed in order here:
◆ 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.
General Tab
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.
Prerolls/Postrolls Tab
Instant Prerolls
Use Instant Prerolls
Instant Preroll provides 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.
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.
GPI Card
Indicates which GPI card is connected to the device activated by this event
Contact Number
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. You must add 1 to the GPI board number when you enter the contact
number. 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. See “Instant Prerolls” on page 7-4.
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.
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.
The following example is a generic requester. 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.
Right-click on the configured device (see Figure 2-2 on page 2-4 and Figure 2-5 on
page 2-7), then choose Properties. A dialog box with multiple tabs appears. Use the left
and right arrows at the upper right to scroll through the other tabs. Each tab is
discussed in order here:
Device Name
The name of the requester. 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.
Weighting
Weighting is used to tell the requester to weight, by time, all requests. 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.
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 as-run logged).
Qualifiers Tab
Select the qualifications that this requester uses to determine if it should make requests for
media. 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.
Program - Spots
Events With Segments Only: Events must have segments in order to be recorded. Single
spots will not be recorded if this option is enabled. Default is disabled.
No Events With Segments: The opposite of the above option. Multi-segment IDs cannot be
recorded if this option is enabled. Default is disabled.
NOTE: If both of the above boxes are left at their default settings (both disabled), you can
record both single spot IDs and multi segment IDs.
Select a range (minimum and maximum) for allowable IDs to be recorded. Any IDs that
fall outside the specified range will not be recorded.
Routing Tab
Routing Modes
Use this tab to define the potential delivery mode for material to a destination device.
Baseband: Real time video signal (either analog or digital). Baseband includes SDI and
SPIT modes. Default is enabled.
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.
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.
Destination Tab
Specify the destination device (the device that receives the requested material). This device
should be a record port of a video disk server. Other devices are not supported in this release.
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.
Distributor Tab
Specify which GMT Distributor that this requester communicates with to acquire material.
The chosen distributor may reside on the same device server as the requester, or may be on a
different device server.
Server
Choose the server from the dropdown menu where the distributor 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.
The following example is a generic distributor. Your distributor may have slightly
different configuration options.
Right-click on the configured device (see Figure 2-2 on page 2-4 and Figure 2-5 on
page 2-7), then choose Properties. A dialog box with multiple tabs appears. Use the left
and right arrows at the upper right to scroll through the other tabs. Each tab is
discussed in order here:
Device Name
The name of the distributor. 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.
Routing Tab
Routing
Select one of the three available routing options (the default is Baseband):
Baseband: Real time video signal (either analog or digital). Baseband includes SDI and
SPIT modes. Default is enabled.
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.
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.
Source Tab
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.
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.
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.
With this option disabled, the missing media is skipped and media searching passes down
to the next available distributor (or returns an error to the play list).
NOTE: This option is only available with baseband and archive routing. Fibre mode is
not supported. See “Routing” on page 9-3.
Next Distributor
Specify an additional distributor for locating material. 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).
Add
Click the Add button to display a dialog box allowing you to enter crosspoints.
The following devices are supported by the Harris ADC Device Server at this time. As
the list is in a constant state of flux, we recommend that you visit our website at
www.harris.com for periodic updates to this list.
Video Disks
Standard Video Disk Ported Tested
Demo Video Disk Ported Tested
Profile Video Disk Ported Tested On Air
Caching Video Disk NOT TO BE PORTED
Demo Cache Vid Disk NOT TO BE PORTED
2-Port Vid Disk Ported
3-Port Vid Disk Ported
4-Port Vid Disk Ported
5-Port Vid Disk Ported
Demo 5-Port Vid Disk Ported
8-Port Vid Disk Ported
10-Port Vid Disk Ported
Quantel Clip Box In Progress
HP Buffer Video Disk Ported
Extended ID Video Disk Ported Tested On Air
Sony Stas10 Ported Tested On Air.
Sony Mav70 Ported
VTRs
Sony VTR Ported Tested On Air
Ampex VTR Ported Untested
Ampex Cassette Ported Untested
Demo VTR Ported Tested
Cart Machines
Sony BetaCart Ported Untested
Sony Flexicart Ported Tested
Demo BetaCart Ported Tested
Sony DVC-80 Cart Ported Untested
Sony BVC-80 Cart Ported Untested
Sony DVC-300 Cart Ported Untested
Sony BVC-400 Cart Ported Untested
Sony BVC-400B Cart Ported Untested
Sony DVC-500 Cart Ported Untested
Sony BVC-500 Cart Ported Untested
Sony DVC-1000 Cart Ported Untested
Sony BVC-1000S Cart Ported Untested
Sony BVC-1000A Cart Ported Untested
Demo DVC-1000 Ported Tested
Odetics TCS90 Ported Untested
Odetics TCS90M Ported Untested
Odetics TCS90LEM Ported Untested
Odetics TCS90A Ported Untested
Odetics TCS2000 Ported Untested
Odetics PROPHET Ported Untested
MARC SMART CART Ported Untested
MARC 100-MII Cart Ported Untested
MARC 400-MII Cart Ported Untested
MARC 800-MII Cart No DOS Support
MARC 1200-MII Cart No DOS Support
MARC 100-D3 Cart No DOS Support
MARC 400-D3 Cart No DOS Support
MARC 800-D3 Cart No DOS Support
MARC 1200-D3 Cart No DOS Support
Thomson PROCART Ported Untested
M/C Switchers
GVG 100 Series Ported Untested
BTS MCS 2000 Ported Untested
GVG Master21 DOS Only
MCS GVG Master21 Ported Untested
Utah MC 500 Ported Untested
BTS Saturn Ported Untested
Routers
Datatek D4300A Ported Untested
GVG Tenxl Ported Untested
GVG 20-TEN Ported Untested
GVG Horizon Ported Untested
GVG 440 Ported Untested
GVG 7000 Ported Untested
USI AVS Series Ported Untested
USI UDI Series Ported Untested
Datatek D2400 Ported Untested
BTS Venus Ported Untested
Image Video Ported Untested
Pro-Bel System 2/3 DOS Only Untested
Pro-Bel Router Ported Untested
Sony DVS-V1616 Ported Untested
Demo Router Ported Untested
Sony DVS-V3232 Ported Untested
Sony DVS-V6464 Ported Untested
Panasonic AU-CSW25 Ported Untested
GPI 8X1 Ported Untested
Sony 12X1 Ported Untested
Pesa 2400E Ported Untested
Leitch Xplus Series Ported Untested
Leitch 16x1 Ported Untested
Quartz Router Ported Untested
Telect Router Ported Untested
Adcom Router Ported Untested
NVision 1308 Router Ported Untested
NVision 3064 Router Ported Untested
NVision 3128 Router Ported Untested
NVision 3512 Router Ported Untested
BTS Mars Router Ported Untested
Audio Carts
Digicart Audio Cart Ported Tested On Air
Sony Mini Disk Ported
Enco DAD Ported Tested
Orban Airtime Ported Tested
Character Generators
Chyron MAX!> Ported (Does not support IDNAME)
Chyron MAX! 2Chan Ported
Chyron Codi Ported Tested On Air
(Weather Channel) as part of TADD
Presto CG Ported
Quanta Delta CG Not working under DOS
Chyron Scribe Ported
Chyron MAXINE Ported
Chyron Text Codi Ported Tested On Air
(Weather Channel) as part of TADD
Collage CG Ported
Chyron Infinite! Ported
Digital Graphix Deko Ported
Aston CG Ported
SERCOM
Serial Com Device Ported Tested
BFE Timer Ported
CPT Timer Ported
4CH Cavena Ported
DPM 700 Ported
16Ch Irdeto Ported
Wegener Ported Tested On Air
IBT VPS 9601 Ported
10 Ch Serial Com Device Ported
10 Ch NDS ESS Device Ported
Oxtel ImageStore Keyer Only Ported
IBT VPS 9701 Ported
IBT VPS 9702 Ported
SCREEN SRV2 Ported Tested
Still Stores
Sony SSCU-1000 Ported
Leitch Still Store Ported
Leitch Still Store 2Chan Ported
BTS VIDIFONT No DOS Support
Quantel Still Store Ported
Quantel PictBox 2C Ported
Bronto Still Store Ported
Ampex ESS-3 No DOS Support
Flash File Still Store Ported
Flash File SS 2Chan Ported To be tested
Leitch LogoMotion Ported Tested
Oxtel ImageStore Ported
Barcode Readers
Sony BVRB-10 Barcode Ported
PCWand Model 300 Ported Tested
GMT
RDRO Ported Untested
Requester Ported Tested
Distributor Ported Tested
Avalon Archive Manager Ported Tested
Annotators
Harris Annotator No DOS Support
Harris GPI Anno No DOS Support
Harris GPIA Anno No DOS Support
Demo Annotator No DOS Support
D G
Delete from disk, automatically when full, GMT list
3-8 Description, 2-6
Deleting devices, 2-5 GMT list parameters
Device drivers, 1-1 Events to Log tab, 2-21
Device name Options tab, 2-21
Cart machine, 5-1 Parameters tab, 2-21
Master control switcher, 6-1
Video disk, 3-1 H
VTR, 4-1 Hardware, optional, 5
Device server components, 3 How to configure a
Device server, illustration, 3 Device, 2-3
Device server, what is it?, 2 List, 2-6
Devices, configuring, 2-3
Devices, deleting, 2-5
Disk has archive, 3-12
I
Disk port is air protected, 3-4 ID match name, 3-2
Disk prerolls, 3-7 ID title mismatch, 5-4
Disk specific warnings, 3-14 Input crosspoints, 6-2
Disk to use as storage port, 3-4 Insert and remove tapes (demo devices
Distributor only), 5-4
General tab, 9-2 Installation, 1-1
Global Delete Targets tab, 9-5 Checkkey.exe, 1-3
Overview, 9-1 Command line parameters, 1-7
Routing tab, 9-2 Configuration software, 1-6
Source tab, 9-3 NT device drivers, 1-1
DOS to NT upgrade issues, 1-7 Requirements, 1-1
Dub list, 3 Server software, 1-4
Duration based lookahead, 2-14 Instant prerolls,use, 3-6
Introduction, 1
K N
Keep list threaded, 2-13 NT device drivers, 1-1
Keep media in VTR, 4-2
Keyer on/off, 2-17 O
Object oriented programming, 7
L On-air time, update, 2-13
Latency, 6-2 Only record events with ID in, 3-10
List, keep threaded, 2-13 Optional equipment
Lists, configuring, 2-6 Air Client workstation, 4, , 5
Local fibre channel handle, 3-15 Backup server, 4
Logically configuring your devices, 2-5 Control panel, 5
Lookahead, duration based, 2-14 Hardware and software, 5
Output crosspoints, 6-2
M Overview, 1
M/C switccer
Backup switcher, 6-6 P
M/C switcher Password, changing, 2-23
Audio mode, 6-7 Play hard hits, 2-12
Backup tab, 6-6 Play list
Cascade data, 6-8 Description, 2-6
Cascade tab, 6-7 Play list parameters
Destinations tab, 6-3 Events to Log tab, 2-15
Dimensions, 6-2 Linking tab, 2-20
Effect durations in frames, 6-5 Lookahead tab, 2-14
Effect Durations tab, 6-5 Mix/Wipe tab, 2-19
General tab, 6-1 Options tab, 2-12
Latency, 6-2 Parameters tab, 2-10
Miscellaneous tab, 6-7 Play lists, 9
Reporting tab, 6-5, , 6-6 Post-black, 2-23
System inputs, 6-4 Postroll, 3-6
System Inputs tab, 6-4 Pre-black, 2-23
Master control (M/C) switcher Prerolls, 3-7
Overview, 6-1 Prerolls, use instant, 3-6
Media Client, 3 Protect disk, configuring, 2-8
Media list
Descrtiption, 2-6
R SERCOM, A-5
Still stores, A-5
Recording, allow on video disk, 3-9
Switch-only, A-4
Recording, back to back, 3-9
Video disks, A-1
Reinitialize device (cart machine), 5-5
VTRs, A-1
Release tension when cued, 2-13
Switch to black, 2-12
Reporting tab, 6-6
Switcher latency, 6-2
Requester
Distributor tab, 8-6 Switch-only
General tab, 8-2 General tab, 7-3
Overview, 8-1 GPI Sheet tab, 7-5
Qualifiers tab, 8-3 Overview, 7-1
Routing tab, 8-4 Prerolls/Postrolls tab, 7-4
Requirements, 1-1 System components, 4
Rewind compile material, 2-11 System inputs, 6-4
Rewind spot, 2-10 Black input, 6-4
Rewind to first program segment, 2-10 Colorbars, 6-4
Routing Initial input, 6-4
Baseband, 9-3 StationID, 6-4
System requirements, 1-1
S
T
Secondary record event, 10
Tension after up counter, 2-13
Secondary record events, 3-9
Tension, release when cued, 2-13
Security
Thread after break, 2-13
Protecting the password, 1-6
Threaded, keep list, 2-13
Segment play/record, enable, 3-11
Traffic department, 3
Send disk EE mode commands, 3-13
Transfer switch, 4
Server, configuring, 2-1
Transmission lists, 9
Skip bad events, 2-13
Software, optional, 5
Spot, rewind, 2-10 U
Standbyoff for tension release, 4-2 Update event durations from disk, 3-2
Station ID on skip, 2-13 Update on-air time, 2-13
Stop disk play/record on init, 3-2 Upgrading from DOS to NT, 1-7
Supported devices Use instant prerolls, 3-6
Annotators, A-6 Use postroll, 3-6
Audio carts, A-4 Using in a broadcast environment, 3
Barcode readers, A-5
Cart machines, A-2 V
Character generators, A-4
Video disk
GMT, A-6
Additional port of same disk, 3-4
M/C switchers, A-2
Allow recording, 3-9
Routers, A-3
Archive tab, 3-12