advertisement
ADC™ Device Server and Config Tool
Installation and Operations
Global Media Transfer
Global Media Transfer
Overview
Global Media Transfer (GMT) is Automation Solutions’ technology for automatically copying media among the devices controlled by the automation system, as it is needed for playout on a Transmission list. If a video server assigned to a Transmission list does not have a piece of media available in its storage collection, GMT will attempt to find the material in other media devices and copy it to the playout video server. This process occurs in the background and requires little or no operator intervention.
Purchase Note: GMT is a for-purchase option to ADC systems. Contact your Automation Sales representative for details.
Reference Note: For more information reference the ADC GMT Configuration and Operations Guide document.
GMT Transfer Modes
GMT supports four transfer modes or mechanisms for copying media: fibrechannel transfers, baseband transfers, archive transfers and wide-area network FTP transfers.
Fibrechannel transfers – Media may be copied among video servers linked by a fibrechannel connection. Fibrechannel transfers are data transfers of compressed MPEG or JPEG files and occur faster than real time. Fibrechannel transfers may occur between devices controlled by multiple
Device Servers.
Archive transfers – Media may be copied to or from an archive device either by the normal background GMT process, or manually through the Media Client application. Archive transfers are data transfers of compressed MPEG or JPEG files and occur faster than real time. Archive transfers may be "single-hop" or "double-hop" transfers. Single-hop transfers copy the media from the archive directly to the requesting playout video server. Double-hop transfers copy the media from the archive to an intermediate video server, and then execute a fibrechannel transfer from the intermediate video server to the requesting playout video server. Archive transfers may occur between devices controlled by multiple Device Servers.
Baseband transfers – Media may be copied from a baseband source device, such as a cart machine,
VTR or a video server’s decoder port, to a video server’s encoder port. Baseband transfers are real-time transfers. Audio and video are automatically routed from the source device to the destination device according to the A/V routing tables configured for the GMT list. Baseband transfers may be "single-hop" or "double-hop" transfers. Single-hop transfers copy the media from the source device directly to the requesting playout video server. Double-hop transfers copy the media from the source device to an intermediate video server, and then execute a fibrechannel transfer from the intermediate video server to the requesting playout video server. Baseband transfers may only occur between devices controlled by a single Device Server. Only the fibrechannel "hop" of double-hop baseband transfers may occur between devices controlled by multiple Device Servers.
© 2015 Imagine Communications Corp. Proprietary and Confidential. 12/17/2015 | Page 440
ADC™ Device Server and Config Tool
Installation and Operations Global Media Transfer
WAN FTP transfers – Media may be copied among video servers using the video server’s native FTP transfer mechanism. This may be accomplished on a local-area or wide-area network. FTP transfers are data transfers of compressed MPEG or JPEG files and may occur faster than real time, depending on the bandwidth available on the wide-area network. Only the local video server, designated as the site manager, need be controlled by a Device Server.
GMT Components
GMT consists of three fundamental components: Requesters, Distributors and GMT lists.
Requesters – are virtual media devices assigned to a Transmission list and associated with destination devices (playout video servers). Media that is not available in the Requester’s destination device is requested from a Distributor (or Distributors) associated with source devices.
Requests are made when events enter the lookahead of a Transmission list and cannot be registered with any of the physical media devices assigned to that list.
Distributors – are virtual media devices assigned to a GMT list and associated with source devices.
These source devices may be video server ports, cart machines, VTRs, archives or ProxyFTP devices.
Distributors create and run events on the GMT list to accomplish the transfer of media to the requesting destination device. A single distributor can only support a single transfer mode, depending on the type of its associated source device, but may be "pointed to" or linked with other
Distributors supporting other transfer modes. By "chaining" Distributors in this manner, search paths may be created to pass requests through a number of Distributors of different types. The first
Distributor whose source device contains the requested media will execute a transfer - of that
Distributor’s type - to the Requester’s destination device.
GMT Lists – are modified Transmission lists used exclusively by GMT. Distributors assigned to the
GMT list will create events to execute transfers of one type or another. Non-real-time transfers
(fibrechannel, archive and WAN FTP) are executed by events registered and run by the Distributors.
Baseband transfers are created by Distributors but run by the physical media devices assigned to the
GMT list.
(OPTION) Push Lists are simply Transmission Lists used for a specific purpose other than on-air playout. Push Lists are used to "push" media from a source device to a destination device ahead of time. Under normal circumstances, Requesters request missing media at roughly the same rate as events enter the lookahead of the requesting Transmission List. GMT is driven by the Transmission
List and will fulfill requests for missing media as events undergo the registration process.
A Push List allows GMT to move ("push") media in advance of the Transmission List. The traffic department may create a "push list" log consisting of spots needed for air tomorrow. The log file may then be translated into a playlist file by the Traffic Translator and loaded into the Push List.
A Simple GMT System
The illustration below shows a simple fibrechannel GMT system.
A Requester assigned to the Transmission List queries the destination device for availability of media. If an ID on the Transmission List cannot be registered by the destination device (because the
ID does not exist in the destination device), the Requester passes a request to the Distributor.
The Distributor is assigned to the GMT List and is in communication with a source device. If the
Distributor, after querying its source device, finds that the media is available, it will create an event on the GMT List that will initiate a Fibrechannel transfer.
© 2015 Imagine Communications Corp. Proprietary and Confidential. 12/17/2015 | Page 441
ADC™ Device Server and Config Tool
Installation and Operations Global Media Transfer
The Distributor will run the event on the GMT List and the media will be copied from the source device to the destination device. Once the copy process has begun, the source device will inform the system that the media is now available for registration on the Transmission List and playout.
© 2015 Imagine Communications Corp. Proprietary and Confidential. 12/17/2015 | Page 442
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 9 Device Server Overview
- 9 About the Device Server
- 9 Clarification of Nomenclature
- 10 About Internet Protocol Version 6 (IPV6)
- 10 Minimum System Requirements
- 10 Supported Database
- 10 Supported OS Level
- 10 Maximum Number of Connections to the Device Server
- 10 Server Requirements
- 11 Client Requirements
- 11 Hardware Chassis
- 11 ADC Device Controller
- 12 Backup (Redundant) Device Controller
- 12 Supported (32-bit/64-bit) Drivers
- 12 Supported Broadcast Devices
- 13 Play lists and Transmission Lists
- 14 Automated Recording
- 14 Global Media Transfer
- 15 Operating as a Virtual Machine
- 15 Device Server Display Overview
- 16 Main Menu
- 16 File menu
- 16 View menu
- 16 Help menu
- 18 Installation
- 18 The Pre-installed Device Server Application
- 18 To Reinstall the OS (if required)
- 18 To reinstall the Device Server application (if required)
- 19 Confirm the Application Icon Command Line
- 20 BuildInformation.ini
- 20 To Install the Config Tool application (if required)
- 21 Rename the Application Icon (Optional)
- 22 IPv6 Setup
- 23 Operation
- 23 To Start the Device Server
- 24 To Exit the Device Server
- 24 To View Connections
- 25 To Close a Hung API connection
- 25 To Show IP Address Connections
- 26 Help Information
- 26 To Launch the Help System
- 27 To View About Information
- 27 Configuration from the Device Server Display
- 27 To Configure a Server Handle
- 27 About the Server Port for Device Server v12.22 and higher
- 28 To Modify the Port Number:
- 28 To Disable/Enable Cloning
- 28 Using Alternate Handle
- 28 Change Rules:
- 29 Disable cloning feature
- 29 Enable cloning feature again
- 29 Monitor List Updates and Actions
- 31 Configuring Devices using Configuration Manager
- 31 About Device Types
- 31 Media Devices
- 32 Storage Collection of Available Media
- 32 Media Head
- 32 Non-Media Devices
- 33 Special Device Types
- 33 About Device Control
- 33 RS-422 Control
- 34 8 Port Serial Card LEDs
- 34 8-port serial board (rear)
- 34 16 port Serial Card LEDs
- 35 16-port serial board (top)
- 35 Ethernet Control
- 36 GPI Control
- 36 To Change the Config Tool Password
- 37 To Start Device Configuration
- 38 Main Menu Options
- 38 File menu
- 39 Edit menu
- 39 View menu
- 40 Help menu
- 40 To close a hung API connection from Config Tool
- 40 To configure the System Reference Clock (Clocking)
- 42 About Drop Frame / Non Drop Frame Settings
- 42 About Device Server Clocking
- 43 Sequence 1:
- 44 Sequence 2:
- 44 Sequence 3:
- 44 About Consuming Chronos Timings over a Network
- 46 To Configure GPI Control
- 47 To Configure Enhanced GPI Triggering
- 48 GPI Card Support
- 49 To Change/Configure the GPI Adapter/Device Type
- 49 Use External Network Attached GPI/O Hardware
- 50 To configure skipping a commercial break after a GPI (input)
- 50 In Operation
- 51 To Configure this functionality
- 52 To configure Sync Skip after a GPI (input)
- 52 To Configure this functionality
- 52 Basic Functionality
- 53 To Set Device Server ‘Keep Alive Time’
- 54 To Assign a Device to a Device Channel
- 54 (Option) To Remove a Device from a Device Channel
- 55 Video Disk Configuration (VDCP Driver)
- 55 To Configure a Video Disk (VDCP Driver)
- 74 DTP Insertion Driver
- 75 Summary of function lists
- 75 To configure the DTP Insertion Driver
- 82 Video Disk Configuration (API/IP Driver)
- 82 Additional Port of Same Disk (w/ Air Protect)
- 83 To Configure a NEXIO Video Disk (API/IP Driver)
- 83 Driver Limitations
- 83 Multi-Stream Driver Limitations
- 84 About NEXIO ARC (Aspect Ratio Conversion) override
- 84 Automation Network Consideration
- 84 NEXIO high-speed Mediabase poll method
- 84 To configure the NEXIO Driver (API/IP)
- 108 To Configure an Omneon Spectrum Video Disk (API/IP Driver)
- 108 Multi-Stream Driver Limitations
- 109 Example: The following example configuration is used to illustrate the impact of ADC limitations. If two Ports of an Omenon device are assigned to the same list and have the same type (for example, both ports are Player), two possible configurations c...
- 109 Impact on Feature/Functions:
- 109 Recommendations:
- 109 To configure the Omneon Driver (API/IP)
- 131 To Configure a GVG K2 Video Disk (API/IP Driver)
- 131 About Loop Playback Mode option
- 131 To configure the GVG K2 Driver (API/IP)
- 152 To Configure the mCapture Driver
- 155 N+1 Video Server Redundancy Configuration (Virtual Pool Driver)
- 156 (N+M) Protection Concept
- 156 Driver Configuration
- 159 List Assignment
- 160 To configure A/V tables for a general pool device
- 161 VTR Configuration (General)
- 161 To Configure a VTR
- 168 Cart Machine Configuration (General)
- 169 To Configure a Cart Machine
- 185 M/C Switcher Configuration (General)
- 185 To Configure an M/C Switcher
- 210 Router Configuration (General)
- 210 To Configure a Router
- 234 Switch Only Configuration (General)
- 235 About Switch Only Device
- 235 About Switch Only (missing) Configuration
- 236 About Extended Switch Only Device
- 236 To Configure a Switch Only Device
- 239 Requestor Configuration (General)
- 239 About Requestors
- 239 About the Content Handler Requestor
- 240 To Configure a Requestor
- 253 Distributor Configuration (General)
- 253 About Distributors
- 254 To Configure a Distributor
- 266 Proxy Device Configuration (General)
- 266 To Configure a Proxy Device
- 271 Transcode Configuration (General)
- 271 To Configure a Transcode Device
- 275 Archive Configuration (General)
- 275 To Configure an Archive Device
- 279 Video Effect Device Configuration (General)
- 279 To Configure a Video Effect Device
- 281 Still Store Device Configuration (General)
- 281 To Configure a Still Store Device
- 289 Character Generator Device Configuration (General)
- 289 To Configure a Character Generator Device
- 292 Audio Disk Cart Configuration (General)
- 293 To Configure an Audio Disk Device
- 296 Serial Device Configuration (General)
- 296 To Configure a Serial Device
- 301 Advanced Device Configuration (General)
- 301 To Configure an Advanced Device
- 317 For SCTE-104 Macros only
- 323 SCTE driver initialization
- 324 SCTE-104 Driver Polling
- 326 For Selenio Macros only:
- 330 Barcode Reader Configuration (General)
- 330 To Configure a Barcode Reader
- 332 VChip Encoder Configuration (General)
- 332 To Configure a VChip Encoder Device
- 335 Database Update Redirector Support Configuration (General)
- 335 To Configure Database Update Redirector Support
- 336 Configuring Moxa NPorts and Legacy Serial Ports
- 336 Configure Ports Count
- 337 Review Ports Usage
- 337 Port Usage
- 338 Device Driver Configuration
- 339 About Warning Messages
- 340 Configuring AB4 Ports
- 340 Example device config
- 340 Ports Count
- 341 Port Usage
- 342 Device Driver Configuration
- 342 About Warning Messages
- 344 Configuring Device Assignments
- 344 Assigning Devices to Lists
- 344 To Start List Configuration
- 345 Main Menu Options
- 345 File menu
- 345 View menu
- 346 Help menu
- 346 To Assign a Device to a List
- 346 Assigning a Breakaway Device to a Breakaway List
- 347 Add Breakaway Device to a Channel
- 347 Assign a Switch Only Breakaway Device to a Breakaway List
- 348 Assigning a Protect Device
- 348 To Assign a Protect Device to a List
- 349 Configuring a GPI Trigger
- 349 To Configure a GPI Trigger
- 352 Configuring List Types
- 352 About Play lists and the Traffic Translator
- 353 Examples:
- 353 About List Configuration
- 354 Configuring Transmission List Options
- 354 Event Registration
- 355 The Lookahead
- 356 Record Lists and GMT Push Lists
- 356 To Configure Transmission List Options
- 380 About Dynamic List Selection for API triggering
- 384 Configuring Media List Options
- 384 To Configure Media List Options
- 398 Configuring GMT List Options
- 398 To Configure GMT List Options
- 413 Configuring Compile List Options
- 413 To Configure Compile List Options
- 429 About Breakaway Lists
- 430 To View Breakaway Lists in the Config Tool
- 430 About Runway Lists
- 431 Operation
- 435 Configuring Audio / Video Routing Tables
- 435 About AV Routing Tables
- 435 To Configure A/V Routing
- 437 To Configure Preview A/V Routing
- 440 Global Media Transfer
- 440 Overview
- 440 GMT Transfer Modes
- 441 GMT Components
- 441 A Simple GMT System
- 443 Cloning
- 443 Introduction to ADC Cloning
- 444 List Redundancy
- 444 About List Redundancy
- 444 The List Redundancy Process
- 445 Functions
- 446 Diagnostics and Troubleshooting
- 446 Troubleshooting techniques
- 446 Device Server Debugging Logs
- 447 Configuration Manager tools
- 447 Device Status window
- 448 GPI diagnostics
- 449 Real-time diagnostic traces
- 449 Distributor diagnostics
- 452 Diagnostic log file
- 453 Archive diagnostics
- 453 ProxyFTP diagnostics
- 454 VDCP diagnostics
- 454 Diagnostics tab
- 454 Diagnostics Window
- 455 Diagnostic Monitor
- 455 To Set up Diagnostic Monitoring
- 456 TraceView
- 457 To view a trace file
- 457 Example Data Trace
- 458 Application and exception errors
- 458 The ADC List Dump Tool
- 458 GUI application
- 459 To use the GUI
- 459 Console application
- 460 To use the Console
- 461 Appendix A: Error Messages
- 461 Device Server Errors
- 475 WARNING-SPOT SHORTER THAN SCHEDULED: <ID> - The spot in the video server is too short to play well the next event.SQL Server Database Error Messages
- 476 For SQL Server Error Definitions