ELECTRA VS Convergent Video System
Version 05.10
User Manual
Rev. A Copyright © 2017 Harmonic Inc. All rights reserved.. Contents
Preface ...... 15
Chapter 1 Overview ...... 21 Purpose ...... 22 Main Features ...... 24 Hardware Delivery...... 25 Chassis ...... 25 Overview ...... 25 Front Panel ...... 25 Rear Panel ...... 26 Software Only Delivery ...... 29 Overview ...... 29 Virtualization Delivery ...... 30 Overview ...... 30 Virtualization Technologies ...... 30
Chapter 2 Installation and Startup ...... 31 Hardware Delivery...... 32 Chassis Overview ...... 32 Front Panel ...... 33 Rear Panel ...... 35 HP Documentation ...... 38 Unpacking ...... 40 Mounting in Rack (Recommendations) ...... 40 Ventilation ...... 40 Cabling...... 40 Power Supply and Protective Ground ...... 41 Power Supply Cord(s)...... 41 Installing the Device (Steps)...... 42 1RU Device...... 42 10RU and 6RU Devices...... 43 Mounting the Front Panel on 10RU Device...... 43 Mounting the Front Panel on 6RU Device...... 46 Powering Up ...... 50 6RU and 10RU Device Specifics ...... 50 Performing the Initial Settings ...... 50 Preparing the Connection ...... 50
Electra VS - Version 05.10 3 User Manual - Rev. A Contents
Accessing the Web Interface for the First Time ...... 51 Checking Node Status...... 51 Performing the IP Configuration ...... 52 Preparing the Definitive Connection...... 52 Establishing the Definitive Connection...... 53 Setting the Date and Time ...... 54 Selecting the Supervision Protocol...... 54 Starting the Operation ...... 56 Software Only Delivery ...... 57 Hardware Recommendation ...... 57 Unpackaging...... 57 Installation ...... 57 Preparing your Network Architecture...... 57 Preparing the System Private LAN...... 57 Creating the Bootable USB Flash drive ...... 58 Preparing the Hardware Platform ...... 58 Installing the Version on the First Node (Master Node)..... 58 Configuring the Interface of the First Node (Master Node) 61 Accessing the Web Interface for the First Time ...... 63 Adding the Second Masterisable Node in Electra VS ...... 65 Asking a License for Electra VS...... 67 Declaring a License for Electra VS ...... 67 Adding Non Masterisable Node(s) to Electra VS...... 68 Defining Processing Capacity of the Nodes ...... 68 Finalizing Network Configuration ...... 68 Starting the Operation ...... 68 Virtualization Delivery ...... 69 Hardware Recommendation ...... 69 Unpackaging...... 69 Installation ...... 69 Installing the First Node (Master Node) ...... 69 Installing the OVA on the first Node (Master Node)...... 72 Configuring the Interface of the First Node (Master Node) 75 Accessing the Web interface for the First Time ...... 76 Adding the Second Node in Electra VS (Masterisable Node) 76 Asking a License for Electra VS...... 76 Declaring a License for Electra VS ...... 76 Adding Non Masterisable Node(s) to Electra VS...... 76 Defining Processing Capacity of the Nodes ...... 76 Finalizing Network Configuration ...... 77 Starting the Operation ...... 77
Chapter 3 Web User Graphical Interface ...... 79 Workflows and Jobs Concept...... 80 Workflow Management ...... 81 Public, Private and Protected Parameters ...... 82 Using Predefined Workflows...... 82 Building your Own Workflows ...... 83 Job Management ...... 84
4 Electra VS - Version 05.10 User Manual - Rev. A Contents
Creating Job...... 84 Hot Folder...... 86 Operating Instructions (Tutorial)...... 87 GUI Overview ...... 88 Reaching the GUI...... 88 Using the GUI...... 89 General Organization...... 89 Customizing the Display...... 89 Commonly Used Elements...... 90 Basic Operations ...... 92 Creating a Job from a Predefined Workflow...... 92 Setting Job Parameters Based on the Predefined Workflows 96 Live SD-HD Encoder...... 96 Live SD-HD Transcoder ...... 101 Live Web TV Transcoder ...... 106 Hot Folder...... 112 Configuring the Workflow...... 112 Configuring the Hot Folder...... 112 Using the Hot Folder...... 113 Using the Snapshot View...... 114 Advanced Operations ...... 117 Creating an MPTS Job ...... 117 Creating an MPTS Job with Statmux...... 121 Creating your Own Workflows ...... 125 Creating a Workflow from Scratch ...... 125 Adapting a Sample Workflow...... 137 Creating Sub-Workflows ...... 141 Introduction ...... 141 Example ...... 141 Creating Workflows with Multi-Instantiable Processing Components...... 145 Configuring an SDI System ...... 149 Recommended SDI Redundancy Topologies...... 149 Declaring SDI Sources...... 151 Using SDI Sources ...... 156 SDI Redundancy Configuration ...... 159 Definitions about the SDI Redundancy ...... 159 SDI Redundancy Settings...... 160 SDI Redundancy Monitoring...... 164 GUI Description...... 165 Header Tab...... 165 Setup Tab...... 167 Setup/Identity...... 167 Setup/IP ...... 168 Network interface profiles...... 168 LANs...... 169 Routes ...... 170 DNS ...... 171 System Private LAN...... 171 IGMP ...... 172 Setup/Network Storage...... 173 Setup/Hot Folder...... 173
Electra VS - Version 05.10 5 User Manual - Rev. A Contents
Setup/Monitoring ...... 176 Setup/Date & Time ...... 177 Setup/User Accounts...... 178 Setup/Download ...... 180 Setup/Logs ...... 181 Export...... 181 Purge...... 183 Supervision ...... 184 Setup/Advanced ...... 184 Hardware Tab ...... 185 Hardware/Nodes Panel ...... 185 Hardware/SDI Panel ...... 188 SDI Cards ...... 188 SDI Matrices ...... 188 SDI Redundancy Mode...... 189 Workflows Tab...... 190 Left Area ...... 190 Buttons...... 190 Search ...... 191 List...... 191 Description ...... 193 Right Area ...... 193 Buttons...... 193 Copy and Paste Options ...... 194 Workflow Import and Export Options ...... 195 Categories and Colors ...... 196 Jobs Tab ...... 198 Jobs List Tab...... 198 Buttons...... 198 Jobs List Array ...... 199 State ...... 201 Filters and Sorting Options ...... 202 Job Details...... 202 SDI Redundancy Monitoring Tab...... 206 Snapshot Tab ...... 207 Logs Tab ...... 208 Purpose ...... 208 Logs Array...... 208 Filters and Sorting Options...... 208 Advanced ...... 210 Statmux Tab ...... 211 Statmux Editing ...... 212 Simulation Tab ...... 213 Purpose ...... 213 Operating Instructions ...... 213
6 Electra VS - Version 05.10 User Manual - Rev. A Contents
Step 1: Create a Simulation...... 214 Step 2: Define an Hardware Configuration...... 214 Step 3: Launch the Jobs ...... 217 Step 4: Add Hardware Resource (if Required)...... 218 Step 5: Check the Fail-over...... 222 Step 6: Export/Import Simulation...... 223 Step 7: Consult the Licenses Required for Job Processing 225 Step 8: Exit Simulation Mode ...... 226 Console Tab ...... 227 Footer Bar ...... 228 Workflow Library ...... 229 Processing Component Parameters Overview ...... 231 Processing Component Parameters Array ...... 232 Processing Component Input/Output Tabs ...... 234 Publishing Inputs and Outputs ...... 234 Specific Input and Output Parameters ...... 234 Multi-Instance ...... 235 Processing Component Common Parameters ...... 236 Conditioned Parameters Display Button...... 236 Publication Mode Switch Button ...... 236 Link Tool ...... 236 Processing Component Specific Parameters...... 240 Inputs...... 240 TS over IP Input...... 240 TS Video Extractor ...... 243 TS Audio Extractor...... 247 TS Component Extractor...... 249 TS SCTE 35 Extractor...... 252 SDI Input ...... 253 MP4 File Input...... 256 MP4 Video Extractor ...... 257 MP4 Audio Extractor...... 258 RTMP Input...... 259 RTMP Video Extractor...... 260 RTMP Audio Extractor ...... 261 MXF File Input ...... 262 MXF Video Extractor...... 263 MXF Compressed Audio Extractor...... 264 MXF Uncompressed Audio Extractor...... 265 PS File Input...... 266 PS Video Extractor ...... 267 PS Audio Extractor...... 268 YUV File Input...... 269 Decoding ...... 270 Audio Decoder...... 270 Dolby® E Decoder...... 270 Video Decoder...... 272 Preprocessing ...... 275
Electra VS - Version 05.10 7 User Manual - Rev. A Contents
Audio processing ...... 275 Tx audio interface AES67 ...... 278 Rx audio interface AES67...... 278 SCTE 35 Conditioner...... 280 Chunker...... 281 DVB Subtitle Inserter ...... 285 Mosaic Editor ...... 286 Video format converter ...... 288 Video overlay ...... 296 Encoding ...... 309 MPEG-2 Encoder ...... 309 H.264 AVC Encoder...... 311 H.265 HEVC Encoder...... 315 H.265 HEVC Hardware Encoder ...... 318 MPEG-1 Layer 2 Encoder...... 319 AAC Encoder ...... 320 Dolby Digital Encoder...... 321 Outputs...... 324 TS Video Packetizer ...... 324 TS Audio Packetizer ...... 325 TS Multiplexer...... 327 TS over IP Streamer...... 332 MPTS over IP Output ...... 334 TS File Output ...... 337 RTMP...... 338 HLS...... 340 HLS File Output ...... 352 Smooth Streaming ...... 356 Smooth Streaming File Output...... 363 MPEG-DASH ...... 366 MPEG-DASH File Output ...... 374 MP4 File Output ...... 378 Selector and Choice Tools...... 380 Dialog Description ...... 380 Parameter ...... 380 Conditions ...... 380 Choice...... 380 Selector ...... 381 Description of the Predefined Favorite Workflows...... 383 Description of the Live SD-HD Encoder Predefined Favorite Workflow ...... 383 Description of the Live SD-HD Transcoder Predefined Favorite Workflow ...... 383 Description of the Live Web TV Transcoder Predefined Favorite Workflow ...... 385 Layout of the Sample Workflows...... 387 Layout of the File-to-File Transcoding Sample Workflow 387 Layout of the IPTV SDI Input Sample Workflow ...... 388 Layout of the IPTV SDI Input HD to SD Sample Workflow 388 Layout of the IPTV TSoIP input Sample Workflow ...... 388 Layout of the Mosaic - 6 HD Inputs Sample Workflow..... 389 Layout of the WebTV - HLS WebDAV Sample Workflow. 390
8 Electra VS - Version 05.10 User Manual - Rev. A Contents
Layout of the WebTV - Smooth Streaming to IIS Server Sample Workflow ...... 391 Recommended Settings...... 392 Recommended MPEG-2 Settings in CBR ...... 392 All / Complex Contents...... 392 Simple / Movie Contents...... 393 Recommended MPEG-2 Settings in VBR (Statmux) ...... 394 Recommended H.264 Settings in CBR ...... 394 All / Complex Contents...... 395 Simple / Movie Contents...... 395 Recommended H.264 Settings in VBR (Statmux)...... 396 Recommended H.264 Settings in WEBTV...... 397 All / Complex Contents...... 398 Simple / Movie Contents...... 399 Recommended H.265 Settings in CBR ...... 400 All / Complex Contents...... 400 Simple / Movie Contents...... 401 Recommended H.265 Settings in VBR (Statmux)...... 402 Recommended H.265 Settings in WEBTV...... 403 All / Complex Contents...... 404 Simple / Movie Contents...... 404 Recommended H.265 Settings in Live UHD...... 406
Chapter 4 Servicing ...... 407 Common...... 408 Managing the Recovery Points ...... 408 Overview ...... 408 Recovery Points Management...... 408 Upgrading the Software Release ...... 410 Requesting a new license File ...... 411 Declaring a new License File ...... 412 Hardware Delivery...... 413 Managing the Recovery Points ...... 413 Upgrading the Software Release ...... 413 Requesting a New License File ...... 413 Declaring a New License File ...... 413 Unmounting the Front Panel on a 1RU Server ...... 413 Adding a Diskless Node to Electra VS ...... 415 Enabling the New Diskless Node (6RU and 10RU) ...... 415 Connecting to the ILO Interface ...... 415 Enabling the Node ...... 416 Configuring the BIOS of a Diskless Node ...... 416 For a 6RU or 10RU blade: Accessing the BIOS...... 416 For 1RU Devices: Accessing the BIOS...... 421 Requesting a New License File...... 427 Declaring a New License File...... 427 Adding a 1RU Diskless Node to Electra VS ...... 427 Replacing a Hot Swappable Part...... 429
Electra VS - Version 05.10 9 User Manual - Rev. A Contents
6RU and 10RU Server ...... 429 1RU Server ...... 431 Replacing a Diskless Node in Electra VS...... 433 Configuring the BIOS of the New Node ...... 433 Replacing a Node ...... 433 Blade Center - Upgrading OnBoard Administrator firmware 436 Connecting to the ILO Interface...... 436 Blade Center - Upgrading Flex10 firmware...... 437 Connecting to the ILO Interface...... 437 Software Only Delivery ...... 439 Managing the Recovery Points ...... 439 Upgrading the Software Release...... 439 Requesting a New License File ...... 439 Declaring a New License File ...... 439 Creating a Bootable USB Flash Drive...... 439 Installing the Version on the First Node (Master node)...... 439 Adding Masterisable Node to Electra VS...... 439 Adding Non Masterisable Node(s) to Electra VS...... 439 Replacing a Masterisable Node in Electra VS...... 442 Virtualization Delivery ...... 444 Managing the Recovery Points ...... 444 Upgrading the Software Release...... 444 Requesting a New License File ...... 444 Declaring a New License File ...... 444 Adding a Masterisable Node to Electra VS...... 444 Adding a Slave Node to Electra VS ...... 445 Replacing a Masterisable Node in Electra VS...... 446
Chapter 5 Troubleshooting ...... 449 Troubleshooting Procedures ...... 450 Exporting Information for Customer Support ...... 450 Modifying a Workflow from a Text Editor...... 451 Exporting Logs ...... 451 Using the Console...... 451 Providing Remote Access to the Electra VS...... 452 Frequently Asked Questions...... 453 Why cannot I instantiate my job whereas there is space on the Electra VS? ...... 453 I do not see my workflow in the list when I want to create a job. Why?...... 453 I cannot create a workflow. Why?...... 453 I cannot create a job. Why? ...... 453 When I want to launch a job, I get a "Job is waiting: license not available" message. What should I do? ...... 454 I cannot modify the system parameters. Why?...... 454 I modified a workflow parameter, but it was not applied to the currently running jobs. Why?...... 454 My Windows network storage directory is not accessible. What should I do? ...... 454
10 Electra VS - Version 05.10 User Manual - Rev. A Contents
The SNMP agent does not work. What should I do? ...... 455 It takes a long time to launch the GUI. Why?...... 455 I want to remove the bonding of one interface on my 1RU platform. How can I do this? ...... 457
Chapter 6 Customer Service ...... 459 Support Center Contacts...... 460 Warranty...... 461 Services ...... 462 Spare Parts...... 462 Returning Equipment ...... 462 Repackaging for Shipment ...... 462 Long Term Product Support...... 463 Recycling the Product...... 463
Chapter 7 Tools ...... 465 NodeBench...... 466 Overview ...... 466 Operation ...... 466 Launching VOS Flex NodeBench on New Hardware Resource 466 Using VOS Flex NodeBench ...... 467 Equipment Setup...... 469 Overview ...... 469 Operation ...... 469 Launching Equipment Setup ...... 469 Connecting to a Device ...... 470 Setting Device Parameters...... 472 HP Monitoring Tools (6RU and 10RU Devices)...... 473 Connecting to the HP Monitoring Tools...... 473 Method #1: Connecting via the iLO Port in DHCP...... 473 Method #2: Connecting on the DHCP Network using the IP Address of the Device ...... 474 Method #3: Connecting After Manually Configuring the IP Address of the Device...... 475 Performing the IP Configuration from the HP Interface...... 477 Accessing the Interconnect Bays’ Management Console 477 Configuring the Interconnect Bays...... 479 Saving your Configuration...... 479 More Information...... 480
Electra VS - Version 05.10 11 User Manual - Rev. A Contents
Appendix A Technical Specifications ...... 481 Hardware Delivery Specifications ...... 482 Electrical, Thermal and Mechanical Specifications...... 482 Electra VS 10RU...... 482 Electra VS 10RU (AC 200-240V single phase)...... 482 Electra VS 10RU (AC NA Triple Phase @ 208VAC) ...... 486 Electra VS 10RU (AC INTL Triple Phase @ 230VAC).... 490 Electra VS 10RU (AC JPN Triple Phase @ 200VAC)..... 494 Electra VS 10RU (DC 48V) ...... 497 Electra VS 6RU...... 501 Electra VS 6RU (AC 100-240V single phase @ 115VAC) 501 Electra VS 6RU fitted with 8 system storage and processing blades...... 501 Electra VS 6RU (AC 100-240V single phase @ 230VAC) 502 Electra VS 6RU (DC 48V) ...... 503 Electra VS 1RU...... 504 Electra VS 1RU (AC 100-240V single phase)...... 504 Blade Center Physical Interface Specifications...... 505 HP 1RU Hardware available Configurations ...... 506 Software Only Requirements Specifications...... 512 Virtualization Requirements Specifications...... 512 Common Specifications ...... 513 Input Specifications...... 513 Live TS Over IP Inputs...... 513 Live RTMP Inputs...... 513 SDI Inputs (Depending on Server Type)...... 513 SDI Matrices ...... 515 File Formats ...... 516 Decoding Specifications ...... 518 Video Decoding ...... 518 Audio Decoding ...... 520 Processing Specifications...... 522 Video Processing ...... 522 Audio Processing...... 523 Encoding Specifications ...... 524 Video Encoding...... 524 Audio Encoding ...... 527 Teletext, Subtitles and Closed Captions Processing ...... 530 Output Specifications...... 531 Live Output...... 531 File Output...... 534 Control-Command Specifications...... 537 IP TV Latency ...... 538 Security Specifications ...... 539 Standard Compliance ...... 540 Ordering Guide ...... 544
12 Electra VS - Version 05.10 User Manual - Rev. A Contents
Appendix B SNMP Management ...... 551 MIB Description ...... 552 Trap Descriptions ...... 553 Register/Unregister a Manager to Receive Traps...... 555 Get the Active Log List or Closed Log List ...... 556 Registering SNMP Manager on the GUI...... 557 Enabling HP Blade Center SNMP Agent...... 558
Appendix C Safety Instructions ...... 559
Appendix D Regulatory Notices ...... 561
Appendix E Logs ...... 563 Log Categories...... 564 List of Logs...... 565
Appendix F Network Settings ...... 573 Hardware Delivery - 6RU and 10RU devices ...... 574 Blades...... 574 Internal Switches (Flex10)...... 574 Interface Bonding ...... 574 10RU Device ...... 574 6RU Device ...... 575 VLAN Tagging ...... 575 Internal Switches & Software Configuration Consistency.... 575 Flex10 ...... 576 External Connector Description...... 576 FLEX10 ...... 576 FLEX10-D ...... 576 Grouping Possibilities ...... 576 Flex10 Configuration ...... 576 How to Use a Configuration File...... 576 Description of Configuration Files...... 577 Multicast Management ...... 579 Heterogeneous System Configuration ...... 579 Interface Bitrates ...... 580 Bitrate Allocation on 10RU Interfaces ...... 580
Electra VS - Version 05.10 13 User Manual - Rev. A Contents
Bitrate Allocation on 6RU Interfaces...... 580 Bitrate Allocation Rules...... 581 Hardware Delivery - 1RU device...... 582 Network Configuration ...... 582 Software Only Delivery ...... 583 Virtualization Delivery ...... 583
Appendix G ESAM ...... 585 ESAM Implementation ...... 586
Appendix H Aspect Ratio Conversions ...... 587 Conversions according to input AFD and output display aspect ratio...... 588 Conversions according to default strategies and output display aspect ratio...... 590 Specific output AFD according to source or output display aspect ratio ...... 591
Glossary ...... 593
14 Electra VS - Version 05.10 User Manual - Rev. A Preface
Standard Documentation Set
The Electra VS documentation set consists of:
A User Manual
A Quick Start Guide
A Web Services SOAP API Getting Started document
The Electra VS User Manual contains background information about the Electra VS Convergent Video System, and describes operating procedures. This manual can be used while learning about Electra VS, and for enhancing your basic knowledge of the product.
The Electra VS Quick Start Guide contains information about installing and configuring the equipment.
The Electra VS Web Services SOAP API documentation provides you with the basic information you need to use the product’s SOAP API.
Software Version
This manual covers the functionality of the software version 05.00 of the Electra VS product.
This manual continues to be relevant to subsequent software versions where the functionality of the equipment has not changed. When a new software version changes the functionality of the product, a new version of this manual is provided.
Electra VS - Version 05.01 15 User Manual - Rev. A Preface — About this Manual
About this Manual
This manual is written for Operators of the Electra VS.
This manual should be kept in a safe place for reference for the life time of the equipment. If passing the equipment to a third party, please ensure to pass all relevant documentation including this manual.
The manual is organized into the following chapters and appendices:
Chapter 1 ’Overview’ gives a general description of the equipment and its main features. It also identifies the controls, indicators and connectors on the front and rear panels.
Chapter 2 ’Installation and Startup’ provides the procedures required for Electra VS installation and initial configuration. It also contains a list of HP documents to which you can refer for more information on the blade centers (Hardware delivery).
Chapter 3 ’Web User Graphical Interface’ details how to use the Web Browser Graphical User Interface.
Chapter 4 ’Servicing’ describes how to add or replace nodes of your system (Hardware delivery), and how to add licenses.
Chapter 5 ’Troubleshooting’ describes the procedure to follow when you face any problem with the equipment.
Chapter 6 ’Customer Service’ provides you with the customer service contacts and information on how to return a product.
Chapter 7 ’Tools’ describes the Equipment Setup tool delivered on the DVD-ROM with the product. It describes also the NodeBench tool.
Appendix A ’Technical Specifications’ gives specifications of the device, device compliance, declarations of conformity and ordering guide to order the Electra VS and its options.
Appendix B ’SNMP Management’ explains how to set the SNMP community string and the access rights. You will also find MIB description, how to register the SNMP Manager on the Electra VS Graphical User Interface etc. It also describes the MIB used to configure and monitor the equipment.
Appendix C ’Safety Instructions’ gives instructions related to risk of fire, electric shock or injury to persons. This important section is available in English, German and French versions.
Appendix D ’Regulatory Notices’ provides device compliances.
Appendix E ’Logs’ gives the list of alarms visible in the Logs panel of the GUI (XML file).
Appendix F ’Network Settings’ provides detailed information on the network configuration.
16 Electra VS - Version 05.01 User Manual - Rev. A Preface — About this Manual
Appendix G ’ESAM’ provides information on how Electra VS is implementing the API Signal Confirmation and Conditioning for CableLabs® ESAM (Event Signaling and Management).
Appendix H ’Aspect Ratio Conversions’ provides the default conversion performed and the AFD value set according to the input AFD and aspect ratio.
A ’Glossary’ can be found at the end of the manual.
Electra VS - Version 05.01 17 User Manual - Rev. A Preface — Conventions Used in This Manual
Conventions Used in This Manual
Warnings, Cautions and Notes
Heed Warnings
All warnings on the product and in the operating instructions should be adhered to. The manufacturer cannot be held responsible for injuries or damages where warnings and cautions have been ignored or taken lightly.
Read Instructions
All the safety and operating instructions should be read before this product is operated.
Follow Instructions
All operating and use instructions should be followed.
Terms in this Manual
Safety-related statements appear in this manual in the following form:
Warning statements identify conditions or practices that may result in personal injury or loss of life.
Caution statements identify conditions or practices that may result in damage to equipment or other property, or which may cause equipment crucial to your business environment to become temporarily non-operational.
Notes provide supplementary information. They are highlighted for emphasis, as in this example, and are placed immediately after the relevant text.
18 Electra VS - Version 05.01 User Manual - Rev. A Preface — Important Notice
Formatting
Naming conventions for the interface elements and Windows elements in this manual follow the Microsoft Manual of Style, Third Edition. Naming conventions for MPEG-2, ATSC, and DVB structures follow the conventions derived from the standards documents listed in Appendix A ’Technical Specifications’. In addition, the following formatting conventions apply to this manual:
Bold text refers to specific interface elements that you are instructed to select, click, or clear. Example: “Select Settings from the Configuration menu”.
Blue text refers to document names, sections, figures or tables. Example: “Refer to Section ’Warnings, Cautions and Notes’ on page 13 for more information”. Mono-spaced text can indicate the following: Text you enter from a keyboard Example: “Enter administrator for your login and administrator for your password”. Paths to components on your hard drive Example: “The MIB is at the following location: C:\MIB”.
Important Notice
Harmonic reserves the right to make corrections, modifications, enhancements, improvements and other changes to its products or services at any time and to discontinue any product or service without notice.
Electra VS - Version 05.01 19 User Manual - Rev. A Preface — Trademarks
Trademarks
and the double-D symbol are registered trademarks of Dolby Laboratories. Pro Logic and Surround EX are registered trademarks of Dolby Laboratories. Supply of this Implementation of Dolby technology does not convey a license nor imply a right under any patent, or any other industrial or intellectual property right of Dolby Laboratories, to use this Implementation in any finished end-user or ready-to-use final product. It is hereby notified that a license for such use is required from Dolby Laboratories.
MPEG-2 / MPEG-4 AAC audio encoding technology is authorized by the Fraunhofer IIS license (http://www.iis.fraunhofer.de/amm/).
All other tradenames referenced are service marks, trademarks, or registered trademarks of their respective companies.
20 Electra VS - Version 05.01 User Manual - Rev. A Chapter 1 Overview
Introduction
This chapter gives a general description of the Electra VS and its main features.
In this Chapter
’Purpose’ ...... page 22
’Main Features’ ...... page 24
’Hardware Delivery’ ...... page 25
’Software Only Delivery’ ...... page 29
’Virtualization Delivery’ ...... page 30
Electra VS - Version 05.10 21 User Manual - Rev. A Chapter 1 ’Overview’ — Purpose
Purpose
The Electra VS Video System is a fully-integrated video solution tailored for all new convergent applications such as Web TV and Over-The-Top (OTT) service delivery, as well as traditional television delivery (Terrestrial /Satellite/IPTV).
The Electra VS provides a flexible way to design workflows. The Workflow Builder allows the creation of live, file-based and mixed workflows, for any kind of network.
Combining all the major audio/video codecs and the latest adaptive streaming formats, the Electra VS provides a unique answer to IPTV delivery, Mobile 3G/4G, Web TV streaming and OTT services broadcasting.
Simplicity: one unique graphical user interface lets you control and monitor hundreds of channels simultaneously. With built-in 10GigE switches, racking and cabling nightmares vanish.
Reliability: built around highly resilient IT platforms equipped with hot-swappable, redundant components, the Electra VS provides native load-balancing and system redundancy to avoid downtime.
Scalability: from a single-server to multi-blade systems, the Electra VS is designed to scale and grow with your business.
Flexibility: the Electra VS allows heterogeneous architectures (SDI and IP inputs depending on the server type) and simultaneous live and off line encoding.
The Electra VS can be delivered in different ways:
Hardware delivery: In this way the Electra VS software is delivered installed on an HP server (1RU/6RU/10RU platform)
Software only delivery: In this way the Electra VS software is delivered with an Operating System and must be installed on a HP/Dell/Cisco/Fujitsu server not provided.
Virtualization delivery: In this way a Virtual machine including an Operating system and Electra VS application is delivered.
22 Electra VS - Version 05.10 User Manual - Rev. A Chapter 1 ’Overview’ — Purpose
Figure 1-1. Electra VS applications
Electra VS 1RU
Electra VS 10RU
Electra VS - Version 05.10 23 User Manual - Rev. A Chapter 1 ’Overview’ — Main Features
Main Features
Premium video quality
Support of multiple video/audio codecs
Support of MPEG transport stream
Adaptive Bit Rate:
Adobe Flash
Apple HTTP Live Streaming
Microsoft Smooth Streaming
MPEG-DASH
Video resolution up to 3840 x 2160 (UHD)
Progressive and interlaced modes
Multiple output formats per channel
Scalable number of input channels
Scalable number of output profiles
Advanced video and audio pre-processing
Integrated content protection
HTTP Centralized Operation
Workflow Builder
SOAP/Web services for external interfacing
Integrated load balancing and failover
IPV4 support
SDI/HD-SDI and router management available only with Hardware delivery and 1RU HP server.
Interface with Placement Opportunity Information System (POIS) compliant with CableLabs® ESAM (Event Signaling and Management) for ad-insertion.
Black out management and slate insertion on WebTV applications.
24 Electra VS - Version 05.10 User Manual - Rev. A Chapter 1 ’Overview’ — Hardware Delivery
Hardware Delivery
Chassis
Overview
The hardware delivery of the Electra VS product is proposed on two HP chassis: 1RUx19” or 10RUx19”. The Electra VS software can also be deployed on hardware used by VS7000 product but no more available with Electra VS. These chassis (6RU chassis, G7/G8 1RU chassis) are still described in this manual but not available for sale.
Physical characteristics are as follows:
Hot swappable power supplies
Hot swappable fans
Hot swappable processing units
Hot swappable IP switches
Cooling: front-rear airflow
The HP chassis are described in the Chapter 2 ’Installation and Startup’, section ’Hardware Delivery’ on page 25.
Front Panel
1RU Front Panel
Figure 1-2. Electra VS 1RU server front panel
Electra VS - Version 05.10 25 User Manual - Rev. A Chapter 1 ’Overview’ — Hardware Delivery
6RU Front Panel
Figure 1-3. Electra VS 6RU server front panel
10RU Front Panel
Figure 1-4. Electra VS 10RU server front panel
Rear Panel
1RU Rear Panel
Figure 1-5. Electra VS G7 1RU server rear panel
slot 1 slot 2
slot 0
26 Electra VS - Version 05.10 User Manual - Rev. A Chapter 1 ’Overview’ — Hardware Delivery
Figure 1-6. Electra VS G8 1RU server rear panel
slot 1 slot 2
slot 0
Figure 1-7. Electra VS G9 1RU server rear panel
slot 0 slot 1 slot 2
6RU Rear Panel
Figure 1-8. Electra VS 6RU server rear panel
Electra VS - Version 05.10 27 User Manual - Rev. A Chapter 1 ’Overview’ — Hardware Delivery
10RU Rear Panel
Figure 1-9. Electra VS 10RU server rear panel
28 Electra VS - Version 05.10 User Manual - Rev. A Chapter 1 ’Overview’ — Software Only Delivery
Software Only Delivery
Overview
Electra VS is a software-based solution leveraging Harmonic’s dedicated Video Operating System: VOS Flex. It operates on off-the-shelf IT servers. For operators owning their servers, Electra VS is available as Electra VS Software Edition.
More informations on requirements and examples of platforms are available in Appendix A ’Technical Specifications’, section ’Software Only Requirements Specifications’ on page 512.
Electra VS - Version 05.10 29 User Manual - Rev. A Chapter 1 ’Overview’ — Virtualization Delivery
Virtualization Delivery
Overview
Electra VS is a software-based solution leveraging Harmonic’s dedicated Video Operating System: VOS Flex. It operates on off-the-shelf IT servers.
For operators owning virtualization infrastructure, Electra VS is available as Electra VS Virtualized Edition.
Virtualization Technologies
Electra VS Virtualized edition can be delivered as a virtual machine. Today, it supports the following virtualization technology:
- VMWare technology
More informations on minimum Hardware and Virtualization requirements are available in Appendix A ’Technical Specifications’, section ’Virtualization Requirements Specifications’ on page 512.
30 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 Installation and Startup
Read and follow the important safety information in section ’Safety Instructions’ on page 559, noting especially those instructions related to risk of fire, electric shock or injury to persons.
Introduction
This chapter provides the procedures required for Electra VS installation and initial configuration in the different cases of delivery.
It also contains a list of HP documents to which you can refer for more information on the blade centers.
In this Chapter
’Hardware Delivery’ ...... page 32
’Software Only Delivery’ ...... page 57
’Virtualization Delivery’ ...... page 69
Electra VS - Version 05.10 31 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
Hardware Delivery
Chassis Overview
The hardware delivery of the Electra VS product is proposed on three HP chassis: 1RUx19”, 6RUx19”, or 10RUx19”.
Physical characteristics are as follows:
Hot swappable power supplies
Hot swappable fans
Hot swappable processing units
Hot swappable IP switches
Cooling: front-rear airflow
For more information on the specifications, refer to Appendix A ’Technical Specifications’ on page 481.
The sections below show the front and rear panels of the devices. For a full description of the device, refer to the HP documentation:
For a 1RU server, see:
G7: on the DVD-ROM delivered with the Electra VS
G8: http://www8.hp.com/h20195/v2/GetDocument.aspx?docnam e=c04128242
G9: http://www8.hp.com/h20195/v2/GetDocument.aspx?docnam e=c04447818
For a 6RU server, see: http://www8.hp.com/h20195/v2/GetHTML.aspx?docname=c04123 379
For a 10RU server, see: http://www8.hp.com/h20195/v2/GetHTML.aspx?docname=c04229 580
32 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
Front Panel
Figure 2-1. Electra VS 10RU server front panel
Figure 2-2. Electra VS 6RU server front panel
Figure 2-3. Electra VS 1RU server front panel
Electra VS - Version 05.10 33 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
The 1RU front panel is equipped with a Slide-out System Insight Display (SID) panel which shows the equipment status.
Figure 2-4. Slide-out System Insight Display on the Electra VS 1RU server front panel
This SID features LEDs that help you to diagnose a server failure.
When an internal component fails, the indication is made on an internal component LED (amber) and on the front panel. If the item is serviceable without removing the server hood, as in the case of a redundant power supply failure, the External Health LED will illuminate. If the item is serviceable by removing the hood, as in the case of a fan failure, the Internal Health LED will illuminate.
If no failures have occurred, the system health LEDs will be green. If a failure has occurred, but a redundant feature has enabled the system to continue running, the LED will be amber. If the failure is critical and is/has caused the system to shutdown, the LED will be red. These LEDs serve as local indicators for several failure conditions. Insight Manager will continue to report these, and many other failure conditions, as well.
34 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
Rear Panel
Figure 2-5. Electra VS 10RU server rear panel
Figure 2-6. Electra VS 6RU server rear panel
Figure 2-7. Electra VS G7 1RU server rear panel
slot 1 slot 2
slot 0
Electra VS - Version 05.10 35 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
Figure 2-8. Electra VS G8 1RU server rear panel
slot 1 slot 2
slot 0
Figure 2-9. Electra VS G9 1RU server rear panel
slot 0 slot 1 slot 2
Depending on the server, the content of the slots may vary:
On a G7 server:
Slot 0: 4 Ethernet interfaces
Slot 1: optional additional Ethernet board
Slot 2: optional SDI board
Figure 2-10. G7 1RU server rear panel connector
36 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
On a G8 server:
Slot 0: 4 Ethernet interfaces
Slot 1: optional SDI board (dual, quad or octo)
Slot 2: optional additional Ethernet board or SDI board (octo)
Figure 2-11. G8 1RU server rear panel connector
Optional board D Optional SDI board A, B or C (network) or E (SDI)
Network connectors VGA Serial/ iLO USB Optional Power 4 to 1 output* COM port* ports* redundant power supply port* * not used supply unit connectors
HD/SD SDI dual board*: HD/SD SDI quad board*: IN2 IN1 IN4 IN3 IN2 IN1 * Other connectors are A B not used. Depends on IN1 IN2 board model IN1 IN2 IN3 IN4
SD SDI octo board: Optional additional network SD SDI octo board: IN5IN6IN7IN8 connectors (8 to 5) IN13 IN14 IN15 IN16
C D E
IN1 IN2 IN3 IN4 IN9 IN10 IN11 IN12
Electra VS - Version 05.10 37 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
On a G9 server:
Slot 0: optional SDI board (dual, quad or octo) or 3G-SDI quad board
Slot 1: optional SDI board (octo) or optional hardware accelerator board for UHD encoding
Slot 2: Optional hardware accelerator board for UHD encoding
Figure 2-12. G9 1RU server rear panel connector
HP Documentation
HP provides a number of documents for their blade centers. These documents are available on the HP Web site, but you can also find them on the DVD-ROM delivered with the Electra VS:
HP BladeSystem c7000 Enclosure - Setup and Installation Guide
HP BladeSystem c3000 Enclosure - Setup and Installation Guide
HP Troubleshooting Guide
HP Virtual Connect - Ethernet Networking Scenario Cookbook
BladeSystem for ProLiant Release Set Compatibility Table
HP BladeSystem Onboard Administrator - User Guide
HP Virtual Connect for c-Class BladeSystem - Setup and Installation Guide
38 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
HP Virtual Connect for c-Class BladeSystem - User Guide
HP Virtual Connect Manager Command Line Interface for c-Class BladeSystem - User Guide
HP BladeSystem c3000 Enclosure Quick Specs
HP BladeSystem c7000 Enclosure Quick Specs
HP Proliant BL460c G7 Quick Specs
HP Proliant DL360 G7 Quick Specs
HP Proliant BL460c G8 Quick Specs
HP Proliant DL360p G8 Quick Specs
HP Proliant DL360 G9 Quick Specs
HP Proliant DL460c G9 Quick Specs
Electra VS - Version 05.10 39 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
Unpacking
Table 2-1 lists the accessories that are always shipped with the device. Use this list to ensure that the order is complete.
More accessories can be delivered depending on options you chose.
Table 2-1. List of accessories delivered with the device
Quantity Description
n Electra VS blade center or server: 10RU, 6RU or 1RU
n Bays (if the device is a blade center)
n Ethernet connectors (if the device is a blade center)
n Power cords
1 Cable to connect a screen, a keyboard and a mouse to a bay (if the device is a blade center)
4 or 8 If you ordered an SDI Quad board, 4 SDI female BNC cables If you ordered an SDI Octo board, 8 SDI female BNC cables
1 Front panel
1 DVD-ROM
Mounting in Rack (Recommendations)
Rack mounting is not mandatory for Electra VS but the ventilation and safety requirements given in this section must be observed in all cases.
Ventilation
Please refer to the recommendations provided by HP.
Cabling
It is essential to separate the power supply cables from the signal cables. When facing the rear of the rack (as the device is connected via the rear panel), the power supply cables must be guided to the right of the chassis and the signal cables to the left.
40 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
Power Supply and Protective Ground
Power Supply Cord(s)
Never supply a power supply unit which is not in the chassis. The built-in overload protection cannot be accessed or reset.
Specifications
The AC mains power cords are only shipped with the device if ordered.
For DC supply units, use power cords suitable with the HP specifications.
Connecting AC Mains Power Supply Cord(s)
Power Supply End
The connection panel should comply with the legislation in force in the country of installation. The connection panel must be positioned in the rack in such a way that the plug and power cord(s) are within easy reach for switching off purposes.
For (each) mains inlet, the wiring system must feature overload and earth fault protection and a bipolar cut-off device or a differential circuit breaker. If in doubt, contact a qualified electrician.
Electra VS End
Plug the power cord(s) into the mains inlet.
Electra VS - Version 05.10 41 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
Installing the Device (Steps)
Depending on the type of device, follow the steps below to install the device and perform its initial configuration.
1RU Device 1. Mount the device in a rack. 2. If not already installed, mount the front panel shipped with the server a. Engage the right side of the front panel in the notches of the server.
Figure 2-13. Mounting the front panel – Engaging the right side of the front panel
b. Press the left side of the front panel to fix it.
Figure 2-14. Mounting the front panel – Press the left side on the front panel
42 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
10RU and 6RU Devices 1. Install the blade center in its final position.
If you need to move the blade center, it must be empty.
2. On the front panel, install the blades in the blade center: the blades and bays in the blade center are numbered (stickers). Insert blade #1 in bay #1, blade #2 in bay #2, etc. 3. Install the power supply units. 4. For 6RU devices: slide-out the BladeSystem Insight Display, which will later show the equipment status. 5. Install the front panel. The procedure is not the same for 10RU and 6RU devices.
Mounting the Front Panel on 10RU Device
The following items are shipped with the device:
1 front panel (left or right opening) in a plastic bag
1 top left hinge + 1 bottom left hinge + 1 top right hinge + 1 bottom right hinge mounted on the chassis
1 screw at the top of the top left hinge + 1 screw at the bottom of the bottom left hinge
To install the front panel, the left or right hinge must be removed depending on whether left- or right-opening is required. This operation is explained below.
Procedure to Install a Left-Opening Front Panel (Hinges on Left)
Figure 2-15. Front panel with left-opening
Electra VS - Version 05.10 43 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
1. Remove the top left hinge from the chassis (see below).
Figure 2-16. Removing the left hinge
Remove the screw.
left side
2. Install the front panel in the left hinges as follows:
Position the top left hinge so that its top screw inserts into the hole in the top part of the front panel.
Figure 2-17. Inserting the top left hinge in the top part of the front panel
Raise the front panel and top left hinge together so that the bottom screw of the bottom left hinge inserts into the hole in the bottom part of the front panel.
Figure 2-18. Inserting the front panel into the bottom left hinge
44 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
3. Re-mount the top left hinge and front panel together on the chassis.
Figure 2-19. Remounting the top left hinge
upright upright of the chassis of the chassis
top left Front 2. Fix with a top hinge panel screw. left hinge 1. Push the top left Left side panel hinge against the Left side panel upright of the chassis. of the chassis of the chassis
Procedure to Install a Right-Opening Front Panel (Hinges on Right)
Figure 2-20. Front panel with right-opening
1. Remove the top right hinge as shown in Figure 2-23 (this time with the right hinge).
Electra VS - Version 05.10 45 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
2. Remove the top and bottom screws from the left hinges then screw them tightly onto the right hinges (see below).
Figure 2-21. Moving the top and bottom screws from the left hinges to the right hinges
Move the top screw from the top left hinge to the top right hinge
Move the bottom screw from the bottom left hinge to the bottom right hinge
3. Install the front panel in the right hinges as shown in Figure 2-24 and Figure 2-25 (this time with the right hinges). 4. Re-mount the top right hinge and front panel together on the chassis as shown in Figure 2-26 (this time with the top right hinge).
Mounting the Front Panel on 6RU Device
The following items are shipped with the device:
1 front panel (left or right opening) in a plastic bag
1 left hinge and 1 right hinge mounted on the chassis
2 screws at the top and bottom of the left hinge
To install the front panel, the left or right hinge must be removed depending on whether left- or right-opening is required. This operation is explained below.
46 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
Procedure to Install a Left-Opening Front Panel (Hinges on Left)
Figure 2-22. Front panel with left-opening
1. Remove the left hinge from the chassis (see below).
Figure 2-23. Removing the left hinge
left side
Remove the 6 screws.
2. Install the front panel in the left hinge as follows:
Position the left hinge so that the top screw inserts into the hole in the top part of the front panel.
Figure 2-24. Inserting the left hinge in the top part of the front panel
(top)
Electra VS - Version 05.10 47 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
Bend (slightly) the hinge in order to insert the bottom screw into the hole in the bottom part of the front panel.
Figure 2-25. Bending slightly the hinge to insert it in the bottom part of the front panel
(bottom)
3. Re-mount the left hinge and front panel together on the chassis.
Figure 2-26. Fixing the left hinge
1. Push the left hinge left side against the upright of the chassis.
2. Fix with 6 screws.
Procedure to Install a Right-Opening Front Panel (Hinges on Right)
Figure 2-27. Front panel with right-opening
1. Remove the right hinge as shown in Figure 2-23 (this time with the right hinge).
48 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
2. Remove the top and bottom screws from the left hinge then screw them tightly onto the right hinge.
Figure 2-28. Moving the top and bottom screws from the left hinge to the right hinge
Move the top screw from the left hinge to the right hinge
Move the bottom screw from the left hinge to the right hinge
3. Install the front panel in the right hinge as shown in Figure 2-24 and Figure 2-25 (this time with the right hinge). 4. Re-mount the right hinge and front panel together on the chassis as shown in Figure 2-26 (this time with the right hinge).
Electra VS - Version 05.10 49 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
Powering Up
Check that Electra VS is not yet connected to a LAN. Factory-set IP addresses may cause disturbance (address conflict) on the LAN when Electra VS is switched on.
Connect the power cord(s).
6RU and 10RU Device Specifics
If needed, configure the power supply management (refer to the HP Blade System Enclosure Setup and Installation Guide that corresponds to the Electra VS, provided on the DVD-ROM).
On initial start-up, use the front panel screen to check the status of the equipment. To do so: 1. Press OK to activate the display. 2. Select Health Summary from the menu. 3. Check that all indicators are green.
Performing the Initial Settings
Preparing the Connection 1. Connect the system private LAN of all the platforms composing the Electra VS to a single GigE switch:
For blade centers: insert an SFP coupler on interface x1 of the first internal switch of the blade center, and connect it to the GigE switch.
Gigabit copper couplers are not fast-Ethernet compliant. Make sure you use a device that is able to process Gigabit.
For 1RU devices: connect NIC 1 to the GigE switch.
50 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
2. Connect a PC in DHCP on the GigE switch.
The GigE switch should be isolated from the network as the presence of a DHCP server could cause conflicts. Only the Electra VS node of the current system shall be linked to the internal system network. Do not connect any additional equipment on the network. If you install two Electra VS systems, each system should have its own system private LAN.
3. To ensure a proper multicast management in the system private LAN, it must contain an IGMP Querier. The switch must act as such. The IP source of the IGMP querier shall exist in the system private LAN. 4. If the Electra VS includes at least one 10RU HP blade center and others hardware platforms, to ensure a proper multicast management in the System Private LAN, it must contain an IGMP Querier. The switch must act as such. The IP source of the IGMP querier shall exist in the system private LAN.
Accessing the Web Interface for the First Time
To access the Web interface, proceed as follows: 1. Open a Web browser.
2. Type the 192.168.250.9 IP address in the address bar and press Enter. 3. Use the following account information: Login: admin Password: admin
If you cannot connect to the 192.168.250.9 IP address, which might happen if the factory-set IP address has been modified, use the Discover feature of the equipment set-up tool. See Chapter 7 ’Tools’ on page 465.
Before launching the signed GUI application, the client station checks through Java (starting in version 1.7.xx) that the related certificate has not been revoked by the issuing authority. If the Java setting does not allow internet access, the certificate revocation check attempt will fail after about 1 minute. The starting applet will be run but only after this time. Solutions to reduce this startup time exist. They are given in the section ’It takes a long time to launch the GUI. Why?’ on page 455 in the '’Troubleshooting’' chapter. Please refer to this section.
Checking Node Status 1. Select the Hardware tab.
Electra VS - Version 05.10 51 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
2. Go to the Nodes category. 3. Check that:
All nodes present in the device are displayed in the list in the GUI.
The status of each node is OK.
Performing the IP Configuration 1. Select the Setup tab. 2. Go to the IP category. 3. Set the Control (X2 on 6RU and 10RU devices) network on the control-command network:
If there are n nodes in the Electra VS, you need n consecutive addresses, plus one for supervision.
Set the following parameters: - Address - Mask - Gateway (optional) - First address: first address of the n consecutive addresses - Supervision address 4. Set the Data 1 (X3 on 6RU and 10RU devices) network on the data network:
If there are n nodes in the Electra VS, you need n consecutive addresses.
Set the following parameters: - Address - Mask - Gateway (optional) - First address: first address of the n consecutive addresses 5. Click Apply.
Preparing the Definitive Connection
Once you have made the IP configuration from the GUI: 1. Disconnect the supervision PC from the GigE switch. 2. Depending on the composition of the Electra VS: If the Electra VS contains several 10RU blade centers or a mix of 1RU and 10RU devices:
52 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
Please refer to Appendix F ’Heterogeneous System Configuration’ on page 579 for connection recommendations. For a stand-alone blade server: a. Remove the SFP coupler from interface X1.
b. Insert an SFP coupler on interfaces X2 and X3 of the two internal switches of the blade center.
You could perform the operation on one internal switch of the blade center only but there would be no redundancy.
c. Connect interfaces X2 on the control-command network, on a single switch or two switches if redundancy is required.
d. Connect interfaces X3 on the data network, on one unique switch or on two switches if they are redunded. For 1RU devices: a. Disconnect NIC 1 from the GigE switch. b. Depending on the hardware configuration: 1RU including two SD SDI octo boards - Connect NIC 3 on the data network. Other hardware configurations - Connect NIC2 on the control-command network. - Connect NIC3 on the data network.
Establishing the Definitive Connection 1. From a supervision PC connected on the control-command network, open a Web browser. 2. Type in the address bar the supervision IP address that you configured earlier and press Enter. 3. Use the following account information: Login: admin Password: admin
Electra VS - Version 05.10 53 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
Setting the Date and Time
Date settings must be performed during the installation phase. Modifying the date (except the time zone or the daylight saving time option) while the services are on-air may cause temporary disturbances on those services.
To set the date and time: 1. Select the Setup tab. 2. Go to the Date & time category. 3. Choose the method that should be used to get the UTC:
Set it manually: enter the date and time in the UTC date and time field.
Get it from one or more NTP servers: add the IP address(es) of the server(s) to the NTP synchronized list.
Get it from one PTP Grandmaster clock server: add the LAN number and the Domain number of the server. 4. Choose the time zone to use from the drop-down list. 5. Indicate if you want to adjust the time automatically for Daylight Saving Time.
Figure 2-29. Date and time settings
6. Click Apply.
Selecting the Supervision Protocol
If you want to secure the protocol used to communicate with the Electra VS 1. Select the Setup tab.
54 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
2. Go to the Monitoring category. 3. The LAN protocol access category lets you indicate the protocols that are available in the external and management LANs. You can allow or block the HTTP, HTTPs, SSH and SNMP connections.
It is recommended to allow the protocols only in the management LAN in order to avoid security breaches.
Figure 2-30. Selecting the LAN protocol access
1. If you select HTTPS only and you are currently in HTTP, you will have to stop the connection and restart a new one. 2. If HTTPS only is activated, the webTV outputs with get mode will not work on the corresponding network. The get mode corresponds to Use local web server set to true for Microsoft Smooth Streaming and DASH outputs or Stream available on local web server set to true for HLS output, and/or ESAM conditioning set to true in the Chunker processing component. 3. Our Electra VS in HTTPS is secured by a certificate, therefore the explorer will warn you that the security certificate was issued for a different website's address. You can check that it is effectively issued for www.harmonicinc.com.
Electra VS - Version 05.10 55 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Hardware Delivery
Starting the Operation
Refer to Chapter ’Web User Graphical Interface’, section ’Operating Instructions (Tutorial)’ on page 87.
56 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Software Only Delivery
Software Only Delivery
Hardware Recommendation
For operators owning their servers, Electra VS is available as Electra VS Software Edition.
More information on requirements and examples of platforms are available in the Electra VS-Checklist documentation delivered in the DVD-ROM with the product.
Unpackaging
Table 2-2 lists the content that are shipped with the product.
Table 2-2. Content delivered with the product
Quantity Description
1 DVD-ROM
A bootable USB flash drive (minimum 8 Gbits) is mandatory to install the Electra VS.
Installation
Follow the steps below to install the device and perform its initial configuration.
Preparing your Network Architecture
Read all the recommendations related to the network in the IP architecture document delivered with the product in the DVD-ROM directory Documentation/SDI&IP architecture.
Prepare your network environment and the network addressing plan.
Preparing the System Private LAN
The first physical interfaces of the Electra VS platforms will be connected to a single GigE switch. The GigE switch shall be use for the Electra VS System Private LAN:
The GigE switch should be isolated from the network as the presence of a DHCP server could cause conflicts.
Electra VS - Version 05.10 57 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Software Only Delivery
The System Private LAN shall be reserved to the nodes of one Electra VS. Do not connect any additional equipment on the network. If you install two Electra VS, each one should have its own System Private LAN.
If the Electra VS includes at least one blade center and others hardware platforms, to ensure a proper multicast management in the System Private LAN, it must contain an IGMP Querier.
Creating the Bootable USB Flash drive
In order to install the version on the hardware platform you shall create a bootable USB Flash drive that will launch automatically the installation of the Electra VS at boot. 1. Download an utility that lets you write an image to USB Flash Drive (for example imageUSB): http://www.osforensics.com/tools/write-usb-images.html 2. Plug the USB Flash drive in the PC. 3. Copy the installation image from the DVD-ROM "Software-only Delivery" directory to the PC. 4. Start the utility. 5. Write the image on the USB Flash drive.
Preparing the Hardware Platform 1. Select the node that will be one of the two masters of the Electra VS. 2. If you have two disks Install hardware RAID 1 if you want to use a hardware RAID. Otherwise install two RAID 0 if you want to use the software RAID. Note: It is possible to install Electra VS on a platform with only one disk but it is not recommended. In this case install only one disk with RAID 0. 3. Check the platform boot parameters (generally, click F11 at reboot). Check that the platform is ready to boot to USB Flash drive.
Installing the Version on the First Node (Master Node)
Install the version using the bootable USB Flash Drive 1. Power down the server
58 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Software Only Delivery
2. Plug the USB Flash drive in the master server. 3. Power up the server. 4. Select Install Electra VS on local host:
RUN VS7000 (for evaluation using NodeBench tool) Install VS7000 on Local host
5. Partition disks a. Selection of the partitioning method. Depending on the hardware configuration: - If you have installed an Hardware RAID, select Use one entire disk (Hardware RAID or single disk) or if you have installed two independent disks, select Use two entire disks in a Software RAID1 array
b. Selection of the disk to partition: - Select the HDD disk of the hardware platform. Be sure to not select the USB Flash drive disk. - Press Enter.
Electra VS - Version 05.10 59 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Software Only Delivery
c. Finish the partitioning - Select Finish partitioning and write changes to disk. - Press Enter.
d. Select Ye s and press Enter.
The installation of the Electra VS starts.
60 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Software Only Delivery
6. When the installation is complete, remove the USB Flash drive, select Continue and press Enter in order to reboot.
The platform restarts.
Configuring the Interface of the First Node (Master Node)
Configure the first interface of the master node to be in the System Private LAN and set the management address.
1. Connect in Guest mode (User = THVNguest Pwd = THVNpwd0). Note that by default us keyboard is loaded. 2. Execute the following commands: loadkeys [fr|us]: load the keyboard translation table if required. setSystemIP: declare the node as master node. It may be used to configure the interface of the platform to be in the System Private LAN (by default eth0). setIP -a @IP/mask -g @IPgateway -l lannumber <-t if tagged> -d interface/bond: configure the Master Node virtual IP address, after configuration you can access the Web interface using the address configured. Example: setIP -a 198.18.69.244/21 -g 198.18.64.1 -l 3064 -d eth1 The management address will be set to 198.18.69.244 in LAN 3064. ifConfig: display the configuration of the interfaces present in the node. Eth0 is preconfigured and eth1 is in our exemple configured to support the management network.
Electra VS - Version 05.10 61 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Software Only Delivery
eth0 Link encap:Ethernet HWaddr bc:30:5b:e4:fa:5a inet addr:192.168.250.11 Bcast:192.168.250.255 Mask:255.255.255.0 inet6 addr: fe80::be30:5bff:fee4:fa5a/64 Scope:Link UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:478 errors:0 dropped:0 overruns:0 frame:0 TX packets:818 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:40444 (39.4 KiB) TX bytes:141000 (137.6 KiB)
eth1 Link encap:Ethernet HWaddr bc:30:5b:e4:fa:5e inet addr:198.18.69.244 Bcast:198.18.71.255 Mask:255.255.248.0 inet6 addr: fe80::be30:5bff:fee4:fa5e/64 Scope:Link UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:6922 errors:0 dropped:447 overruns:0 frame:0 TX packets:1273 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:801049 (782.2 KiB) TX bytes:689902 (673.7 KiB)
Eth2 Link encap:Ethernet HWaddr bc:30:5b:e4:fa:5c UP BROADCAST ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Eth3 Link encap:Ethernet HWaddr 00:1b:21:bb:da:78 UP BROADCAST ALLMULTI MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Memory:de7c0000-de7dffff
3. Connect the first interface (eth0 / INTF_1) of the master node to the System Private LAN. 4. Connect the management interface (eth1 / INTF_2) of the master node to a remote PC or the management system. You can now connect to the Electra VS Web interface using the remote PC..
If you reboot the master node before importing the license file, the network configuration will be lost. In this case you must reconfigure the interfaces of the node.
62 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Software Only Delivery
Accessing the Web Interface for the First Time
To access the Web interface, proceed as follows: 1. Open a Web browser in the remote PC. 2. Type the previously configured management address in the address bar and press Enter.
If you cannot access to the management IP address previously configured: Try to connect the PC to one of the others interfaces of the platform. The interface may not be ordered as expected. If it is the case then check also that the System Private LAN is effectively connected to eth0. Connect a screen directly to the server, connect as THVNguest and check the interface configuration typing IfConfig command (see step Configure the interface of the master node).
3. Connect to the Electra VS Use the following account information: Login: admin
Electra VS - Version 05.10 63 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Software Only Delivery
Password: admin
4. Read and accept the End User License Agreement (EULA).
The End User License Agreement shall be accepted only the first time the Web interface is opened or after an upgrade if the agreement condition have been updated.
64 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Software Only Delivery
5. Check the Node Status: a. Select the Hardware tab.
b. Go to the Nodes category.
c. Check that: - The node is displayed in the Hardware/Node tab in the GUI. - The state of the first node shall be Slave, its status OK and the processing capacity set to 0. The node shall be in integration mode (check its status in the bottom-right corner of the windows).
Adding the Second Masterisable Node in Electra VS 1. Install the version from the USB Flash drive on a second node with disk (Refer to steep 1 to 6 in the section ’Installing the Version on the First Node (Master Node)’ on page 58.
Electra VS - Version 05.10 65 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Software Only Delivery
2. Connect the first physical interface of the node (eth0) to the GiGE switch. 3. From the Web Interface connected to the first node: a. Select the Hardware tab.
b. Go to the Nodes category. c. Select Add Nodes.
The second node should be detected and displayed in the list. If it is not the case check the interface configuration and the switch connection.
d. Select it and click Next. A Network interface profile compatible with the hardware is automatically associated with the node. Check if the number of physical interfaces detected is correct.
66 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Software Only Delivery
The second node is added to the Electra VS:
Asking a License for Electra VS
Ask a license file for the Electra VS in order to declare the two masterisable nodes. The license file shall contain all the licenses you purchased. Refer to Chapter 4 ’Servicing’, section ’Requesting a new license File’ on page 411.
Declaring a License for Electra VS 1. Import the license generated by Harmonic. Refer to Chapter 4 ’Servicing’, section ’Declaring a new License File’ on page 412. 2. Verify that the license has correctly been taken in account - The state of the first node shall now be set to Master and its status OK. The state of the second node shall now be set to Slave (can be Master) and its status set to OK. - The two nodes shall not be anymore in integration mode.
Electra VS - Version 05.10 67 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Software Only Delivery
- The node is associated with a network interface profile. If no interface profile corresponding to the hardware platform exists, a new one is created. if two nodes have the same hardware type by default they are associated with the same network interface profile. The Network Interface profile lists the physical interfaces detected on the hardware platform and allows you to associate them with logical interfaces. Refer to section ’Setup/IP’ on page 168.
Adding Non Masterisable Node(s) to Electra VS
Refer to Chapter 4 ’Servicing’, section ’Adding Non Masterisable Node(s) to Electra VS’ on page 439.
Defining Processing Capacity of the Nodes
If you have a NodeBench result file performed on an identical hardware platform (exactly the same hardware and exactly the same configuration of the BIOS parameters), import it on each node. Otherwise, launch a NodeBench analyze to measure the performances of the nodes. Refer to Chapter 7 ’Tools’, section ’NodeBench’ on page 466.
Finalizing Network Configuration
The network recommendations are described in the IP architecture documentation delivered in the DVD-ROM with the product.
Finalize the network configuration by: 1. Adding a new redundant switch in the System Private LAN (physical interface bonding is mandatory, redundant switch is mandatory). 2. Setting a Master node virtual IP address to the management LAN, and use the Master node virtual IP address to connect to the Web Interface. 3. Finalize the network setup configuring the input and output network following the recommendation in the Network IP document available in the DVD-ROM.
Starting the Operation
Refer to Chapter ’Web User Graphical Interface’, section ’Operating Instructions (Tutorial)’ on page 87.
68 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Virtualization Delivery
Virtualization Delivery
Hardware Recommendation
For operators already owning their VMware virtualization infrastructure, Electra VS is available as Electra VS Virtualized Edition. It is delivered as a virtual machine (loadable in ESXi).
More information on requirements and examples of platforms are available in the Electra VS-Checklist documentation delivered in the DVD-ROM with the product.
Unpackaging
Table 2-3 lists the content that are shipped with the product.
Table 2-3. Content delivered with the product
Quantity Description
1 DVD-ROM
Installation
Follow the steps below to install the Electra VS and perform its initial configuration.
Read all the recommendations related to the network in the IP architecture document delivered with the product in the DVD-ROM directory Documentation/SDI&IP architecture.
Installing the First Node (Master Node) 1. Install ESXi. It is recommended to use the installer adapted to the hardware and to upload only one virtual machine per physical hardware. 2. Download vSphere Client and install it. 3. Connect to the ESXi using the credentials set during installation.
In vmWare environment:
A physical NIC of a server is presented as a vmnic.
A VLAN is represented by a Virtual Machine Port Group (VMPG). A VMPG must be added for each Electra VS VLAN.
Electra VS - Version 05.10 69 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Virtualization Delivery
Check the recommended VLAN for virtualization in the Network IP document available in the DVD-ROM. Two LAN are mandatory, the others are optional:
Mandatory: Management LAN, System Private LAN
Optional: Data In LAN, Data Out LAN, Internal Data LAN The VMPG/LAN number is not limited. The limitation comes from the internal networks: Only one System Private LAN in the Electra VS and one Internal Data (per node)
The link between a vmnic and a VMPG is achieved with the help of a vSwitch. Each vSwitch must be associated to a different physical adapter.
At Virtual machine level, associate each physical interface to one VMPG needed in the Electra VS. For example, Network adapter 2 (used for Electra VS Management LAN) will be eth1 at Electra VS OS layer, and NIC2 in Electra VS GUI.
During the deployment of the Electra VS VM, the networks of the VM will be associated to the ones configured in the ESXi, so use explicit names such as: VM Network CC, VM Network System Private, VM Network Data In, VM Network Data Out, VM Network Internal Data.
Bonding shall be configured at hypervisor level for at least System Private Network and Internal Data network.
In this example, Network System Private is connected to vmnic0 and vmnic1 while Network Internal Data is connected to vmnic2 and vmnic3.
From the node point of view, physical interfaces are different.
70 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Virtualization Delivery
System private VMPG is mandatory, even if you have only one node. But in this case, there is no need to associate this VMPG to a physical interface.
Electra VS - Version 05.10 71 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Virtualization Delivery
Installing the OVA on the first Node (Master Node) 1. Copy the OVA image from the " Virtualization Delivery " directory to the PC. 2. During the deployment of the OVA image, associate the networks of the VM and the ones of the ESXi.
When the deployment is finished check the configuration as follows: 3. Right-click the virtual machine name (for example Electra VS_1) > Edit Settings....
72 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Virtualization Delivery
4. Select Memory. If your server has less than 32G of RAM, reduce the memory size to correspond to your real RAM. Otherwise you may have an error when you start the Virtual machine.
5. Select CPU. a. Configure the Number of virtual sockets to correspond to the real number of processors in your server. b. Configure the Number of cores per socket to correspond to the real number of core per processor (without hyperthreading). The following picture indicates the configuration for a server with two XEON E5-2690V3 processors.
Electra VS - Version 05.10 73 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Virtualization Delivery
6. Check the Network adapter mapping. At Virtual machine level, we have associated one physical interface to one VMPG. For example, Network adapter 2 (Management VS) will be eth1 in Electra VS OS layer and NIC2 in Electra VS GUI.
7. Click the Options tab. a. Select the line Advanced/General.
b. Click Configuration Parameters....
74 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Virtualization Delivery
8. Add one by one the following line in the configuration parameters pushing add line. monitor_control.halt_desched = false numa.autosize.once = false numa.autosize = true sched.cpu.latencySensitivity = high
Configuring the Interface of the First Node (Master Node)
Configure the first interface of the master node to be in the System Private LAN and set the IP address for the Management LAN. 1. Open a console on the Node.
1. Connect in Guest mode (User = THVNguest Pwd = THVNpwd0). Note that by default us keyboard is loaded. 2. Execute the following commands: loadkeys [fr|us]: load the keyboard translation table if required.
Electra VS - Version 05.10 75 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Virtualization Delivery
setSystemIP: declare the node as master node. It may be used to configure the interface of the platform to be in the System Private LAN (by default eth0). setIP -a @IP/mask -g @IPgateway -l lannumber <-t if tagged> -d interface/bond: configure the Master Node virtual IP address, after configuration you can access the Web interface using the address configured. Example: setIP -a 198.18.76.244/21 -g 198.18.64.1 -l 3064 -d eth1 The management address will be set to 198.18.76.244 in LAN 3064. ifConfig: display the configuration of the interfaces present in the node. Eth0 is preconfigured and eth1 is in our example configured to support the management network.
Accessing the Web interface for the First Time
Refer to section ’Accessing the Web Interface for the First Time’ on page 63.
Adding the Second Node in Electra VS (Masterisable Node)
Add the second node as the first node. Follow all the steps in the section ’Installing the First Node (Master Node)’ on page 69 and section ’Installing the OVA on the first Node (Master Node)’ on page 72. Do not execute the steps describe in the section ’Configuring the Interface of the First Node (Master Node)’ on page 75.
Asking a License for Electra VS
Refer to section ’Asking a License for Electra VS’ on page 67.
Declaring a License for Electra VS
Refer to section ’Declaring a License for Electra VS’ on page 67.
Adding Non Masterisable Node(s) to Electra VS
Refer to the Chapter 4 ’Servicing’, section ’Adding a Slave Node to Electra VS’ on page 445.
Defining Processing Capacity of the Nodes
Refer to section ’Defining Processing Capacity of the Nodes’ on page 68.
76 Electra VS - Version 05.10 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Virtualization Delivery
Finalizing Network Configuration
The network recommendations are described in the IP architecture documentation delivered in the DVD-ROM with the product.
Finalize the network configuration by: 1. Setting a Master node virtual IP address to the management LAN and use the Master node virtual IP address to connect to the Web Interface. 2. Finalize the network setup configuring the input and output network.
Starting the Operation
Refer to Chapter ’Web User Graphical Interface’, section ’Operating Instructions (Tutorial)’ on page 87.
Electra VS - Version 05.10 77 User Manual - Rev. A Chapter 2 ’Installation and Startup’ — Virtualization Delivery
78 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 Web User Graphical Interface
Introduction
This chapter explains the Workflows and Jobs concept then describes how to use the Web Graphical User Interface to configure the equipment.
In this Chapter
’Workflows and Jobs Concept’...... page 80
’Operating Instructions (Tutorial)’...... page 87
’GUI Description’ ...... page 165
’Workflow Library’ ...... page 229
’Recommended Settings’ ...... page 392
Electra VS - Version 05.10 79 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflows and Jobs Concept
Workflows and Jobs Concept
The configuration of the Electra VS Convergent Video System is based on Workflows (a set of video processing tasks going from content acquisition to encoding and streaming) and Jobs (implementation of a given Workflow on a specific signal). This permits to match any customer specific use case in a very easy way by creating only a few Workflows (e.g. one for HD, one for SD) and applying them to create multiple jobs (the actual channels). This makes the configuration of the platform much faster and the operations much easier.
Figure 3-1. As many jobs as needed based on a workflow
80 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflows and Jobs Concept
Workflow Management
Electra VS Convergent Video System offers the possibility to create as many templates as you need. Such templates are called workflows. A workflow describes the different processes that will be applied to the video streams.
The provided flexibility allows the operator to build any kind of encoding process:
Encoding for traditional networks (IPTV, Cable, DTH and DTTV)
Encoding for WebTV (multi-screens)
In addition to the standard encoding capability, Electra VS Convergent Video System allows
Logo addition in the video
Text addition in the video
Black Out Management
Automatic Loudness Control on audio
Content Protection
Internal statistical multiplexing
Etc.
The following figure shows a simple IPTV workflow.
Figure 3-2. Simple IPTV workflow
Workflows are made of processing components (e.g. TS over IP input, MPEG-4 decoding,...) which make up an audio/video processing chain when they are linked together.
Each processing component has its own parameters (e.g. IP@destination and UDP destination port parameters for the TS over IP input processing component). These parameters can receive default values and can be defined to be visible/hidden and editable/not editable when an audio/video process is launched (job) based on the workflow.
Electra VS - Version 05.10 81 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflows and Jobs Concept
Public, Private and Protected Parameters
When building the workflow, you will set the visibility of parameters as
Private for parameters that should not be visible nor changed when launching a job.
Protected for parameters that should be visible but not be changed when launching a job.
Public for parameters that should be visible and changed when launching a job.
Figure 3-3. Public, Private and Protected Parameters
As a result, when launching a job based on a workflow, the operator only has to modify the public parameters.
Using Predefined Workflows
Predefined workflows are provided with the Electra VS equipment.
The following workflows are provided:
Live SD HD encoder
Live SD HD transcoder
Live Web TV transcoder
82 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflows and Jobs Concept
Building your Own Workflows
If the predefined workflows do not fully match your requirements, you may build your own workflows from sample workflows delivered in the DVD-ROM. This expert mode lets you expand the Electra VS capabilities considerably.
It is recommended to create your workflow in the ‘favorite’ category: thus it will be proposed preferentially when you will create a job.
Figure 3-4. WebTV-HLS WebDAV sample workflow
Electra VS - Version 05.10 83 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflows and Jobs Concept
Job Management
Creating Job
After creating the workflows, the operator is ready to start an encoding process by creating a job.
When launching the job, the operator selects the workflow to be used; the audio and video will be processed accordingly. S/he just needs to customize the workflow by setting the public parameters.
The operator can launch as many jobs as needed based on this workflow.
As example, when launching 20 OTT channels, the operator will just have to launch 20 jobs based on a predefined workflow instead of building a new configuration for each. If we have defined a workflow with the following parameters as public (Inputs, Audio bitrate, Video resolution, fps and bitrate for each of the 4 resolutions, External servers), these parameters will be adjusted as required:
Figure 3-5. Public parameters to be changed (if needed)
Global Input
HLS output Smooth Streaming output
84 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflows and Jobs Concept
Video Common
Video Profile 1 Video Profile 2
Video Profile 3 Video Profile 4
Audio 1 Subtitle
Electra VS - Version 05.10 85 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflows and Jobs Concept
It is important to note that all parameters are set with default values (default values are defined in the workflow). Consequently, if an OTT channel uses the default values, the parameters to be changed can be limited to the inputs and outputs only.
It makes the product configuration flexible, easy and quick.
After the few minutes required to launch the jobs they are all visible in a ‘Jobs list’ view:
Figure 3-6. Jobs list view
Hot Folder
Electra VS Convergent Video System also supports hot folder management. When a file is placed in the hot folder, Electra VS Convergent Video System detects and transcodes it according to the workflow that has been placed in the hot folder.
86 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Operating Instructions (Tutorial)
This section is a tutorial. It is structured as follows:
GUI Overview
Reaching the GUI
Using the GUI
Basic Operations
Creating a Job from predefined workflows
Setting Job parameters for predefined workflows
Using the Snapshot view
Advanced Operations
Creating an MPTS job
Creating an MPTS job with Statmux
Creating your own workflow - from scratch - by adapting an existing workflow.
Creating sub-workflows
Creating workflows with multi-instantiable processing components
Electra VS - Version 05.10 87 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
GUI Overview
Reaching the GUI
You can run the Electra VS GUI provided your personal computer meets the requirements specified in Chapter Installation.
The Graphical User Interface (GUI) is a Java applet. To launch it: 1. Open a Web browser.
2. Type the equipment IP address in the address bar and press Enter. A welcome screen is displayed.
Figure 3-7. Welcome screen
3. Click the image to launch the application. 4. Enter the login and password
Figure 3-8. Login and password
Use the following account information: Login: admin Password: admin
88 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
This is the default factory account. With administrator rights, you can change the password at your convenience.
Using the GUI
General Organization
The graphical user interface is divided into four main areas, shown in the figure below.
Figure 3-9. Graphical user interface overview
The GUI contains the following areas:
An header bar that provides information on the equipment status, the date and time, etc.
A Main area from where you can perform configuration and monitoring. This area contains several tabs. Click them to navigate in the GUI.
A Logs panel that shows the logs raised on the equipment.
A Footer bar that provides the name of the connected user, the Electra VS name and IP address and the Electra VS software release.
Customizing the Display
Resizing the Columns
In arrays, columns can be resized. Move the mouse cursor between two header columns. The mouse cursor should change to . Click and drag the column to the desired size, and then release the mouse button.
Electra VS - Version 05.10 89 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Sorting Elements in Arrays
In any array, you can sort elements by any column. To do so, click the header column once. A white arrow appears in this header.
To change the sorting mode, click the header once more. When sorted in increasing order, the arrow is displayed. In decreasing order, the arrow is shown.
Moving and Docking
Each view can be moved by dragging and dropping its title bar. You can also move a view to drag the view over the left, right, top, or bottom border of another view or on a new independent window.
Commonly Used Elements
Some elements are recurrent in the GUI, as pictograms for instance. These elements are described here.
Status Pictograms
Table 3-1 lists the status pictograms used in the GUI.
Table 3-1. Status pictograms
Status icon Meaning
OK
Information message
Warning
Minor error
Major error
Critical error
90 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Other Pictograms
Table 3-2. Pictograms
Pictogram Meaning Behavior
Add Adds a processing component to a list.
Remove Removes a selected processing component from a list.
Edit Edits a parameter.
Search Indicates a search field.
Tables
The GUI contains numerous tables. In some of them, it is possible to modify the content.
To add a processing component to a list, click the button.
To remove a processing component from a list, select a line and click the button.
To modify a value in a table, double-click the corresponding cell and type the new value or if it is a list, select a value from the list. In some lists, it is also possible to add values. For instance, in a TS audio extractor processing component, you can leave the PMT PID to Auto or enter your own value.
Figure 3-10. Example of editable drop-down list
Electra VS - Version 05.10 91 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Basic Operations
This section is divided into 4 sub-sections.
Table 3-3. Basic settings sub-sections
Sub-section Description
‘Creating a Job from a describes how to create a job from a predefined workflow’ predefined workflow installed in the Electra VS.
‘‘Setting Job parameters presents the different tabs of the jobs based for the predefined on the predefined workflows. workflows’’
‘Hot Folder’ explains how to use the hot folder. A hot folder is a directory that, when you place a file in it, automatically detects the file and creates a job to apply the processing you specified.
‘Using the Snapshot explains how to see the input contents in a View’ snapshot view so as to ease your configuration.
Creating a Job from a Predefined Workflow 1. Click the Jobs tab.
Figure 3-11. Opening the Jobs tab
2. Click Create.
Figure 3-12. Creating a job
The list of predefined workflows is displayed. In this list, you will find
Live SD-HD Encoder: to be used for live encoding from an SDI input to an SPTS or MPTS (Statmux included) output.
Live SD-HD Transcoder: to be used for Live transcoding to an SPTS or MPTS (statmux included) output.
92 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Live WebTV Transcoder: to be used for Live transcoding for WebTV (with or without packaging).
Figure 3-13. Favorite workflows
(Later it will be possible for you to add your own favorite workflows in this list). 3. Choose a workflow according to the target application (e.g. Live Web TV Transcoder). 4. Click Ok.
The list of parameters that you must set to create the job is displayed.
Figure 3-14. Setting the job parameters (e.g., Live Web TV transcoder)
Electra VS - Version 05.10 93 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
5. Fill in the Name field on the top left. This name will later appear in the list of jobs. Choose this name carefully so that you are able to recognize it easily in the list, as there may be a high number of jobs in the list. 6. For a file encoding job, you can set a priority for the job and its speed:
Figure 3-15. Setting file encoding job parameters
- Priority: if there are not enough resources (CPU, memory...) to process all the jobs, and if you want this particular job to be processed before the others, set an important priority (between 1 and 250; 250 being the highest priority). The other jobs will be processed more slowly. - Speed: if set to 1, the job will last at most as long as the video duration. If set to 2, the job will last at most half as long as the video duration, etc. Note that if the network bitrate is too low, the speed goal might not be respected. If not configured, the job will get the available resources of the most available node. Note that a live job always holds priority over file encoding jobs. If there are not enough resources, the transcoding is kept in waiting state until resources become available. 7. Set the parameters in the right part of the view. The content depends on the selected workflow. Refer to the next section for a presentation of the different tabs of the jobs based on predefined workflows. 8. Click Create and start.
The job is displayed in the Jobs list. Check its status and its state.
Figure 3-16. Job is running
94 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
9. Double-click the job to gain access to the job monitoring panels: Parameters, Logs, Nodes, Snapshot
Figure 3-17. Information on job
The Parameters panel allows you to show/edit the job parameters.
The Logs panel gives the alarms and events related to the selected job.
The Nodes panel indicates the node(s) where the job is running.
The Snapshot panel shows the contents of input for the selected job as a tree.
Electra VS - Version 05.10 95 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Setting Job Parameters Based on the Predefined Workflows
This section presents the parameter tabs of jobs based on the predefined workflows delivered with the product.
If you need details on the parameters, refer to section ’Workflow Library’ on page 229.
Live SD-HD Encoder
Figure 3-18. Live SD-HD Encoder job
Figure 3-19. Live SD-HD Encoder job - Global parameters
Figure 3-20. Live SD-HD Encoder job - Input parameters
96 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-21. Live SD-HD Encoder job - Video parameters
Electra VS - Version 05.10 97 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-22. Live SD-HD Encoder job - PIP parameters
Figure 3-23. Live SD-HD Encoder job - Audio parameters
98 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-24. Live SD-HD Encoder job - Audio1 parameters
Electra VS - Version 05.10 99 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-25. Live SD-HD Encoder job - Output parameters
If Output TS type is SPTS in the Global Parameters tab
100 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
If Output TS type is MPTS in the Global Parameters tab
Live SD-HD Transcoder
Figure 3-26. Live SD-HD Transcoder job
Figure 3-27. Live SD-HD Transcoder job - Global parameters
Electra VS - Version 05.10 101 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-28. Live SD-HD Transcoder job - Input parameters
Figure 3-29. Live SD-HD Transcoder job - Video parameters
102 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-30. Live SD-HD Transcoder job - PIP parameters
Figure 3-31. Live SD-HD Transcoder job - Audio transcoding parameters
Electra VS - Version 05.10 103 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-32. Live SD-HD Transcoder job - Pass-through component parameters
Figure 3-33. Live SD-HD Transcoder job - Output parameters
If Output TS type is SPTS in the Global Parameters tab
104 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
If Output TS type is MPTS in the Global Parameters tab
Electra VS - Version 05.10 105 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Live Web TV Transcoder
Figure 3-34. Live Web TV Transcoder job
Figure 3-35. Live Web TV Transcoder job - Global parameters
106 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-36. Live Web TV Transcoder job - Input
Figure 3-37. Live Web TV Transcoder job - HLS output
Electra VS - Version 05.10 107 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-38. Live Web TV Transcoder job - MPEG-DASH output
Figure 3-39. Live Web TV Transcoder job - RTMP output
Figure 3-40. Live Web TV Transcoder job - Smooth Streaming output
108 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-41. Live Web TV Transcoder job - TS output
Figure 3-42. Live Web TV Transcoder job - Video common parameters
Electra VS - Version 05.10 109 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-43. Live Web TV Transcoder job - Video profile 1/2
110 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-44. Live Web TV Transcoder job - Audio component
Figure 3-45. Live Web TV Transcoder job - Subtitle component
Electra VS - Version 05.10 111 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Hot Folder
In this section, you will learn how to use the hot folder. A hot folder is a directory that, when you place a file in it, automatically detects the file and creates a job based on the workflow that has been placed in the hot folder.
Configuring the Workflow
Create the workflow that you wish to apply on the files that will be placed on the hot folder. For instance, use the workflow procedure given in section ’Example: Encoding a File’ on page 134.
Configuring the Hot Folder 1. Go to the Setup tab and choose the Hot folder category. 2. Edit the configuration.
3. Click the button and add a hot folder. 4. Choose from the list the workflow you wish to apply on the files that will be placed in the hot folder. 5. Set the public parameters of the workflow. 6. Apply the configuration.
Figure 3-46. Configuring the hot folder
112 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Using the Hot Folder
Place a file in the input folder.
A job is automatically created to process the file and an output file is placed in the output folder.
Electra VS - Version 05.10 113 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Using the Snapshot View
In this section, you will learn how to see your input contents as a tree in a snapshot view so as to ease your configuration. 1. In the Snapshot tab top-right corner, click New.
Figure 3-47. Snapshot tab
2. Choose the type of input: TS over IP or TS file. 3. Depending on the type of input, set the following parameters: For a TS over IP input:
Figure 3-48. Creating a new snapshot view for a TS over IP input
a. If your input is multicast, check the corresponding box and set the LAN.
b. Enter the destination IP address and UDP port of the TS over IP stream.
c. If you want to choose the source of the stream, check the Select source IP address box and fill in the field. You can specify only one source IP address. If you do this, the operating mode varies according to the type of IP stream (multicast or unicast) and the IGMP version indicated in the Electra VS setup parameters (Setup tab, IP category): - Multicast, IGMP v2: IGMP requests does not contain the source IP address. The filtering on source is done in Electra VS.
114 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
- Multicast, IGMP v3: IGMP v3 request uses the SSM mode and can specify the source IP address. Only multicast with the specified source IP address will be received. - Unicast: when a datagram is received, it is discarded if it does not come from the specified source IP address.
d. Indicate a maximum TS bitrate, in bits per second. This parameter is used not to saturate the node input network. The entered value can be higher than the actual bitrate (e.g. 40 Mbps for 38 Mbps actual rate). If the entered value is lower than the actual bitrate, a congestion is likely to occur on the receiving node.
e. Indicate the standard (DVB, MPEG-2, ATSC). For a TS file input:
Figure 3-49. Creating a new snapshot view for a TS file input
a. Enter the network storage where the TS file to use as a source is stored.
b. Enter the name of the folder on the network storage where the TS file to use as a source is stored.
c. Enter the name of the TS file to use as a source. 4. Select the standard of the input stream: MPEG-2, DVB or ATSC.
The snapshot view is automatically created and updated.
Electra VS - Version 05.10 115 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-50. Snapshot view _ Buttons and input content as a tree
You can freeze the snapshot with the button .
To delete the snapshot, you can either click the cross button in the Snapshot panel, or remove the job corresponding to the snapshot in the Jobs tab.
116 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Advanced Operations
This section gives additional information on
how to create an MPTS job
how to create an MPTS job with Statmux
how to declare an SDI source
how to use an SDI source
how to configure the SDI redundancy
how to create your own workflow from scratch or by adapting an existing workflow.
how to create sub-workflows
how to create workflows with multi-instantiable processing components
Creating an MPTS Job
To create an MPTS, the following method is recommended: 1. Create one job per program, each job being based on a workflow using ‘MPTS over IP’ processing component (e.g. Live SD-HD Transcoder workflow). a. In the Jobs tab, click Create and select the Live SD-HD Transcoder workflow.
Figure 3-51. Selecting the Live SD-HD Transcoder workflow
b. Enter a name to your job (e.g. UM_TV1CBR)
Figure 3-52. UM_TV1CBR job parameter - Name
Electra VS - Version 05.10 117 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
c. Set the parameters for Input, Video, PIP, Audio transcoding, Pass-trough component, and Output. Attention should be given to the following points: - set the Output TS type to MPTS in the Global parameters
Figure 3-53. UM_TV1CBR job parameter - Global parameters
- set the Rate mode to CBR in the Video section.
Figure 3-54. UM_TV1CBR job parameter - Video
118 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
- Click MPTS name field in the Output section. A dialog box is opened allowing you to choose an existing MPTS over IP output or to create a new MPTS over IP output (e.g. UM_MPTS_CBR).
Figure 3-55. UM_TV1CBR and UM_MPTS_CBR jobs parameter
Existing MPTS UM_TV1CBR job
MPTS selection Creating a new MPTS
UM_MPTS_CBR job
MPTS job name
MPTS name
2. Click to create a new MPTS and configure it with UM_MPTS_CBR as name. 3. Click Create and start at the bottom of the dialog box to launch the multiplexing job UM_MPTS_CBR.
The first program UM_TV1CBR as well as the MPTS multiplexing UM_MPTS_CBR are processed in separate jobs. They are visible in the jobs list in the Jobs tab.
Figure 3-56. The first program job and the multiplexing job
Electra VS - Version 05.10 119 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
4. Create the next program jobs (you can duplicate and adapt the UM_TV1CBR job). Do not forget to choose the same MPTS name for each job (here UM_MPTS_CBR) since all jobs must share a same MPTS name to belong to the same MPTS. Each program as well as the multiplexing are processed in separate jobs. Each program can be controlled separately. To start (or stop) a program, you just have to start (or stop) the corresponding job.
Figure 3-57. Two program jobs and the multiplexing job
120 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Creating an MPTS Job with Statmux
To create a job that uses statistical multiplexing, proceed as follows: 1. Create one Live SD-HD Transcoder job for each program of the MPTS you wish to create. The procedure is the same as previously, except that you must set the Rate mode to Statmux and set the Minimum bitrate, Maximum bitrate and Quality parameters in the Video category (Output TS type must be set to MPTS in the Global parameters category).
Figure 3-58. UM_TV1VBR job parameter - Video (Statmux)
In our example, we choose the following names: UM_TV1VBR for the 1st program, UM_TV2VBR for the 2nd program,... and UM_MPTS_VBR for the MPTS.
Electra VS - Version 05.10 121 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-59. UM_TV1VBR and UM_MPTS_VBR jobs parameter
Existing MPTS UM_TV1VBR job
MPTS selection Creating a new MPTS
UM_MPTS_VBR job
MPTS job name
MPTS name
On the first time you create a job in MPTS mode, 2 jobs are actually created: one for the MPTS multiplexing process and one for the encoding process. When creating the next jobs, only the encoding job is created and it is linked to the MPTS multiplexing job created earlier.
Figure 3-60. Three program jobs and the multiplexing job in Statmux mode
Monitoring can be done in the Statmux tab.
122 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-61. Statmux tab - Consult mode
List of MPTS with statmux
Stamux parameters for each VBR program in the selected MPTS: Selected MPTS • Name of the job included in the statistical multiplexing • PID of the video component • Minimum bitrate of the video component, in bits per second • Maximum bitrate of the video component, in bits per second • Quality of the video component, in percentage (set 90 for the maximum quality) • Fallback bitrate, in bits per second: this is the bitrate used if the communication is lost between the allocator and the encoder. This is not configurable, the value is automatically computed by the equipment. • State of the job • Status of the job
Parameters of the selected MPTS
Electra VS - Version 05.10 123 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Click Edit in the top-right corner of the tab and change the parameters at your convenience (if required).
Figure 3-62. Statmux tab - Edit mode
124 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Creating your Own Workflows
In this section, you will learn how to create your own workflow
from scratch. The procedure will be followed by an example.
by adapting a sample workflow
Creating a Workflow from Scratch
If the predefined workflows do not fully match your requirements, you may build your own workflows. This expert mode lets you expand your Electra VS capabilities considerably.
Creating the Workflow
The process to create any workflow is the same. 1. Click the Workflows tab.
Figure 3-63. Workflows tab
2. Click New. The following screen is displayed.
Electra VS - Version 05.10 125 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-64. Creating a workflow
3. Enter a name for your workflow. 4. Assign a category. Categories are used by Electra VS to classify the workflows (this will be useful later to find a workflow more easily). A number of categories are defined by default, but you can create your own categories (see section ’Categories and Colors’ on page 196). A color is associated to each category.
126 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
5. Enter a summary (short description) and a description (detailed description) to provide information on your workflow. This (optional) information can be edited or changed after workflow creation. 6. Click OK.
Adding Processing Components to the Workflow
Once the workflow is created, you need to fill it with processing components. 1. To add the first processing component, click a processing component from the list in the left area, and drag it to the right area.
Figure 3-65. Adding a processing component to the workflow
Drag and Drop
Electra VS - Version 05.10 127 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
2. Right-click one of the processing component’s interface buttons and choose Link to new from the menu. 3. Choose a processing component from the proposed list. The option you are pointing with the mouse pointer is highlighted in the list and its description is displayed.
Figure 3-66. Linking to a new processing component
4. Repeat steps 2 and 3 for each processing component to add.
Do not forget to hit the Save button once in a while.
After completion, you will get a workflow which may look like this.
Figure 3-67. Workflow after completion
128 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Setting the Parameters of the Processing Component
To access the parameters of a processing component: 1. Double-click the processing component. This displays a Properties dialog box that lists parameters in a tab.
Figure 3-68. Setting the parameter of a processing component (e.g. TS over IP input)
Double-click
2. Select each tab in turn (Parameters, Input, Output). 3. Choose the parameters that you want to publish, i.e. the parameters that the person who will create a job based on your workflow will need to define. By default all parameters are set to private. Set the parameters that should be editable to public. 4. From the default value column, click the cells to add your values if needed. This column displays
the actual value when the parameter is private or protected.
the default value when the parameter is public. This value is able to be changed by the person who will create a job based on this workflow. Any change of the default value has no impact on the running jobs. 5. Click OK to validate.
Organizing the Parameters of the Workflow
By default all the public parameters are displayed in the same panel and in the same section when creating a job. If you have a great number of public parameters, you may want to sort them into sections and groups.
As example you will find hereunder the job panel based on a workflow where parameters are not sorted.
Electra VS - Version 05.10 129 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-69. Job panel based on a workflow where parameters are not sorted
Now hereunder the job panel based on the same workflow where parameters are sorted. You can note that the parameters are now regrouped in more than one section with several groups in each section making job editing easier and most intuitive.
Figure 3-70. Job panel based on a workflow where parameters are sorted
sections groups in the selected section (‘IP input’ here)
130 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
To organize the workflows parameters, proceed as follows: 1. Click Layout.
Figure 3-71. Layout button
2. Create each section (New button in the top area of the Parameters panel). Sections are edited on the left part of the Parameters panel. The following tools are available to edit the sections.
Figure 3-72. Section tools
a. Click New to create a new section.
b. Click Rename to give it a proper name. c. Repeat these two operations for all the sections to create.
d. Adjust the sections sequencing by moving up or down the sections (Up or Down buttons). e. Delete unnecessary sections if required (Remove button).
f. Once edited, the Parameters panel may look like this:
Figure 3-73. Parameters panel after sections edition
3. Create groups inside sections to refine parameter sorting (e.g. Nominal input, Backup input, Others groups under the IP input section). Groups are edited on the right part of the Parameters panel. The New Group tool is available to edit the groups.
Figure 3-74. Groups tools
Electra VS - Version 05.10 131 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
a. Click the New group button to create a new group of parameters. A new group is created. It appears underneath the list of parameters.
Figure 3-75. New group of parameters
b. Click the (Rename) button and give it a proper name. 4. From the list of parameters, select a parameter and drag it to the suitable section and group (you can select multiple parameters by pressing the Ctrl key and selecting successively the parameters to move).
Figure 3-76. Moving a parameter to a section
132 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-77. Moving multiple parameters to a group
Repeat these steps as many times as needed to sort all your parameters, for instance as shown in Figure 3-78 below.
Figure 3-78. Parameters sorted
Checking the Consistency
To know if your workflow is consistently built, click Check.
Figure 3-79. Check button
Electra VS - Version 05.10 133 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
A report is displayed and indicates the problems, if any.
If there are errors: 1. Click the link of each error to open the processing component where the problem is located. 2. Click Check again.
Saving the Workflow
Click Save. The configuration is implicitly checked prior to saving.
Figure 3-80. Save button
Example: Encoding a File
This section provides you with an example of workflow using a TS file in input and in output.
Figure 3-81 shows what the workflow example looks like.
Figure 3-81. TS file workflow example
This workflow contains:
1 TS file input
For the video component:
1 TS video extractor
1 Video decoder
1 H.264 AVC encoder
134 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
1 TS video packetizer
For the audio component:
1 TS audio extractor
1 Audio decoder
1 MPEG-1 layer 2 encoder
1 TS audio packetizer
1 TS multiplexer
1 TS file output
Prerequisite: before creating the workflow, make sure you have created the network storage(s) that will be used to read the input files and write the output files in the Setup tab, Network Storage category.
To create this workflow: 1. Proceed as described in section section ’Creating a Workflow from Scratch’ on page 125 and add all the processing components listed above.
Electra VS - Version 05.10 135 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
2. Perform the settings described in the table below.
Table 3-4. Settings to perform to encode a file Processing Parameter Action component TS file TS file network Set the default value and set to public input storage TS file folder Set the default value and set to public TS file name Set to public, label = "Input TS filename" TS video Maximum format Set to HD 1080i@25 fps extractor Program number Label = "Input PN" PMT PID Label = "Input PMT PID" Component PID Label = "Input video PID" Codec Set to Any H.264 AVC Bitrate Set to public, label = "Output video encoder bitrate" Profile Set to High Frame structure Set to Interlace, public TS audio Program number Set to First one extractor PMT PID Set to Auto Component PID Label = "Input audio PID" Codec Set to Any MPEG-1 Bitrate Set to public, label = "Output audio Layer 2 bitrate" encoder Stereo mode Set to Stereo TS TS bitrate Set to 2,500,000 bps, public, label = multiplexer "Output TS bitrate" TS Component PID Make a link to "Input video PID"a multiplexer PMT PID Make a link to "Input PMT PID"a (input 1) TS Component PID Make a link to "Input audio PID"a multiplexer (input 2) TS file TS file network Set the value output storage TS file folder Set the value TS file name Make a link to "Input TS filename"a a To know how to make links between parameters, refer to section ’Link Tool’ on page 236.
3. Apply the configuration.
136 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
4. Launch a job based on your workflow.
Adapting a Sample Workflow
If the predefined workflows do not fully match your requirements, you may build your own workflows from sample workflows delivered in the DVD-ROM.
List of Sample Workflows to Adapt
The following sample workflows are provided:
Sample IP TV - SDI input:
SDI input
No preprocessing
Audio and video encoding
TS over IP output
Sample IP TV - SDI input HD to SD:
SDI input in HD
Resize into SD
Audio and video encoding
TS over IP output
Sample IPTV - TSoIP input:
TS over IP input
No preprocessing
Audio and video transcoding
TS over IP output
Sample Mosaic - 6 HD inputs:
6 TS over IP inputs in HD
Mosaic generation
TS over IP output
Sample Web TV - HLS WebDAV:
TS over IP input
Generation of 3 adaptive bitrate profiles with audio encoding
HLS output sent to a remote Web server in WebDAV
Sample Web TV - Smooth Streaming to IIS server:
TS over IP input
Generation of 3 adaptive bitrate profiles with audio encoding
Smooth Streaming output sent to an IIS server in http post
Electra VS - Version 05.10 137 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Sample file-to-file transcoding:
TS file input
Video transcoding in [email protected] fps resolution
Audio and data in pass-through
TS file output with PIDs identical to the ones in input
TS output filename identical to TS input filename
Workflow usable directly or via a hot folder
You can see their layouts in section ’Layout of the Sample Workflows’ on page 387.
138 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Adapting a Sample Workflow (Steps)
To adapt a sample workflow, proceed as follows:
Figure 3-82. Duplicate button
1 3
2
1. In the Workflows tab, import the sample workflows from the DVD-ROM (mark 1 in the figure above). 2. Identify the sample workflow in which you are interested (e.g. ‘Sample IPTV transcoding’) in the workflows library (you can find sample workflows under the red category ( )). Double-click it to display it in the right area (mark 2). 3. Click Duplicate so as to keep the original sample workflow and to work on a copy (mark 3). 4. Click Properties and enter an explicit name for your workflow.
Figure 3-83. Properties button
Electra VS - Version 05.10 139 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
5. Assign a category (Favorite is recommended). 6. Open the processing components and modify the values at your convenience. 7. Save the workflow.
You can now create jobs based on this workflow.
140 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Creating Sub-Workflows
Introduction
A sub-workflow can be seen as a customized processing component made up of a series of processing components. The benefit of creating sub-workflows is that you can save a series of processing components, and then use them without having to define all the parameters all over again.
The sub-workflow is used as a standard processing component, except that it is necessary to publish the inputs and/or outputs. As any standard processing component, a sub-workflow cannot be used alone to generate a job.
Figure 3-84. Creating a workflow using sub-workflows
Example
Let us create a sub-workflow 'Audio Transcode to MPEG-1 layer 2' whose bitrate parameter will be set to public to make it editable in the jobs. 1. Create the sub-workflow in the same way as a workflow: a. In the Workflows tab, select Create.
b. Give a name, a description, a summary and a category.
Electra VS - Version 05.10 141 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-85. Creating a workflow using sub-workflows
c. Drag and drop the following processing components 'Audio Decoder' and 'MPEG-1 layer 2 Encoder'.
d. Link the two components.
Figure 3-86. Sub-workflows layout
2. Publish the input of the 'Audio decoder' processing component and the output of the 'MPEG-1 layer 2 encoder' processing component.
Figure 3-87. Publishing the input of the 'Audio decoder' processing component
142 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-88. Publishing the output of the 'MPEG-1 layer 2 encoder' processing component
The labels are displayed in the sub-workflow.
Figure 3-89. Sub-workflows layout with input and outputs labels
3. Set the 'MPEG-1 layer 2 encoder' processing component parameters as public to make them editable in the workflow which will embed this sub-workflow.
Figure 3-90. Sub-workflows parameters set as ‘public’
Electra VS - Version 05.10 143 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
4. Click Save. 5. Now you can create instantiable workflows which embed the sub-workflow ('UM_Sub_WKF_AudioXCode').
Figure 3-91. Example of workflow embedding the sub-workflows
sub-workflow 'UM_Sub_WKF_AudioXCode'
The public parameters of the sub-workflow are visible and can be set as public/private/protected in the main workflow.
Figure 3-92. Audio parameters in the main workflow
144 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Creating Workflows with Multi-Instantiable Processing Components
The multi-instance feature allows a processing component to be instantiated several times in a job. As a result, a workflow which includes a multi-instantiable processing component is as powerful as several workflows which include the same processing component with no multi-instance capability.
The following example 'Transmitting SI/PSI tables in ghost mode (pass-though)' will highlight the advantage of multi-instance feature.
If ‘Multi-instances’ feature is disabled
You have to install in your workflow as many 'Component Extractor' Processing components as tables to transmit1. Hence you will create 1. one workflow to pass through one PSI/SI,
Figure 3-93. Multi-instance feature disabled - One workflow with the corresponding job
1. or range of contiguous tables
Electra VS - Version 05.10 145 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
2. another workflow to pass through two PSI/SI tables
Figure 3-94. Multi-instance feature disabled - Another workflow with the corresponding job
3. etc.
If ‘Multi-instances’ feature is enabled 1. Configure the multi-instantiable 'Component Extractor' Processing component as follows: a. Check the box Multi instance
b. Give a name to the Processing component (Name, e.g. TableExtract) c. Define the number of instances present in the list by default (Default value, e.g. 1)
146 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-95. Multi-instance feature enabled - Setting the Multi-instance feature in a processing component
2. When using multi-instantiable 'Component Extractor' Processing component, only one workflow is required to transmit as many tables as required through the jobs based on this workflow. Hence you will a. Create the workflow with the multi-instantiable 'Component Extractor' Processing component.
Figure 3-96. Multi-instance feature enabled - Creating the unique workflow
M: Multi-instantiable
b. Create a job (job1) based on this workflow to pass-through one table. Enter the PID of the table to extract.
Figure 3-97. Multi-instance feature enabled - Unique workflow with the first job
Electra VS - Version 05.10 147 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
c. Create another job (job2) based on the same workflow to pass-through two tables. Enter the PID of the two tables to extract.
To add instances, click the button Add (Add TableExtract).
Figure 3-98. Multi-instance feature enabled - the same unique workflow with the other jobs
1. Click ‘Add TableExtract’ to add a second instance
2. Set the first instance (i.e. the first table to pass-through)
3. Set the second instance (i.e. the second table to pass-through)
148 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Configuring an SDI System
If the Electra VS is equipped with SDI inputs, this section explains how to configure and use them.
Recommended SDI Redundancy Topologies
The SDI topology is valid only if it is a set of following sub configurations. Three SDI redundancy topologies are recommended and are described below:
SDI redundancy topology (N + M, redundant nodes linked to the same matrix with dynamic crosspoints).
SDI redundancy topology (N + M, all nodes linked to the same matrix).
SDI redundancy topology (1 + 1, without matrix).
When an SDI topology is created in the Hardware/SDI panel is recognized as an SDI redundancy topology, all the jobs using the attached SDI sources will be defined as SDI redundant jobs.
SDI Redundancy Topology (N + M, redundant nodes linked to the same matrix with dynamic crosspoints)
This topology is recommended and consists of nominal nodes, redundant nodes and one matrix:
The nominal nodes are directly linked to the SDI sources.
The redundant nodes are linked to the SDI sources via a matrix. The crosspoints of the matrix are dynamic.
The SDI sources are connected to the nominal nodes and to the matrix.
This topology is used to manage redundant SDI sources. The main source is connected to the main node, the backup source is connected to the matrix.
Figure 3-99. SDI topology: SDI redundancy - N + M, redundant nodes linked to a matrix
Electra VS - Version 05.10 149 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
SDI Redundancy Topology (N+M , all nodes linked to the same matrix)
This topology consists of nominal nodes, redundant nodes and one matrix.
Matrix crosspoints between SDI sources and nominal nodes must be static.
Matrix crosspoints between SDI sources and redundant nodes must be dynamic.
Figure 3-100. SDI topology: SDI redundancy - N + M, all nodes linked to the same matrix
SDI Redundancy Topology (1+1)
This topology consists of nodes with identical SDI sources.
The nominal node is the node with the lower node Id.
Additional unique SDI sources can be connected directly to nominal node but in this case job using these sources will not be SDI redundant job.
This topology is used to manage redundant SDI sources. The main source is connected to the main node, the backup source is connected to the backup node.
Figure 3-101. SDI topologies: SDI redundancy - 1+1
1st example
2nd example
150 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Declaring SDI Sources
Declaring SDI sources connected to a Node
If you want to connect directly SDI sources to the SDI inputs of a node, it is recommended to name the SDI sources so that they have explicit names that you can easily recognize when configuring jobs. To do so: 1. Go to the Hardware tab and choose the SDI category. The tab displays the nodes that contain SDI inputs. 2. Edit the configuration. 3. Double-click the node(s) you wish to use and enter names for the sources in the fields. 4. Apply the configuration.
Figure 3-102. Naming the SDI sources of a node
Adding an SDI Matrix in an SDI System
If you want to connect the SDI sources to the SDI inputs of a node via a matrix, you must: 1. Add the SDI matrix and name the SDI sources.
Electra VS - Version 05.10 151 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
2. Connect the outputs of the matrix to the node. 3. Configure the crosspoints of the matrix (for main nodes).
Adding the matrix1 and naming the SDI sources
To declare the SDI matrix and name the SDI sources, proceed as follows: 1. Go to the Hardware tab. 2. Choose the SDI category. 3. In the right of the view, click Edit.
In the right of the view, click Add matrix.
Figure 3-103. Add matrix
Figure 3-104. Create a new SDI matrix
4. Set the SDI matrix parameters:
Number of inputs/outputs: size of the matrix.
Name: enter a name for the matrix, at your convenience.
1. Note: SDI matrix management interface shall be connected to the Electra VS management LAN
152 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
IP address and TCP port to connect to the SDI matrix remote equipment. 5. Click OK.
Once you have declared a matrix, the GUI displays a representation of the matrix.
Figure 3-105. New SDI matrix representation
6. Configure the name of the SDI sources connected to the SDI inputs of the matrix. To do so, double-click the purple matrix bar to access its parameters. Then enter a name for each source in the Input list area.
Figure 3-106. Naming the SDI source of the matrix
Connecting the Matrix Outputs to a Node
Electra VS - Version 05.10 153 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
To connect a matrix output to a Node, click an output of the matrix, hold the mouse and drag it over an input node of an SDI board. A link is created.
The figure below shows an example of a redundant topology example.
Figure 3-107. Linking the matrix to the node inputs (Redundant topology)
Nominal nodes
Redundant nodes
Configuring the Crosspoints of the Matrix
By default, the crosspoints are dynamic and are managed by the Electra VS. However it is also possible to create static crosspoints.
To create a static crosspoint, click an input of the matrix, hold the mouse and drag it over an output of the matrix. A static crosspoint is created. The static crosspoints are blue.
To delete a static crosspoint, right-click the crosspoint and select remove link.
The figure below shows a redundancy topology with static crosspoints in the matrix.
154 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Figure 3-108. Linking the SDI inputs to the matrix
Static crosspoints
Nominal node
Nominal node
Redundant node
For more information on the SDI category, see section ’Hardware/SDI Panel’ on page 188.
Tips:
When placing the cursor over an internal crosspoint of the matrix, a tooltip is displayed to help you identify matrix’ connections.
You can copy the internal crosspoints of the matrix to the clipboard and paste them into a text or Excel document.
Figure 3-109. SDI matrix with a tooltip
Electra VS - Version 05.10 155 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Using SDI Sources
Using an SDI Source in a Live SD-HD Encoder Job
To select an SDI source in a Live SD-HD Encoder job proceed as follows: 1. Create the Live SD-HD Encoder Job.
Figure 3-110. Create the Live SD-HD Encoder Job
2. In the Job Parameters view select Global parameters/Input and choice the SDI source you wish to use among the sources you named previously.
Figure 3-111. Live SD-HD Encoder job, select a SDI source
3. Build the rest of the job at your convenience.
When you launch a job, if a matrix is used, it is automatically configured. If static crosspoints have been previously created, they are not modified (refer to section ’Configuring the Crosspoints of the Matrix’ on page 154).
156 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
Using an SDI Source in a Workflow
To select an SDI source in a workflow proceed as follows: 1. Create a new workflow. 2. Add an SDI Input processing component in the workflow. 3. Edit the SDI Input processing component. 4. In the SDI input list, choose the SDI source you wish to use among the sources you named previously.
Figure 3-112. SDI input processing component, select a SDI source
If the SDI input parameter is set to public it can be configured at the job creating.
When you launch a job, if a matrix is used, it is automatically configured. If static crosspoints have been previously created, they are not modified (refer to section ’Configuring the Crosspoints of the Matrix’ on page 154).
Electra VS - Version 05.10 157 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
5. Build the rest of the workflow at your convenience, or use the example provided in the next section.
Workflow Example with an SDI Input
Here is an example of workflow that uses an SDI input.
Figure 3-113. Workflow example with an SDI input
This workflow contains:
1 SDI input
For the video component:
1 H.264 AVC encoder
1 TS video packetizer
For the audio component:
1 MPEG-1 Layer 2 encoder
1 TS audio packetizer
1 TS multiplexer
1 TS over IP streamer
158 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
SDI Redundancy Configuration
Definitions about the SDI Redundancy
SDI redundant job
A job is an SDI redundant job if it contains a SDI input and if the SDI source is available (according to SDI topology) through at least two distinct nodes in the Electra VS (refer to section ’Recommended SDI Redundancy Topologies’ on page 149).
If a job is a SDI redundant job, two jobs (main and backup) are created in the Electra VS. Only one of the two jobs is active (i.e running and generating output streams) at a time.
Switching triggers
The switching between main and backup jobs is triggered by the following events in the active job, ordered from the higher to the lower criticality:
Job not running: the job cannot be started (node unreachable, …).
SDI sync loss (optional): no SDI signal detected.
When triggers are raised on both main and backup jobs, the job with the trigger with lower criticality will be set active. A job may contain several modules raising switching trigger (for example two SDI inpu modules with job switching trigger set to true). If at least one input module detects a SDI sync loss, the job raises a switching trigger. A job shall contain only one module raising switching trigger. If a job contains two SDI input modules with job switching triggers, only one shall be set to true.
Backup job standby activity
The Backup job standby activity determines the rapidity of switching between the main and backup jobs.
If backup job is running when standby, the backup job is running but the output is muted (output streams are not generated). It is ready to immediately broadcast the output streams when a switch is requested. However it uses resources in the system (SDI input, CPU,…). This mode is suitable for premium channels.
If backup job is stopped when standby, the backup job is stopped if not active. It is started when a switch is requested. The recovery of output streams takes more time (few seconds). However it does not use resources when not started.
Whatever Backup job standby activity selected, the backup job does not use licenses.
Electra VS - Version 05.10 159 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
SDI redundancy Mode
By default the main job is running. The automatic switching-back from backup to main jobs is determined by the SDI redundancy mode.. Two modes are configurable:
Automatic switch-back = on main recovery: When a switching trigger is raised on the main job, the switch to the backup job is automatic. When there is no switching trigger raised on the main job, the switch back from the backup job to the main job is also automatic. It is not possible to perform manual switching between main and backup.
Automatic switch-back = on backup failure: When the switching trigger is raised on the main job, the switch from the main job to the backup job is automatic. The switch-back from the backup job to the main job is automatic when a switching trigger is raised on the backup job (if the switching condition in the main job allow it). Switch and switch-back operations can be performed manually.
A manual switch or switch back from the active job to the inactive job is allowed if: - There is no switching trigger raised on the inactive job or - There is a switching trigger raised on the inactive job but with a lower criticality than on the active job.
A running standby backup job can be automatically stopped if it is not active, another SDI redundant backup job must be activated (automatic switch) and no SDI input or CPU resources are available.
An active backup job can be automatically switch-back (even if "Automatic switch-back = On backup failure" redundancy mode is selected) when: - The main job has no switching trigger raised. - And another SDI redundant backup job must be activated (automatic switch) and no SDI input is available. - And it is not possible to free SDI resources stopping a standby backup job.
SDI Redundancy Settings
To create a redundant job from SDI input: 1. Create and configure the SDI system The declaration of SDI input / matrix, the linking of SDI input to existing nodes is done in the Hardware/SDI panel. Refer to section ’Declaring SDI sources connected to a Node’ on page 151.
When an SDI topology is created in the Hardware/SDI panel, it is automatically recognized as an SDI topology with redundancy or not.
160 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
2. Select the Redundancy mode The declaration of redundancy mode is done in the Hardware/SDI panel. Refer to section ’Hardware/SDI Panel’ on page 188.
Figure 3-114. SDI panel - Redundancy Mode Select
3. Select if the backup job must be Stopped or Running when it is in Standby A running backup job is an instantiated job. The backup job is running but it is not active. This allows faster switching to the backup job if the main job fails. The selection can be done in the Workflow tab or in the Jobs tab. a. Backup job standby activity selection in the Workflows tab (all backup job(s) based on the workflow will be instantiated): - Edit the Properties of the workflow and display Global Parameters tab. - Select Backup job standby activity = Stopped when standby or Running when standby.
Figure 3-115. Backup job standby activity selection in the Workflows tab
b. Backup job standby activity selection in the Jobs list tab (after creating the job and if the Backup job standby activity parameter sets above is public): - Select the jobs and click Show job details.
Electra VS - Version 05.10 161 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
- Select Parameters tab. - Click Edit. - Select Backup job standby activity = Running when standby if the backup job must be instantiated. - Click Save.
Figure 3-116. Mirroring selection in Jobs list tab
6 4 2
3 1
5
Figure 3-117. Mirroring selection in the Live SD-HD Encoder Jobs list tab
162 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
4. Set the switching trigger SDI signal loss is an optional switching trigger. It is by default enabled. It may be disabled in the Jobs list tab modifying the Job switching on SDI sync loss parameter or in the SDI input module modifying the Job switching trigger parameter.
Job not running is also a switching trigger. It can not be disabled
Figure 3-118. Switching trigger selection in the Live SD-HD Encoder Jobs list tab
Figure 3-119. Switching trigger selection, SDI input module
Electra VS - Version 05.10 163 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Operating Instructions (Tutorial)
SDI Redundancy Monitoring
Refer to section ’Jobs List Tab’ on page 198 and section ’SDI Redundancy Monitoring Tab’ on page 206.
Figure 3-120. Jobs list tab
Figure 3-121. SDI Redundancy monitoring tab
164 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
GUI Description
This section provides full details of the Electra VS interface menus.
Header Tab
Figure 3-122. Header bar
The status bar gives the following information:
Import: lets you import to the server the workflows and jobs of an exported file (see Export command below).
Export: lets you export a file from the server, containing the whole system configuration, all the workflows and jobs present on the server.
About displays software and hardware information about the equipment.
Serial number
Version number You can also find contact information for Harmonic.
Figure 3-123. About
Electra VS - Version 05.10 165 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
CPU: graphical indication of the allocated CPU, in percentage, based on the average value of all nodes of the system except those that are unreachable.
Memory: graphical indication of the allocated memory, in percentage, based on the average value of all nodes of the system except those that are unreachable. Measured usage is indicated by a green horizontal bar.
Status: general status of the Electra VS equipment. See Table 3-1 ’Status pictograms’ on page 90 for the list of possible statuses.
Connection
Date and Time
Time zone: lets you force the time zone value to apply to the graphical user interface, which can be selected among:
Figure 3-124. Time zone
Local: The time zone of the supervision PC device
UTC
Any time zone GMT - XXX available in the list
This settings is taken into account for the display of all date and time values in the client GUI: time in the status bar and logs raising and clearing times (active and closed) in the Logs panel, as well as jobs times in the Jobs panel. This setting does not have any impact on the time of alarms stored in the database, or on the time in other client GUI connected to the equipment. This is different from the date and time settings that you set in the Setup tab, as those apply to the equipment.
166 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Setup Tab
The Setup tab lets you define all the parameters related to the Electra VS. The Setup tab includes several panels, detailed in the coming sections.
Setup/Identity
The Identity panel lets you assign a name to the Electra VS and describe it.
Figure 3-125. Setup tab – Identity category
Parameters:
Device name: enter your chosen name for the Electra VS.
Description: provide a brief description of the Electra VS.
Specifying these parameters enables you to identify the Electra VS in a list of equipment more easily, for example if the Electra VS is integrated into a management system.
Electra VS - Version 05.10 167 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Setup/IP
The IP category lets you configure all the parameters related to the IP network.
It is divided into six main areas.
Network interface profiles
Figure 3-126. Network interface profiles
The physical interfaces are the NIC of the hardware platform. A logical interface can be a bond (aggregation of 2 physical interfaces) or can be directly associated to a single physical interface. Each Network interface profile applied to a configurable set of nodes define the logical interfaces, and their relations to the physical interfaces. The logical interface is then used in the IP setup to configure LAN.
Pre-defined profiles are automatically created and linked to Harmonic on-the-shelf hardware platform (server 1U platform, server 6U platform, server 10U platform) when present in the Electra VS. These network interfaces profiles cannot be modified.
Network interface profile are also automatically created each time you integrate a new hardware platform type in the system automatically detecting the physical interfaces detected on the platform.
You can create new profiles, or duplicate the off-the-shelf platforms profiles
168 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
In each Network interface profile, you can link the physical interfaces to a logical interface declaring its name, you can define the bonding and if alarms shall be raised when the link is down.
About Hardware delivery (1RU, 6RU, 10RU platforms): An 1RU platform can be associated with another Network interface profile. On the other side, the Network interface profile of a blade in 6RU or 10RU platforms can not be changed.
LANs
Figure 3-127. LAN configuration
For each LAN the table displays the following processing components:
Number: number of the LAN, used to identify the LAN in logs.
Name
Network Address
Mask
Default gateway
Logical interface name
When selecting a LAN, additional parameters are displayed on the right:
Logical interface name: logical interface to connect to this LAN. The logical interface names are in bold if available on all the nodes linked to the LAN. Otherwise you will have to modify the network interface profiles to give an acces to the LAN to the missing nodes. For more information on blade interfaces, refer to Appendix F ’Network Settings’ on page 573.
Electra VS - Version 05.10 169 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Data access: there are two types of network:
Internal: reserved for communicating audio/video data between nodes (including communication between statmux controller and encoders).
External only: used for audio/video data exchanged with the outside environment (both input and output) or for control-command purposes.
Management: reserved for management or control command purposes. You can configure protocol access from external only and management LAN in the Setup/monitoring tab (Refer to section ’Setup/Monitoring’ on page 176).
Master node virtual IP address: this is a virtual IP address allocated to the master node, allowing supervision of the Electra VS on this LAN. It allows you to connect to the Electra VS without knowing which node is currently the master node. You are recommended to set it on the control-command network.
VLAN tagging: VLAN tagging is IEEE 802.1Q standard compliant and allows several Virtual LANs to be grouped on a single Ethernet network.
Maximum input bitrate and Maximum output bitrate: these bitrates may be automatically computed based on the link speed. They indicate the maximum quantity of data that the system is allowed to exchange on the network. These values are used by the load-balancer to check that there is enough network bandwidth to instantiate a job on a node.
If you are using VLAN tagging to share an Ethernet network between several VLANs, you must define the available bandwidth allocation between the VLANs: this is done via the above two parameters.
All nodes: this mode lets you quickly configure the network on all the nodes.
Ranges: use this mode if you want to apply a different configuration on the nodes, for instance to authorize access to a network from certain nodes only or use non contiguous addresses.
First address: address of the first node. Node #1 will have this 1st address, Node #2 will have this address plus 1, etc.
Routes
Figure 3-128. Route configuration
170 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
The table shows a list of routes and displays the following for each one:
IP address
IP mask
Gateway
Metric: lets you define a preferred path if there are several routes to reach the same destination. By default, the IP stack always chooses the least costly route.
DNS
DNS servers are used by Web TV outputs (HLS, RTMP, Smooth Streaming and MPEG-DASH) and optionally for remote file storage in several components (file storage in input and output components, thumbnail file storage in Video decoder, text or image file storage in Video Overlay, ....). If the connection is lost, the Electra VS performs a DNS request and the connection is quickly restored.
Figure 3-129. DNS configuration
You can specify up to 3 DNS servers.
For each server, check the box and enter its IP address in the field.
If you want to specify a DNS suffix, check the corresponding box and enter a suffix value in the field.
System Private LAN
Figure 3-130. System private LAN configuration
This area contains parameters related to the private LAN of the system:
Logical interface name: always interface INTF_1.
Electra VS - Version 05.10 171 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Number: number of the LAN, used to identify the LAN in logs.
Network address
Network mask
Address range: range of addresses that the Electra VS can use. This range should include at least (more if possible) one address per node plus 2 addresses. Note that at least one of these addresses will be available through the included DHCP server, for any additional node or for a supervision PC. The first address is reserved for internal use, the second is for node #1, the third for node #2, etc.
Master node virtual IP address: this is a virtual IP address allocated to the master node, allowing supervision of the Electra VS on this LAN. It allows you to connect to the Electra VS without knowing which node is currently the master node.
IGMP
Figure 3-131. IGMP version configuration
This area lets you choose the IGMP version to use when performing IGMP requests to receive multicast streams: version 2 or 3.
This parameter should be coherent within the network (the same IGMP version should be used in the other system devices).
IGMP v3 allows you to receive a multicast stream from a specific source IP address (SSM mode).
172 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Setup/Network Storage
The Network Storage category lets you define specific storage locations on the system for subsequent direct access to logs, logo, text.
Figure 3-132. Network storage configuration
The table contains the list of network storage locations with associated details:
Name: name that you will be able to use to refer to this network storage. Note that this is a name, not a path: do not use the "/" or "\" symbol.
Type: Network File System (NFS) or Common Internet File System (CIFS).
IP address: IP address of the file server.
Directory: target directory on the file server. There are no conventions to observe in this field, simply follow those that match the type of network storage you defined. For instance, there is no need to enter a "/" or "\" symbol on Windows, but on a Linux operating system you must enter the full path to the network storage from the root.
Login: if authentication is required to access the network storage, enter the login.
Password: if authentication is required to access the network storage, enter the password.
Workgroup: if needed, specify the workgroup on which the network storage is located.
On Microsoft Windows, you must first share the directory before being able to mount it.
Setup/Hot Folder
A hot folder is a directory that, when you place a file in it, automatically detects the file and creates a job to apply the processing you specified.
The Hot folder category lets you set the parameters for hot folders. This is where you can create hot folders and define the processing to be applied to the files placed in them.
Electra VS - Version 05.10 173 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
You must create one hot folder for each processing type.
Figure 3-133. Hot folder configuration
1. Add 4. Apply
2. Set the hot folder parameters
3. Set the workflow parameters
The table shows the list of hot folders. Click one of them to access its parameters:
File network storage (mounting point): indicate in which network storage the hot folder should be created.
File folder: enter the name of the folder on the network storage where the hot folder should be created.
File name filter: if you want to process only some of the files placed in the hot folder, enter filter rules. For instance, if you want to process any file with a trp extension, enter: *.trp. Delete source file after treatment: check the box to delete the source file once the workflow has been applied to it.
Workflow: select the workflow to be applied to the files in the hot folder from the list. In the frame below the list of workflows, you can see the public parameters of the workflow. You can change the values as required. For workflows that use a file input, the network storage, file folder and file name parameters are automatically linked to the parameters set above for the hot folder. If you want to use different parameters, select the workflow parameter from the list and click the button to remove the link.
174 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
You can also specify the following parameters for the job:
Name: name of the job. The name of the file that triggered the job is also appended to the name of the job.
Priority (available for file workflows only): if there are not enough resources (CPU, memory, etc.) to process new jobs and you want this particular job to be processed anyway, set an important priority (between 1 and 250; 250 being the highest priority). The jobs with high priority will be launch. The jobs may be processed more slowly.
Speed (available for file workflows only): if set to 1, the job will last at most as long as the video duration. If set to 2, the job will last at most half as long as the video duration, etc. Note that if the network bitrate is too low, the speed target might not be met. If not configured, the job will be allocated the available resources of the most available node.
Electra VS - Version 05.10 175 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Setup/Monitoring
Figure 3-134. Monitoring configuration
The SNMP category lets you perform the SNMP configuration.
Read community: enter the name of the community.
Read/Write community: enter the name of the community.
SNMP port
The table gives you the list of trap destination IP addresses with their associated SNMP version.
For more information on SNMP, refer to Appendix B ’SNMP Management’ on page 551.
The LAN protocol access category lets you indicate the protocols accessible from external only and management LANs. You can allow or block HTTP, HTTPs, SSH and SNMP connections.
It is recommended to allow protocol access only from management LAN in order to avoid security breaches.
176 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Setup/Date & Time
Figure 3-135. Date and time configuration
You can choose to:
Use the UTC date and time: enter the current date and time of your location.
Synchronize the Electra VS with an NTP server: choose NTP synchronize and enter the IP address(es) of one or more NTP servers.
Synchronize the Electra VS with one PTP Grandmaster Clock server: add the LAN number and domain number of the server.
You can also:
Select the Time zone to use from the drop-down list.
Enable the Automatic adjustment for the daylight saving time option.
Electra VS - Version 05.10 177 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Setup/User Accounts
The User accounts category is available provided you have administrator rights.
Figure 3-136. User accounts configuration
In this panel, you can define and manage user accounts and groups of users, via two tables and a LADP server section.
HTTPS must be active on the management network to enable LADP.
The table on the left lists the user accounts with their associated group. You can add or remove accounts using the and buttons.
The admin administrator account cannot be removed.
You can modify the values by double-clicking them in the table. A password protects each user account. The password can be saved locally (local) or retrieve from a remote server (LDAP). To change a local password, click the Change password button.
The table on the right lists the groups of users. You can add or remove accounts using the and buttons. Double-click the group name to set the actions that users of this group will be able to perform:
178 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Figure 3-137. Setting the actions that users of this group will be able to perform
System: you can grant rights for configuration and supervision, for supervision only, or no rights at all.
Workflow configuration: you can let the group’s users edit the configuration of the workflows or not.
Job configuration: you can grant rights for: - Jobs configuration - Modification of the jobs you created (User), of the jobs created by another member of your group (Group), of any job (All) or of no job (No).
Job supervision: you can grant rights for the supervision of the jobs you created (User), of the jobs created by another member of your group (Group), of any job (All) or of no job (No).
Simulation: you can let the group’s users launch simulation mode or not.
The LDAP server section at the bottom allows the configuration of the LDAP server access.
Figure 3-138. Setting the access to the LDAP server
You can activate it by checking Active LDAP server check box.
Electra VS - Version 05.10 179 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
LDAPS: check this box to activate LDAPS, and then select the certificate file to import and set the certificate type. If the certificate is incorrect, the LDAPS authentication will fail. LDAPS is usable only through HTTPS interface. You can activate it for the management LAN in the Setup/Monitoring tab.
Figure 3-139. Importing the LDAPS certificate
LDAP server: configure the LDAP server IP address and port.
LDAP server credential: configure the username and password required to access the LDAP server.
Base DN: configure the point from where a server will search for users. Example : dc=corp,dc=company,dc=com
Schema: set if the remote server implement Open LDAP or Active Directory.
Setup/Download
The Download category lets you manage software versions, licenses, and Recovery Points.
Figure 3-140. Download panel
Please refer to the Chapter ‘Servicing’ for further information on these features.
180 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Setup/Logs
The Logs category lets you define settings related to the logs generated by Electra VS.
It is divided into three parts.
Figure 3-141. Logs configuration
Export
Automatically export: click to automate the export of the logs and define the frequency.
Frequency: define how often the logs should be exported (in days, weeks or months).
Export logs older than: define the age that the logs should have to be exported (in days, weeks or months). The date taken into account is the date of log closure.
Network storage: choose from the list the network storage where the exported logs should be saved. To define network storage places, go to the Network Storage category. For more information, refer to section ’Setup/Network Storage’ on page 173.
Path: enter the path to where the exported logs should be saved on the network storage defined earlier. To set sub-directories, use the / separator. If the directories you enter do not already exist, they are automatically created. If no path is defined, the exported logs are saved at the root of the network storage.
Purge exported logs: if enabled, logs that have been exported will be deleted from the equipment. Note that if the export fails, for instance if the network storage is unreachable, logs are not purged.
Electra VS - Version 05.10 181 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
You can also click the Export now button to export the logs immediately. The name of the exported logs file follows the convention below: ExportLogs_yyyymmdd_hhmmss.txt where yyyy is the year mm is the month dd is the day hh is the hour (in 24 hour format) mm are the minutes ss are the seconds
For example, the file ExportLogs_20150406_101536.txt was saved on April, 6th of 2015 at 10:15:36.
Tip: you can open the logs export files in Microsoft Excel. For a correct display of the dates with Microsoft Excel: select the date column, right-click and select "Format cell...", and then select the category "Custom". In the field "Type", enter yyyy/mm/dd-hh:mm:ss.000 The exported logs file contains all the same categories of information as this displayed in the Logs tab, as well as additional information that is useful for a management system equipment.
Table 3-5. Categories of information about logs
Column name in the Column name in Description export file the GUI
Severity Severity
Category Category
Type Not available An event is punctual, and has a severity from information to critical. An alarm has a duration, and has a severity from warning to critical. A status has a duration and has a severity of information.
NId Node Id Identifier of the node
JobId Job Id
182 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Table 3-5. Categories of information about logs
Column name in the Column name in Description export file the GUI
ProbableCause Not available Identifier
Description Description
UTCStartDate Raising date Start date and time of the log
UTCEndDate Clearing date End date and time of the log
Resource Resource
JobName Job name Name and identifier of the job
JobStartDate Raising file time Used for file encoding. Indicates the start time of the log, based on the file start. For example, when encoding a 2 hours movie, this parameter will be in the range [0; 2 hours]".
JobEndDate Clearing file time Used for file encoding. Indicates the end time of the log, based on the file start.
The export feature exports all the logs stored in the database.
Purge
The Purge feature removes logs to clear the database. Only past logs can be purged.
Automatically purge: if enabled, the past logs are automatically removed from the Logs view after a given period. Specify the parameters.
Frequency: define how often the past logs should be purged (in days, weeks or months).
Keep logs for: specify how long the past logs should be kept (in days, weeks or months). All older logs will be removed during the automatic purge.
You can also click the Purge now button to purge the past logs immediately.
Electra VS - Version 05.10 183 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Supervision
This part is purely informative and indicates:
Percent usage: use rate of the logs database, in percentage. The database can host up to 1,000,000 logs.
Number of logs into database.
Setup/Advanced
The Advanced category presents the following options:
The ESAM (Event Signaling and Management) out-of-band section lets you enable POIS additional UDP port (listening) port on Electra VS and set its number. The UDP port 80 is always open. These ports are used for data exchanges between Electra VS and the Placement Opportunity Information System (POIS) as defined in the Real-time Event Signaling and Management API specification (ESAM) from CableLabs®. For more information, refer to Appendix ’ESAM’.
The Parental Control section lets you define the HTTP port for the reception of the parental sections from remote server (customer-specfiic protocol).
These ports are disabled if Allow HTTP connection is unchecked. Refer to section ’Setup/Monitoring’ on page 176.
Figure 3-142. Port for ESAM out-of-band
184 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Hardware Tab
The Hardware tab includes several panels, detailed in the coming sections.
Hardware/Nodes Panel
The Nodes panel describes the nodes (i.e. blades or servers) of the Electra VS and the distribution of jobs in the nodes.
Figure 3-143. Nodes panel
Selected node
Job(s) in the selected node
The Nodes sub-panel table contains the following processing components:
ID: identifier of the node. This ID cannot be modified.
State: Master (possible only for a masterisable node) or Slave or Slave (can be master) or Preparing maintenance job or In maintenance.
Status (refer to Table 3-1 for status details).
CPU usage: allocated CPU, as a percentage. Measured usage is indicated by a vertical bar and can temporarily be higher than allocated. When a file encoding job is running on the node, the measured CPU can also be much higher than allocated.
Processing Capacity: maximal Processing capacity estimated for the node. The Node processing capacity in association with the estimated maximal cost of each job is used to determine on which node a new job can be launched. It is set manually (Set processing capacity), and can be calculated launching a NodeBench analyze on the node (Start NodeBench) or importing the result of a analyse (Import NodeBench). Refer to Chapter 7 ’Tools’, section ’Using VOS Flex NodeBench’ on page 467. The processing capacity configuration is reserved to the nodes resulting from «Virtualization delivery» or «Software only delivery». It can not be used with the nodes resulting from «Hardware delivery».
Memory usage: allocated memory, as a percentage. Measured usage is indicated by an horizontal bar.
CPU: number and type of CPU.
Memory: size.
Electra VS - Version 05.10 185 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Disk: number and capacity.
Description: serial number, vendor, type.
Profile: Network Interface profile linked to the Node. Refer to section section ’Network interface profiles’ on page 168.
From the Nodes panel, you can perform the following actions:
Figure 3-144. Commands available in the Nodes panel
Requesting a new license: click the New license request button. To find out how to request a license for a new node, refer to Chapter ‘Servicing’, section ’Requesting a new license File’ on page 411.
Searching for the nodes available on the internal system network. If you want to obtain a list of available nodes click the Add nodes button. Refer to Chapter ‘Servicing’.
Modifying the Processing capacity of a node:
Click the Start NodeBench button to launch the processing capacity analyze on the selected node if you don’t know its value.
You can perform the analyze only if the NodeBench files are present on the node. If the NodeBench files are missing, a popup request to download files. The files are delivered with the product in the DVD-ROM directory VOS Flex - NodeBench. The analyze cannot be launched on a node with running jobs. The analyze may take up to five hours.
When the NodeBench analyse is complete, the resulting processing capacity is indicated between brackets in the interface.
Figure 3-145. Processing capability .
186 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Click the Set Processing Capacity button to set it. If you reduce a capacity and if jobs are running on the node they may be stopped and may be restarted on another nodes. If the capacity is higher than the real capacity of the node the jobs may not work correctly.
Click the Export NodeBench button to upload the result file. You can download it on another node with the same characteristics.
Click the Import NodeBench button to download a result file in the selected node. The processing capacity will be updated. You shall use the result of an analyze in another node ONLY if the hardware and the BIOS version of the 2 nodes ares strictly identical.
Click the Delete NodeBench button to remove the result file. The processing capacity will not be changed but you will not be able to export the result file anymore.
Rebooting a node: click the Reboot node button. This operation may be requested after the activation of a new version (Linux kernel update, for example).
Setting a node in maintenance:
Click the Maintenance button to remove the node from the Electra VS and set it in maintenance mode. A node is set in maintenance after all the live jobs running on it are moved to other nodes and after all the file to file jobs are completed. The node remains in status Preparing maintenance as long as there is jobs running on it.
Click the Maintenance button again to reintegrate the node in the Electra VS. If the Slave (can be master) node is in maintenance mode and the Master node falls, there will be no Master node in the Electra VS. The Web interface will not be operational. You can force the reintegrationof the node from the Management Web Interface: - Enter its management IP address in a Web browser - Click on the Maintenance menu in the header.
Figure 3-146. Slave (can be master) node in maintenace mode, Management Web Interface .
Electra VS - Version 05.10 187 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Hardware/SDI Panel
The SDI panel provides a representation of nodes and SDI cards in the system and lets you configure SDI matrices and Redundancy mode to manage redundancy.
Figure 3-147. SDI panel
SDI redundancy mode selection
SDI matrix
SDI cards
SDI Cards
The nodes that contain SDI cards are represented. The slot in which the SDI board is installed is indicated.
You can double-click the board to name it and give a name to the sources connected on the inputs. This will ease configuration when creating workflows and jobs.
SDI Matrices
If you have a matrix in the system, you need to declare it in this view. The list of supported SDI matrices is available in Table A-60 on page 515.
The GUI displays a representation of the matrices declared in the Electra VS equipment.
To find out how to declare a matrix, refer to section ’Configuring an SDI System’ on page 149.
You can right-click a matrix processing component to access the following actions:
Properties: lets you see the properties defined when creating the matrix.
188 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Align (available in edit mode): aligns the processing components in the view.
Remove (available in edit mode): removes the matrix.
Copy crosspoints: copies the internal crosspoints of the matrix, that is the links between the inputs and outputs of the matrix, to the clipboard. You can then paste them into a text document (e.g. Notepad) or Excel document.
You can find the SDI matrix alarms in the Logs panel.
SDI Redundancy Mode
If SDI redundancy is managed in the Electra VS, you need to declare the Redundancy mode in this view. Refer to section ’SDI redundancy Mode’ on page 160.
The SDI redundancy mode is common to all the SDI redundant jobs running in the Electra VS.
Electra VS - Version 05.10 189 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Workflows Tab
The Workflows tab is where you are going to create workflows.
The Workflows tab is divided into two main parts:
The left part contains the list of all the existing workflows.
The right part displays the structure of the workflow selected from the list.
Left Area
The left area contains the following elements:
A series of buttons.
A search field, that lets you filter the list.
A list of existing workflows, sorted by category.
A Description field describing the selected workflow from the list.
Figure 3-148. Left area of the Workflows tab
Buttons
New: to create a new workflow.
Delete: to delete the workflows selected from the list.
Show: to display the details of the workflow selected from the list in the right area.
Edit: to display the workflow selected from the list in the right area and open it in edit mode.
Create job: to create a job based on the workflow selected from the list.
Rights: to set the rights to see, instantiate, modify, delete or manage the workflow.
190 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Figure 3-149. Rights on workflow
Export: to export all workflows, selected workflows, or displayed workflows, at your convenience. Refer to section ’Exporting a Workflow’ on page 195.
Import: to import a workflow. Refer to section ’Importing a Workflow’ on page 196.
Search
You can search the name of the workflows, the keywords defined for the workflows, or both. Click the arrow on the right of the search field to choose where to search.
Figure 3-150. Searching in the Workflows tab
List
The list contains a library of workflows and tools.
Workflows Library
The list displays the workflows that have been delivered with the software version, and the workflows that you or another user have created and saved.
Electra VS - Version 05.10 191 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Figure 3-151. Workflows library
The workflows displayed with a lock sign are those delivered with the software version that you cannot delete nor modify. Other workflows can be modified or deleted.
A shortcut menu is associated to each workflow. The following commands are available:
Delete, Show, Edit, Create job, Rights, Export for (instantiable) unlocked workflows
Create job, Rights for (non instantiable) locked workflows
These commands have the same effect as the buttons on the top bar of the Workflows tab left area (refer to section ’Buttons’ on page 190).
Description and details of workflows are given in section ’Workflow Library’ on page 229.
Tools
Two tools are available: the Choice and the Selector. They both let you define a condition in your workflow, to choose either the output or the input that should be used.
The condition can be set on a parameter that is already defined, or on a new parameter that will be displayed when creating the job.
The first met condition is applied.
Figure 3-152. Workflows tools
192 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
For more information on how to use these tools, refer to section ’Selector and Choice Tools’ on page 380.
Description
The description helps you understand the workflow. It indicates what the workflow does. Be sure to fill in the field carefully when creating a new workflow, as this information is very useful to people who create jobs and to people who create other workflows based on the one you created.
Right Area
The right-area is used to build a workflow as explained in section ’Building your Own Workflows’ on page 83.
Buttons
Figure 3-153. Buttons on the top-right area of the Workflows tab
The following buttons are available in this area to edit a workflow:
Layout: displays the list of public and protected parameters in a separate panel on the right, i.e. the parameters that are visible (protected) and editable (public) by job authors. In this panel, you will organize the visible parameters into sections and groups to facilitate job editing.
Properties: lets you set the properties of the workflow. You can also double-click the box of a workflow, located on the top-left corner of the right area to open this dialog.
Edit/Unedit: switches to the edit mode / cancels the changes applied to the workflow.
Save: saves the changes applied to the workflow. If there is at least one error message, the configuration is not applied. If there is at least one warning message, a confirmation is required. Be aware that all running jobs based on this workflows will apply the new parameters.
Check: checks the coherence of the workflow. If there are errors, a summary is displayed. You can click the links to open the processing component where the problem is located.
Duplicate: duplicates the workflow.
Delete: removes the workflow from the list.
Create job: creates a job based on the workflow.
Electra VS - Version 05.10 193 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Rights: lets you set the rights to see, instantiate, modify, delete or manage the workflow.
Copy and Paste Options
When manipulating a workflow in the right area, there are several possibilities to copy and paste processing components:
Paste at the location of the mouse pointer: select the processing component to copy, press Ctrl + C, then right-click and select paste, or press Ctrl + V. Multiple paste: to select several processing components to copy, hold the Ctrl key and click the processing components. You can then copy and paste the processing components as usual.
Copy from a workflow to another: you can copy one or several processing components from a workflow and paste it/them in another workflow.
When copying and pasting processing components, only the boxes are copied, not the links between them.
Parameters Name Conflict
If a parameter you are meaning to publish (parameter B) has the same name as a parameter already published (parameter A), a message is displayed to warn you and it offers you the following options:
Unpublish: unpublishes parameter B, which consequently remains private.
Cancel: cancels the action and lets you go back to the edition dialog to modify the parameters and avoid the name conflict.
Auto rename: automatically renames parameter B by adding a digit at the end of the name.
194 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Workflow Import and Export Options
Exporting a Workflow
It is possible to export workflows to a zip file.
From the list of workflows, you can export
all workflows
selected workflows in the Workflow Library
displayed workflows in the Workflows Library if filter is applied.
Figure 3-154. Exporting workflows
From the right area of the workflow panel, you can export the current workflow
Figure 3-155. Exporting a workflow displayed in the panel
You obtain a ZIP file containing the workflow you selected.
Electra VS - Version 05.10 195 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Importing a Workflow
To import a workflow that you have previously exported, or that someone else has transmitted to you, proceed as follows: 1. Click Import.
Figure 3-156. Importing a workflow selected in the list
2. Browse to select the ZIP file corresponding to the workflow to import.
In case of name conflict between the workflow contained in the zip and a workflow already present, the imported workflow is renamed (a popup indicates the new name of the workflow).
3. Click Open.
The workflow is added to the list.
Categories and Colors
A number of categories are defined by default. A color is associated to each category of workflow.
Colors are used in the list of workflows, and in the headers of the boxes in the right area.
Table 3-6 shows the colors associated with the categories available by default.
Table 3-6. Colors associated to categories of workflows.
Color Associated category
Input
Decoding
Preprocessing
Encoding
Output
Sample
196 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Table 3-6. Colors associated to categories of workflows.
Color Associated category
Favorites. Workflows of this category are preferentially proposed when creating a job.
You can create your own categories. In this case, you can associate the color. Proceed as follows:
Figure 3-157. Creating a category
1. Click the Properties button. 2. From the Category drop-down list, select Create a new category. 3. Enter a name for your category and pick a color from the color chart. 4. Click Ok.
Electra VS - Version 05.10 197 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Jobs Tab
The Jobs tab displays the list of existing jobs in the Job list tab and displays the monitoring of the redundant jobs in the SDI Redundancy monitoring tab.
Jobs List Tab
Figure 3-158. Jobs list tab
Redundant SDI job No redundant SDI job
Buttons
Figure 3-159. Buttons
If the job is redundant
The following buttons are available:
Create: lets you create a job from a workflow, to select from the displayed list.
Duplicate: duplicates the selected job. In the displayed dialog, enter a name for the new job, and if necessary, adjust the parameters. Click Create to validate job creation.
Start: starts the selected job.
Stop: stops the selected job.
Edit: lets you change the configuration parameters.
Save: saves the configuration parameters.
198 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Switch: if the selected job is a redundant SDI job, switches from the main job to the backup job. This button displayed a windows that displays the backup job status and lets you select the switch mode:
Smooth: If required the backup job is created and it is activated after 10 seconds if the switching conditions permit it (Switching trigger status = not raised). This limits the disruption of service.
: If required the backup job is created and it is activated as soon as the switching conditions permit it (Switching trigger status = not raised). There may be a disruption of service.
Switch-back: if the selected job is a redundant SDI job, switches from the backup job to the main job.
Show job details: displays the configuration parameters and lets you change them, displays the job Node distribution, logs and snapshot.
Show workflow: displays the workflow that corresponds to the job in the Workflows tab.
Export: exports a ZIP file containing the jobs you have selected and the related workflows. If no jobs are selected you can choose in a pop-up window Export all jobs (default), Export jobs checked or Export jobs displayed.
Import: imports a ZIP file containing the jobs you want to import and the related workflows. If the workflows already exist, the imported workflows are renamed with the extension "ImportX".
Delete: deletes the selected job (the job must be stopped before deletion).
Jobs List Array
The Jobs list displays the list of all existing jobs. For each job various information is provided.
Electra VS - Version 05.10 199 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
By right-clicking on the titles of column or by click on , it is possible to select the columns that will be displayed or hidden.
Figure 3-160. Jobs list array
Right-click to select the information displayed
No redundant job Redundant job
For each job, the following information can be provided:
Logs: if checked the logs of the job will be displayed in the Logs tab. Refer to section ’Logs Tab’ on page 208.
Job id (Main/Backup): identifier of the main and backup jobs. These identifiers are automatically created. Active jod are in bold.
Job name: at your convenience. You can modify it in the job parameters.
Alarm status (Active Job): alarm status of the active job. List of possible status and their meaning is provided in Table 3-1 ’Status pictograms’ on page 90.
Backup is active: if checked indicates that the backup job is active. This column allows to see at first glance all the redundant job with backup active.
Activity status (Main/Backup): state of the main and backup jobs. See section ’State’ below.
Workflow: workflow on which the job is based.
Alarm status (Main/Backup): alarm status of the main and backup jobs. List of possible status and their meaning is provided in Table 3-1 ’Status pictograms’ on page 90.
Source: user who created the job.
Progress: for offline jobs only, indicates the progress percentage of the job.
200 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
You cannot modify the values in the array. To change the properties of a job, click the Show job details button.
By right-clicking on a redundant SDI job, a contextual menu allows manual switch and switch back operations. The operations are available only if Automatic switch-back = On backup failure redundancy mode is selected. Refer to section ’Hardware/SDI Panel’ on page 188.
State
Table 3-7 lists the possible states of the jobs and provides informations about the states and the possible actions that you can perform.
Table 3-7. Job states: colors, descriptions and possible actions
Description of the Job state Possible actions state
Wait The job has been Duplicate created and is waiting Stop before switching to Show parameters Running state. Show workflow Export Import
Running The job is being Duplicate executed. Stop Show parameters Show workflow Export Import Switch (for redundant SDI job) Switch-back (for redundant SDI job)
Completed Job execution has Duplicate ended. Start Show parameters Show workflow Delete Export Import
Stopped The job has been Duplicate created but not started, Start or started and then Show parameters stopped. Show workflow Delete Export Import
Electra VS - Version 05.10 201 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Filters and Sorting Options
You can filter and sort the jobs in the array to display only the ones on which you want to focus.
You can filter the jobs by their state - running, waiting, stopped - by checking the corresponding boxes.
Figure 3-161. Job sorting and grouping
filtering the jobs by their state grouping the jobs by their common characteristics
You can also group the jobs that have similar characteristics by selecting an option from the Group by list.
At the end of the sorting options line, the number of matching jobs is indicated.
Figure 3-162. Job sorting and grouping
Number of matching jobs
Job Details
To display ‘Job details’ panels, select a job from the list and click Show jobs details.
Figure 3-163. Show job detail’ button
‘Job details’ panels consists in the following panels:
(Job) Parameters panel
Logs panel
202 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Snapshot panel
Redundancy panel (if the job is a redundant job)
Nodes panel (if a job is running)
Figure 3-164. Job detail tabs
These panels are described below.
Job Parameters
Figure 3-165. Job parameters panel
This panel allows you to show/edit the job parameters.
You will find in the upper part:
Workflow: workflow on which the job is based (non-editable).
Id: Job id (Main/Backup).
Name: name of the selected job.
Submission date: date and time of creation of the job.
Start date: date and time when the job started.
End date: date and time when the job was stopped.
Type: real-time or offline.
Backup is active: If checked indicates that the backup job is active.
Alarm status (Active Job): Alarm status of the job (of the active job if the job is a redundant job).
Alarms status (Main/Backup): Alarm status of the job (of the main and backup jobs if the job is a redundant job).
Electra VS - Version 05.10 203 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Activity status (Main/Backup): Activity status of the job (of the main and backup jobs if the job is a redundant job).
Description of the workflow on which the job is based (non-editable).
You will find in the lower part the job parameters, displayed in a tree and sorted by sections and groups (if any). You can edit the values and apply them, even while the job is running.
Job Logs
Figure 3-166. Job Logs view
This panel gives the alarms and events related to the selected job.
The following information is provided:
Severity: see Table 3-1 ’Status pictograms’ on page 90.
Resource: resource to which the log refers.
Description: log description.
Raising date: log raising date and time.
Clearing date: log falling date and time (for closed logs only).
Job id: Job identifier if the job is a redundant job.
You can use the filter (Current logs only/Past logs only/Current & Past logs) to display only the ones on which you want to focus.
If the job is a redundant job, you can use the filter (Main/Backup/Main and Backup) to display only the ones on which you want to focus.
Job Snapshot
Figure 3-167. Job Snapshot view
204 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
The contents of input for the selected job is showed in a tree (available for jobs that include a TS file input or a TS over IP input only).
Job Nodes
Figure 3-168. Job Nodes view
No redundant SDI job
Redundant SDI job
This panel indicates the node(s) where the job is running.
The following information is provided for the selected job:
Node id: nodes used by the main and backup jobs if the job is redundant
State: state of the node(s)
Status: status of the node(s). See Table 3-1 ’Status pictograms’ on page 90
Description: node(s) description
Job id: Identifiers of main and backup nodes if the job is redundant
Job Redundancy
This view is displayed if the selected job is a redundant job.
Figure 3-169. Job Redundancy view
Active job is highlighted
This panel indicates the status of the selected redundant job.
The following information is provided:
Automatic switch-back: Status of the SDI redundancy mode. SDI redundancy mode must be set in the Hardware/SDI panel. Refer to section ’SDI Redundancy Mode’ on page 189.
Job name: name of the job
Electra VS - Version 05.10 205 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Main or Backup area
Job id: identifier of the main/backup job
Alarm status: alarm status of the main/backup job. List of possible alarm status and their meaning is provided in Table 3-1 ’Status pictograms’ on page 90.
Activity status: activity status of the main/backup job. List of possible activity status and their meaning is provided in Table 3-7 ’Job states: colors, descriptions and possible actions’ on page 201.
Switching trigger status: indicates if switch trigger is raised on the main/backup job: - Not raised: no switching trigger is raised. Switch or switch back operations on this job is authorized. The job can be set active. - SDI sync loss: no input SDI signal detected. Switch or switch back on this job is forbidden. - Job is not running: the job is not running due to lack of resources. Switch or switch back on this job is forbidden. - "-": the backup job is not started, the switching condition is unkown. Switch on this backup job is authorized but may fail if it is not possible to start the backup job (job not running) or if the SDI input is in sync loss.
SDI Redundancy Monitoring Tab
The SDI Redundancy Monitoring tab is displayed if the SDI topology is a topology with redundancy. It shows the information of all the SDI redundant jobs in view more oriented redundancy. The SDI redundancy mode is also displayed and can be modified. To modify it click Change and refer to section ’SDI Redundancy Mode’ on page 189.
Figure 3-170. SDI Redundancy monitoring tab
Redundant jobs To modify the SDI redundancy mode Active jobs
Refer to section ’Job Redundancy’ on page 205 to have the fields description.
206 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Snapshot Tab
The Snapshot view is available for jobs that include a TS file input ora TS over IP input.
It provides a tree representation of the transport streams’ composition, basing itself on MPEG, DVB or ATSC tables, as specified in the workflow or snapshot configuration.
Note that ghosts PID are not displayed.
Figure 3-171. Snapshot view
To know how to create a snapshot view, refer to section ’Using the Snapshot View’ on page 114.
Electra VS - Version 05.10 207 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Logs Tab
Purpose
The Logs tab, at the bottom of the view, lists all current and past equipment logs. It contains an array with the list of logs, filters and sorting options. Logs (current and past) are saved in a database on Electra VS hard drives.
Figure 3-172. Logs tab
Logs Array
The array provides the following information for each log:
Severity: see Table 3-1 ’Status pictograms’ on page 90.
Node Id: identifier of the node on which the error occurred.
Category: category of the log. See section ’Log Categories’ on page 564 for the list of categories.
Resource: resource to which the log refers.
Description: log description.
Raising date: raising log date and time.
Clearing date (for closed logs only): falling log date and time.
Job Id: identifier of the job to which the log relates, if applicable.
Job name: name of the job to which the log relates, if applicable.
Raising file time: in file mode, moment in the file when the log was raised.
Clearing file time: in file mode, moment in the file when the log was cleared.
Filters and Sorting Options
You can filter and sort the logs to display only the ones on which you want to focus. Filters and sorting options are located above the array. You can apply several types of filters simultaneously.
208 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
From the first drop-down list, you can choose to display only the current logs, only the past logs or both.
You can filter the logs by their source:
System: check the System logs box to display the logs that regard the system.
Job: choose if you want to display the logs that regard:
My jobs: only the jobs you created
Group jobs: the jobs created by members of your group: Group jobs.
All jobs.
Selected jobs: first select jobs in the array of the Jobs tab. Or select None if you do not want to display logs that regard jobs.
You can also choose to display the logs of only a given severity. Table 3-8 details the options of this filter and the logs consequently displayed.
Table 3-8. Options of the severity filter of the logs.
Option Icon Info Warning Minor Major Critical
Info to critical x x x x x
Warning to critical x x x x
Minor to critical x x x
Major to critical x x
Critical x
At the end of the sorting options line, you can see the number of displayed logs out of the number of logs that correspond to the filters.
See Appendix E ’Logs’ on page 563 for the list of logs (XML file).
Electra VS - Version 05.10 209 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Advanced
Click Advanced to define the number of logs that should be displayed in the array. This parameter is also taken into accounts for requests related to the logs.
Figure 3-173. Advanced
210 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Statmux Tab
The Statmux view combines a monitoring view and a configuration view.
It displays the list of MPTS with statistical multiplexing and for each of them, the list of video components included in the statistical encoding.
It lets you edit and checks the statistical multiplexing job parameters.
Figure 3-174. Statmux tab - Consult mode
List of MPTS with statmux
Stamux parameters for each VBR program in the selected MPTS: Selected MPTS • Name of the job included in the statistical multiplexing • PID of the video component • Minimum bitrate of the video component, in bits per second • Maximum bitrate of the video component, in bits per second • Quality of the video component, in percentage (set 90 for the maximum quality) • Fallback bitrate, in bits per second: this is the bitrate used if the communication is lost between the allocator and the encoder. This is not configurable, the value is automatically computed by the equipment. • State of the job • Status of the job
Parameters of the selected MPTS
Electra VS - Version 05.10 211 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Click Edit in the top-right corner of the tab and change the parameters at your convenience (if required).
Figure 3-175. Statmux tab - Edit mode
Statmux Editing
Refer to section ’Creating an MPTS Job with Statmux’ on page 121.
212 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Simulation Tab
Purpose
Simulation is used to determine the number of nodes and licenses required when designing a new Electra VS or increasing the number of jobs on an existing system.
When the simulation is satisfactory, you can export it and send it to Harmonic representative to order.
In simulation mode, the GUI no longer represents the actual state of Electra VS, but is dedicated to the simulation. If you want to continue to supervise the Electra VS during the simulation, it is necessary to open a new GUI. The simulation is not saved in the equipment.
Operating Instructions
Simulation involves several steps: 1. Creating a simulation. 2. Defining an hardware configuration. 3. Launching the jobs. 4. Adding hardware resource to enable job processing. 5. Checking the Fail-over. 6. Exporting the simulation, as required. 7. Determining the licenses required for job processing. 8. Quitting simulation mode.
These steps are described in the next sections.
Electra VS - Version 05.10 213 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Step 1: Create a Simulation
Display the Simulation view and click New to create a simulation.
Figure 3-176. Create a Simulation
Step 2: Define an Hardware Configuration
Define an hardware configuration
either from an empty configuration (From empty configuration button). Select this mode if you want to design a new system.
or from the current configuration (From current configuration button). Select this mode if you want to increase the number of jobs on the current Electra VS.
Figure 3-177. Create a Simulation
Simulation from an empty configuration
Simulation from the current configuration
214 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
If simulation mode is From empty configuration, the following parameters must be set:
Blade center C7000 (10RU): C7000 blade center is added to the configuration. The Power Supply must be selected. Choice between AC 200-240V single phase, AC 208V triple phase, AC 380V triple phase and DC 48V.
Blade center C3000 (6RU): C3000 blade center is added to the configuration. The Power Supply must be selected. Choice between AC 100-240V single phase and DC 48V.
Server 1RU: 1RU Server is added to the configuration. - If necessary, indicate the SDI board(s) and its model(s) in the server. - Indicate the server type. Choice between: Dual processor, Mono processor.
Number of nodes: number of nodes in the configuration. - diskless: node(s) without disk - with disk: node(s) with disk If simulation mode is From empty configuration or From current configuration, the following parameters must be set:
Redundancy module number: number of nodes used for redundancy purposes.
Check IP configuration. Check this parameter if you want simulation to check the network resource (addresses & bandwidth) required by all the jobs. 9. Click OK to launch the Simulation mode.
The Simulation view is displayed with a blue background to indicate that the GUI no longer represents the actual state of Electra VS, but is dedicated to the simulation.
Electra VS - Version 05.10 215 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Figure 3-178. Simulation view
The hardware configuration is visible in the Hardware tab. It corresponds to a virtual Electra VS if configuration has been created from scratch.
Figure 3-179. Hardware tab
216 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Step 3: Launch the Jobs
Create or add jobs corresponding to your needs.
Example: 6 Live SD-HD transcoding channels in IPTV.
The procedure for creating / modifying Jobs in simulation mode is the same as usual (it is described in section ’Creating a Job from a Predefined Workflow’ on page 92). 1. Select the Jobs tab. 2. Create a job through the Create button in the top-right area of the tab. 3. Select the ‘Live SD-HD transcoding’ workflow.
Figure 3-180. Creating/adding a job
Click the button ‘Create’
Select the workflow
Electra VS - Version 05.10 217 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
4. Set the public job parameters as usual (see section ’Live SD-HD Transcoder’ on page 101). 5. Enter the number of jobs to be created then start the jobs (see the figure below).
Figure 3-181. Starting the jobs
6 channels Start the jobs
Step 4: Add Hardware Resource (if Required)
Check the job state in the Jobs list panel.
Figure 3-182. Jobs status
1 x transcode running 5 x transcode waiting Not enough resource
If a job state is , add the necessary hardware resource (node or SDI board for a server ).
218 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
In this case the Simulation Status below will be .
Figure 3-183. Simulation status (failed)
1. In the Hardware tab, select the Rack category. 2. Enter the Edit mode.
To add node(s) to new blade center(s) or to add server(s) 3. Click the Add button in the top-right area of the tab then define the new resource characteristics.
Figure 3-184. Adding blade center(s) or server(s)
Add blade centers or servers
Electra VS - Version 05.10 219 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Select the type and the number of nodes.
Figure 3-185. Rack category – Add nodes
By default the hardware type of the added blades is performed to be the latest available one. If the simulation should be perform using old hardware, you can change the type of the added blade in Advanced tab. Click Advanced to select the type of blade, G7, G8, G8 v2 or G9.
Click Ok.
Click Apply.
220 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
To add a node to an existing blade center
Right click the empty location and select the node type to add.
Figure 3-186. Adding node to an existing blade center
Click Apply.
To remove a node or blade center
Right click the node to be removed and select Remove node or right click the blade center to be removed and select Remove rack.
Figure 3-187. Edit mode – Remove a node
Figure 3-188. Edit mode – Remove a rack
Click Apply.
The new resource is added to the configuration.
Electra VS - Version 05.10 221 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Figure 3-189. Hardware tab - new resource
New resource
Once the necessary hardware resource has been added, all the jobs show status and state.
Figure 3-190. Jobs status
6 x transcode running
Enough resource for 6 transcodes
Step 5: Check the Fail-over 1. In the Simulation tab, click the Compute button to launch the simulation computing.
Figure 3-191. Launching the Simulation computing - Simulation view
222 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
2. Check the simulation status.
Figure 3-192. Simulation Status - Simulation view (failed)
Figure 3-193. Simulation Status - Simulation view (OK)
Table 3-9. Simulation Status icon meanings
Simulation Status Meanings icons
The simulation is valid, all jobs can run on the Electra VS defined, in accordance with the number of nodes redundancy required.
The simulation is not valid. Either all jobs requested could not be instantiated or we do not have the number of redundancy nodes required.
The simulation status is undefined. Click Compute to determine it and read the simulation status icon.
3. Modify the hardware resource (Nodes to enable jobs processing, as required.
According to the simulation status (too many or too few Nodes), you can add blade centers, blades and servers (or remove if too many), as described in the previous step.
Step 6: Export/Import Simulation
A simulation can be exported to or imported from the same or a different device. The simulation is stored in a zip file. A Summary.xml file gives the list of the hardware and licenses needed to run the simulation.
Electra VS - Version 05.10 223 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Export Simulation
To export an active simulation, click Export in the Simulation view, specify the pathname to access the storage folder and click Export simulation file.
Figure 3-194. Export a simulation - Simulation view
Reversely, to import a simulation, click Import in the Simulation view, specify the pathname to access the storage folder and click Import simulation file. You are not allowed to import a simulation if it is already in progress.
Figure 3-195. Import a simulation - Simulation view
224 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Step 7: Consult the Licenses Required for Job Processing
The licenses required to process jobs are displayed in the Setup/Download view.
Quantity used: Number of licenses required to process jobs.
Quantity max: Number of licenses available on the equipment.
The licenses which are insufficient in number are displayed in orange. It has no impact on the simulation state but it indicates the number of licenses that you must acquire to run the system.
Figure 3-196. Setup/Download view - Licenses
License Part number Quantity
The licenses required to process jobs are also present in the exported XML file.
Electra VS - Version 05.10 225 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Figure 3-197. Licenses in the exported XML file
Step 8: Exit Simulation Mode
To exit simulation mode click Exit in the Simulation view. The simulation content is cleared.
Figure 3-198. Exit simulation mode - Simulation view
226 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Console Tab
The Console tab is available only if you are connected with an administrator account.
To display / hide the Console tab press CTRL+D keys.
The Console tab should be used only under the customer support’s supervision.
Figure 3-199 shows the different areas of the Console tab.
Figure 3-199. Console tab
The Clear buttons above the command list let you clear the list of commands.
The Clear buttons above Debug traces let you clear the Debug trace messages (in Dynamic mode only).
The Pause button lets you stop scrolling messages to be able to read them more easily.
Electra VS - Version 05.10 227 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — GUI Description
Footer Bar
Figure 3-200. Footer bar
The footer bar gives
the name of the connected user
the Electra VS name and IP address
the Electra VS software release
228 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Workflow Library
This section provides details on the content of the Workflow Library.
Figure 3-201. Workflow Library
Processing components
Favorite workflows
Sample workflows
Choice and Selector tools
Electra VS - Version 05.10 229 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
The Workflow Library is made up of the following elements.
Processing components: they constitute a workflow.
Figure 3-202. Workflow example
link
Processing components
In the example above, the workflow is made up of 10 interconnected processing components: TS over IP input, TS video extractor, TS audio extractor, Video Decoder, Audio decoder, H.264 AVC encoder, AAC-HE v2 encoder, TS video packetizer, TS audio packetizer, TS Multiplexer, TS over IP streamer.
Selector and Choice tools: they let you define a condition to choose the input or output of a processing component that should be used, respectively.
Favorite workflows: they are proposed preferentially when creating a job. The following predefined workflows are available:
Live SD-HD Encoder
Live SD-HD Transcoder
Live WebTV Transcoder You can add your own workflows in this category for a direct access when you create a job.
Sample workflows: If the predefined workflows do not fully match your requirements, you may build your own workflows from sample workflows delivered in the DVD-ROM.
230 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Processing Component Parameters Overview
To access the parameters of a processing component, double-click the processing component.
The Properties dialog box displayed for a processing component always looks the same. It contains:
A parameter tab with an array listing the parameters
One or several input tabs
One or several output tabs
A multi-instance check box
Figure 3-203. Parameters of a processing component in a workflow
Double-click
Parameters tab
Array with the list of parameters
multi-instance check box
Input tab
Output tab
Electra VS - Version 05.10 231 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Processing Component Parameters Array
The array lists the parameters that should be set for the processing component. It contains a row per parameter, and the following columns:
Name: name of the parameter, not editable.
Default value: click to enter a default value.
for private and protected parameters, the default value is applied when creating or starting a job.
for public parameters, the default value is proposed when creating a job but it can be modified. Any change of the default value does not apply to the running jobs.
Publish: choose if the parameter should be:
Private: the parameter is set and invisible when creating a job. This is the status you must use when creating a workflow for parameters that you do not want the job authors to see or change.
Protected: the parameter is visible but not editable when creating a job. Use this status if you want to let the job authors see the value of a parameter without being able to change it.
Public: the parameter is visible and editable when creating a job. Use this status for all parameters that the job authors must set.
Label (optional): click to choose an explicit name for the parameter, as it will appear to the workflow user instead of the original name. If you want to be able to link a parameter to a private parameter, it is imperative that you give a label to this private parameter. Refer to section ’Link Tool’ on page 236.
Value restriction: double-click to define restrictions for a value. Check the box and choose a type of restriction:
Range: enter the minimum and maximum values.
Figure 3-204. Restriction configuration on a processing component – Range
232 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
List: use this option to restrain the value to a list of values. Enter the possible values in the list. Click to add a value, and to remove a value.
Figure 3-205. Restriction configuration on a processing component – List
Condition
Figure 3-206. Condition configuration
Double-click the elements of the condition to set them:
Select a parameter from the available parameters. Only the public parameters with labels are proposed, as well as the parameters specially created to be used in the condition.
Choose the operator: equal to, different than, lower than or superior to.
Enter a value in the field. You can use the OR, AND and NOT operators on the right to build a more complex condition. Click if you want to remove a condition in the list (select it beforehand).
Summary: check the box if you want the parameter to appear in the summary of the workflow.
Electra VS - Version 05.10 233 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Processing Component Input/Output Tabs
Whether the Input and Output tabs are available depends on the nature of the processing component.
When such a tab is available, it lets you publish the input or output and specify a label, as well as setting some specific parameters.
Publishing Inputs and Outputs
Publishing the input or output is useful if the workflow you create is not a full, instantiable workflow, but is an intermediate workflow (i.e. a series of processing components) that will later be used in other workflows. In this case, you may for example publish the input of the first processing component and the output of the last processing component.
To publish an input or output, check the Publish box.
If you want, type a Label in the field.
Refer to section ’Creating Sub-Workflows’ on page 141.
Figure 3-207. Example of workflow embedding the sub-workflows
sub-workflow 'UM_Sub_WKF_AudioXCode'
Specific Input and Output Parameters
For some processing components, a table is also available and lets you define parameters for this specific input or output.
For example, in the TS multiplexer output processing component, you can set if the input type should be a program or a component.
234 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-208. Specific parameters in the TS multiplexer output processing component
Multi-Instance
The multi-instance feature lets you define how many instances of the workflow you wish to create.
To use the multi-instance feature, check the Multi-instance box.
Figure 3-209. Multi-Instances
The following parameters are displayed:
Disable parameter and set the multi-instance to a dependent input or output: this option lets you define as many instances as of inputs or outputs. First publish the input or output you want to use, and then check this box.
Name: enter a name for the multi-instance parameter.
Default value: enter the default number of instances.
Publish: set the publication status for the multi-instance parameter.
Refer to section ’Creating Workflows with Multi-Instantiable Processing Components’ on page 145.
Electra VS - Version 05.10 235 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Processing Component Common Parameters
Parameters or tools that are systematically or commonly found in the processing components are described in this section.
Conditioned Parameters Display Button
A workflow can contain a large number of parameters; some of them being conditioned on other parameters’ values. These are called conditioned parameters.
By default, conditioned parameters are hidden in the list of parameters and are displayed automatically when you select an option that requires setting other parameters. This prevents you from setting parameters that will not be used in the configuration.
If you want to display all parameters nonetheless, you can click the button. Conditioned parameters that should be hidden are grayed.
Figure 3-210. Conditioned Parameters
Conditioned parameter (hidden by default)
Publication Mode Switch Button
The button lets you apply the same publication mode to all the parameters of a workflow. The mode switches from public to protected and then private. Click the button until you reach the publication mode that suits you.
This is useful when you need to change the publication mode to a large number of parameters in a workflow.
Link Tool
When making a configuration where the same parameter is asked several times, it can be useful to set it once and then make a reference back to it. This is what the link tool is for. It lets you make a reference to a parameter that is already specified in another processing component.
The following conditions should be respected:
The two parameters must be of the same type.
The parameter toward which the link will be made must be public, or private with a label defined.
236 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Example 1: lets us consider an IPTV transcoding workflow. We want to have the same video PID in the output program as the one present in the input program.
Use the link tool as follows: 1. Open the first processing component. In our example, open the TS video extractor processing component. 2. Edit a label for the parameter you wish to take as reference (in our example, the Video PID).
Figure 3-211. Setting a label for the reference parameter
3. Select the parameter for which you wish to make a link to the reference parameter. In our example, select the Component PID in the first ‘Input’ tab of the TS multiplexer processing component.
Figure 3-212. Setting the link
1
3
2
Electra VS - Version 05.10 237 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
4. Click the button located in the top-right corner to build the link. 5. Select the parameter that should be used as reference (the parameter to link with).
Figure 3-213. Selecting the parameter to link with
In the TS multiplexer processing component, you can see that there is now a link to the reference.
Figure 3-214. Link established between two parameters
You can click the link to open the processing component in which the parameter is specified.
To remove the link, select the parameter and click the button again.
In case you try to remove the processing component toward which a link is made, a message is displayed to warn you. Click Cancel to cancel the removal, or OK to proceed, knowing that the links will be broken.
Example 2: We want to use the same PMT PID for the output program: you set a label to the input PMT PID parameter in the TS video extractor processing component, and link the output PMT PID parameter in the TS multiplexer processing component to this parameter.
238 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-215. Setting a label for the input PMT PID reference parameter
Figure 3-216. Setting the link
1
3
2
4
Figure 3-217. Link established between the two PMT PID parameters
Electra VS - Version 05.10 239 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Processing Component Specific Parameters
This section lists all processing components and details their specific parameters. Processing components are sorted by category.
Inputs
TS over IP Input
Description
The TS over IP input processing component manages a MPEG-2 TS, over UDP/IP or RTP/UDP/IP.
MPTS (multiple program) and SPTS (single program) are supported.
CBR and VBR TS are supported.
Figure 3-218. TS over IP input parameters
Parameters
For this processing component, you must set the following parameters:
IP address: set the IP and LAN parameters. If it is a unicast address, it must be part of a local network and must be consistent with the IP configuration of the Electra VS.
Figure 3-219. IP parameters
225.1.4.5#4 stands for IP = 225.1.4.5 on LAN 4
240 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
UDP port: set the port used to get the stream.
Select source IP address: set to true if you want to choose the source of the stream. In this case, fill in the Source IP address field. You can specify only one source IP address. If you do this, only the datagrams from this source IP address are used. SSM mode is used to join a multicast input stream only if IGMP version 3 is configured in System parameters (Setup tab, IP category).
Synchro loss threshold: set the number of milliseconds after which the absence of signal in input is considered a loss of synchronization raising an alarm and a backup switch-over (if any).
Maximum TS bitrate: enter the maximum bit rate of the transport stream, in bits per second. Be sure to set a correct value as the system will use it to decide which node will be able to manage this input.
Define backup input: set to true if you want to define a backup input for this input. In that case, enter values in the Backup input IP address and Backup input UDP port fields.
Monitoring view: set to True if you want to create a snapshot view for this input. In this case, indicate the Standard that the input stream respects (DVB, MPEG-2 or ATSC), so that suitable information will be displayed.
Standard: select the standard between MPEG-2, DVB, ATSC.
Add latency for network jitter smoothing: set to 0 ms if you want to reduce the product latency and if your input streams have low jitter. If your input stream have a high level of jitter, it is recommended to increase the value. 1s to correspond to the product previous behavior in version v03.08 and below.
TS file input processing component supports:
SPTS in CBR and VBR (i.e. without stuffing packets) modes
MPTS in CBR mode only (MPTS in VBR mode are not supported)
Figure 3-220. TS file input parameters
Electra VS - Version 05.10 241 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Parameters
For this processing component, you must set the following parameters:
TS file storage: location on the server where the TS file to import in input is stored. Several methods allows to define the location. Refer to section ’Video overlay’ on page 296 for the possible syntaxes.
TS file folder: folder on the network storage where the TS file to import in input is stored.
TS file name: name of the TS file to import in input.
Iterations: number of consecutive times the file will be played.
Loops are not seamless: there are continuity counter errors, and audio/video disruption.
Monitoring view: set to True if you want to create a snapshot view for this input. In this case, indicate the Standard that the TS file to import respects (DVB, MPEG-2 or ATSC), so that suitable information will be displayed. For more information on snapshot views, refer to section ’Using the Snapshot View’ on page 114.
Standard: select the standard between MPEG-2, DVB, ATSC.
The TS bitrate is automatically computed from the file PCRs.
242 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
TS Video Extractor
Description
This workflow extracts a video stream from a TS.
The output video elementary stream can be forwarded to a video decoder, for example.
Figure 3-221. TS video extractor parameters
Parameters
Program number: program number (also known as Service ID in DVB standard) of the program (or service) that contains the requested video stream. You can also use one of the predefined values:
First one: the first program referenced by the PAT table is considered. This value is suitable when the input TS is a single program TS (SPTS).
All: all the programs referenced by the PAT table are processed.
PMT PID: PMT PID of the program that contains the requested video stream. When set to Auto, the value will be automatically discovered by the device. This parameter is useful when you want to use the same PMT PID for the output program: you can set a label to this parameter, and link the output PMT PID parameter to this parameter.
Video PID: PID of the requested video component. You can also use one of the predefined values:
First one: the first video component that matches the global criteria is processed.
All: all the video components that matches the global criteria are processed. Can be useful when you want to process the video of all the programs of a MPTS, for example.
Electra VS - Version 05.10 243 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Maximum format: maximum format than this input can receive. You can use one of the predefined formats, or Custom: in this case, you will have to define Maximum picture size and Maximum frame rate. Note: this parameter allows to allocate the system resources (CPU, memory, license) to the job. If it is higher than the real one (for example HD 1080i@30 fps is selected while the input is SD), then system resources are wasted (but it works). If it is lower than the real one, then the stream will not be decoded. If Maximum format is set to HD 1080p@60 fps or UHD 2160p@25/30/50/60 fps, color dynamic range parameters are displayed. You can select a dynamic range between SDR, HDR-HDR10, HDR-PQ10, HDR-HLG and depending of the Dynamic range you must configure the corresponding parameters: - If dynamic range is set to SDR, define the Color space. - If dynamic range is set to HDR-PQ10 or HDR-HDR10, define the Display primaries, White point position, Maximum and Minimum display mastering luminance, Maximum content and Maximum frame average light levels. - If dynamic range is set to HDR-HLG, define the HLG signaling. The following parameters can be set to Auto: Color space, Display primaries, White point position, Max and Min display mastering luminance, Max content light level, Max frame average light level. If it is the case, their values are extracted from the input stream if available. Note that if the parameters are not correctly configured alarms will be raised and the color dynamic range information are updated as follows: - If the input stream and the configured dynamic range are not consistent, the input information is broadcast without modification. - If the input stream is HDR and the configured dynamic range is set to SDR, input HDR information are removed from the output stream. - If the input stream is SDR and the configured dynamic range is set to HDR, if parameters are configured to Auto the output stream remains SDR otherwise configured HDR information are taken in account in the output stream.
Video Compression type: if set to Contribution then the video contribution streams are supported (refer to Appendix Technical Specifications Section Decoding Specifications to know the supported contribution video bitrates).
244 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Codec: H.264 or MPEG-2. If set to Any, the codec is automatically detected: this value is suitable when you do not want to use this parameter as a criterion to select the video stream. Note: this parameter allows to allocate the system resources (CPU, memory, license) to the job.
Clock management: if set to Convert to device internal clock (default value), then the input clock is converted to the device clock. If set to Keep input clock, then the input clock is kept. When you want to multiplex components from different input programs, the clocks shall be converted to the device clock. When you want to output a pass-through component that is scrambled, or that contains private sections that contain some clock values, you shall keep the input clock for the whole program.
Generate fake component on absence: set it to true if you want to create of fake component on absence of input component. When no video is detected at the extractor input then a fake video component is declared in the PMT with the configured information:
Fake Program Number
Fake PMT PID
Fake Component PID
Fake Codec When a real video is detected then the fake component is removed. Even if Program number or Video PID are configured to All only one fake component is created in the output PMT. This mechanism can be used to generate a Dash MPD if there is no stream at the input of the job.
If Maximum format is set to HD 1080p@60 fps or UHD 2160p@25/30/50/60 fps, color dynamic range parameters are displayed.
You can select a dynamic range between SDR, HDR-HDR10, HDR-PQ10, HDR-HLG and depending of the Dynamic range you must configure the corresponding parameters:
If dynamic range is set to SDR, define the color space.
If dynamic range is set to HDR-PQ10 or HDR-HDR10, define the Display primaries, White point position, Maximum and Minimum display mastering luminance, Maximum content and Maximum frame average light levels.
If dynamic range is set to HDR-HLG, define the HLG signaling.
The following parameters can be set to Auto: Color space, Display primaries, White point position, Max and Min display mastering luminance, Max content light level, Max frame average light level. If it is the case, their values are extracted from the input stream if available.
Electra VS - Version 05.10 245 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Note that if the parameters are not correctly configured alarms will be raised and the color dynamic range information are updated as follows:
If the input stream and the configured dynamic range are not consistent, the input information is broadcast without modification.
If the input stream is HDR and the configured dynamic range is set to SDR, input HDR information are removed from the output stream.
If the input stream is SDR and the configured dynamic range is set to HDR, if parameters are configured to Auto the output stream remains SDR otherwise configured HDR information are taken in account in the output stream.
246 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
TS Audio Extractor
Description
This workflow extracts an audio stream from a TS.
The output audio elementary stream can be forwarded to an audio decoder, for example.
Figure 3-222. TS audio extractor parameters
Parameters
Program number: program number (also known as Service ID in DVB standard) of the program (or service) that contains the requested audio stream. You can also use one of the predefined values:
First one: the first program referenced by the PAT table is considered. This value is suitable when the input TS is a single program TS (SPTS).
All: all the programs referenced by the PAT table are processed.
PMT PID: PMT PID of the program that contains the requested audio stream. When set to Auto, the value will be automatically discovered by the device. This parameter is useful when you want to use the same PMT PID for the output program: you can set a label to this parameter, and link the output PMT PID parameter to this parameter.
Audio PID: PID of the requested audio component. You can also use one of the predefined values:
First one: the first audio component that matches the global criteria is processed.
All: all the audio components that matches the global criteria are processed.
Nth: the component in the audio PID position that matches the global criteria is processed. You can optionally Raise a log when the component is absent.
Electra VS - Version 05.10 247 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Maximum number of audio channels: if the expected audio if 5.1, set this value to 6, if it is stereo, set this value to 2, and if it is mono, set this value to 1. Note: this parameter allows to allocate the system resources (CPU, memory, license) to the job. If it is higher than the real one, then system resources are wasted (but it works). If it is lower than the real one, then the stream will not be decoded.
Language: leave to Any if you do not want to use the language as a criterion to select the audio component, or use a code from the ISO 639 standard1 to specify it (for instance, enter eng for English, spa for Spanish, etc.). You can also use one of the predefined values.
Codec: AAC, MPEG-1 Layer 2, AC-3 or Dolby E. If set to Any, the codec is automatically detected: this value is suitable when you do not want to use this parameter as a criterion to select the audio stream. Note: this parameter allows to allocate the system resources (CPU, memory, license) to the job.
Clock management: if set to Convert to device internal clock (default value), then the input clock is converted to the device clock. If set to Keep input clock, then the input clock is kept. When you want to multiplex components from different input programs, the clocks shall be converted to the device clock. When you want to output a pass-through component that is scrambled, or that contains private sections that contain some clock values, you shall keep the input clock.
Generate fake component on absence: set it to true if you want to create of fake component on absence of input component. When no audio component is detected at the extractor input then a fake audio component is declared in the PMT with the configured information:
Fake Program Number
Fake PMT PID
Fake Component PID
Fake Codec
Fake Language When a real audio is detected then the fake component is removed. Even if Program number or Video PID are configured to All only one fake component is created in the output PMT. This mechanism can be used to generate a Dash MPD if there is no stream at the input of the job.
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
248 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
TS Component Extractor
Description
This workflow extracts, from an input MPEG-2 TS, the Transport Packets from a component of a program (service) or from a ghost component.
The descriptors associated to a program component are extracted as well, so you can forward it directly to an output TS program, as a pass-through component.
Figure 3-223. TS component extractor parameters
If the output is linked to a TS multiplexer processing component, the input descriptors will be kept in the output TS.
Parameters
Type: defines if you want to extract the component of a program, or a ghost component. Note: do not extract a PCR PID as a ghost component.
When Type is Ghost component:
First ghost PID and Last ghost PID: these parameters allows to select a range of PID (both values are included in the range).
When Type is Program component:
Program number: program number (also known as Service ID in DVB standard) of the program (or service) that contains the requested component. You can also use one of the predefined values:
First one: the first program referenced by the PAT table is considered. This value is suitable when the input TS is a single program TS (SPTS).
All: all the programs referenced by the PAT table are processed.
Electra VS - Version 05.10 249 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
PMT PID: PMT PID of the program that contains the requested component. When set to Auto, the value will be automatically discovered by the device. This parameter is useful when you want to use the same PMT PID for the output program, even when you do not know its value: you can set a label to this parameter, and link the output PMT PID parameter to this parameter.
Component PID: PID of the requested component. You can also use one of the predefined values:
First one: the first component that matches the global criteria is processed.
All: all the components that matches the global criteria are processed.
Component Type: Any, Video, Audio, Subtitle or Custom. Depending of its value, you will have to configure the following parameters.
Stream Type (if Component Type is Custom): The stream type in decimal of the requested component or one of the predefined values (from MPEG Standard).
Subtitle type (if Component Type is Subtitle): leave to Any if you do not want to use the Subtitle type as a criterion to select the component, or specify DVB subtitle or Teletext subtitle.
Subtitle component type (if Component Type is Subtitle): leave to Any if you do not want to use the subtitle component type as a criterion to select the component, or specify Normal or Hearing impaired.
Language (if Component Type is not Video): leave to Any if you do not want to use the language as a criterion to select the component, or use a code from the ISO 639 standard1 to specify it (for instance, enter eng for English, spa for Spanish, etc.). You can also use one of the predefined values.
Output type (if Component Type is Subtitle): this parameter is meaningful when a PID contains several subtitles, and only some of these subtitles match the criteria.
TS output: all the subtitles are extracted.
OTT output: only the subtitles that match the criteria are extracted, the others are removed from the component. This mode is not suitable for a standard TS output, but can be used for a WebTV output (HLS, MPEG-DASH, TS sent to a packager...).
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
250 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Clock management: if set to Convert to device internal clock (default value), then the input clock is converted to the device clock. If set to Keep input clock, then the input clock is kept. When you want to multiplex components from different input programs, the clocks shall be converted to the device clock. When you want to output a pass-through component that is scrambled, or that contains private sections that contain some clock values, you shall keep the input clock.
Generate fake component on absence: set it to true if you want to create of fake component on absence of input component. When no component is detected at the extractor input then a fake component is declared in the PMT with the configured information:
Fake Program Number
Fake PMT PID
Fake Component PID
Fake Language
Fake Stream Type When a real component is detected then the fake component is removed. Even if Program number or Video PID are configured to All only one fake component is created in the output PMT. This mechanism can be used to generate a Dash MPD if there is no stream at the input of the job.
Electra VS - Version 05.10 251 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
TS SCTE 35 Extractor
Description
This workflow lets you extract, from an MPEG-2 TS, the SCTE 35 sections from a program.
In the case of ESAM management, the output sections can be forwarded to a Chunker, that will send notifications to the POIS server for each section it received. The POIS server sends answers to the Chunker to validate, modify or discard these original input SCTE 35 sections. Thus, the Chunker is able to send new SCTE 35 sections to the TS multiplexer and it also will condition the output video stream to match the splice points validated by the POIS server.
In the case of simple SCTE 35 Conditioning, the output sections can also be forwarded to a Chunker, that will condition the output video stream to match the splice points. The Chunker will also forward the SCTE 35 sections to the TS multiplexer.
Figure 3-224. TS SCTE 35 extractor parameters
Parameters
Program number: program number (also known as Service ID in DVB standard) of the program (or service) that contains the requested SCTE 35 sections. You can also use one of the predefined values:
First one: the first program referenced by the PAT table is considered. This value is suitable when the input TS is a single program TS (SPTS).
All: all the programs referenced by the PAT table are processed.
Component PID: set a specific PID or choose All, to extract all the SCTE 35 components present in the PMT.
Clock management: if set to Convert to device internal clock (default value), then the input clock is converted to the device clock. If set to Keep input clock, then the input clock is kept. When you want to multiplex components from different input programs, the clocks shall be converted to the device clock.
252 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
SDI Input
Description
The input can be the input of an SDI matrix (when redundancy is required), or directly the SDI input of a node.
The maximum format of the video shall be given.
The display aspect ratio can be retrieved from input data (WSS and/or AFD), or can be manually forced.
Dolby Digital, Dolby Digital Plus and Dolby E inputs are supported.
SCTE104 over SMPTE2010 sections can be retrieved from SDI input and transcoded in SCTE 35 section. This feature depends on the SDI input board capability.
Figure 3-225. SDI input parameters
Parameters
For this processing component, you must set the following parameters:
SDI input: number of the physical SDI input to use. The names set in the SDI category of the Hardware tab are available in the list. If UHD 2160p format is configured you need to configure four SDI inputs.
Maximum video format: PAL, NTSC, or a variety of HD/UHD resolutions. If Maximum format is set to HD 1080p@30/50/59.94/60 fps or UHD 2160p@25/30/50/60 fps, color dynamic range parameters are displayed. You can select a dynamic range between SDR, HDR-HDR10, HDR-PQ10, HDR-HLG and depending of the Dynamic range you must configure the corresponding parameters:
Electra VS - Version 05.10 253 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
If dynamic range is set to SDR, define the color space.
If dynamic range is set to HDR-HLG, define the HLG signaling.
If dynamic range is set to HDR-PQ10, define if SEI 137 or SEI 144 are inserted.
If dynamic range is set to HDR-HDR10 or HDR-PQ10 with SEI 137 inserted, define the Display primaries, White point position, Maximum and Minimum mastering luminance.
If dynamic range is set to HDR-HDR10 or HDR-PQ10 with SEI 144 inserted, define the Maximum content and Maximum frame average light levels.
Output video bit depth: if it is set to 8 bits, the video will be re-quantized on 8 bits. If it is set to 10 bits, the video will be kept on 10 bits.
Job switching trigger: If set to true, if the SDI signal is missing (SDI sync loss) then the redundant job will be activated.
Default display aspect ratio: 16/9 or 4/3.
Display aspect ratio mode: Auto (WSS or AFD when WSS is absent), Auto (WSS), Auto (AFD), Manual.
If set to Auto (WSS or AFD when WSS is absent), set the Display aspect ratio when WSS and AFD are absent to Keep last WSS/AFD or Use default display aspect ratio in case of WSS and AFD absence. Set Raise a log when WSS and AFD are absent to true if you want to see a log for this absence.
If set to Auto (WSS), set the Display aspect ratio when WSS are absent to Keep last WSS or Use default display aspect ratio in case of WSS absence. Set Raise a log when WSS is absent to true if you want to see a log for this absence.
If set to Auto (AFD), set the Display aspect ratio when AFD are absent to Keep last AFD or Use default display aspect ratio in case of AFD absence. Set Raise a log when AFD is absent to true if you want to see a log for this absence.
If set to Manual, set Display aspect ratio to 16/9 or 4/3.
Number of audio components: enter the number of audio components that the SDI input contains. For each component, set the following parameters:
Mode: 5.1, Stereo, Mono Left or Mono Right.
254 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Source L/R: select the audio component to be extracted from the SDI signal. An SDI signal can contain several audio channels which can be dissociated (dual mono mode) or associated (stereo mode). Two mono audios or one stereo audio form an AES/EBU mux. AES/EBU mux are grouped into pairs, each one forming a group. An AES/EBU mux is referenced by the group number and the number of the AES/EBU mux in the group. The term channel in the audio source parameter in fact refers to the channel pair number.
SMPTE 272M Electra VS Audio labeling Group Channel
1 1 Group 1/Channel 1 - Mono Left
1 2 Group 1/Channel 1 - Mono Right
1 3 Group 1/Channel 2- Mono Left
1 4 Group 1/Channel 2 - Mono Right
2 5 Group 2/Channel 1 - Mono Left
2 6 Group 2/Channel 1 - Mono Right
2 7 Group 2/Channel 2 - Mono Left
2 8 Group 2/Channel 2 - Mono Right
3 9 Group 3/Channel 1 - Mono Left
3 10 Group 3/Channel 1 - Mono Right
3 11 Group 3/Channel 2 - Mono Left
3 12 Group 3/Channel 2 - Mono Right
4 13 Group 4/Channel 1 - Mono Left
4 14 Group 4/Channel 1 - Mono Right
4 15 Group 4/Channel 2 - Mono Left
4 16 Group 4/Channel 2 - Mono Right
Source C/LFE (5.1 mode): select the Center & Low Frequency Effects audio component to be extracted from the SDI signal.
Source Ls/Rs (5.1 mode): select the Right surround & Left surround audio component to be extracted from the SDI signal.
Number of Dolby components: indicate the number of component (Dolby Digital/Dolby Digital Plus or Dolby E audio) you wish to extract from the SDI input. Dolby Digital / Dolby Digital Plus components can be transmitted to an Audio decoder. Dolby E components can be transmitted to a Dolby E decoder.
Electra VS - Version 05.10 255 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Dolby x: source: group and channel of the Dolby source. For more details on groups and channels, see the Source L/R parameter explanation above.
Dolby x: codec: select AC3 for Dolby Digital/Dolby Digital Plus, or Dolby E.
Auto switch mode (if codec = Dolby E): set it to true if you want to activate an automatic switching between the Dolby E and a backup PCM 2.0 component. The backup PCM may be transported in the Dolby E component or may be a separate PCM component. The Dolby E / PCM transition is done in two frames (1/2 fade out frame, 1 silence frame, 1/2 fade in frame).
Raise a log when audio PCM is on air (if Auto switch mode = true): a minor alarm will be raised when the PCM source is on air.
For more information on SDI inputs, see also section ’SDI Inputs (Depending on Server Type)’ on page 513.
MP4 File Input
Description
This workflow manages a MP4 file input.
Figure 3-226. MP4 file input parameters
Parameters
For this processing component, you must set the following parameters:
MP4 file storage: location on the server where the MP4 file to import in input is stored. Refer to section ’Video overlay’ on page 296 for the possibles syntaxes.
MP4 file folder: folder on the network storage where the MP4 file to import in input is stored.
MP4 file name: name of the MP4 file to import in input.
Iterations: number of consecutive times the file will be played.
Loops are not seamless: there is audio/video disruption.
256 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
MP4 Video Extractor
Description
The MP4 Video Extractor processing component lets you extract a video stream from an MP4 file. The output stream can be forwarded to a decoder, for example.
Figure 3-227. MP4 video extractor parameters
Parameters
For this processing component, you must set the following parameters:
Maximum format: maximum format that this input can receive. This information is essential for the load-balancer as it will use it to allocate resources (CPU, memory, license). Setting an HD format when the source is SD results in Electra VS system underuse. If you choose custom, set the Maximum picture size and Maximum frame rate fields.
Track ID: you may enter the value directly in the field or use a predefined value:
First one: the first track that matches the criteria.
All: all the tracks that match the criteria.
Codec: H.264, MPEG-2, Apple ProRes, Any. If set to Any, the codec is automatically detected.
Clock management: if set to Convert to device internal clock (default value), then the input clock is converted to the device clock. If set to Keep input clock, then the input clock is kept. When you want to multiplex components from different input programs (to create a mosaic for instance), the clocks shall be converted to the device clock.
Electra VS - Version 05.10 257 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
MP4 Audio Extractor
Description
The MP4 Audio Extractor processing component lets you extract an audio stream from an MP4 file. The output stream can be forwarded to a decoder, for example.
Figure 3-228. MP4 audio extractor parameters
Parameters
For this processing component, you must set the following parameters:
Maximum number of audio channels: if the expected audio if 5.1, set this value to 6, if it is stereo, set this value to 2, and if it is mono, set this value to 1.
Track ID: you may enter the value directly in the field or use a predefined value:
First one: the first track that matches the criteria.
All: all the tracks that match the criteria.
Codec: AAC, MPEG-1 Layer 2, AC3 or Any. If set to Any, the codec is automatically detected.
Language: leave to Any if you do not want to specify the language of the audio component, or use the ISO codes1 to specify it (for instance, enter eng for English, spa for Spanish, etc.).
Clock management: if set to Convert to device internal clock (default value), then the input clock is converted to the device clock. If set to Keep input clock, then the input clock is kept. When you want to multiplex components from different input programs, the clocks shall be converted to the device clock.
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
258 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
RTMP Input
Description
The RTMP Input processing component lets you receive audio/video. Only single profile is supported. Multi-bitrate is not supported.
Figure 3-229. RTM input parameters
Parameters
For this processing component, you must set the following parameters:
RTMP server IP address: the destination IP address on which server will accept the connection. This is a virtual IP address that will be configured on the node that will instantiate this RTMP input.
RTMP Port: the destination TCP port on which server will accept the connection (default 1935).
Maximum IP bitrate: the maximum IP bitrate that will be broadcast to the Electra VS for the session.
Electra VS - Version 05.10 259 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
RTMP Video Extractor
Description
The RTMP video Extractor processing component lets you extract an video stream from a RTMP input stream. The output stream can be forwarded to a video decoder, for example.
Figure 3-230. RTM video extractor parameters
Parameters
For this processing component, you must set the following parameters:
Maximum Format: maximum format that this input can receive. This information is essential for the load-balancer as it will use it to allocate resources (CPU, memory, license). If you choose Custom, set the Maximum picture size and Maximum frame rate fields.
RTMP stream name: this parameter identifies the stream in the RTMP session.
Auto: the stream name is not checked.
Value: the stream name is verified, if it is different from the configured one, the video will not be extracted.
260 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
RTMP Audio Extractor
Description
The RTMP Audio Extractor processing component lets you extract an AAC audio stream from a RTMP input stream. The output stream can be forwarded to an audio decoder, for example.
Figure 3-231. RTMP audio extractor parameters
Parameters
For this processing component, you must set the following parameters:
Maximum number of audio channel: maximum number of audio channel that this input can receive. This information is essential for the load-balancer as it will use it to allocate resources (CPU, memory, license).
RTMP stream name: this parameter identifies the stream in the RTMP session.
Auto: the stream name is not checked.
Value: the stream name is verified, if it is different from the configured one, the audio will not be extracted.
Electra VS - Version 05.10 261 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
MXF File Input
Description
This workflow manages a MXF file input.
Figure 3-232. MXF file input parameters
Parameters
For this processing component, you must set the following parameters:
MXF file storage: location on the server where the MXF file to import in input is stored. Refer to section ’Video overlay’ on page 296 for the possibles syntaxes.
MXF file folder: folder on the network storage where the MXF file to import in input is stored.
MXF file name: name of the MXF file to import in input.
Iterations: number of consecutive times the file will be played.
Loops are not seamless: there is audio/video disruption.
262 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
MXF Video Extractor
Description
The MXF Video Extractor processing component lets you extract a video stream from an MXF file. The output stream can be forwarded to a decoder, for example.
Figure 3-233. MXF video extractor parameters
Parameters
For this processing component, you must set the following parameters:
Maximum format: maximum format that this input can receive. This information is essential for the load-balancer as it will use it to allocate resources (CPU, memory, license). Setting an HD format when the source is SD results in Electra VS system underuse. If you choose custom, set the Maximum picture size and Maximum frame rate fields.
Track ID: you may enter the value directly in the field or use a predefined value:
First one: the first track that matches the criteria.
All: all the tracks that match the criteria.
Codec: H.264, MPEG-2, Any. If set to Any, the codec is automatically detected.
Clock management: if set to Convert to device internal clock (default value), then the input clock is converted to the device clock. If set to Keep input clock, then the input clock is kept. When you want to multiplex components from different input programs (to create a mosaic for instance), the clocks shall be converted to the device clock.
Electra VS - Version 05.10 263 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
MXF Compressed Audio Extractor
Description
The MXF Compressed Audio Extractor processing component lets you extract a compressed audio stream from an MXF file. The output stream can be forwarded to a decoder, for example.
Figure 3-234. MXF compressed audio extractor parameters
Parameters
For this processing component, you must set the following parameters:
Maximum number of audio channels: if the expected audio if 5.1, set this value to 6, if it is stereo, set this value to 2, and if it is mono, set this value to 1.
Track ID: you may enter the value directly in the field or use a predefined value:
First one: the first track that matches the criteria.
All: all the tracks that match the criteria.
Codec: AAC, MPEG-1 Layer 2 or Any. If set to Any, the codec is automatically detected.
Clock management: if set to Convert to device internal clock (default value), then the input clock is converted to the device clock. If set to Keep input clock, then the input clock is kept. When you want to multiplex components from different input programs (to create a mosaic for instance), the clocks shall be converted to the device clock.
264 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
MXF Uncompressed Audio Extractor
Description
The MXF Uncompressed Audio Extractor processing component lets you extract an uncompressed audio stream from an MXF file. The output stream can be forwarded to a coder, for example.
Figure 3-235. MXF uncompressed audio extractor parameters
Parameters
For this processing component, you must set the following parameters:
Output mode: Mono, Stereo or 5.1.
xxxx Track: Each output channel can be assigned an input track. When the input track is set to None or is missing from the input file, the output channel is muted (a silence is generated).
Clock management: if set to Convert to device internal clock (default value), then the input clock is converted to the device clock. If set to Keep input clock, then the input clock is kept. When you want to multiplex components from different input programs (to create a mosaic for instance), the clocks shall be converted to the device clock.
Electra VS - Version 05.10 265 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
PS File Input
Description
This workflow manages a Program Stream file input.
Figure 3-236. PS file input parameters
Parameters
For this processing component, you must set the following parameters:
PS file storage: location on the server where the PS file to import in input is stored. Refer to section ’Video overlay’ on page 296 for the possibles syntaxes.
PS file folder: folder on the network storage where the PS file to import in input is stored.
PS file name: name of the PS file to import in input.
Iterations: number of consecutive times the file will be played.
Loops are not seamless: there is audio/video disruption.
266 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
PS Video Extractor
Description
The PS Video Extractor processing component lets you extract video stream from a Program Stream file.
The output stream can be forwarded to a decoder, for example.
Figure 3-237. PS video extractor parameters
Parameters
The parameters you set here act as filters for the component extraction, that is, the Electra VS will extract the component(s) it finds that matches the parameters you defined.
For this processing component, you must set the following parameters:
Maximum format: maximum format that this input can receive. This information is essential for the load-balancer as it will use it to allocate resources (CPU, memory, license). Setting an HD format when the source is SD results in Electra VS system underuse. If you choose custom, set the Maximum picture size and Maximum frame rate fields.
Stream Id: Stream identifier. If set to First component, the Electra VS will extract the first component it finds that matches the parameters you defined. If set to All, the Electra VS will extract the all components it finds that matches the parameters you defined.
Codec: H.264, MPEG-2 or Any. If set to Any, the codec is automatically detected.
Clock management: if set to Convert to device internal clock (default value), then the input clock is converted to the device clock. If set to Keep input clock, then the input clock is kept. When you want to multiplex components from different input programs (to create a mosaic for instance), the clocks shall be converted to the device clock.
Electra VS - Version 05.10 267 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
PS Audio Extractor
Description
The PS Audio Extractor processing component lets you extract audio stream from a Program Stream file.
The output stream can be forwarded to a decoder, for example.
Figure 3-238. PS audio extractor parameters
Parameters
The parameters you set here act as filters for the component extraction, that is, the Electra VS will extract the component(s) it finds that matches the parameters you defined.
For this processing component, you must set the following parameters:
Maximum number of audio channels: if the expected audio if 5.1, set this value to 6, if it is stereo, set this value to 2, and if it is mono, set this value to 1.
Stream Id: Stream identifier. If set to First component, the Electra VS will extract the first component it finds that matches the parameters you defined. If set to All, the Electra VS will extract the all components it finds that matches the parameters you defined.
Codec: AAC, MPEG-1 layer 2, AC3 or Any. If set to Any, the codec is automatically detected.
Language: leave to Any if you do not want to specify the language of the audio component, or use the ISO codes1 to specify it (for instance, enter eng for English, spa for Spanish, etc.).
Clock management: if set to Convert to device internal clock (default value), then the input clock is converted to the device clock. If set to Keep input clock, then the input clock is kept. When you want to multiplex components from different input programs (to create a mosaic for instance), the clocks shall be converted to the device clock.
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
268 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
YUV File Input
Description
Figure 3-239. YUV file input parameters
Parameters
For this processing component, you must set the following parameters:
YUV file storage: location on the server where the YUV file to import in input is stored. Refer to section ’Video overlay’ on page 296 for the possibles syntaxes.
YUV file folder: folder on the network storage where the YUV file to import in input is stored.
YUV file name: name of the YUV file to import.
Video format: format of the video stored in the YUV file to import. If set to Custom, also set the following parameters:
Picture size: size of the picture in pixels (H; V).
Frame rate: picture frames per second. This can be a decimal value.
Display aspect ratio: aspect ratio of the picture (4:3, 16:9).
YUV format: select the YUV format:
P010: 4:2:0,10 bits (coded on 16 bits, little endian), planar (different from Microsoft definition)
I420: 4:2:0, 8 bits, planar (different from Microsoft definition)
Iterations: number of consecutive times the file will be played.
Electra VS - Version 05.10 269 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Decoding
Audio Decoder
Description
Decode AAC-LC/AAC-HEv1/AAC-HEv2, Dolby Digital/Dolby Digital Plus, MPEG-1 Layer 2 audio.
Figure 3-240. Audio decoder parameters
Parameter
For this processing component, you must set the following parameters:
Dolby stereo downmixing: the decoder can be configured to downmix a Dolby Digital/Dolby Digital Plus 5.1 input to a stereo output. If the input is different from Dolby Digital/Dolby Digital Plus 5.1, this parameter is ignored.
Dolby compression mode: Controls the dynamic of the decoded audio signal. For the output level, select between Line mode and RF mode. RF mode can provide a better rendering when decoding audio with voices.
Dolby® E Decoder
Description
This workflow decodes Dolby E audio.
Figure 3-241. Dolby E decoder parameters
270 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-242. Dolby E decoder with Dolby E and PCM inputs connexions
PCM stream
Dolby E stream
Parameter
For this processing component you must:
Connect a Dolby E stream. It can come from an IP input or SDI input.
If it comes from an SDI Input, you shall connect the Dolby E stream on main input and optionally a PCM 2.0 reversion stream on secondary input. The automatic switch between the main and the reversion stream is configurable in the SDI input. The PCM reversion stream may also be embedded in the main input, in this case you do not have to connect the second one.
Set the following parameter:
Dolby compression mode: Controls the dynamic of the decoded audio signal. For the output level, select between Line mode and RF mode. RF mode can provide a better rendering when decoding audio with voices. If the input is different from Dolby Digital/Dolby Digital Plus, this parameter is ignored.
The Dolby E stream is de-embedded. The Dolby E source carries up to 8 audio tracks which may be combined to carry surround (5.1), stereo (2.0) or mono (1.0) audio programs. It is possible to decode up to 4 audio programs from the same Dolby E source.
Electra VS - Version 05.10 271 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Video Decoder
Description
Figure 3-243. Video decoder parameters
Parameter
For this processing component, you must set the following parameters:
Output video bit depth:
Same as input: the video will be quantized with the same bit depth value as the input.
8-bits: the video will be quantized on 8 bits whatever the bit depth value at the input.
10-bits: the video will be quantized on 10 bits whatever the bit depth value at the input.
Therefore it is recommended to apply the following rules: Set the parameter to Same as input if the input is MPEG 10-bits and you want to encode it in HEVC without preprocessing but resize. Set the parameter to 10bits if the input is MPEG 8-bits and you want to encode it in HEVC without preprocessing but resize. Set the parameter to 8 bits in all the other cases.
Generate thumbnails on remote server: If its value is true, then the following parameters shall be configured:
Use FTP/SFTP transfert: if the value is set to True then indicate the FTP username, FTP password to use and the FTP server address where the thumbnail files must be place. A valid address has to respect the patterns as in the following examples: "ftp://1.2.3.4:21/path" or "sftp://1.2.3.4:2021/path".
Thumbnail period: periodicity of the thumbnail generation. It can be configured between 10 and 300 seconds. The thumbnails are generated on best effort.
Thumbnail file storage: indicate the network storage where the thumbnail files must be place. It can be NFS or CIFS. Refer to section ’Video overlay’ on page 296 for the possibles syntaxes.
272 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Thumbnail file folder: indicate the path to the folder on the network storage where the thumbnails files must be placed.
Number of thumbnails: number of thumbnail exported. The following parameters shall be configured for each thumbnail: - Thumbnail X: height definition: the unit of the height in lines or in percent or 1/N of the original picture. - Thumbnail X: height value: the height of the thumbnail depending of the unit selected. Whatever is the height configured, thumbnail height will be at minimum set to 32 lines and at maximum the height of original picture. The number of columns is then computed from the input display aspect ratio, in order to obtain a jpg file with square pixels. The number of columns is for example 133 for 4:3 input and 100 lines. - Thumbnail X: file name: The file name can be customized with $time (current UTC time). Examples: File name = MyThumbnail.jpg. The created file has always the same name, the new one replaces the previous one. File name = MyThumbnail_$time.jpg. The 5th of February at 9h7 UTC, with a periodicity of 10 seconds, the files are: • MyThumbnail_20150205090700.jpg • MyThumbnail_20150205090710.jpg • ... The Electra VS is not responsible for old files deletion.
Support input variable frame rate: set this parameter to true if the input video has a variable frame rate. You shall also configure the Output frame rate. The output frame rate of this workflow is then constant.
Freeze duration: indicate the display duration of the last freezed image before displaying the slate.
Slate insertion: specify the expected behavior in case of loss of video signal.
Select infinite freeze to continue to display the freeze image when the a video loss occurs.
Select freeze then black to display a black slate when the video is lost.
Select freeze then slate insertion to display a specific slate picture when a video loss occurs. You shall configure: - Slate file storage: server location where the slate file is stored. Refer to section ’Video overlay’ on page 296 for the possibles syntaxes.
Electra VS - Version 05.10 273 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- Slate file folder: folder on the network storage where the slate file is stored. - Slate file name: name of the slate file. If there is no video component when the job is started, the video line is not created and by consequence the slate insertion will not be performed. If you want to have a slate insertion in this case you must configure generate fake component on absence to true in the Video extractor module.
274 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Preprocessing
Audio processing
Description
Process uncompressed audio.
Figure 3-244. Audio processing parameters
Parameters
This workflow offers:
Use audio mixer and Audio mixer mode: modifies the number of audio channels, from 5.1, stereo or mono to 5.1, stereo or mono.
If you want to downmix a Dolby Digital 5.1 or Dolby Digital Plus 5.1 audio, you are recommended to use the Audio Decoder processing component instead.
For stereo to mono down-mixing, 3 modes are available (Audio mixer Stereo to Mono conversion choice):
Mix: mono channel is built from both channels.
Left: the mono channel is the input left channel. This is useful for input dual channel.
Right: the mono channel is the input right channel. This is useful for input dual channel.
Use audio resampler: modifies the sampling frequency.
Electra VS - Version 05.10 275 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Use audio loudness control: performs automatic loudness control, static loudness control, or is a peak limiter.
Figure 3-245. Automatic loudness control
Figure 3-246. Automatic loudness control block diagram
The leveler is a limiter (compressor with an infinite ratio) with slow timing. The Peak compressor is a compressor with fast timing. It acts on the peaks that remain in the attack phase of the leveler. The Hard limiter is a limiter with very fast timing. When enabled, it removes the remaining loudness peaks after leveling and peak compressing. The output stage is equipped with a soft clipper to avoid any hard digital clipping.
276 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
If set to Automatic loudness control: - ALC mode: 3 modes are available: EBU R128, A-Weighting or Flat. - Compression ratio: from 1 to 100, with predefined values soft(2), medium(10) and hard(40). The higher the ratio is, the lower the output audio dynamic will be. - Loudness target: the target level. The unit depends on the ALC mode. In decibels in the case of FLAT or A-weighting ALC mode, or loudness units relative to full scale (LUFS) in the case of EBU R128 ALC mode.
The loudness level and correction are processed on the fly. Integrated in the long-term scale the loudness level may be lower than the entered loudness target.
- Noise level: when the input is lower than the Noise level, then the signal is not modified. level of noise below which the audio level is ignored by the loudness analysis, in decibels or loudness units relative to full scale (LUFS). Signal below this level is modified equally (without audio dynamic modification) according to the compression ratio and the loudness target.
If set to Static loudness control: a static gain is configured separately for all the channels. For mono input, the Left gain is applied.
If set to Peak limiter: the level is limited to Loudness target. It corresponds to the Automatic Loudness Control in Flat mode with a Compression ratio set to 1.
Audio delay: delays/advances the audio (+/- 3 seconds). Note: several audio delays can be added if a 3 seconds delay is not enough. In the case of a statmux program, the audio latency shall never exceed the video latency, so the global delay that you can apply on the audio component will be limited.
Audio mute: allows muting and unmuting dynamically. This can be useful for blackout management.
Electra VS - Version 05.10 277 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Tx audio interface AES67
Description
Broadcast stereo audio using AES67 protocol to external equipment. The Electra VS shall be connected to a PTP server.
Figure 3-247. Tx audio interface AES67 parameters
Parameters
This workflow offers:
IP address: IP address of the external receiver equipment. The multicast addresses shall be scoped in the range 239.192.0.0 to 239.192.128.0. The lower 15 bits correspond to the audio channel number.
Additional delay: adds a delay in the audio before sending it to the external device. If you connect the Electra VS to an external Mixer, this delay can be used to delay the audio coming from the Electra VS in order to synchronize it with another audio source. The Additionnal delay shall be identical in for all the modules connected to the same external equipment.
Rx audio interface AES67
Description
Receive stereo audio using AES67 protocol from external equipment. The Electra VS shall be connected to a PTP server.
Figure 3-248. Rx audio interface AES67 parameters
Parameters
This workflow offers:
278 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
IP address: IP address of the receiver equipment. If you use a xMixer, the first two digits are the equipment id and the last digit the audio channel.
Mixer Latency: set the latency introduced by the external equipment in the received audio.
Example
For the generation of a live multi-lingual commentary events, the following workflow shall be created: 1. Electra VS receives a TSoIP stream containing the event video and ambient noise audio(s). 2. The video is transcoded and integrated in the output SPTS. 3. The audios are extracted and transmitted to an external equipment using AES67 protocol. In the external equipment, the event ambient noise will be mixed with comments in different languages (4 in this example). In each Tx audio interface AES67 box, the additional delay parameter can be set so that the ambient audio is synchronized with the comment. 4. The mixed commentary and ambient noise stereo audios are received from the mixer (one per comment language). In each Rx audio interface AES67 box, the mixer latency parameter shall be configured to take in account the delay introduced by the mixing operation. 5. The audios are multiplexed with the source video.
Figure 3-249. Workflox using two Rx and Txaudio interface AES67 example
Video transcoding
Ambient audio decoding & transmission Mixed audios reception and encoding
Electra VS - Version 05.10 279 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
SCTE 35 Conditioner
Description
This workflow parses the SCTE 35 sections received and defines the video frames that will be encoded as IDR frames according with the following rules:
reception of a splice insert immediate or a time_signal, no IDR defined in the encoded stream.
reception of a not immediate splice insert OUT, determine a video frame that will be encoded as an IDR.
reception of a not immediate splice insert IN, determine the video frame that will be encoded as an IDR.
When no splice insert IN message is received after a splice insert OUT, the frame corresponding to return break point in the splice insert IN will be encoded as an IDR.
Only SCTE 35 splices insert, splices null and time_signal sections are broadcast at the SCTE 35 output.
The splice_schedule, bandwith_reservation, and private_commands are filtered.
Figure 3-250. SCTE 35 Conditioner in a workflow
Parameters
There is no configuration parameter.
280 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Chunker
Description
This workflow defines chunks for adaptive bitrate outputs. It defines the video frames that will be encoded as IDR frames among all following encoders.
There is no need to define chunks for audio components.
Figure 3-251. Chunker parameters
Parameters
Chunk duration: the duration of each chunk in seconds. Chunk is also known as fragment.
Chunk strategy:
Fixed duration: for example, when the video frame-rate is 29.97 fps, then a 1 second chunk will contain 29 or 30 frames (the average value will be 29.97 frames per chunk). The chunk duration is exactly 1 second.
Fixed number of frames: for example, when the video frame-rate is 29.97 fps, then a 1 second chunk will always contain 30 frames. The chunk duration is more than 1 second.
Segment duration:
A segment definition may be used for HLS (which usually requires higher chunk duration than the other formats) when a single encoding shall be used for both HLS and another format.
When the chunker is used for a TS output with EBP signaling, it defines the video frames that will be considered as a start of segment.
When an HLS output is defined, its chunk duration will be based on the segment duration if it exists, else it will be based on the chunk duration.
When used, this duration must be a multiple of the chunk duration (the start of a segment is always the start of a chunk).
Electra VS - Version 05.10 281 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-252. Segment and chunk for HLS
segment used for HLS
chunk
(10 seconds about) (2 seconds about)
ESAM conditioning: if set to true, the Event Signaling and Management (ESAM) is enabled. The chunker will insert chunk/segment start for the timestamps corresponding to splice in or out points that the Placement Opportunity Information System (POIS) server has validated. The incoming SCTE 35 sections splice_insert and time_signal are considered. The SCTE 35 output produces the SCTE 35 sections following the POIS indications. The following parameters shall be configured.
Figure 3-253. Chunker parameters (ESAM conditioning true)
Acquisition Point Identity: A required string, typically a system-wide unique string, identifying the Electra VS at a specific site on a specific channel/network feed.
POIS URL: the URL to reach the POIS server.
LAN to POIS or POIS IP address: this parameter can be a LAN or an IP address. If this is a LAN, then the IP address of the POIS server will be retrieved from the URL (using DNS if the name of the POIS server is given). The LAN shall be the one that will be used to send data to the POIS server.
Timeout for POIS response: the maximum allowed time for the response of the POIS to a request. After this timeout any response will be discarded. In this case, the original SCTE 35 incoming section is also discarded.
282 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
SCTE 35 conditioning: if true, the chunker will insert chunk/segment start for the timestamps corresponding to the splice in or out points defined in the incoming SCTE 35 sections (splice_insert). To improve stream stability the segment duration is adapted to avoid short segments. It may vary between ½ and 1½ time the configured duration. Refer to figure below.
Figure 3-254. SCTE 35 conditioning, segment duration adaptability
Stream with short segments
Stream without short segment
The following AST and AET parameters only impact MPEG-DASH outputs. Both parameters are only indicative. the segments continue to be generated at the Electra VS Dash output whatever are their values. The dates can be in the past or in the future but AET must be after AST.
Availability start time (acquisition date): the Availability Start Time (AST) is the time instant in UTC time at which an event becomes available at the MPEG-DASH output. Set it to auto if you want to use the acquisition time of the stream after the startup of the job. Set it to Custom if you want to declare an Availability start time and fill it with a custom time.
Availability start time offset: set it to Auto (internal latency) to let Electra VS add automatically the internal latency to the MPD AST. Set it to Additional (internal latency + extra latency) to let Electra VS add automatically the internal latency and a configured extra latency to the MPD AST. Set it to Custom if you want to configure the latency added to the acquisition time and fill the Custom offset field.
Availability end time (acquisition date): the Availability End Time (AET) is the time instant in UTC time at which an event ceases to be available. It is translated in the MPD as a MediaPresentationDuration parameter indicating the duration of the event (AST - AET). Set it to Custom if you want to declare an Availability end time and fill it with a custom time. The date can be in the past or in the future but it must be after the availability Start time.
Check Generate ATS Source Description if you want to generate an ATS Source description following the Adaptive Transport Stream Specification (see OC-SP-ATS-I01-140214 standard) for a TS output. Generating an ATS Description file make sense only if there is in the workflow a WebTv output in TS format. If checked you must also set:
Electra VS - Version 05.10 283 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
ATS Source Description storage: server location where the ATS file is stored. Several methods allows to define the location. Refer to section ’Video overlay’ on page 296 for the possibles syntaxes.
ATS Source Description file folder: folder on the network storage where the ATS file is stored.
ATS Source Description file name: name of the ATS file.
Check Use specific syntax and configure the External namespace containing the SPS parameter if you want to add SPS/PP and indexBox information in the ATS description file.
If you generate ATS file please check that your workflow follows the following rules: The input PIDs are used as « ContentComponent ID » in the ATS source description file. As product “Halo” requires that ContentComponent id (in the ATS source description file) equals to the component PID (in the TS file), please check that you configure the output PIDs to the same value as input PIDs. Select Encoder Boundary Point in TS Video Packetizer. Set Number of frames per PES to 1 in Ts Audio Packetizer. Use only one video component per SPTS. Do not share component in several SPTS.
284 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
DVB Subtitle Inserter
Description
This workflow burns DVB Subtitles in the associated video.
It allows, for a TS input program that contains DVB Subtitles, to extract the subtitles and burn them in the video.
Figure 3-255. DVB subtitle inserter parameters
As indicated in Figure 3-256 :
the video input shall be connected directly to the output of the Video decoder processing component. Note: you can insert a deinterlace between the decoder and this workflow, but you shall not add a resize or a clipping.
the DVB Subtitle input shall be connected directly to the output of a TS component extractor processing component, that extracts the PID that contains the DVB Subtitle for the video.
Figure 3-256. DVB subtitle inserter connection with inputs
Parameters
DVB Subtitle Composition Page Id: set the composition-page-id of the DVB Subtitles that shall be inserted. You can set to Auto, the composition-page-id will then be automatically discovered.
Electra VS - Version 05.10 285 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Mosaic Editor
The Mosaic Editor processing component generates a mosaic of video thumbnails.
Figure 3-257. Mosaic editor general parameters
For this processing component, you must set the following general parameters:
Mosaic size: choose a predefined SD, HD, or UHD format, or set to Custom and specify a Background picture size, which is the size of the file that will be used as the mosaic background, in pixels.
Mosaic frame rate: enter the frame rate that will be applied to the stream, in frames per second.
Use background color:
Set to True to use a color as background. In this case, specify the Background color (RGB value).
Set to False to use a picture as background. In this case, set the following parameters: - Resize the input picture for the background: set to true if your background input picture is not the same size as the mosaic you are creating. In that case, it is resized to fit into the background. - Background file network storage (mounting point): location of the file that will be used as the mosaic background. Refer to section ’Video overlay’ on page 296 for the possibles syntaxes. - Background file name (relative path included): name of the file that will be used as the mosaic background.
Background display aspect ratio: choose from the list the display aspect ratio that should be used for the mosaic background.
286 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-258. Mosaic editor specific parameters
Link inputs to add thumbnails to your mosaic. For each linked input, you must also set the following specific parameters:
Thumbnail size: size to which the input will be resized. Choose a format from the list or choose Custom and specify your values in the Custom thumbnail size field.
X and Y: position of the upper left corner of the thumbnail, relative to the upper left corner of the background.
Thumbnail order: order used if a thumbnail partially covers another one, to know which thumbnail should be on top of the other, 0 being in front of 1, etc. Make sure you do not use twice the same value as the overlap would then be random.
Electra VS - Version 05.10 287 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Video format converter
Description
Modifies the video format, using one of the following preprocessing features: Deinterlace, Interlace, Resize, Clipping, Bit depth conversion, Predefined conversion or Frame rate modification.
Parameters
For this processing component, you must set the following parameters:
Resize: the output size shall be configured. Interlace/progressive conversion is managed. Examples: 1080i@25 fps to 720p@50 fps (which includes a duplication of the frame rate), [email protected] fps to [email protected] fps (same frame rate). It is thus not necessary to add a deinterlace processing before the resize when the input is interlaced and the output is progressive.
Figure 3-259. Video format converter parameters - Resize
For this feature, you must set the following parameters:
Output size: select a standard format for the destination frame from the drop-down list or select Custom and set your own values for the width and the height in the Custom output size field.
Output display aspect ratio: leave to Same as input if you want the input aspect ratio to be kept in the output. If you want to force the ratio, select it in the drop down list (16:9 or 4:3) or enter it manually.
Display aspect ratio conversion strategy (if output aspect ratio different from input): select the strategy for the aspect ratio conversion. The Appendix H ’Aspect Ratio Conversions’ details the default conversion performed and the AFD value set according to the input AFD and aspect ratio.
288 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- Default: default strategy. The input AFD value will not be analyzed. Choose the conversion to be applied in case of narrower (Default conversion to narrover aspect ratio) and wider (Default conversion to wider aspect ratio) aspect ratio (Refer to Appendix ’Aspect Ratio Conversions’, Section ’Conversions according to default strategies and output display aspect ratio’). - AFD automatic: automatic AFD strategy. The input AFD value determines the conversion (Refer to Appendix ’Aspect Ratio Conversions’, Section ’Conversions according to input AFD and output display aspect ratio’). If no AFD value is set in the input video, the default conversion is applied. - AFD manual: manual AFD strategy. The configured AFD value determines the conversion (Refer to Appendix ’Aspect Ratio Conversions’, Section ’Conversions according to input AFD and output display aspect ratio’).
Output frame structure: choose if the video structure should be Progressive or Interlaced.
Modify frame rate: if set to False, the input frame rate is kept in output. If set to True, - define the Frame rate in frames per second. For instance, if you want to change a 1080@30 fps input into a 720p@60 fps output, you need to duplicate the output frame rate; using this parameter will give you the best video quality for this case. - define the Web TV: adaptation to external packager. Set it to true if all the following conditions are met: • A channel contains adaptive bitrate streams with different frame rates. • An external packager is used. The internal design of the external packager requires that the IDR frame of all the chunks of a given period has the same PTS. In this case, an adaptation may be necessary. If the external packager does not have this limitation, do not use this parameter as it may reduce the video quality. This parameter is ignored when there is no chunker before the frame rate adaptation. - Ensure accurate frame rate according to device internal clock: set to true when your output stream must be sharply synchronized with the device internal clock. Do not set this parameter to true if your workflow also uses the TS Video/Audio Extractor and the Clock Management parameter is set to Keep input clock.
Electra VS - Version 05.10 289 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Deinterlace: deinterlace the video
Modify frame rate: if set to False, the input frame rate is kept in output. If set to True, - define the Frame rate in frames per second. - define the Web TV: adaptation to external packager. Set it to true if all the following conditions are met: • A channel contains adaptive bitrate streams with different frame rates. • An external packager is used. The internal design of the external packager requires that the IDR frame of all the chunks of a given period has the same PTS. In this case, an adaptation may be necessary. If the external packager does not have this limitation, do not use this parameter as it may reduce the video quality. This parameter is ignored when there is no chunker before the frame rate adaptation.
Figure 3-260. Video format converter parameters - Deinterlace
Interlace: there is no parameter.
Figure 3-261. Video format converter parameters - Interlace
290 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Frame rate: the output frame rate shall be configured (this preprocessing should not be used with interlaced video).
Figure 3-262. Video format converter parameters - Frame rate
Web TV: adaptation to external packager: (this parameter is ignored when there is no chunker before the frame rate adaptation): when a channel contains adaptive bitrate streams with different frame-rates and an external packager is used, an adaptation may be necessary if the internal design of the external packager requires that the Idr frame of all the chunks of a given period has the same PTS. If the external packager does not have this limitation, do not check this parameter as it may reduce the video quality.
Ensure accurate frame rate according to device internal clock: set to true when your output stream must be sharply synchronized with the device internal clock. Do not set this parameter to true if your workflow also uses the TS Video/Audio Extractor and the Clock Management parameter is set to Keep input clock.
Clipping: clip a video.
Figure 3-263. Video format converter parameters - Clipping
A region of Cropped area size and located at [Cropped area X; Cropped area Y] is extracted from the input video, and inserted at
Electra VS - Version 05.10 291 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
[Insertion area X; Insertion area Y] in an output video of Output size.
Figure 3-264. Video format converter parameters - Clipping
Input video Output video
(Cropped area) X (Insertion area) X
Output size (Cropped area)
(Cropped area) Y area) (Cropped size Y area) (Insertion
If the extracted region does not cover all the output video, then the rest of the video is black.
Position [0;0] is the top left corner.
When Adaptive clipping is used, then different configurations can be applied depending on the input Display Aspect Ratio.
Figure 3-265. Video format converter parameters - Adaptive clipping
292 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Bit depth conversion: convert an input stream bit depth to 8 bits or 10 bits.
Figure 3-266. Video format converter parameters - Bit depth conversion
Output bit depth: the output bit depth available are 10bits or 8bits.
Predefined conversion: a list of predefined conversion is proposed, allowing easy configuration of conversions between usual video formats.
Figure 3-267. Video format converter parameters - Predefined conversion
Conversion: the predefined conversions available are: - PAL 576i @ 25 fps to HD 720p @ 50 fps - PAL 576i @ 25 fps to HD 1080i @ 25 fps - PAL 576i @ 25 fps to NTSC 480i @ 29.97 fps - PAL 576i @ 25 fps to HD 720p @ 59.94/60 fps - PAL 576i @ 25 fps to HD 1080i @ 29.97/30 fps - NTSC 480i @ 29.97 fps to HD 720p @ 59.94 fps - NTSC 480i @ 29.97 fps to HD 1080i @ 29.97 fps - NTSC 480i @ 29.97 fps to PAL 576i @ 25 fps - NTSC 480i @ 29.97 fps to HD 720p @ 50 fps - NTSC 480i @ 29.97 fps to HD 1080i @ 25 fps - HD 720p @ 50 fps to PAL 576i @ 25 fps - HD 720p @ 50 fps to HD 1080i @ 25 fps - HD 720p @ 50 fps to NTSC 480i @ 29.97 fps - HD 720p @ 50 fps to HD 720p @ 59.94/60 fps - HD 720p @ 50 fps to HD 1080i @ 29.97/30 fps
Electra VS - Version 05.10 293 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- HD 720p @ 50 fps to HD 1080p - HD 720p @ 50 fps to UHD 3840x2160 - HD 720p @ 59.94 fps to NTSC 480i @ 29.97 fps - HD 720p @ 59.94/60 fps to HD 1080i @ 29.97/30 fps - HD 720p @ 59.94/60 fps to PAL 576i @ 25 fps - HD 720p @ 59.94/60 fps to HD 720p @ 50 fps - HD 720p @ 59.94/60 fps to HD 1080i @ 25 fps - HD 720p @ 59.94/60 fps to HD 1080p - HD 720p @ 59.94/60 fps to UHD 3840x2160 - HD 1080i @ 25 fps to PAL 576i @ 25 fps - HD 1080i @ 25 fps to HD 720p @ 50 fps - HD 1080i @ 25 fps to NTSC 480i @ 29.97 fps - HD 1080i @ 25 fps to HD 720p @ 59.94/60 fps - HD 1080i @ 25 fps to HD 1080i @ 29.97/30 fps - HD 1080i @ 25 fps to HD 1080p - HD 1080i @ 25 fps to UHD 3840x2160 - HD 1080i @ 29.97 fps to NTSC 480i @ 29.97 fps - HD 1080i @ 29.97/30 fps to HD 720p @ 59.94/60 fps - HD 1080i @ 29.97/30 fps to PAL 576i @ 25 fps - HD 1080i @ 29.97/30 fps to HD 720p @ 50 fps - HD 1080i @ 29.97/30 fps to HD 1080i @ 25 fps - HD 1080i @ 29.97/30 fps to HD 1080p - HD 1080i @ 29.97/30 to UHD 3840x2160 - HD 1080p to PAL 576i @ 25 fps - HD 1080p to NTSC 480i @ 29.97 fps - HD 1080p to HD 720p - HD 1080p to HD 1080i - HD 1080p to UHD 3840x2160 - UHD 3840x2160 to PAL 576i @ 25 fps - UHD 3840x2160 to NTSC 480i @ 29.97 fps - UHD 3840x2160 to HD 720p - UHD 3840x2160 to HD 1080i
294 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- UHD 3840x2160 to HD 1080p Depending on the selected conversion you may have to choose the Output size and the Frame rate. For SD to HD conversion, the display aspect ratio is automatically converted to 16:9, using input AFD when present. Pillar box may be added, for example. For HD to SD conversion, the Output display aspect ratio may be either 4:3 or Same as input, at your convenience. The conversion to 4:3 uses the input AFD when present: letter box may be added, for example.
Electra VS - Version 05.10 295 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Video overlay
Description
The Video overlay processing component lets you insert an overlay with or without effects. An overlay is a static or animated image (a logo, for example), a scrolling text or a static text.
Parameters
Figure 3-268. Video overlay parameters - Text or Image insertion
For this processing component, you must set the following parameters:
Overlay: This parameter allows you to control the presence of the overlay. if set to Show the text or the image appears. If set to Hide it disappears (with effects if configured).
Type: The overlay may be Text or Image.
If you insert a text
Text source: the text source can be stored in a file (File) or entered by the user (Manual). If you select to import a text file (File)
Figure 3-269. Video overlay parameters - Text insertion - File import
Text file storage: server location where the text file is stored. Several methods allows to define the location: - Enter the name of network storage declared in the set up tab (recommended) or
296 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- Enter the complete server path using the following syntax: [CIFS|NFS]://login:password@[IP adress | hostname]/MyDirectory Using this second method we assume that the network storage is accessible from all the nodes of the Electra VS (no IP address or hostname verification is done before launching the job, therefore if the server is not accessible from the node the reception of the file will fail) If you enter a hostname, a DNS lookup will be performed every 30 seconds to check that the resolution of the IP address has not changed.
Text file folder: folder on the network storage where the text file is stored.
Text file name: name of the text file. Note that any modification of the file is immediately reflected on the insertion. If the file is empty, there is no insertion. If the file is missing, there is no insertion. If the storage is unreachable (network problem, for example), the last insertion persists (a job stop-start clears the insertion).
File encoding type: encoding type of the text file. If the text file type is not supported, the file must be converted to an available type.
Raise a log when text file is absent: if set to true, an alarm is raised if the file is missing. You should set this parameter to false if you want to control the apparition or disappearance of text by presence or absence of text file.
If you select to enter directly the text in the configuration (Manual) you must set the following parameter:
Figure 3-270. Video overlay parameters - Text insertion - Manual editing
Text content: enter the text to display.
In both cases you have to define the text font, transparency, color, stroke, and whether the text is scrolling or is static
Electra VS - Version 05.10 297 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-271. Video overlay parameters - Text insertion - text font, transparency, color, stroke, and scrolling or static
Font: select the font you wish to apply from the drop-down list. If set to Custom also set: - Font file storage: server location where the font file is stored. - Font file folder: folder on the network storage where the font file is stored. - Font file name: name of the font file.
Font size: size of the font, in pixels. Note that the font size means the line separation of a font, and does not refer to the actual height of the drawn letters. A letter will appear bigger or smaller at a given font size, depending on the font.
Text transparency: the level of transparency of the text (0% corresponds to a plain text).
Text color (RGB): color of the text (0,0,0 corresponds to a white text).
Text stroke: if set to false there is no stroke around the text. If set to true also set: - Text stroke color (RGB): color of the stroke (0,0,0 corresponds to a white stroke). - Text stroke width: width of the stroke (in pixels).
Scrolling: if set to false the text will be static. If the text is scrolling, you shall define:
298 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-272. Video overlay parameters - Text insertion - (horizontal) scrolling text
Electra VS - Version 05.10 299 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-273. Video overlay parameters - Text insertion - Scrolling text
300 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Direction: direction of movement of the text.
Frame structure: structure of the frame in which the text is inserted. A bad value can have an impact on the video quality.
Speed: a letter of the scrolling text will be displayed for this duration. Note that the actual duration may be slightly different, as the text will be shifted an integer number of pixels between two video samples.
Occurrence: if set to infinite, the overlay is inserted until the text is removed (if overlay is set to hide, disappearance of the text file), otherwise the text is removed after the indicated number of occurrences. Note that if the job is restarted or if the overlay configuration is changed the text scrolling will occur again.
Blank between text occurrences: if set to auto, the beginning of the text is displayed when the end of the text of the previous occurrence is no longer displayed. If set to Custom also set: - Size of blank between text occurrences: space between the end of the text and the beginning of the next occurrence (in pixels).
Background: if set to false there is no background. If set to true also set: - Background transparency: transparency of the background (100% corresponds to a fully transparent background). - Background color (RGB): color of the background (255, 255, 255 corresponds to a black background). - Background margin width: width of the background on either side of the text. - Background margin height: height of the background on either side of the text.
Overlay width (displayed if horizontal scrolling configured, i.e. Direction is set to Right to Left or Left to Right): width of the text box. If set to Full screen also set: - Position Origin: the screen corner from which the positions are defined. - Y: vertical position of the beginning of the text box (in pixels, 0 corresponds to the vertical position of the Position Origin). If set to Custom also set: - Custom overlay width: width of the text box (in pixels).
Electra VS - Version 05.10 301 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- Position Origin: the screen corner from which the positions are defined. - X: horizontal position of the beginning of the text box (in pixels). - Y: vertical position of the beginning of the text box (in pixels).
Overlay height (displayed if vertical scrolling configured, i.e. Direction is set to Bottom to Top or Top to Bottom): height of the text box. If set to Full screen also set: - Position Origin: the screen corner from which the positions are defined. - X: horizontal position of the beginning of the text box (in pixels). If set to Custom distance from screen borders also set: - Custom distance from screen borders: distance between the screen border and the text box. If set to Custom also set: - Custom overlay height: height of the text box (in pixels). - Position Origin: the screen corner from which the positions are defined. - X: horizontal position of the beginning of the text box (in pixels). - Y: vertical position of the beginning of the text box (in pixels).
If the text is static, you shall set
302 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-274. Video overlay parameters - Text insertion - Static text
Figure 3-275. Video overlay parameters - Text insertion - Static text
Vertical text: if set to true, the text will be inserted vertically.
Background: see above.
Position origin: the screen corner from which the positions are defined (Top-Left screen corner, Top-Right screen corner, Bottom-Left screen corner, Bottom-Right screen corner).
Position X: horizontal position of the beginning of the text box (in pixels).
Position Y: vertical position of the beginning of the text box (in pixels).
Electra VS - Version 05.10 303 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
If you insert an image,
Figure 3-276. Video overlay parameters - Image insertion
Figure 3-277. Video overlay parameters - Image insertion
Image file type: indicate if it is a single file or a sequence of numbered files. Note that the file can be a gif integrating a sequence of pictures.
304 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Image file storage: server location where the image file is stored. Several methods allows to define the location: - Enter the name of network storage declared in the set up tab (recommended) or - Enter the complete server path using the following syntax: [CIFS|NFS]://login:password@[IP adress | hostname]/MyDirectory Using this second method we assume that the network storage is accessible from all the nodes of the Electra VS (no IP address or hostname verification is done before launching the job, therefore if the server is not accessible from the node the reception of the file will fail). If you enter a hostname, a DNS lookup will be performed every 30 seconds to check that the resolution of the IP address has not changed.
Image file folder: folder on the network storage where the image file is stored.
Image file name: name of the image file.
Raise a log when image file is absent: if set to true, an alarm is raised if the file is missing. You should set this parameter to false if you want to control the apparition or disappearance of image by presence or absence of image file.
Overlay transparency: transparency of the image (0% corresponds to a plain image).
Adapt overlay to video aspect ratio: if set to true, the insertion of the image in the screen will take in account the aspect ratio. If the image aspect ratio is different from the video aspect ratio, then the image width is modified before the insertion.
Figure 3-278. Video overlay parameters - Image insertion: Adapt overlay to video aspect ratio
Position Origin: the screen corner from which the positions are defined (Top-Left screen corner, Top-Right screen corner, Bottom-Left screen corner, Bottom-Right screen corner).
Electra VS - Version 05.10 305 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Position X: horizontal position of the beginning of the image (in pixels).
Position Y: vertical position of the beginning of the image (in pixels). For all the overlay (image or text) you can add start or stop effects that occur at overlay appearance or disappearance.
Figure 3-279. Video overlay parameters - Start or stop effects (Split and Animation Control respectively in the screen below)
Figure 3-280. Overlay parameters - Effects: Start effect and Stop effect durations
Figure 3-281. Overlay parameters - Effects: Wipe effect
306 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-282. Overlay parameters - Effects: Fly effect
Figure 3-283. Overlay parameters - Effects: Split mode effect
Figure 3-284. Overlay parameters - Effects: Move offset effect
Electra VS - Version 05.10 307 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Start/Stop effect: Several effects are pre-defined: Fade, Wipe, Split, Fly in, Fly out, Animation control (for image overlay only, using the sequence picture from the image file). If set to None, the overlay appear/disappear at/from the indicated position without pre-defined effect.
Start/stop effect: duration (displayed if the effect is not Animation control): duration in second of the effect.
Start/Stop effect: from: Wipe or Fly in/Fly out source (Left, Right, Top, Bottom).
Start/Stop effect: split mode (displayed if configured effect is Split): indicate if the horizontal or vertical split is performed from the side of the overlay (in) or from the center (out).
Start/Stop effect: move offset (displayed if configured effect is Fly in/ Fly out): if set to 0 pixel, the overlay appears at/disappears from its configured position, otherwise it appears/disappears from a position shifted of the indicated offset towards the source effect.
Start/Stop effect: from picture (displayed if configured effect is Animation control): first picture of the animated sequence in the image file.
Start/Stop effect: to picture (displayed if configured effect is Animation control): first picture of the animated sequence in the image file.
308 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Encoding
MPEG-2 Encoder
Description
The MPEG-2 Video Encoder processing component lets you encode video in MPEG-2 format, 4:2:0, 8 bits, from SD to HD.
Figure 3-285. MPEG-2 encoder parameters
Parameters
For this processing component, you must set the following parameters:
Rate mode: indicate if the component bitrate should be CBR, Capped VBR or Statmux. If set to Capped VBR, indicate the characteristics of the video component, as shown hereafter.
Min bitrate: indicate the minimum ES bitrate that the video component should have.
Max bitrate: indicate the maximum ES bitrate that the video component should have.
Rate Control Quality: set the picture quality level required, in percentage. The value must be between 10 and 90% (best quality). Default value: 70%. It is not possible to use values outside of the bitrate range, and it is not recommended to reduce the bitrate range.
If you set the minimum bitrate to a lower value than the minimum value of the range, the value applied is the minimum value on the range, and inversely for the maximum bitrate.
Bitrate (only for CBR): enter the bit rate value (without encapsulation overhead), in bits per second.
Electra VS - Version 05.10 309 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Level: select from the drop-down list the level you wish to apply: Main, High, Auto.
Frame structure: choose from the drop-down list the way you want to handle interlaced streams. Possible options are:
Progressive: the whole frame is encoded. This mode is suitable for 720p and Web TV.
Interlace: fields are encoded separately. This mode is suitable for SD and 1080i. Make sure that the Frame structure parameter respects the format of the input connected to the processing component.
The adaptive mode uses more CPU than the other modes. Consequently, you can make less MPEG-2 encodings on a machine in this mode.
Display Aspect Ratio: leave to Auto to compute automatically the display aspect ratio from the input video one and take into account the video processing you may have added (clipping, for example). If you want to force the ratio, enter it manually in the editable list (for instance: 16:9 and 1.33).
I period: maximum size of the GOP.
P period:
1 if the GOP contains no B frame
2 if a B frame is present between each P frame
3 if two B frames are present between each P frame
etc.
Adaptive GOP: if set to false, GOPs always have the same structure. If set to true, the scene cut detection feature is used and the GOP structure is modified consequently. Adaptive GOP is always the best choice regarding video quality, even for Web TV adaptive bitrates.
Coder delay: this parameter can have 3 values:
Standard: the coder delay is 53 frames. It gives the highest video quality.
Short: the coder delay is 39 frames.
Ultra-short: the coder delay is 25 frames. There is an impact on video quality. Note: Decoder Delay is set to 1 second whatever the coder delay.
Closed caption: set to Insert closed caption if you want closed captions that are present in the incoming video stream to be collected and integrated in output.
310 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
H.264 AVC Encoder
Description
The H.264 AVC encoder processing component lets you encode video in H.264 AVC format, 4:2:0, 8 bits, from low resolution up to HD.
When the input video is chunked, an IDR frame is set at the beginning of the chunk. This overrides the configuration parameters.
Parameters
Figure 3-286. H.264 AVC encoder parameters
Recommended settings can be found in section ’Recommended Settings’ on page 392.
For this processing component, you must set the following parameters:
Rate mode: indicate if the component bitrate should be CBR, Capped VBR or Statmux. If set to Capped VBR, indicate the characteristics of the video component, as shown hereafter.
Min bitrate: indicate the minimum ES bitrate that the video component should have.
Max bitrate: indicate the maximum ES bitrate that the video component should have.
Electra VS - Version 05.10 311 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Rate Control Quality: set the picture quality level required, in percentage. The value must be between 10 and 90% (best quality). Default value: 70%. It is not possible to use values outside of the bitrate range, and it is not recommended to reduce the bitrate range.
If you set the minimum bitrate to a lower value than the minimum value of the range, the value applied is the minimum value on the range, and inversely for the maximum bitrate.
Bitrate (only for CBR): enter the bit rate value (without encapsulation overhead), in bits per second.
Profile: select from the drop-down list the profile you wish to apply:
Baseline: simplest profile in H.264; B pictures and CABAC are not encoded. It is used for low resolutions.
Main: generally used for SD resolutions.
High: generally used for HD resolutions. For Main and High profiles, also set the following parameters: - Frame structure: choose from the drop-down list the way you want to handle interlaced streams. Possible options are: - Progressive: the whole frame is encoded. This mode is suitable for 720p and Web TV. - Interlace: fields are encoded separately. This mode is suitable for SD and 1080i. - Adaptive: the video is encoded in Picture-Adaptive Frame/Field (PAFF) mode, which means that depending on the nature of the incoming image, frames or fields are encoded. This mode is useful when the content in input is likely to vary. This mode is suitable for SD and 1080i, but not in a Web TV context.
The adaptive mode uses more CPU than the other modes. Consequently, you can make less H.264 encodings on a machine in this mode.
Make sure that the Frame structure parameter respects the format of the input connected to the H.264 AVC encoder processing component. - P period: - 1 if the GOP contains no B frame - 2 if a B frame is present between each P frame - 3 if two B frames are present between each P frame - etc.
312 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- Hierarchical GOP: if set to true, B frames can be used as references. - Closed GOP period: set to 0 for no periodicity, 1 means every GOP, 2 means every second GOP, etc.
Level: select from the drop-down list the level you wish to apply: Auto, 1, 1.1, 1.2, 1.3, 2, 2.1, 2.2, 3, 3.1, 3.2, 4, 4.1, 5, 5.1
Mode: select an encoding mode:
Premium: this encoding mode provides the best video quality.
High-density: this encoding mode provides the best density (it uses less CPU and thus allows to perform more encodings).
Display Aspect Ratio: if set to Auto, then the display aspect ratio is automatically computed from the input video one and taking into account the video processing you may have added (clipping, for example). Select Auto (DVB restricted) to force the aspect ratio (Aspect_ratio_idc parameter in the H.264 stream) to a value compatible with ETSI TS 101 154 V1.11.1. If you want to force the ratio, enter it manually in the editable list (for instance: 16:9 and 4:3).
I period: maximum size of the GOP.
Adaptive GOP: if set to false, GOPs always have the same structure. If set to true, the scene cut detection feature is used and the GOP structure is modified consequently. Adaptive GOP is always the best choice regarding video quality, even for Web TV adaptive bitrates.
Delay: this parameter can have the following values:
Standard: the decoder delay is set to 1.5 second, and the coder delay is set to Standard. This mode is a good trade-off between latency and video quality.
Short: the decoder delay is set to 1 second, and the coder delay is set to Short. This mode decreases the latency and the zapping time.
Ultra-short: the decoder delay is set to 800 ms, and the coder delay is set to Ultra-short. This mode gives the lowest latency and the lowest zapping time, but the video quality is impacted.
Web TV: the decoder delay is set to 4 seconds, and the coder delay is set to Standard. This mode can be used for Web TV, when the latency is not a major concern: it can increase the video quality.
Electra VS - Version 05.10 313 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Custom: configure manually the decoder delay and the coder delay (these parameters are not available if the Rate mode is set to Statmux): - Decoder delay: this parameter is associated to the decoder buffer. Increasing this delay improves the quality. However, the zapping time is longer. - Coder delay: this parameter can have 3 values: - Standard: the coder delay is 53 frames. It gives the highest video quality. - Short: the coder delay is 39 frames. - Ultra-short: the coder delay is 25 frames. There is an impact on video quality.
Deblocking: enter a value (Sharp, Medium, Soft) to define the strength of the deblocking filter that will be applied to the stream. This helps to prevent the blocking artifacts resulting from image compression. Disabling the deblocking gives a sharper image, which might be a good choice when the video bitrate is high.
Closed caption: set to Insert closed caption if you want closed captions that are present in the incoming MPEG-2/H.264 video stream or from the SDI input to be collected and integrated in output.
Psycho-visual enhancement: leave to ON to obtain the best video quality. Set to OFF to obtain better results with basic PSNR/DMOS video quality analyzers (however the video quality is lower).
ISDB-Tb syntax: specific adaptation of the syntax to the ISDB-Tb standard.
Web TV chunk size accuracy enhancement: Set to true if you connect the encoder to a packetizer for Web TV output and if the accuracy of the chunk size is a major concern. In this case, only Coder Delay can be changed, Decoder Delay is fixed to 500ms.
Closed Caption Descriptor: if set to Pass through, the descriptors are copied in the output PMT.
314 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
H.265 HEVC Encoder
The H.265 HEVC encoder processing component is able to encode H.265 HEVC video in 4:2:0, 8/10 bits, from low resolution up to UHD.
When the input video is chunked, an IDR frame is set at the beginning of the chunk. This overrides the configuration parameters.
Figure 3-287. H.265 HEVC encoder parameters
For this processing component, you must set the following parameters:
Rate mode: indicate if the component bitrate should be CBR, Capped VBR or Statmux. If set to Capped VBR, indicate the characteristics of the video component, as shown hereafter. It is not possible to use values outside of the bitrate range, and it is not recommended to reduce the bitrate range.
If you set the minimum bitrate to a lower value than the minimum value of the range, the value applied is the minimum value on the range, and inversely for the maximum bitrate.
Min bitrate: indicate the minimum ES bitrate that the video component should have.
Max bitrate: indicate the maximum ES bitrate that the video component should have.
Rate Control Quality: set the picture quality level required, in percentage. The value must be between 10 and 90% (best quality). Default value: 70%.
Bitrate: (CBR only) enter the bit rate value (without encapsulation overhead), in bits per second.
Electra VS - Version 05.10 315 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Display Aspect Ratio: leave to Auto to compute automatically the display aspect ratio from the input video one and take into account the video processing you may have added (clipping, for example). If you want to force the ratio, enter it manually in the editable list (for instance: 16:9 and 1.33).
I period: maximum size of the GOP.
P period: - 1 if the GOP contains no B frame - 2 if a B frame is present between each P frame - 3 if two B frames are present between each P frame - etc.
Hierarchical GOP: if set to true the use of B pictures as a reference is allowed
Adaptive GOP: if set to false, GOPs always have the same structure. If set to true, the scene cut detection feature is used and the GOP structure is modified consequently. Adaptive GOP is always the best choice regarding video quality, even for Web TV adaptive bitrates.
Closed GOP Period: GOP period after which the encoder creates a closed GOP.
Delay: this parameter can have the following values:
Standard: the decoder delay is set to 1.5 second, and the coder delay is set to Standard. This mode is a good trade-off between latency and video quality.
Short: the decoder delay is set to 1 second, and the coder delay is set to Short. This mode decreases the latency and the zapping time.
Ultra-short: the decoder delay is set to 800 ms, and the coder delay is set to Ultra-short. This mode gives the lowest latency and the lowest zapping time, but the video quality is impacted.
Web TV: the decoder delay is set to 4 seconds, and the coder delay is set to Standard. This mode can be used for Web TV, when the latency is not a major concern: it can increase the video quality.
Custom: configure manually the decoder delay and the coder delay: - Decoder delay: this parameter is associated to the decoder buffer. Increasing this delay improves the quality. However, the zapping time is longer.
316 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- Coder delay: this parameter can have 3 values: - Standard: the coder delay is 53 frames. It gives the highest video quality. - Short: the coder delay is 39 frames. - Ultra-short: the coder delay is 25 frames. There is an impact on video quality.
Deblocking: enter a value to define the strength of the deblocking filter that will be applied to the stream. This helps to prevent the blocking artifacts resulting from image compression. Disabling the deblocking gives a sharper image, which might be a good choice when the video bitrate is high.
Closed caption: set to Insert closed caption if you want closed captions that are present in the incoming MPEG-2/H264 video stream or from the SDI input to be collected and integrated in output.
Psycho-visual enhancement: leave to ON to obtain the best video quality. Set to OFF to obtain better results with basic PSNR/DMOS video quality analyzers (however the video quality is lower).
Web TV chunk size accuracy enhancement: Check this option if you connect the encoder to a packetizer for Web TV output and if the accuracy of the chunk size is a major concern. It will not be possible to configure the Decoder Delay, it will be fixed to 500ms. Only Coder Delay is configurable.
Electra VS - Version 05.10 317 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
H.265 HEVC Hardware Encoder
Hardware encoding of HEVC UHD. You shall use this module only if you have the additional accelerator board for UHD encoding installed (ELC-VS-HW-UHD).
Figure 3-288. H.265 HEVC hardware encoder parameters
For this processing component, you must set the following parameters:
Bitrate (only for CBR): enter the bit rate value (without encapsulation overhead), in bits per second.
I period: maximum size of the GOP.
P period:
1 if the GOP contains no B frame
2 if a B frame is present between each P frame
4 if four B frames are present between each P frame
8 if eight B frames are present between each P frame
GOP Type: if set to IB image, no P image will be present in the output stream. Usually, IB is used for UHD resolution and IPB is used for HD resolution.
Adaptive GOP: if set to false, GOPs always have the same structure. If set to true, the scene cut detection feature is used and the GOP structure is modified consequently. Adaptive GOP is always the best choice regarding video quality, even for Web TV adaptive bitrates.
Closed GOP Period: GOP period after which the encoder creates a closed GOP.
Temporal Scalability: Used to enable (true) or disable (false) the temporal scalability. When Temporal Scalability is true, the number of sub-layers depends on the P period:
If the P period is 2, then there are 2 sub-layers
If the P period is 4, then there are 3 sub-layers
If the P period is 8, then there are 4 sub-layers
318 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Decoder delay: this parameter is associated to the decoder buffer. Increasing this delay improves the quality. However, the zapping time is longer. It can be set to 500 or 1000 ms.
Deblocking: enter a value to define the strength of the deblocking filter that will be applied to the stream. This helps to prevent the blocking artifacts resulting from image compression. Disabling the deblocking gives a sharper image, which might be a good choice when the video bitrate is high.
Closed caption: set to Insert closed caption if you want closed captions that are present in the incoming video stream or from the SDI input to be collected and integrated in output.
MPEG-1 Layer 2 Encoder
Description
The MPEG-1 Layer 2 encoder processing component lets you encode audio in MPEG-1 layer 2 format.
Figure 3-289. MPEG-1 layer 2 encoder parameters
Parameters
For this processing component, you must set the following parameters:
Bitrate: enter the bit rate value (without encapsulation overhead), in bits per second.
Stereo mode: choose the stereo mode to use from the drop-down list. Available modes are:
Joint stereo: removes stereo intensity irrelevance
Stereo
Dual channel: uncorrelated (contains two completely different audio streams but encodes them together). This parameter is ignored when the input is mono.
Electra VS - Version 05.10 319 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
AAC Encoder
Description
The AAC encoder processing component lets you encode audio in AAC-LC, AAC-HE v1 and AAC-HE v2 format. It generates a raw audio stream.
Figure 3-290. AAC-encoder parameters
Parameters
For this processing component, you must set the following parameters:
AAC type: choose the format from the list: AAC-LC, AAC-HE v1 (SBR), AAC-HE v2 (SBR+PS). For AAC-HE v1 (SBR) and AAC-HE v2 (SBR+PS) types, also set the following parameter:
Signaling mode: choose the mode from the list: - Implicit and Explicit backward: a player that supports only AAC-LC will be able to decode the AAC-LC part of the stream. - Explicit hierarchical: the stream cannot be decoded by a player that supports only AAC-LC. This ensures that listeners will get the full audio quality.
Bitrate: enter the bitrate of the audio stream, in bits per second.
320 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Dolby Digital Encoder
Description
The Dolby Digital Encoder processing component lets you encode audio in Dolby® Digital and Dolby® Digital Plus.
Figure 3-291. Dolby Digital Encoder parameters
Parameters
For this processing component, you must set the following parameters:
Dolby Digital Plus: set to true for Dolby Digital Plus or to false for Dolby Digital. If set to false, also set:
Room type: type of mixing room that was used for the final mixing: Small room, Large room, not indicated.
Dolby Surround EX: set to enable to identify the encoded audio as material encoded in Surround EX. This parameter is only used if the encoded audio has two Surround channels.
A/D converter type: enables audio that has passed through a particular A/D conversion stage to be marked as such, so that a decoder may apply the complementary D/A process. Choice between: Standard or HDCD.
Electra VS - Version 05.10 321 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Bandwidth lowpass filter: this parameter can be used to activate a low-pass filter with a cut-off near the specified audio bandwidth that is applied to the main input channels. If the digital signal fed to the main input channels does not contain information above the specified audio bandwidth, this filter can be disabled.
Mixing level: acoustic pressure of the sound during the final mixing, in decibels.
Bitrate for Mono: choose from the list the bitrate to use for mono audio.
Bitrate for Stereo: choose from the list the bitrate to use for stereo audio.
Bitrate for 5.1: choose from the list the bitrate to use for 5.1 audio.
Bitstream mode: choose from the list the type of audio service:
Complete main: main audio service
Music and effect: main audio service
Visually impaired: associated service
Hearing impaired: associated service
Dialogue: associated service
Commentary: associated service
Emergency: associated service
Voiceover: associated service
Karaoke: associated service
Line mode DRC: information used by Dolby® Digital audio decoders with line-level outputs, to adjust their output dynamic according to a profile. Choose from the list the line mode to use for Dynamic Range Control.
RF mode DRC: information used by Dolby® Digital audio decoders with an RF-remodulated output, to adjust their output dynamic according to a profile. Choose the profile from the list.
Preferred stereo downmix mode (multi-channel only): choose from the list if you would rather use Lt/Rt or Lo/Ro downmix in a decoder with stereo outputs:
Lt/Rt preferred: Left total/Right total. The Lt/Rt downmix totals the Surround channels and adds them in-phase to the Left channel and out-of-phase to the Right channel. This enables a Dolby Pro Logic decoder to rebuild the L/C/R/S channels for a Pro Logic home theater.
322 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Lo/Ro preferred: Left only/Right only. The Lo/Ro downmix discretely adds the Left and Right Surround channels to the Left and Right speaker channels, respectively. This preserves stereo separation for stereo-only monitoring and produces a monocompatible signal. The LFE channel is not included in any downmixes.
Lt/Rt center downmix level (multi-channel only): level shift applied to the Center channel when adding to the left and right outputs as a result of downmixing to an Lt/Rt output, in decibels.
Lt/Rt surround downmix level (multi-channel only): level shift applied to the Surround channels when downmixing to an Lt/Rt output, in decibels.
Lo/Ro center downmix level (multi-channel only): level shift applied to the Center channel when adding to the left and right outputs as a result of downmixing to an Lo/Ro output, in decibels.
Lo/Ro surround downmix level (multi-channel only): level shift applied to the Surround channels when downmixing to an Lo/Ro output, in decibels.
Dolby surround mode (stereo only): indicates whether the stereo audio is Dolby® Surround encoded or not. The value is not taken into account in 1/0 mode.
Dialogue normalisation: average dialog level, in decibels.
DC highpass filter: set to true to enable the high pass filter on the input audio samples.
Copyright bit: set to true if the encoded Dolby® Digital bitstream is copyright protected.
Original bitstream: set to true if the encoded Dolby® Digital bitstream is the master version or to false if it is a copy.
LFE channel filter: set to true to enable a 120 Hz filter. The filter is applied to the LFE channel input of a Dolby® Digital encoder prior to encoding. It is ignored if the LFE channel is disabled. The filter removes frequencies above 120 Hz that would cause aliasing when decoded. This filter should only be switched off if the audio to be encoded is known not to have any signals above 120 Hz.
Surround 3 dB attenuation: set to true to apply a 3 dB attenuation before encoding the Surround channel(s).
Surround phase shift: set to true to apply a 90-degree phase shift to the Surround channels. The Dolby® Digital decoder can therefore easily create an Lt/Rt downmix.
Electra VS - Version 05.10 323 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Outputs
TS Video Packetizer
Description
The TS Video Packetizer processing component encapsulates a video elementary stream into MPEG-2 transport packets. These packets can then be sent to a TS multiplexer.
Figure 3-292. TS video packetizer parameters
Parameters
For this processing component, you must set the following parameters:
PCR generation: select the PCR generation mode:
Add on component: add PCR on the video component.
Create independent PCR PID: an independent PID for the PCR is created. Choose this mode for ISDB-Tb programs. In this case, you must indicate the PID value in the TS multiplexer processing component, in the Input tab, in the PCR PID field. See section ’TS Multiplexer’ on page 327.
None: no PCR is added.
Encoder Boundary Point: Select the standard to apply (CableLabs) if you want to add adaptive streaming specific signaling information. The generated stream will be pre-conditioned integrating fragments and segment boundaries information (an EBP is added before each Idr frame of the WebTV video stream). Otherwise, select None.
Adaptation for Anevia’s external packager: set to true to generate a transport stream that can be read and processed by Anevia’s ViaMotion devices. Do not use this feature if your TS is not sent to external packager. The following adaptation is performed:
Add of the ES_rate field in all audio and video PES headers.
324 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
TS Audio Packetizer
Description
The TS Audio Packetizer processing component encapsulates an audio elementary stream into MPEG-2 transport packets. These packets can then be sent to a TS multiplexer.
Figure 3-293. TS audio packetizer parameters
Parameters
For this processing component, you must set the following parameters:
PCR generation: select the PCR generation mode:
Add on component: add PCR on the audio component.
Create independent PCR PID: an independent PID for the PCR is created. Choose this mode for ISDB-Tb programs. In this case, you must indicate the PID value in the TS multiplexer processing component, in the Input tab, in the PCR PID field. See section ’TS Multiplexer’ on page 327.
None: no PCR is added.
AAC encapsulation (useful only for an AAC component): choose whether the AAC audio should be encapsulated with
LOAS/LATM header (mandatory for ISDB-Tb)
ADTS header (good choice otherwise)
Audio encapsulation mode: choose whether the number of frames per PES should be fixed number of frames per PES or variable number of frames per PES.
fixed number of frames per PES: the number of frames per PES is fixed. Set the Number of frames per PES.
variable number of frames per PES: The number of frames per PES is variable requiring less bandwidth. However, some receivers do not support this feature.
Electra VS - Version 05.10 325 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Adaptation for Anevia’s external packager: set to true to generate a transport stream that can be read and processed by Anevia’s ViaMotion devices. Do not use this feature if your TS is not sent to this kind of device. The following adaptation is performed:
Add of the ES_rate field in all audio and video PES headers.
Language: leave to Auto to keep the language of the input, or use the ISO codes1 to force the language manually (for instance, enter eng for English, spa for Spanish, etc.).
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
326 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
TS Multiplexer
Description
The TS Multiplexer processing component multiplexes transport packets in an MPEG-2 TS (SPTS or MPTS, no stat mux).
Figure 3-294. TS multiplexer parameters
Figure 3-295. Input: Input tab and Input: Section tab
Input: (TS) input, Input type ‘program’
Input: (TS) input, Input type ‘component’
Input: Section, Input type ‘component’
Parameters
For this processing component, you must set the following parameters:
In the Parameters tab,
TS bitrate: set the TS rate in bits per second.
TS ID
PAT period: define the period of the PAT, in milliseconds. Note: This value is used by Electra VS to set the maximum interval for the table. The real interval value may be lower (down to 50%).
Electra VS - Version 05.10 327 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
PMT period: enter the period of all the PMT, in milliseconds. Same note as before.
Standard: set the standard that the output TS should respect (DVB, MPEG-2 or ATSC). This information is required for some processing (e.g. AC-3 transport since the AC-3 transport mode is not the same in ATSC and DVB).
Generate SDT: If set to true, a SDT will be created and filled using the TS Id, ON Id, Service type, Service name and Provider name configured in the multiplexer.
SDT Period: enter the period of the SDT in milliseconds.
ON Id: enter the Original Network Id.
In the Input: Input tab (one tab per TS input)
Input type: If set to Program, define a program and a component of this program. according to the following parameters:
Figure 3-296. Input: Input tab (Input type Program)
Program number: program number the component belongs to.
Component PID: enter a value or use a link to an input component label.
328 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Add PMT component descriptors: if set to true, type in hexadecimal (02031A005F) the descriptors contents in the PMT component descriptors buffer (hexa). It shall contain the descriptor tags, lengths and bodies according to the following syntax: [descriptor tag (8-bit field)] [descriptor length (8-bit field)] [descriptor body (variable field)]... [descriptor tag (8-bit field)] [descriptor length (8-bit field)] [descriptor body (variable field)]... No verification is performed on the buffer content except the coherence of the descriptor lengths.
Add PMT program descriptors: if set to true, type in hexadecimal (02031A005F) the descriptors contents in the PMT program descriptors buffer (hexa). It shall contain the descriptor tags, lengths and bodies according to the following syntax: [descriptor tag (8-bit field)] [descriptor length (8-bit field)] [descriptor body (variable field)]... [descriptor tag (8-bit field)] [descriptor length (8-bit field)] [descriptor body (variable field)]... No verification is performed on the buffer content except the coherence of the descriptor lengths.
Component tag (DVB): enter a value or set to None
PMT PID: enter a value
PCR PID: the Auto value is suitable in most of cases. Specify the PID if you asked to create an independent PCR PID in the TS video packetizer processing component or TS audio packetizer processing component, in the PCR generation field (see section ’TS Video Packetizer’ on page 324 or section ’TS Audio Packetizer’ on page 325). If SDT generation is requested (i-e Generate SDT set to true in the Parameters tab), fill in the following fields:
Service type: service type of the program: Digital television service (1), Digital radio sound service (2), Mosaic service (6).
Provider name: provider name of the program
Service name: program name of the program
Electra VS - Version 05.10 329 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
If set to Component, define a component of a program that has already been defined. For example: define a program input for the video component as above and a component input for the associated audio component as below.
Figure 3-297. Input: Input tab (Input type Component)
If set to Ghost, define a component that is not referenced in a program.
Figure 3-298. Input: Input tab (Input type Ghost)
In the PID field, leave to Auto if you want the ghost to keep the same PID value as in input, or set to Add an offset if you wish to add an offset to the input PID (e.g. if the input PID is 100 and you want to have an output PID of 300, set the offset to 200).
330 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
In the Input: Section tab (one tab per section input)
Figure 3-299. Input: Section tab (Input type Program)
Figure 3-300. Input: Section tab (Input type Component)
The parameters are identical to those described previously in the section Input: Input tab above.
Electra VS - Version 05.10 331 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
TS over IP Streamer
Description
The TS over IP Streamer output processing component streams an MPEG-2 TS over UDP/IP or over RTP/UDP/IP in CBR mode (i.e. with stuffing packets) or in VBR mode (i.e. without stuffing packets). Both multicast and unicast are supported.
Figure 3-301. TS over IP streamer output parameters
Parameters
For this processing component, you must set the following parameters:
IP address: to set the IP destination address.
If the address is multicast, set the LAN and enter the IP address in the field.
If the address unicast, it must be reachable, otherwise job creation will be refused. To check that the address is reachable, Electra VS uses its IP configuration (LAN, default gateways, IP routes).
Figure 3-302. IP address
UDP port: destination UDP port.
Source IP address: to set the source IP address. Leave to Auto to fill it with the IP address in the output LAN of the node on which the job is running. If the job is stopped and is restarted on a different node, the source IP address will change. Declare a Source IP address if you want to always use the same one whatever the node on which the job is running.
332 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
UDP source port: to set the source UDP port. Leave to same as destination UDP port to keep the same port for both source and destination.
TTL: Time-to-live field of the IP headers. This is the maximum number of IP routers that a stream is allowed to cross.
MTU: Maximum Transmission Unit. This is the maximum size of a datagram that can be streamed on the network without being fragmented. Default value is Ethernet one (1500). This MTU also defines the number of MPEG-2 TS packets by IP datagram. By default this number is set to 7, but if you modify the MTU parameter, the number of MPEG-2 TS packets by IP datagram will be the highest allowed by the MTU.
Protocol: the protocol can be:
TS/UDP/IP: MPEG-2 TS over UDP.
TS/RTP/UDP/IP: MPEG-2 TS over RTP.
VBR TS (no stuffing packets): set to true if you do not want stuffing packets to be added in the output stream.
Electra VS - Version 05.10 333 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
MPTS over IP Output
Description
The MPTS over IP output processing component creates an MPTS and streams it over UDP/IP or over RTP/UDP/IP. It also manage statistical multiplexing (optional).
When this processing component is used, a MPTS name shall be given. All the encoding jobs that uses this MPTS name will be multiplexed in a single MPTS. A job based on this MPTS over IP output processing component is automatically created for this MPTS generation.
Figure 3-303. MPTS over IP output parameters
Parameters
For this processing component, you must set the following parameters:
In the Parameters tab,
Protocol, IP address, UDP port, Source IP address, TTL, MTU: see section ’TS over IP Streamer’ on page 332.
MPTS name: name of the MPTS, that will be used as reference in the jobs that will constitute the MPTS.
TS bitrate: set the TS rate in bits per second.
334 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Statmux pool global bitrate: define the bitrate value that will be allocated for statistical encoding. Only the video components controlled by the statmux will use this bitrate. This bitrate must be under the TS total bitrate so as to keep bandwidth for non-statmuxed components (audio, video CBR, signalization, pass-through components). If you wish to create a simple MPTS without using the statmux feature, leave this parameter to unused.
TS ID
Standard: set the standard that the output TS should respect (DVB, MPEG-2 or ATSC).
PAT period: enter the period of the PAT, in milliseconds.
PMT period: enter the period of all the PMT, in milliseconds.
Define backup output: set to true if you wish to use a backup output and define its characteristics.
Generate SDT: If set to true, a SDT will be created and filled using the TS Id, ON Id, Service type, Service name and Provider name configured in the multiplexer.
SDT Period: enter the period of the SDT in milliseconds.
ON Id: enter the Original Network Id.
Input Tab
Figure 3-304. MPTS over IP output parameters – Input tab
Electra VS - Version 05.10 335 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
In the Input tab, set the following parameter:
Input type: see the Input: Input tab of TS Multiplexer processing component (see section ’TS Multiplexer’ on page 327).
Controlled by statmux (for video only): If set to false the video component is in CBR mode. If set to true, the video component will be driven by the statistical multiplexing mechanism. You have to set the following parameters.
Minimum bitrate (TS overhead included): indicate the minimum bitrate that the video component should have.
Maximum bitrate (TS overhead included): indicate the maximum bitrate that the video component should have.
Quality: set the picture quality level required, in percentage. The value must be between 30 and 90% (best quality). Default value: 70%.
If SDT generation is requested (i-e Generate SDT set to true above), fill in the following fields:
Service type: service type of the program: Digital television service (1), Digital radio sound service (2), Mosaic service (6).
Service name: program name of the program
Provider name: provider name of the program
336 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
TS File Output
The TS file output processing component allows you to record the output of a TS multiplexer into a file.
Figure 3-305. TS file output parameters
For this processing component, you must set the following parameters:
TS file storage: indicate the network storage where the output TS file must be placed. Refer to section ’Video overlay’ on page 296 for the possibles syntaxes.
TS file folder: indicate the folder on the network storage where the output TS file must be placed.
TS file name: specify the name of the output TS file.
TS file name extension: specify the file extension that the output TS file should have. If this parameter is not filled, the TS file name will be kept "as is". If this parameter is filled, any extension of the TS file name parameter will be replaced by this extension. This is useful when you want to keep the input file name (hot folder application, for example) and replace only the extension: you link the TS file name to the input TS file name, and you force the extension using the TS file name extension.
Electra VS - Version 05.10 337 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
RTMP
Description
The RTMP processing component sends audio/video to a Flash Media Server (FMS) using RTMP push (to TCP port 1935 of the FMS server).
Adaptive bitrate is supported (a single chunker shall be defined for all the video components).
Figure 3-306. RTMP output parameters
Parameters
For this processing component, you must set the following parameters.
Parameters Tab
Flash media server URL: indicate the URL used to communicate with the Flash media Server (FMS). The syntax shall be the following rtmp://host_name[:port]/path or rtmp://host_ip[:port]/path If the port is not indicated, the default RTMP port 1935 is used. If the syntax is rtmp://host_name[:port]/path you shall configure the DNS in the Setup tab, IP category (see Chapter Installation)
you shall indicate the LAN used to communicate with the remote RTMP server If the syntax is rtmp://host_ip[:port]/path you do not have to configure the DNS
you shall set the address directly in the Flash media server IP address
Delay before reconnection: indicate the maximum delay between each tentative of reconnection to the Flash media server (default 1 s).
Authentication type: choose:
None or in FMS URL: if there is no authentication or it is indicated in the URL of the flash media server.
Akamai: if the authentication is managed by an Akamai server. In this case, indicate the User name and Password to use.
338 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Level3: if the authentication is managed by a Level3 server. In this case, indicate the User name and Password to use.
Adobe: if the authentication is managed by an Adobe server. In this case, indicate the User name and Password to use.
Traffic smoothing: indicate if you want to smooth the traffic generated by the chunk transmission to the remote web server and the Maximum traffic overhead accepted (30% to 500%). The overhead is calculated on the theoretical broadcast bitrate. It means that with an maximum overhead set to 100% the traffic bitrate will not exceed two times the estimated bitrate.
In the Input tab, you can also set the following parameter:
Stream name: this parameter must be identical to all the components of a stream. When present, an audio component should be present on all the streams of an output.
Figure 3-307. Stream name required for linkage
Profile 1 Encoder Name 1
Profile 2 Encoder Name 2
Profile 3 Encoder Name 3 Links
Audio 1 Name 1 Audio 1 Encoder Name 2 Audio 1 Name 3
Electra VS - Version 05.10 339 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
HLS
Description
The HLS processing component receives audio/video components, creates the chunks and the manifests, encrypts the chunks, and delivers the streams OR makes them available on the local Web server.
Parameters
Figure 3-308. HLS output parameters (1 of 2)
340 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-309. HLS output parameters (2 of 2)
For this processing component, you must set the following parameters:
Manifest file name: name of the main manifest.
Custom naming: this parameter lets you define how to name the chunk files.
If set to false, the name of the chunk files will be built as follows: [manifest name]_[time]_[stream ID_][sequence number] manifest name being the name set earlier in the Manifest file name field without the m3u8 file extension. Define the Add prefix parameter: set to true to use the name of the manifest as a prefix for all file names (chunks and secondary manifests).
Electra VS - Version 05.10 341 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
If set to true, the name of the chunk files will be built according to the following rule: field1_field2_field3_field4_field5 Set the following parameters: - Name: enter a name for the file, at your convenience. - Separator: choose from the list the sign that should be used as separator in the filename: _ or -. - Field 1 to Field 5: choose from the lists the elements you want to use to build the filename, among: name, bitrate, stream ID, sequence number, time and unused. If set to unused, this field and the following ones will not be included in the filename. time being the date of the beginning of the session (and not the date of the chunk). sequence number being incremented at each chunk.
Media URI custom naming: this parameter lets you define how to name the media URI.
If set to false, the name of the URI will be built as follows: stream ID.extension where Stream ID is an internal identifier and extension is m3u8 (e.g. URI = “07.m3u8”) If set to true, several new fields allow to customize the media URI knowing that the URI will be built according to the following rule: Media URI field 1_Media URI field 2_Media URI field 3 - Media URI name: enter a name at your convenience. This name will be used in the Media URI field x fields. - Media URI separator: choose from the list the sign that should be used as separator in the media URI: _ or - or None. - Media URI field 1 to Media URI field 3: choose from the lists the elements you want to use to build the URI, among: Media type (Video, Audio, Subtitle according to the currently selected input component stream), Media URI name set earlier in the Media URI name field, Stream Id (internal id) and Unused. If set to Unused, this field and the following ones will not be included in the URI.
342 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Example: if Media URI Name: MyCustomMediaURIName, Media URI Separator: -, Media URI field 1: Media type, Media URI field 2: Media URI Name, Media URI field 3: Stream Id, the manifest file will be (excerpt): ... NAME="audio_esp1",...,URI="Audio-MyCustomMediaURIName-2. m3u8" for the first audio NAME="audio_fra2",...,URI="Audio-MyCustomMediaURIName-6. m3u8" for the second audio BANDWIDTH=845857,...,Video-MyCustomMediaURIName-1.m3u8 for the video with the first bitrate profile (845857bps) BANDWIDTH=1129247,...,Video-MyCustomMediaURIName-3.m3u8 for the video with the second bitrate profile (1129247bps) ... HLS Protocol version: choose one version:
Version 2: suitable for programs with only one audio language. The generated chunks contain both video and audio components.
Version 3: same as version 2 with durations in ms.
Version 4: mandatory for programs with more than one audio language. Video and audio components are not in the same chunks (only one component per chunk). This version may be not supported by old devices.
Version 5: lets you have subtitles in WebVTT format.
Create I-frame only streams (HLS Protocol version 4 or 5): if set to true, an I-frame only stream is added per video defined in the manifest. The I-frame only stream references I-frames in existing video media segments. It allows the player to perform fast forward and rewind operations.
Add low bitrate audio only stream: if set to true, chunks that contain only the audio component are generated. Set the Audio only stream ID, Audio only stream media order and Audio only NAME attribute in #EXT-X-STREAM-INF parameters as indicated in section ’Input Tab’ on page 347.
Available stream duration: depth in seconds of chunks that are available on the Web server. The minimum duration must be equal to the length of at least two chunks.
Activate directory rollover: if set to true, sub-directories named Rollover_X are created. Each directory contains a Segments number per directory corresponding to the fixed duration. The sub-directories and the chunks are deleted after the available stream duration set above, if stored in the local web server.
Electra VS - Version 05.10 343 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Stream available on local web server: if set to true, the stream is available on the Electra VS internal Web server. In this case, set the following parameters:
Local Web server IP address: virtual IP address. A player can receive the chunks from this address. This address must be part of a Electra VS LAN, otherwise job creation will be refused.
Folder: folder where the manifests and chunks are stored on the local Web server.
Max clients number: expected maximum number of clients for this output stream. This parameter is used to check that the device has the resource to process the requests for this stream.
Push stream on remote web server: if set to true, the stream is pushed to a remote Web server. In this case, set the following parameters:
Remote web server URL: indicate the LAN used to communicate with the remote Web server. If the remote Web server URL contains a name instead of an IP address, you must configure the DNS in the Setup tab, IP category (see section ’DNS’ on page 171). If you do not wish to use the IP address resolution by DNS, you can also directly enter the IP address of the remote Web server in the Remote web server IP address field.
Traffic smoothing: indicate if you want to smooth the traffic generated by the chunk transmission to the remote web server and the Maximum traffic overhead accepted (30% to 500%). The overhead is calculated on the theoretical broadcast bitrate. It means that with an maximum overhead set to 100% the traffic bitrate will not exceed two times the estimated bitrate.
Delete files from remote web server: if set to true, the files posted on the remote Web server are deleted after the Available stream duration set above.
Create directory on remote web server: if set to true, the root directory is created before chunks transfer. If Activate directory rollover is set to true, sub-directories named Rollover_X are automatically created. The sub-directories and the chunks are deleted after the Available stream duration set above.
Remote web server authentication: if the remote Web server requires an authentication select its HTTP type, Basic or Digest, and enter the User name and Password.
344 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Local storage duration when remote server is unreachable: enter the time during which the content should be bufferized if during a push action, the remote server becomes unreachable. When the remote server is available again, all the content is sent at once.
Before using this feature, check that the bandwidth is widely dimensioned, because otherwise there is a risk of network congestion when the remote server is back up, which can impact other streams.
Define backup remote Web server: if set to true, the stream is also sent to a backup remote Web server for redundancy purposes. Indicate the URL and the IP address of the backup server to the dedicated fields, as well as the authentication parameters, if needed.
Generate merge manifest: if set to true, the manifests will reference all the streams sent to main and backup servers.
Encrypt files: if set to true, DRM is activated. Set the following parameters:
Key server connection: select the conditional access server to which Electra VS should connect to get the key from the drop-down list. If set to None, Electra VS generates the key itself. Otherwise, enter the specific parameters of the CAS server: - Content id (Nagra, Irdeto, PolyMedia, ZTE): identifier of the program to encrypt (string). - Resource id (Verimatrix): identifier of the program to encrypt (integer). - Account Id (Irdeto): identifier of the account to connect to the Irdeto server. - Use last key (Irdeto, Viaccess): Set to true to return the last registered encryption key for a specified live event. Use this method if an encoding session reuses the last generated encryption key for the live event instead of generating a new key. This is particularly useful when multiple encoders are configured, to use the same encryption key for a live event. Set to false to generate and return a new PlayReady encryption key for the specified live event. - Key server URL: URL of the CAS server. DNS is not supported for this URL, so the IP address shall be explicitly contained by the URL. - Define backup key server: set to true if you want to declare a backup CAS server. Enter the URL of this backup server in the Backup key server URL field.
Electra VS - Version 05.10 345 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- Use authentication (Nagra, Verimatrix): set to true if the CAS server requires an authentication, and enter the User name and Password. Also specify the HTTP Authentication type (auto, basic or digest). - Irdeto PlayReady protected HLS version (Irdeto): indicate the version supported by the Irdeto player. - License URL (ZTE): enter the URL of the license server to which the player must connect to retrieve the encryption keys. - Non silent license URL (ZTE): enter the URL of the non-silent license acquisition Web page to which the player must connect to retrieve the encryption keys. - Domain service ID (ZTE): service ID for the domain service in GUID format. For example, deb48f11-8b3a-416d-7a1f-00006d57fd05. - Encryption mode (None, Nagra, Verimatrix,Novel DRM, Harmonic KMS, Huawei): - Select Playready Cisco if you want to encrypt the output with playready license compatible with CISCO/ NDS player. The option is available only if Key server connection is set to None. In this case you can set the following parameters: • Key seed: value used to compute the content encryption key (CEK). It must be configured in base64 format (ex: XVBovsmzhP9gRIZxWfFta3VVRPzVEWmJsazEJ46). • Key id: identifier of the key associated to the CEK in the Playready license. It must be configured in GUID format, big endian (ex: 4B640997-E5CD-495F-866B-969CD2E31B52). • License URL: enter the URL of the license server to which the player must connect to retrieve the encryption keys. - Select AES - 128 or SAMPLE-AES if you want to encrypt the stream following pantos standard (draft-pantos-http-live-streaming-11). The option is available if Key server connection is set to None, Nagra, Verimatrix or Novel DRM. - Select Playready Harmonic if you want to encrypt the output with Playready license compatible with player compatible with Harmonic KMS. The option is available if Key server connection is set to Harmonic KMS or Huawei. - Select Apple Fairplay if you want to encrypt the stream following Apple fairplay standard. The option is available if Key server connection is set to Nagra, Verimatrix, Novel DRM, Harmonic KMS or Huawei.
346 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Key mode (Nagra, Verimatrix, Huawei, Harmonic KMS, Novel DRM, ZTE, None + AES-128, None + SAMPLE-AES): - If set to Fixed Key, the key is fixed once. Enter the value of the key in the Key field (32 characters). - If set to Key Rotation, the key is periodically renewed. Enter the refresh period in the Key refresh period field, in number of chunks.
IV value: value of the initial vector. This can be: - Chunk number - Random value: in this case, enter the refresh period of the initial vector in the IV refresh period field, in number of chunks.
Parental Control: set to true if you wish to broadcast the parental control ID received from a remote server (specific customer protocol). Define the channel ID of the HLS output, the protocol used for the broadcast of parental control (ID3 or WebVTT format) and the client URL for the remote server feedback.
Input Tab
Figure 3-310. HLS output – Input parameters
In the Input tab, set the following parameter:
Stream Id: Internal identifier used in the filename and URI to reference the input stream.
Language: leave to Auto to keep the language of the input, or use the ISO codes1 to force the language manually (for instance, enter eng for English, spa for Spanish, etc.).
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
Electra VS - Version 05.10 347 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Playlist media order: this parameter defines the order of presentation of the different versions of the stream in the manifest according to their bitrates. Leave to Low to high bitrate to keep the list in the ascending order of bitrate, or enter the priority number (where 1 is the highest priority).
Audio Group:
if the input is an audio, this parameter gives the name of the mutually-exclusive rendition group it pertains.
if the input is a video, this parameter gives the name of the set of audio renditions that may be used. The rendition group shall exist.
Additional NAME attribute in #EXT-X-STREAM-INF tag: set to none by default, add a not standardized attribute in the tag if the input is a video or an audio rendition.
Video Group: set to none by default. If the input is a video, this parameter gives the name of the mutually-exclusive rendition group it pertains, it is not taken in account for audio input. It may be used for multiangle applications.
Default rendition: if set to true and if the input is part of a group, the rendition should be played by default. Only one default rendition shall be defined per audio or video group.
Auto-select rendition: set to true by default. A player may automatically select a rendition between the ones with auto-select set to true. Only one rendition with the same language shall be auto-selectable. This parameter should be set to false for audio description rendition.
Rendition NAME attribute: set to Auto by default. Fill the NAME attribute of the #EXT-X-MEDIA tag. It is taken in account only if the rendition is part of a audio or video group. it shall be unique in the group.
Additional NAME attribute in #EXT-X-STREAM-INF tag: set to None by default. This attribute is not part of the HLS standard.
Versions v2, v3: available for video and in audio-only renditions
Version v4, v5: available for video and audio renditions
Input: TS Subtitle Tab
You may:
Get the DVB Teletext subtitles from a TS input and convert them in WebVTT format in the HLS output.
Get the DVB Subtitles from a TS input and convert them in SMPTE-TT format in the HLS output.
To do so, you must:
Create a TS component extractor processing component to extract and filter the subtitles.
348 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
In this processing component, set the Component type to subtitle and specify the Subtitle language and/or Subtitle type and/or Subtitle component type.
Link the TS component extractor processing component to a TS Subtitle input of the HLS output.
Note that if you want to extract several IDs coming from the same input PID, you may set the Component type to subtitle and set Any to the Language and/or Subtitle type and/or Subtitle component type. You can also specify all the parameters and link the concerned processing components as many times as of IDs.
For each linked TS subtitle input, an Input: TS Subtitle tab is created in the HLS output processing component.
Figure 3-311. HLS output – TS subtitle parameters
In this tab, you must set the following parameters:
Stream Id: Internal identifier used in the filename and URI to reference the input stream.
Subtitle input ID and Subtitle language.
It is recommended to filter subtitle in the TS Component Extractor workflow by setting the Component type to subtitle and specifying the Subtitle language and/or Subtitle component type parameters. In this case, you shall set Subtitle input ID and Subtitle language values to Auto here in order to accommodate that configuration.
For existing workflows you may continue to use the Subtitle input ID and Language parameters as follows (in the TS Component Extractor workflow, set Component type to Custom and Stream type to PES private data): - Subtitle input ID: indicate the page number you wish to use. If left to Auto, the first page number of the subtitle is used. This mode is not suitable when there are several Subtitle IDs in the same input PID.
Electra VS - Version 05.10 349 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- Subtitle language: if left to Auto, which is fine if the stream complies with the standard, the Electra VS uses the language associated with the teletext indicated by the ID. Otherwise, specify the language manually using the ISO codes1 (e.g., enter eng for English, spa for Spanish, etc.).
Default rendition: if set to true, the rendition should be played by default in the absence of information from the user indicating a different choice. It shall be unique among the subtitles.
Auto-select rendition: set to true by default. A player may automatically select a rendition between the ones with auto-select set to true. Only one rendition with the same language shall be auto-selectable. Auto-select shall is usually set to false for subtitle for hearing impaired.
Forced rendition: set to false by default. If set to yes, the rendition contains content which is considered essential to play. When selecting a forced rendition, a player should choose the one that best matches the current playback environment (e.g. language).
Rendition NAME attribute: set to Auto by default. Fill the NAME attribute of the #EXT-X-MEDIA tag. It shall be unique among the subtitles.
Input: ES Subtitle Tab
The ES Subtitle tab lets you get subtitles from an SDI input and include them in WebVTT format in an HLS output.
To do so, you must link the Teletext output of an SDI input processing component to the ES subtitle input of the HLS output.
For each linked ES subtitle input, an Input: ES Subtitle tab is created in the HLS output processing component.
Figure 3-312. HLS output – ES subtitle parameters
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
350 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
In this tab, you must set the following parameters:
Stream Id: Internal identifier used in the filename and URI to reference the input stream.
ES Subtitle input ID: indicate the page number you wish to use. If left to Auto, the first page number of the subtitle is used. This mode is not suitable when there are several Subtitle IDs in the same input.
ES Subtitle language: if left to Auto, which is fine if the stream complies with the standard, the Electra VS uses the language associated with the teletext indicated by the ID. Otherwise, specify the language manually using the ISO codes1 (e.g., enter eng for English, spa for Spanish, etc.).
Default rendition: if set to true, the rendition should be played by default in the absence of information from the user indicating a different choice. It shall be unique among the subtitles.
Auto-select rendition: set to true by default. A player may automatically select a rendition between the ones with auto-select set to true. Only one rendition with the same language shall be auto-selectable. Auto-select shall is usually set to false for subtitle for hearing impaired.
Forced rendition: set to false by default. If set to yes, the rendition contains content which is considered essential to play. When selecting a forced rendition, a player should choose the one that best matches the current playback environment (e.g. language).
Rendition NAME attribute: set to Auto by default. Fill the NAME attribute of the #EXT-X-MEDIA tag. It shall be unique among the subtitles.
Input: Section Tab
You can link the output of a SCTE 35 extractor to the input of HLS output.
Figure 3-313. SCTE 35 extractor linked to HLS output
Each time a SCTE 35 section is received, a tag containing the section as a base64 string is added in the HLS media list.
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
Electra VS - Version 05.10 351 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
#EXT-SCTE-35:CUE="/DAIAAAAAAAAAAAQAAZ/I0VniQAQAgBDVUVJQ AAAAH+cAAAAAA=="
If you want the chunk to insert a segment when receiving a SCTE 35 splice in or splice out, you must also activate the option "SCTE 35 conditioning» in the chunker.
Figure 3-314. HLS output – Section parameters
HLS File Output
The HLS File output receives audio/video components, creates the chunks and manifests, encrypts the chunks and makes them available on a network storage.
Parameters Tab
Figure 3-315. HLS file output parameters
For this processing component, you must set the following parameters:
352 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
HLS files storage: indicate the network storage where the output files must be placed. Refer to section ’Video overlay’ on page 296 for the possibles syntaxes.
HLS files folder: indicate the path to the folder on the network storage where the output file must be placed.
HLS Protocol version: choose one version:
Version 2: suitable for programs with only one audio language. The generated chunks contain both video and audio components.
Version 3: same as version 2 with durations in ms.
Version 4: mandatory for programs with more than one audio language. Video and audio components are not in the same chunks (only one component per chunk). This version may not be supported by old devices.
Version 5: lets you have subtitles in WebVTT format.
Manifest file name: name of the main manifest.
Custom naming: this parameter lets you define how to name the chunk files.
If set to false, the name of the chunk files will be built as follows: manifest name_time_stream ID_sequence number manifest name being the name set earlier in the Manifest file name field without the m3u8 file extension. Define the Add prefix parameter: set to true to use the name of the manifest as a prefix for all file names (chunks and secondary manifests). This is useful to differentiate the files originating from several streams.
If set to true, the name of the chunk files will be built according to the following rule: field1_field2_field3_field4_field5 Set the following parameters: - Name: enter a name for the file, at your convenience. - Separator: choose from the list the sign that should be used as separator in the filename: _ or -. - Field 1 to Field 5: choose from the lists the elements you want to use to build the filename, among: name, bitrate, stream ID, sequence number, time and unused. If set to unused, this field and the following ones will not be included in the filename. time being the date of the beginning of the session (and not the date of the chunk). sequence number being incremented at each chunk.
Media URI custom naming: The parameters are the same as for a live HLS output (refer to page 342).
Electra VS - Version 05.10 353 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Add low bitrate audio only stream (HLS Protocol version 2 or 3): if set to true, chunks that contain only the audio component are generated. Set the Audio only stream ID, Audio only stream media order and Audio only NAME attribute in #EXT-X-STREAM-INF parameters as indicated in section ’Input Tab’ on page 347.
Create I-frame only streams (HLS Protocol version 4 or 5): if set to true, an I-frame only stream is added per video defined in the manifest. The I-frame only stream references I-frames in existing video media segments. It allows the player to perform fast forward and rewind operations.
Encrypt files: if set to true, DRM is activated. Set the following parameters:
Key server connection: select the conditional access server to which Electra VS should connect to get the key from the drop-down list. If set to None, Electra VS generates the key itself. Otherwise, enter the specific parameters of the CAS server: - Key server URL: URL of the CAS server. - Use authentication (Nagra, Verimatrix, Irdeto): set to true if the CAS server requires an authentication, and enter the User name and Password. Also specify the HTTP Authentication type (auto, basic or digest). - Define backup key server: set to true if you want to declare a backup CAS server. Enter the URL of this backup server in the Backup key server URL field. - Content id (Nagra, Irdeto, PolyMedia, ZTE): identifier of the program to encrypt (string). - Resource id (Verimatrix): identifier of the program to encrypt (integer). - Account Id (Irdeto): identifier of the account to connect to the Irdeto server. - Use last key (Irdeto): Set to true to return the last registered encryption key for a specified live event. Use this method if an encoding session reuses the last generated encryption key for the live event instead of generating a new key. This is particularly useful when multiple encoders are configured, to use the same encryption key for a live event. Set to false to generate and return a new PlayReady encryption key for the specified live event.
Key mode: - If set to Fixed Key, the key is fixed once. Enter the value of the key in the Key field (32 characters).
354 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- If set to Key Rotation, the key is periodically renewed. Enter the refresh period in the Key refresh period field, in number of chunks.
IV value: value of the initial vector. This can be: - Chunk number - Random value: in this case, enter the refresh period of the initial vector in the IV refresh period field, in number of chunks.
Input Tab
As for a live HLS output, you can set the following parameters Stream Id, Language, Playlist media order ...... Refer to section ’Input Tab’ on page 347.
Input: TS Subtitle Tab As for a live HLS output, you can get the DVB Teletext subtitles or DVB subtitles from an input and include them as WebVTT subtitles or SMPTE TT in an HLS File output. The process and parameters are exactly the same as in live. Refer to section ’Input: TS Subtitle Tab’ on page 348.
Input: ES Subtitle Tab
As for a live HLS output, you can get subtitles from an SDI input and include them in WebVTT format in an HLS file output. The process and parameters are exactly the same as in live. Refer to section ’Input: ES Subtitle Tab’ on page 350.
Input: Section
As for a live HLS output, you can link the output of a SCTE 35 extractor to the HLS file output. The process and parameters are exactly the same as in live. Refer to section ’Input: Section Tab’ on page 351.
Electra VS - Version 05.10 355 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Smooth Streaming
Description
The Smooth Streaming output receives audio/video components, creates the chunks and the manifest, encrypts the chunks, makes them available on the local Web server and/or on a remote Web server.
Parameters
Figure 3-316. Smooth streaming parameters
For this processing component, you must set the following parameters:
Parameters Tab
Push on remote Web server: if set to true, the manifest and chunks are posted to a remote Web server, an IIS server for example. In this case, set the following parameters:
Remote web server URL: indicate the URL used to communicate with the remote Web server. The syntax shall be the following http://remote_web_server_name/path/publishing_point.isml or http://remote_web_server_ip/path/publishing_point.isml If the syntax is http://remote_web_server_name/path/publishing_point.isml - you shall configure the DNS in the Setup tab, IP category (see Chapter Installation)
356 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- you shall indicate the LAN used to communicate with the remote Web server If the syntax is http://remote_web_server_ip/path/publishing_point.isml - you do not have to configure the DNS - you shall set the address directly in the Remote Web server IP address
Connection to remote server: select One single connection for all profiles or One connection per profile depending on the remote web server requirements.
Traffic smoothing: indicate if you want to smooth the traffic generated by the chunk transmission to the remote web server and the Maximum traffic overhead accepted (30% to 500%). The overhead is calculated on the theoretical broadcast bitrate. It means that with an maximum overhead set to 100% the traffic bitrate will not exceed two times the estimated bitrate.
Authentication type: set the server authentication type (auto, basic or digest) if the remote Web server requires an authentication, and enter the User name and Password.
Use local Web server: if set to true, the chunks are available on the device’s Web server. In this case, set the following parameters:
Local Web server IP address: virtual IP address. A player can receive the chunks from this address. This address must be part of a Electra VS LAN, otherwise job creation will be refused.
Folder: folder where the manifests and chunks are stored on the local Web server.
Max clients number: expected maximum number of clients for this output stream. This parameter is used to check that the device has the resource to process the requests for this stream.
Available stream duration: depth of chunks that are available on the Web server. The minimum duration must be equal to the length of at least two chunks.
Encrypt files: if set to true, DRM is activated. Set the following parameters:
Algorithm: two algorithms are available: - AES CBC - AES CTR
Key server connection: select the conditional access server to which Electra VS should connect to get the key from the drop-down list. If set to None, Electra VS generates the key itself. You must set
Electra VS - Version 05.10 357 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- Key: value used to compute the content encryption key (CEK). It must be configured in base64 format (ex: XVBovsmzhP9gRIZxWfFta3VVRPzVEWmJsazEJ46). - Key id: identifier of the key associated to the CEK in the Playready license. It must be configured in GUID format, big endian (ex: 4B640997-E5CD-495F-866B-969CD2E31B52). - License URL: enter the URL of the license server to which the player must connect to retrieve the encryption keys. - Non-silent License URL: enter the URL of the non-silent license acquisition web page to which the player must connect to retrieve the encryption keys. - Domain service ID: enter the service ID for the domain service in GUID format. For example: deb48f11-8b3a-416d-7a1f-00006d57fd05. - PIFF version: enter the PIFF version 1.3 or 1.1 (deprecated). Otherwise, enter the specific parameters of the CAS server: - Key server URL: URL of the CAS server. - Use authentication (BuyDrm): set to true if the CAS server requires an authentication, and enter the User name and Password. Also specify the HTTP Key server authentication type (auto, basic or digest). - Key server user name (Irdeto): enter the user name required to access the Irdeto key server. - Key server password (Irdeto): enter the password required to access the Irdeto key server. - Server key, User key, Key Id and Media Id (BuyDrm): enter the values provided by BuyDrm. - Account Id (Irdeto): identifier of the account to connect to the Irdeto server. - Content id: identifier of the program to encrypt (string). - Use last key (Irdeto, Viaccess): Set to true to return the last registered encryption key for a specified live event. Use this method if an encoding session reuses the last generated encryption key for the live event instead of generating a new key. This is particularly useful when multiple encoders are configured, to use the same encryption key for a live event. Set to false to generate and return a new PlayReady encryption key for the specified live event. - Define backup key server: set to true if you want to declare a backup CAS server. Enter the URL of this backup server in the Backup key server URL field.
358 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- License URL (PlayReady Live TV): enter the URL of the license server to which the player must connect to retrieve the encryption keys. - Non silent license URL (PlayReady Live TV): enter the URL of the non-silent license acquisition Web page to which the player must connect to retrieve the encryption keys. - Domain service ID (PlayReady Live TV): service ID for the domain service in GUID format. For example: deb48f11-8b3a-416d-7a1f-00006d57fd05. - Key mode (PlayReady Live TV, Huawei, Harmonic KMS, Viaccess, Nagra): • If set to Fixed Key, the server set the key. • If set to Key Rotation, the server set the key and it is periodically renewed. Enter the refresh period in the Key refresh period field, in number of chunks. - PIFF version: enter the PIFF version 1.3 or 1.1 (deprecated).
Upon an important configuration change, it is necessary to restart the IIS server. For instance, when adding a new video profile, the Electra VS stops and restarts the IIS server. However, for this restart action to be possible, the IIS server configuration must authorize it. To do so, the IIS server administrator must add the following line to the isml file: Without this line being present, the administrator will need to restart manually the IIS server publishing point.
Input Tab
Figure 3-317. Smooth streaming output - input parameter
In the Input tab, set the following parameter:
Language: leave to Auto to keep the language of the input, or use the ISO codes1 to force the language manually (for instance, enter eng for English, spa for Spanish, etc.).
Electra VS - Version 05.10 359 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Input: TS Subtitle Tab
You may:
Get the DVB Teletext subtitles from a TS input and include them in DFXP format in the Smooth Streaming output.
Get the DVB Subtitles from a TS input and include them in SMPTE-TT format in the Smooth Streaming output.
To do so, you must:
Create a TS component extractor processing component to extract and filter the subtitles.
In this processing component, set the Component type to subtitle and specify the Subtitle language and/or Subtitle type and/or Subtitle component type.
Link the TS component extractor processing component to a TS Subtitle input of the Smooth Streaming output.
Note that if you want to extract several IDs coming from the same input PID, you may set the Component type to subtitle and set Any to the Language and/or Subtitle type and/or Subtitle component type. You can also specify all the parameters and link the concerned processing components as many times as of IDs.
For each linked TS subtitle input, an Input: TS Subtitle tab is created in the Smooth Streaming output processing component.
Figure 3-318. Smooth streaming output – TS subtitle parameters
In this tab, you must set the following parameters:
Subtitle input ID and Subtitle language.
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
360 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
It is recommended to filter subtitle in the TS Component Extractor workflow by setting the Component type to subtitle and specifying the Subtitle language and/or Subtitle component type parameters. In this case, you shall set Subtitle input ID and Subtitle language values to Auto here in order to accommodate that configuration.
For existing workflows you may continue to use the Subtitle input ID and Subtitle language parameters as follows (in the TS Component Extractor workflow, set Component type to Custom and Stream type to PES private data): - Subtitle input ID: indicate the page number you wish to use. If left to Auto, the first page number of the subtitle is used. This mode is not suitable when there are several Subtitle IDs in the same input PID. - Subtitle language: if left to Auto, which is fine if the stream complies with the standard, the Electra VS uses the language associated with the teletext indicated by the ID. Otherwise, specify the language manually using the ISO codes1 (e.g., enter eng for English, spa for Spanish, etc.).
Subtitle stream name: if left to Auto, the stream name is set following the default syntax "text_[language]" in case of EBU Teletext or "sub_[language]" in case of DVB subtitle. Otherwise, the stream name is set to the string that is entered by user.
Subtitle FourCC: if left to Auto, the FourCC is set to DFXP in case of EBU Teletext or TTML in case of DVB Subtitle. Otherwise, the FourCC is set to the string that is entered by user.
TS User syntax: if set to true, it is possible for the user to configure the TS Subtitle field TT, TS Subtitle field Head and TS Subtitle template of TTML files. The generated TTML file will be as follows: Green sections will be replaced by the configured parameters, red sections will be updated according to received subtitle. SUBTITLE_TEXT
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
Electra VS - Version 05.10 361 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
SUBTITLE_TEXT
is the string entered in the Subtitle template field.Input: ES Subtitle Tab
The ES Subtitle tab lets you get subtitles from an SDI input and to include them in DFXP format in a Smooth Streaming output.
To do so, you must link the Teletext output of an SDI input processing component to the ES subtitle input of the Smooth Streaming output.
For each linked ES subtitle input, an Input: ES Subtitle tab is created in the Smooth Streaming output processing component.
Figure 3-319. Smooth streaming output – ES subtitle parameters
In this tab, you must set the following parameters:
ES Subtitle input ID: indicate the page number you wish to use. If left to Auto, the first page number of the subtitle is used. This mode is not suitable when there are several Subtitle IDs in the same input.
ES Subtitle language: if left to Auto, which is fine if the stream complies with the standard, the Electra VS uses the language associated with the teletext indicated by the ID. Otherwise, specify the language manually using the ISO codes1 (e.g., enter eng for English, spa for Spanish, etc.).
ES Subtitle stream name: if left to Auto, the stream name is set following the default syntax "text_[language]" in case of EBU Teletext or "sub_[language]" in case of DVB subtitle. Otherwise, the stream name is set to the string that is entered by user.
ES Subtitle FourCC: if left to Auto, the FourCC is set to DFXP in case of EBU Teletext or TTML in case of DVB Subtitle. Otherwise, the FourCC is set to the string that is entered by user.
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
362 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
ES User syntax: if set to true, it is possible for the user to configure the ES Subtitle field TT, ES Subtitle field Head and ES Subtitle template of TTML files. See page 361 for more details about the editing rules.
Smooth Streaming File Output
Description
The Smooth Streaming file output receives audio/video components, creates chunks and manifests, encrypts the chunks and makes them available on network storage.
Parameters
Figure 3-320. Smooth Streaming file output parameters
For this processing component, you must set the following parameters:
Parameters Tab
Smooth Streaming files storage: indicate the network storage where the output files must be placed. Refer to section ’Video overlay’ on page 296 for the possibles syntaxes.
Smooth Streaming files folder: indicate the path to the folder on the network storage where the output file must be placed.
Smooth Streaming file format: choose whether the output file should be in disk file format or in wire file format.
Output file prefix: prefix added to the output file name.
Encrypt files: if set to true, DRM is activated. Set the following parameters:
Algorithm: two algorithms are available: - AES CBC - AES CTR
Electra VS - Version 05.10 363 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Key server connection: select the conditional access server to which Electra VS should connect to get the key from the drop-down list. If set to None, Electra VS generates the key itself. You must set - Key: value used to compute the content encryption key (CEK). It must be configured in base64 format (ex: XVBovsmzhP9gRIZxWfFta3VVRPzVEWmJsazEJ46). - Key id: identifier of the key associated to the CEK in the Playready license. It must be configured in GUID format, big endian (ex: 4B640997-E5CD-495F-866B-969CD2E31B52). - License URL: enter the URL of the license server to which the player must connect to retrieve the encryption keys. - Domain service ID: enter the service ID for the domain service in GUID format. For example: deb48f11-8b3a-416d-7a1f-00006d57fd05. - PIFF version: enter the PIFF version 1.3 or 1.1 (deprecated). Otherwise, enter the specific parameters of the CAS server: - Key server URL: URL of the CAS server. - Use authentication (BuyDrm): set to true if the CAS server requires an authentication, and enter the User name and Password. Also specify the HTTP Key server authentication type (auto, basic or digest). - Key server user name (Irdeto): enter the user name required to access the Irdeto key server. - Key server password (Irdeto): enter the password required to access the Irdeto key server. - Server key, User key, Key Id and Media Id (BuyDrm): enter the values provided by BuyDrm. - Account Id (Irdeto): identifier of the account to connect to the Irdeto server. - Content id: identifier of the program to encrypt (string). - Use last key (Irdeto): Set to true to return the last registered encryption key for a specified live event. Use this method if an encoding session reuses the last generated encryption key for the live event instead of generating a new key. This is particularly useful when multiple encoders are configured, to use the same encryption key for a live event. Set to false to generate and return a new PlayReady encryption key for the specified live event. - Define backup key server: set to true if you want to declare a backup CAS server. Enter the URL of this backup server in the Backup key server URL field.
364 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- PIFF version: enter the PIFF version 1.3 or 1.1 (deprecated).
Input Tab
In the Input tab, set the following parameter:
Language: leave to Auto to keep the language of the input, or use the ISO codes1 to force the language manually (for instance, enter eng for English, spa for Spanish, etc.).
Input: TS Subtitle Tab
As for a live Smooth Streaming output, you can get the DVB Teletext or DVB-Subtitle subtitles from an input and include them in a Smooth Streaming File output. The process and parameters are exactly the same as in live. Refer to section ’Input: TS Subtitle Tab’ on page 360.
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
Electra VS - Version 05.10 365 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
MPEG-DASH
Description
The MPEG-DASH output receives audio/video components, creates the chunks and manifests and makes them available on the local Web server and/or on a remote Web server.
Parameters
Figure 3-321. MPEG-DASH output parameters
Parameters Tab
Available stream duration: depth of chunks that are available on the Web server. The minimum duration must be equal to the length of at least two chunks.
MPEG-DASH ISO/IEC version: select the version of the DASH standard you want to be compliant with.
HbbTV compliant: set to true to generate an HbbTV compliant stream. Chunks are then compatible with MPEG-DASH and HbbTV. Manifests for MPEG-DASH and HbbTV are generated.
366 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Interleaving: if set to true, video and audio are in the same files. This parameter SHALL be set to false if there is more than one audio component.
Use file prefix (if manifest naming or segment template are set to auto): if set to true the output file prefix is used as prefix for automatic manifest or segment file names.
Output file prefix: prefix added to the manifest name [prefix]manifest.mpd and the segment file names if segment template is not customized.
Manifest naming: if set to Auto, the manifest names are set to [prefix]manifest.mpd or [prefix]static_manifest.mpd (for static MPD). If set to Custom, the manifest names are entirely defined by MPD file name or Static MPD file name (for static MPD).
Create static MPD: if set to true, a manifest is created (in addition to the basic one) that defines explicitly the name of the segment currently available. The name of the static manifest is set to [prefix]static_manifest.mpd if manifest naming is set to Auto. Otherwise you can define your own static manifest name in the Static MPD file name.
Segment template:
If set to Auto, the media and initialization segment names will be built as follows: - Video media segment: [prefix]video-$Number$_$Bandwidth$bps.mp4 - Audio media segment: [prefix]audio-$Number$_$Bandwidth$bps_Input_ $RepresentationID$.mp4 - Subtitle media segment: [prefix]subtitle-$Number$_$Bandwidth$bps_Input_ $RepresentationID$.mp4 - Video initialization segment: [prefix]video_$Bandwidth$bps-init.mp4 - Audio initialization segment: [prefix]audio_$Bandwidth$bps_Input_ $RepresentationID$-init.mp4 - Subtitle initialization segment: [prefix]subtitle_$Bandwidth$bps_Input_ $RepresentationID$-init.mp4 For interleaved media segment (i.e. if Interleaving is set to true), the Multiplexer media and initialization segment names will be built as follows: - Multiplexer media segment: [prefix]mux-av-$Number$_$Bandwidth$bps.mp4
Electra VS - Version 05.10 367 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- Multiplexer initialization media segment: [prefix]mux-av_$Bandwidth$bps-init.mp4 If set to Custom, you can define your own template inserting the following elements in the names: - $Bandwidth$: bandwidth of the media - $RepresentationID$: media identifier - $Number$: sequence number being incremented at each segment.
Use local Web server: if set to true, the chunks are available on the device’s Web server. In this case, set the following parameters:
Local Web server IP address: virtual IP address. A player can receive the chunks from this address. This address must be part of a Electra VS LAN, otherwise job creation will be refused.
Folder: folder where the manifests and chunks are stored on the local Web server.
Max clients number: expected maximum number of clients for this output stream. This parameter is used to check that the device has the resources to process the requests for this stream.
Push on remote Web server: if set to true, the manifest and chunks are posted to a remote Web server. In this case, set the following parameters:
Remote Web server URL: indicate the URL used to communicate with the remote Web server. If the remote Web server URL contains a name instead of an IP address, you must configure the DNS in the Setup tab, IP category (see section ’DNS’ on page 171). If you do not wish to use the IP address resolution by DNS, you can also directly enter the IP address of the remote Web server or enter the number of the LAN to connect to the remote server in the LAN to remote Web server or remote Web server IP address field.
Authentication: set to true if the remote Web server requires an authentication, and enter the User name and Password.
Traffic smoothing: indicate if you want to smooth the traffic generated by the chunk transmission to the remote web server and the Maximum traffic overhead accepted (30% to 500%). The overhead is calculated on the theoretical broadcast bitrate. It means that with an maximum overhead set to 100% the traffic bitrate will not exceed two times the estimated bitrate.
Delete files from remote web server: if set to true, the files posted on the remote Web server are deleted after the Available stream duration set above.
Create directory on remote web server: if set to true, the root directory is created before chunks transfer.
368 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Local storage duration when remote server is unreachable: enter the time during which the content should be bufferized if during a push action, the remote server becomes unreachable. When the remote server is available again, all the content is sent at once.
Before using this feature, check that the bandwidth is widely dimensioned, because otherwise there is a risk of network congestion when the remote server is back up, which can impact other streams.
Encrypt files: if set to true, DRM is activated. Set the following parameters:
Key server connection: select the conditional access server to which Electra VS should connect to get the key. If set to None, Electra VS generates the key itself. You have to set - Key: value used to compute the content encryption key (CEK). It must be configured in base64 format (ex: XVBovsmzhP9gRIZxWfFta3VVRPzVEWmJsazEJ46). - Key id: identifier of the key associated to the CEK in the Playready license. It must be configured in GUID format, big endian (ex: 4B640997-E5CD-495F-866B-969CD2E31B52) - License URL: enter the URL of the license server to which the player must connect to retrieve the encryption keys. If set to Huawei or Harmonic KMS enter the specific parameters of the CAS server - Key server URL: URL of the CAS server - Define backup key server: set to true if you want to declare a backup CAS server. Enter the URL of this backup server in the Backup key server URL field - Content id: identifier of the program to encrypt (string) - Key mode: • If set to Fixed Key, the key is fixed once. Enter the value of the key in the Key field (32 characters). • If set to Key Rotation, the key is periodically renewed. Enter the refresh period in the Key refresh period field, in number of chunks. If set to PlayReady LiveTv, enter the specific parameters of the CAS server - Key server URL: URL of the CAS server - Define backup key server: set to true if you want to declare a backup CAS server. Enter the URL of this backup server in the Backup key server URL field. - Content id: identifier of the program to encrypt (string).
Electra VS - Version 05.10 369 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- Key mode: • If set to Fixed Key, the key is fixed once. Enter the value of the key in the Key field (32 characters). • If set to Key Rotation, the key is periodically renewed. Enter the refresh period in the Key refresh period field, in number of chunks. - License URL (PlayReady Live TV): enter the URL of the license server to which the player must connect to retrieve the encryption keys. - Non silent license URL (PlayReady Live TV): enter the URL of the non-silent license acquisition Web page to which the player must connect to retrieve the encryption keys. - Domain service ID (PlayReady Live TV): service ID for the domain service in GUID format. For example: deb48f11-8b3a-416d-7a1f-00006d57fd05. If set to Widevine, enter the specific parameters of the CAS server - Key server URL: URL of the CAS server. - Content id: identifier of the program to encrypt (string). - Policy: name of a previously stored policy to use for this content. The policy contains playback duration information and output protection information for SD, HD and AUDIO. If Policy is not specified, the content provider must provide all policy attributes at the time of license acquisition). - Signer: identifies the entity sending the message. - Add signature: Allow to add a signature in the key requests. - Signer Key: Key used to create the signature (hexadecimal format, 32 bytes). - Signer IV: Initial vector used to create the signature (hexadecimal format, 16 bytes). If set to Piksel, enter the specific parameters of the CAS server - Key server URL: URL of the CAS server. - Content id: identifier of the program to encrypt (string).
Set Minimum Update Period: set the minimum time between each update of the manifest content. Values can range between PT10S and P1Y (one year). The string must follow a period syntax, for example: PyyYmmMddDThhHmmMssS.
370 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Input Tab
Figure 3-322. DASH output- input parameter
In the Input tab, set the following parameter:
Language: leave to Auto to keep the language of the input, or use the ISO codes1 to force the language manually (for instance, enter eng for English, spa for Spanish, etc.).
Representation ID: media identifier. If left to Auto a numeric identifier will be automatically set. If you enter an identifier, it must be unique for the component (i.e. it is guaranteed to be unique among all identifiers).
Input: TS Subtitle Tab
To get the DVB Teletext or DVB-Subtitle subtitles from a TS input and include them as SMPTE-TT subtitles in a DASH output, you must:
Create a TS component extractor processing component to extract the subtitles.
In this processing component, set the Component type to subtitle and specify the Subtitle language and/or Subtitle type and/or Subtitle component type.
Link the TS component extractor processing component to a TS Subtitle input of the DASH output.
Note that if you want to extract several IDs coming from the same input PID, you may set the Component type to subtitle and set Any to the Language and/or Subtitle type and/or Subtitle component type. You can also specify all the parameters and link the concerned processing components as many times as of IDs.
For each linked TS subtitle input, an Input: TS Subtitle tab is created in the DASH output processing component.
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
Electra VS - Version 05.10 371 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-323. DASH output – TS subtitle parameters
In this tab, you must set the following parameters:
Subtitle input ID and Subtitle language.
It is recommended to filter subtitle in the TS Component Extractor workflow by setting the Component type to subtitle and specifying the Subtitle language and/or Subtitle component type parameters. In this case, you shall set Subtitle input ID and Subtitle language values to Auto here in order to accommodate that configuration.
For existing workflows you may continue to use the Subtitle input ID and Language parameters as follows (in the TS Component Extractor workflow, set Component type to Custom and Stream type to PES private data): - Subtitle input ID: indicate the page number you wish to use. If left to Auto, the first page number of the subtitle is used. This mode is not suitable when there are several Subtitle IDs in the same input PID. - Subtitle language: if left to Auto, which is fine if the stream complies with the standard, the Electra VS uses the language associated with the teletext indicated by the ID. Otherwise, specify the language manually using the ISO codes1 (e.g., enter eng for English, spa for Spanish, etc.).
Subtitle representation ID: media identifier. If left to Auto a numeric identifier will be automatically set. If you enter an identifier, it must be unique for the component (i.e. it is guaranteed to be unique among all identifiers).
Input: ES Subtitle Tab
The ES Subtitle tab lets you get subtitles from an SDI input and to include them in SMPTE-TT format in a DASH output.
To do so, you must link the Teletext output of an SDI input item to the ES subtitle input of the DASH output.
For each linked ES subtitle input, an Input: ES Subtitle tab is created in the DASH output item.
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
372 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-324. DASH output – ES subtitle parameters
In this tab, you must set the following parameters:
ES Subtitle input ID: indicate the page number you wish to use. If left to Auto, the first page number of the subtitle is used. This mode is not suitable when there are several Subtitle IDs in the same input.
ES Subtitle language: if left to Auto, which is fine if the stream complies with the standard, the Electra VS uses the language associated with the teletext indicated by the ID. Otherwise, specify the language manually using the ISO codes1 (e.g., enter eng for English, spa for Spanish, etc.).
ES Subtitle representation ID: media identifier. Enter an identifier. It must be unique for the component (i.e. it is guaranteed to be unique among all identifiers). If left to Auto a numeric identifier will be automatically set.
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
Electra VS - Version 05.10 373 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
MPEG-DASH File Output
Description
The MPEG-DASH file output receives audio/video components, creates chunks and manifests and makes them available on network storage.
Parameters
Figure 3-325. MPEG-DASH file output parameters
For this item, you must set the following parameters:
MPEG-DASH files storage: indicate the network storage where the output files must be placed. Refer to section ’Video overlay’ on page 296 for the possibles syntaxes.
MPEG-DASH files folder: indicate the folder on the network storage where the output files must be placed.
MPEG-DASH file format: choose one of the available formats:
Disk file format: in this format, all chunks are grouped into a single MP4 file (moof).
Wire file format: in this format, all chunks are delivered in distinct files. This format is compatible with all types of Web servers.
HbbTV compliant: set to true to generate an HbbTV compliant stream. Chunks are then compatible with MPEG-DASH and HbbTV. Manifests for MPEG-DASH and HbbTV are generated.
Interleaving: if set to true, video and audio are in the same files. This parameter SHALL be set to false if there is more than one audio components.
374 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Output file prefix: prefix added to the manifest name [prefix]_manifest.mpd and the segment file names if segment template is not customized.
Segment template:
If set to Auto, the media and initialization segment names will be built as follows: For disk file format (i.e. if MPEG-DASH files format is set to Disk file format) - Video file: [prefix]_video-$Number$_$Bandwidth$bps.mp4 - Audio file: [prefix]_audio-$Number$_$Bandwidth$bps_Input_ $RepresentationID$.mp4 - Subtitle file: [prefix]_subtitle-$Number$_$Bandwidth$bps_Input_ $RepresentationID$.mp4 For interleaved media segment (i.e. if Interleaving is set to true), the media and initialization segment names will be built as follows: - Multiplexer file: [prefix]_mux-av_$Bandwidth$bps_Input_ $RepresentationID$.mp4 For disk file format (i.e. if MPEG-DASH files format is set to Wire file format) - Video media segment: [prefix]_video-$Number$_$Bandwidth$bps.mp4 - Audio media segment: [prefix]_audio-$Number$_$Bandwidth$bps_Input_ $RepresentationID$.mp4 - Subtitle media segment: [prefix]_subtitle-$Number$_$Bandwidth$bps_Input_ $RepresentationID$.mp4 - Video initialization segment: [prefix]_video_$Bandwidth$bps-init.mp4 - Audio initialization segment: [prefix]_audio_$Bandwidth$bps_Input_ $RepresentationID$-init.mp4 - Subtitle initialization segment: [prefix]_subtitle_$Bandwidth$bps_Input_ $RepresentationID$-init.mp4
Electra VS - Version 05.10 375 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
For interleaved media segment (i.e. if Interleaving is set to true), the Multiplexer media and initialization segment names will be built as follows: - Multiplexer media segment: [prefix]_mux-av-$Number$_$Bandwidth$bps.mp4 - Multiplexer initialization media segment: [prefix]_mux-av_$Bandwidth$bps-init.mp4 If set to Custom, you can define your own template inserting the following elements in the names: - $Bandwidth$: bandwidth of the media - $RepresentationID$: media identifier - $Number$: sequence number being incremented at each segment.
Encrypt files: if set to true, DRM is activated. Set the following parameters:
Key server connection: select the conditional access server to which Electra VS should connect to get the key. If set to None, Electra VS generates the key itself. You have to set - Key: value used to compute the content encryption key (CEK). It must be configured in base64 format (ex: XVBovsmzhP9gRIZxWfFta3VVRPzVEWmJsazEJ46). - Key id: identifier of the key associated to the CEK in the Playready license. It must be configured in GUID format, big endian (ex: 4B640997-E5CD-495F-866B-969CD2E31B52). - License URL: enter the URL of the license server to which the player must connect to retrieve the encryption keys. If set to Huawei, Harmonic KMS or ZTE, enter the specific parameters of the CAS server - Key server URL: URL of the CAS server. - Define backup key server: set to true if you want to declare a backup CAS server. Enter the URL of this backup server in the Backup key server URL field. - Content id: identifier of the program to encrypt (string). If set to Widevine, enter the specific parameters of the CAS server - Key server URL: URL of the CAS server. - Content id: identifier of the program to encrypt (string). - Policy: Name of a previously stored policy to use for this content. The policy contains playback duration information and output protection information for SD, HD and AUDIO. If Policy is not specified, the content provider must provide all policy attributes at the time of license acquisition).
376 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
- Signer: Identifies the entity sending the message. - Add signature: allow to add a signature in the key requests. - Signer Key: key used to create the signature (hexadecimal format, 32 bytes). - Signer IV: initial vector used to create the signature (hexadecimal format, 16 bytes). If set to Piksel, enter the specific parameters of the CAS server - Key server URL: URL of the CAS server. - Content id: identifier of the program to encrypt (string).
Set Minimum Update Period: set the player minimum period between to verification of manifest update.
Input Tab
In the Input tab, set the following parameter:
Language: leave to Auto to keep the language of the input, or use the ISO codes1 to force the language manually (e.g., enter eng for English, spa for Spanish, etc.).
As for a live DASH output, you can set the following parameters Language and Representation ID. Refer to section ’Input Tab’ on page 371.
Input: TS Subtitle Tab
As for a live DASH output, you can get the DVB Teletext or DVB-Subtitle subtitles from a TS input and include them as SMPTE-TT subtitles in a DASH output. The process and parameters are exactly the same as in live. Refer to section ’Input: TS Subtitle Tab’ on page 371.
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
Electra VS - Version 05.10 377 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
MP4 File Output
Description
The MP4 file output supports the following tracks:
Video: H.264, H.265, MPEG-2
Audio: AAC, Dolby Digital, MPEG-1 layer 2
The generated MP4 files are compatible with progressive download.
Parameters
Figure 3-326. MP4 file output parameters
For this processing component, you must set the following parameters:
MP4 file storage: indicate the network storage where the output file must be placed. Refer to section ’Video overlay’ on page 296 for the possibles syntaxes.
MP4 file folder: indicate the folder on the network storage where the output file must be placed.
MP4 file name: enter the name of the MP4 file.
MP4 file name extension: specify the file extension that the output MP4 file should have. If this parameter is not filled, the MP4 file name will be kept "as is". If this parameter is filled, any extension of the MP4 file name parameter will be replaced by this extension. This is useful when you want to keep the input file name (hot folder application, for example) and replace only the extension: you link the MP4 file name to the input file name, and you force the extension using the MP4 file name extension. If the extension is set to .3GP then 3GP file is generated.
Add RTP hint tracks: Set this parameter to true if you want to add RTP hint in the tracks.
Input Tab
For each component added in the output stream, a new Input tab is created.
378 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-327. MP4 file output – Input tab parameters
The Input tab contains the following parameters:
Track ID: the value set for the parameter must be unique. Leave it to Auto to ensure its uniqueness.
Language: leave to Auto to keep the language of the input, or use the ISO codes1 to force the language manually (e.g., enter eng for English, spa for Spanish, etc.).
1. For the whole list of ISO codes, refer to: http://www-01.sil.org/iso639-3/codes.asp?or- der=639_3&letter=%25
Electra VS - Version 05.10 379 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Selector and Choice Tools
The Selector and Choice tools let you define a condition to choose the input or output that should be used, respectively. They are both built the same way.
Dialog Description
The dialog contains two parts.
Parameter
Create a parameter to be used in the condition: check the box if you want the job’s author to set a parameter that will be used in the condition to choose the output. Edit the cells to create the parameter.
Conditions
The array lets you set a condition for each output. Double-click in the Condition column or click the button to access the condition editor. This editor is described in section ’Processing Component Parameters Array’ on page 232.
You can add inputs or outputs if needed.
Choice
The Choice tool lets you define a condition to choose the output that should be used. For example, let us imagine you want to send the stream to a different output based on the input bitrate, e.g. send it to output A if the bitrate is lower than 80,000 kbps, and to output B if it is higher.
To use the Choice tool, you first need to have in your workflow a public parameter with a label. For our example, publish and give a label to the bitrate parameter in the input processing component.
Insert the Choice processing component in your configuration and link it to the preceding processing component.
Figure 3-328. Inserting the Choice processing component in a workflow
380 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Use the condition editor to perform your configuration. For our example, set the condition of the Choice processing component as shown below.
Figure 3-329. Example of condition configuration for a Choice processing component
Selector
The Selector tool lets you define a condition to choose the input that should be used. It works basically the same way as the Choice tool, but reversely.
Let us take an example: a configuration contains two inputs: one TS over IP input#1 and one TS over IP input#2. We want the job author to choose whether to use one input or the other. We thus use the Selector tool, as shown in Figure 3-330.
Figure 3-330. Example of use of the Selector tool
Electra VS - Version 05.10 381 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Figure 3-331 shows the parameters set for the Selector tool.
Figure 3-331. Selector properties
In our example, we create a parameter called TSoverIP#1 to be used in the condition and we limit the possible values to true or false.
Then we set the condition as follows:
Input #1, i.e. the TS over IP input#1, must be used if the TSoverIP#1 parameter is set to true.
Input #2, i.e. the TS over IP input#2, must be used if the TSoverIP#1 parameter is not set to true (i.e. false).
382 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Description of the Predefined Favorite Workflows
Favorite workflows are offered preferentially when creating a job.
The following predefined favorite workflows are provided:
Live SD-HD Encoder
Live SD-HD Transcoder
Live WebTV Transcoder
You can add your own workflows in the Favorite category.
Description of the Live SD-HD Encoder Predefined Favorite Workflow
This workflow encodes an SDI input into a TS over IP output.
Video is encoded into H.264 or HEVC.
Audio PCM is encoded into AAC, Dolby Digital or MPEG-1 Layer 2.
Dolby input is transcoded into AAC, Dolby Digital or MPEG-1 Layer 2, or pass-through
Optional video processing is available (in this order): deinterlace, clipping, resize, frame-rate, logo insertion, text insertion.
Optional audio processing is available (in this order): mixer, resampler, loudness control, delay.
The output TS can be a SPTS or a MPTS. When MPTS is chosen,
Statmux is also possible.
You shall create one job per service. These jobs shall reference the same MPTS name.
The MPTS creation is done in its own job; this job is automatically created, its name is the MPTS name.
A PIP (picture-in-picture; H.264 Baseline) output can also be generated, in its own SPTS.
I period: when set to auto, the I period will depend on the output video frame rate: 24 at 25 fps, 32 at 29.97 fps, 48 at 50 fps, 64 at 59.94 fps.
Description of the Live SD-HD Transcoder Predefined Favorite Workflow
This workflow transcodes a TS over IP input into a TS over IP output.
Video is transcoded into H.264, HEVC or MPEG-2.
Electra VS - Version 05.10 383 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Audio is transcoded into AAC, Dolby Digital or MPEG-1 Layer 2, or pass-through.
Pass-through components are possible.
Optional video processing (in this order): deinterlace, clipping, resize, frame-rate, logo insertion, text insertion.
Optional audio processing (in this order): mixer, resampler, loudness control, delay, mute.
The output TS can be a SPTS or a MPTS.
When MPTS is chosen:
Statmux is also possible.
You shall create one job per service. These jobs shall reference the same MPTS name.
The MPTS creation is done in its own job; this job is automatically created, its name is the MPTS name.
A PIP (picture-in-picture; H.264 Baseline) output can also be generated, in its own SPTS.
I period: when set to auto, the I period will depend on the output video frame rate: 24 at 25 fps, 32 at 29.97 fps, 48 at 50 fps, 64 at 59.94 fps.
The parameters of a job based on the Live SD-HD Transcoder workflow are shown in section ’Setting Job Parameters Based on the Predefined Workflows’ on page 96.
384 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Description of the Live Web TV Transcoder Predefined Favorite Workflow
This workflow generates one or several WebTV outputs from a TS over IP input.
Video is transcoded in H.264, HEVC. Up to 12 video profiles can be generated. The video parameters can be configured globally or per profile.
Audio is transcoded into AAC.
Available outputs: HLS, MPEG-DASH, RTMP, Smooth Streaming, or TS (for an external packager). When several outputs are defined, you can choose, for each video profile, which outputs will use it.
Input subtitles (Teletext and DVB-Subtitles) can be transcoded (HLS, MPEG-DASH, Smooth Streaming) or pass-through (TS).
HLS: the HLS stream can be available on the local web server, or pushed to a remote origin server (and optionally its backup). DRM are available. When a segment duration is defined, HLS chunks are based on these segments.
MPEG-DASH: the MPEG-DASH stream can be available on the local web server, or pushed to a remote origin server. DRM are available.
RTMP: the audio/video can be pushed to a Flash Media Server. There is one stream per video profile. The audio is sent within each stream. There are 2 modes:
One connection per video profile (i.e. one stream per connection).
One connection for all the video profiles (i.e. all the streams in the same connection).
Smooth Streaming: the Smooth Streaming stream can be available on the local web server, or pushed to a remote IIS server (and optionally its backup). DRM are available.
TS: the components are sent on TS over IP. Encoder Boundary Point (CableLabs) can be added when required by the packager. There are 3 modes: - One SPTS is generated for each video profile. The SPTS of the first profile also contains the audio and subtitles. All the SPTS use the same multicast IP address. - One SPTS with all the components is generated (i.e. several video components, audio and subtitles in the same program). - One MPTS is generated, with one program per video profile. The program of the first profile also contains the audio and subtitles.
Video preprocessing:
DVB-Subtitle inserter: the DVB Subtitles are burned in the video.
Electra VS - Version 05.10 385 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Clipping: the video frame is cropped and inserted in another frame. It can be useful to manage aspect ratio (letterbox, pillarbox).
VBI blanking: removes the VBI lines (black and white pixels) on the top of the SD video.
Logo insertions: up to 2 logos (static or animated) can be inserted. A parameter allows to mute these logos seamlessly. A different logo for each profile can also be inserted.
Text insertions: static, scrolling. It can also be used to manage EAS. A different text for each profile can also be inserted.
Audio preprocessing: Dolby stereo downmixing, mixer, resampler, audio loudness control, delay.
Advanced:
Blackout management: a blackout can be activated seamlessly. The video is replaced by a picture and the audio is muted. The provided picture shall have the size of the first video profile.
The parameters of a job based on the Live Web TV Transcoder workflow are shown in section ’Setting Job Parameters Based on the Predefined Workflows’ on page 96.
386 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Layout of the Sample Workflows
Sample file-to-file transcoding
Sample IP TV - SDI input
Sample IP TV - SDI input HD to SD
Sample IPTV - TSoIP input
Sample Mosaic - 6 HD inputs
Sample WebTV - HLS WebDAV
Sample WebTV - Smooth Streaming to IIS server
Layout of the File-to-File Transcoding Sample Workflow
This is an example of file-to-file transcoding. This workflow can then be associated to a hot-folder.
Figure 3-332. File-to-File Transcoding sample workflow
Electra VS - Version 05.10 387 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Layout of the IPTV SDI Input Sample Workflow
This example performs IP TV encoding of an SDI input
Figure 3-333. IPTV SDI Input sample workflow
Layout of the IPTV SDI Input HD to SD Sample Workflow
This example performs IP TV encoding, with an HD 1080i input and a SD output
Figure 3-334. IPTV SDI Input HD to SD sample workflow
Layout of the IPTV TSoIP input Sample Workflow
This example performs a simple TSoIP TV transcoding.
Figure 3-335. IPTV TSoIP Input sample workflow
388 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Layout of the Mosaic - 6 HD Inputs Sample Workflow
This example creates a mosaic based on 6 HD inputs
Figure 3-336. Mosaic - 6 HD Inputs sample workflow
Electra VS - Version 05.10 389 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Layout of the WebTV - HLS WebDAV Sample Workflow
This example provides an HLS output pushed to a remote Web server.
Figure 3-337. WebTV - HLS WebDAV sample workflow
390 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Workflow Library
Layout of the WebTV - Smooth Streaming to IIS Server Sample Workflow
This example provides a Smooth Streaming output pushed to a remote Microsoft IIS server.
Figure 3-338. WebTV - Smooth Streaming to IIS Server sample workflow
Electra VS - Version 05.10 391 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
Recommended Settings
Recommended MPEG-2 Settings in CBR
Assuming the following settings:
Level = Main
Output Frame Structure = Progressive for 720p, Interlaced for all 1080i, 576i, 480i
I Period = 24, P Period = 3 (25 fps) I Period = 30, P Period = 3 (30 fps) I Period = 48, P Period = 3 (50 fps) I Period = 60, P Period = 3 (60 fps)
Adaptive GOP = true
Coder delay = standard
All / Complex Contents
Table 3-10. Recommended MPEG-2 video bitrate in CBR - All or Complex contents
Channel sensitive Quality sensitive Resolution (Mbit/s) (Mbit/s)
1920x1080i - 10.8 14 25/29.97/30
1440x1080i - 9.2 12 25/29.97/30
1280x720p - 9.2 12 25/29.97/30
720x576i - 25 4.0 4.6
544x576i - 25 3.1 3.8
720x480i - 29.97/30 3.5 4.2
544x480i - 29.97/30 2.9 3.3
392 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
Simple / Movie Contents
Table 3-11. Recommended MPEG-2 video bitrate in CBR - Simple or Movie contents
Channel sensitive Quality sensitive Resolution (Mbit/s) (Mbit/s)
1920x1080i - 9.2 12 25/29.97/30
1440x1080i - 7. 8 1 0 25/29.97/30
1280x720p - 7. 8 1 0 25/29.97/30
720x576i - 25 3.4 3.9
544x576i - 25 2.6 3.2
720x480i - 29.97/30 3.0 3.6
544x480i - 29.97/30 2.4 2.8
Electra VS - Version 05.10 393 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
Recommended MPEG-2 Settings in VBR (Statmux)
Assuming the following settings:
Profile = Main, Level = Auto
Output Frame Structure = Progressive for 720p, Interlaced for all 1080i, 576i, 480i
I Period = 24, P Period = 3 (25 fps) I Period = 30, P Period = 3 (30 fps) I Period = 48, P Period = 3 (50 fps) I Period = 60, P Period = 3 (60 fps)
Adaptive GOP = true
Coder delay = long
Table 3-12. Recommended MPEG-2 video bitrate in VBR (Statmux)
Resolution Min (Mbit/s) Max (Mbit/s) Quality
1920x1080i@25/29 2.63 40 70 .97/30
1280x720p@25/29. 1.67 40 70 97/30
720x576i@25 0.48 15 70
[email protected]/3 0.49 15 70 0
Recommended H.264 Settings in CBR
Assuming the following settings:
Profile = Main or High, Level = Auto
Output Frame Structure = Progressive for 720p, Interlaced for all 1080i, 576i, 480i
Mode = Premium
I Period = 24, P Period = 8 (25 fps) I Period = 32, P Period = 8 (30 fps) I Period = 48, P Period = 8 (50 fps) I Period = 64, P Period = 8 (60 fps)
Hierarchical GOP = true
Adaptive GOP = true
Close GOP Period = 0
Coder delay = standard
Decoder delay = 1000 ms
394 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
Deblocking = medium
Psycho-visual enhancement (PVE) = On (for best video quality)
All / Complex Contents
Table 3-13. Recommended H.264 video bitrate in IPTV - All or Complex contents
Channel sensitive Quality sensitive Pristine quality Resolution (Mbit/s) (Mbit/s) (Mbit/s)
1920x1080i@25/ 4.9 6.4 7.9 30 fps
1440x1080i@25/ 4.2 5.6 6.8 30 fps
1280x720p@50/6 4.2 5.5 6.7 0 fps
720x576i@25 fps 1.8 2.1 2.4
544x576i@25 fps 1.4 1.7 1.9
720x480i@30 fps 1.6 1.9 2.1
544x480i@30fps 1.3 1.5 1.7
Simple / Movie Contents
Table 3-14. Recommended H.264 video bitrate in IPTV - Simple or Movie contents
Channel sensitive Quality sensitive Pristine quality Resolution (Mbit/s) (Mbit/s) (Mbit/s)
1920x1080i@25/ 2.8 3.5 4.4 30 fps
1440x1080i@25/ 2.4 3 3.6 30 fps
1280x720p@50/6 2.3 2.9 3.6 0 fps
720x576i@25 fps 1.2 1.4 1.6
544x576i@25 fps 0.9 1.1 1.3
720x480i@30 fps 1.1 1.3 1.4
544x480i@30 fps 0.9 1 1.2
Electra VS - Version 05.10 395 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
Recommended H.264 Settings in VBR (Statmux)
Assuming the following settings:
Profile = Main or High, Level = Auto
Frame Structure = Progressive for 720p, Interlaced for all 1080i, 576i, 480i
Mode = Premium density
I Period = 24, P Period = 8 (25 fps) I Period = 32, P Period = 8 (30 fps) I Period = 48, P Period = 8 (50 fps) I Period = 64, P Period = 8 (60 fps)
Hierarchical GOP = true
Adaptive GOP = true
Close GOP Period = 0
Deblocking = medium
Psycho-visual enhancement (PVE) = On (for best video quality)
Table 3-15. Recommended H.264 video bitrate in VBR (Statmux)
Default (Mbit/s) Resolution Min (Mbit/s) Max (Mbit/s) /Quality
1920x1080i@25/3 1.11 6.0 / 70 12.0 0 fps
1280x720p@50/6 0.95 4.0 / 70 8.0 0 fps
720x576i@25 fps 0.40 2.0 / 70 6.0
720x480i@30 fps 0.41 2.0 / 70 6.0
396 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
Recommended H.264 Settings in WEBTV
Assuming the following settings:
Profile = Baseline, Main or High, Level = Auto
Output Frame Structure = Progressive
I Period = 24, P Period = 8 (25 fps) , I Period = 32, P Period = 8 (30 fps)
I Period = 24, P Period = 8 (25 fps) I Period = 32, P Period = 8 (30 fps) I Period = 48, P Period = 8 (50 fps) I Period = 64, P Period = 8 (60 fps)
Hierarchical GOP = true
Adaptive GOP = true
Close GOP Period = 0
Coder delay = standard
Decoder delay = 2000 ms
Deblocking = medium
Psycho-visual enhancement (PVE) = On (for best video quality)
If Mode = High density then increase bitrate in the tables below by 20%
If Profile = Baseline then increase bitrate in the tables below by 10%
Electra VS - Version 05.10 397 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
All / Complex Contents
Table 3-16. Recommended H.264 video bitrate in WebTV - All or Complex contents
Resolution - Channel sensitive Quality sensitive Pristine quality Frame rates (Mbit/s) (Mbit/s) (Mbit/s)
1920x1080p@25/3 4.3 4.9 5.9 0 fps
1280x720p@25/30 2.8 3.5 4.4 fps
960x540p@25/30 2.1 2.4 2.9 fps
704x528p@25/30 1.6 1.8 2.2 fps
704x396p@25/30 1.2 1.4 1.7 fps
640x480p@25/30 1.3 1.6 1.9 fps
640x360p@25/30 1.0 1.2 1.5 fps
480x320p@25/30 0.80 0.93 1.1 fps
480x270p@25/30 0.72 0.86 1.0 fps
400x300p@25/30 0.70 0.83 0.98 fps
400x224p@25/30 0.58 0.72 0.83 fps
320x240p@25/30 0.53 0.66 0.77 fps
320x180p@25/30 0.47 0.60 0.68 fps
398 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
Simple / Movie Contents
Table 3-17. Recommended H.264 video bitrate in WebTV - Simple or Movie contents
Resolution - Channel sensitive Quality sensitive Pristine quality Frame rates (Mbit/s) (Mbit/s) (Mbit/s)
1920x1080p@25/ 2.5 3.1 3.9 30 fps
1280x720p@25/3 1.7 2.1 2.5 0 fps
960x540p@25/30 1.2 1.5 1.9 fps
704x528p@25/30 0.91 1.1 1.4 fps
704x396p@25/30 0.74 0.90 1.1 fps
640x480p@25/30 0.79 0.96 1.2 fps
640x360p@25/30 0.65 0.80 0.95 fps
480x320p@25/30 0.48 0.59 0.69 fps
480x270p@25/30 0.42 0.53 0.62 fps
400x300p@25/30 0.40 0.50 0.59 fps
400x224p@25/30 0.33 0.41 0.50 fps
320x240p@25/30 0.30 0.37 0.46 fps
320x180p@25/30 0.26 0.33 0.41 fps
Electra VS - Version 05.10 399 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
Recommended H.265 Settings in CBR
Assuming the following settings:
Profile = Main or Main-10, Level = Auto
Output Frame Structure = Progressive for 720p, Interlaced for all 1080i, 576i, 480i
Mode = Premium density
I Period = 24, P Period = 8 (25 fps) I Period = 32, P Period = 8 (30 fps) I Period = 48, P Period = 8 (50 fps) I Period = 64, P Period = 8 (60 fps)
Hierarchical GOP = true
Adaptive GOP = true
Close GOP Period = 0
Coder delay = standard
Decoder delay = 1000 ms
Deblocking = medium
Psycho-visual enhancement (PVE) = On (for best video quality)
All / Complex Contents
Table 3-18. Recommended H.265 video bitrate in IPTV - All or Complex contents
Channel sensitive Quality sensitive Pristine quality Resolution (Mbit/s) (Mbit/s) (Mbit/s)
1920x1080i@25/ 45.26.4 30 fps
1440x1080i@25/ 3.4 4.5 5.5 30 fps
1280x720p@50/6 3.4 4.4 5.4 0 fps
720x576i@25 fps 1.5 1.7 2
544x576i@25 fps 1.2 1.4 1.6
720x480i@30 fps 1.3 1.6 1.7
544x480i@30fps 1.1 1.22 1.4
400 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
Simple / Movie Contents
Table 3-19. Recommended H.265 video bitrate in IPTV - Simple or Movie contents
Channel sensitive Quality sensitive Pristine quality Resolution (Mbit/s) (Mbit/s) (Mbit/s)
1920x1080i@25/ 2.3 2.8 3.6 30 fps
1440x1080i@25/ 22.42.9 30 fps
1280x720p@50/6 1.9 2.4 2.9 0 fps
720x576i@25 fps 11.21.3
544x576i@25 fps 0.8 0.9 1.1
720x480i@30 fps 0.9 1.1 1.2
544x480i@30 fps 0.8 0.8 1
Electra VS - Version 05.10 401 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
Recommended H.265 Settings in VBR (Statmux)
Assuming the following settings:
Profile = Main or Main-10, Level = Auto
Frame Structure = Progressive for 720p, Interlaced for all 1080i, 576i, 480i
Mode = Premium density
I Period = 24, P Period = 8 (25 fps) I Period = 32, P Period = 8 (30 fps) I Period = 48, P Period = 8 (50 fps) I Period = 64, P Period = 8 (60 fps)
Hierarchical GOP = true
Adaptive GOP = true
Close GOP Period = 0
Coder delay = long
Decoder delay = 1000 ms
Deblocking = medium
Psycho-visual enhancement (PVE) = On (for best video quality)
Table 3-20. Recommended H.265 video bitrate in VBR (Statmux)
Default (Mbit/s) Resolution Min (Mbit/s) Max (Mbit/s) /Quality
1920x1080i@25/3 0.91 6.0 / 70 12.0 0 fps
1280x720p@50/6 0.79 4.0 / 70 8.0 0 fps
720x576i@25 fps 0.33 2.0 / 70 6.0
720x480i@30 fps 0.35 2.0 / 70 6.0
402 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
Recommended H.265 Settings in WEBTV
Assuming the following settings:
Profile = Baseline, Main or Main-10, Level = Auto
Output Frame Structure = Progressive
Mode = Premium density
I Period = 24, P Period = 8 (25 fps) , I Period = 32, P Period = 8 (30 fps)
I Period = 24, P Period = 8 (25 fps) I Period = 32, P Period = 8 (30 fps) I Period = 48, P Period = 8 (50 fps) I Period = 64, P Period = 8 (60 fps)
Hierarchical GOP = true
Adaptive GOP = true
Close GOP Period = 0
Coder delay = standard
Decoder delay = 2000 ms
Deblocking = medium
Psycho-visual enhancement (PVE) = On (for best video quality)
Electra VS - Version 05.10 403 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
All / Complex Contents
Table 3-21. Recommended H.265 video bitrate in WebTV - All or Complex contents
Resolution - Channel sensitive Quality sensitive Pristine quality Frame rates (Mbit/s) (Mbit/s) (Mbit/s)
1920x1080p@25/3 3.544.8 0 fps
1280x720p@25/30 2.3 2.8 3.6 fps
960x540p@25/30 1.7 2 2.4 fps
704x528p@25/30 1.3 1.5 1.8 fps
704x396p@25/30 11.21.4 fps
640x480p@25/30 1.1 1.3 1.6 fps
640x360p@25/30 0.8 1 1.2 fps
480x320p@25/30 0.7 0.8 0.9 fps
480x270p@25/30 0.6 0.7 0.8 fps
400x300p@25/30 0.6 0.7 0.8 fps
400x224p@25/30 0.5 0.6 0.7 fps
320x240p@25/30 0.5 0.6 0.7 fps
320x180p@25/30 0.4 0.5 0.6 fps
Simple / Movie Contents
Table 3-22. Recommended H.265 video bitrate in WebTV - Simple or Movie contents
Resolution - Channel sensitive Quality sensitive Pristine quality Frame rates (Mbit/s) (Mbit/s) (Mbit/s)
1920x1080p@25/ 22.53.2 30 fps
404 Electra VS - Version 05.10 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
Table 3-22. Recommended H.265 video bitrate in WebTV - Simple or Movie contents
Resolution - Channel sensitive Quality sensitive Pristine quality Frame rates (Mbit/s) (Mbit/s) (Mbit/s)
1280x720p@25/3 1.4 1.7 2 0 fps
960x540p@25/30 11.21.6 fps
704x528p@25/30 0.8 0.9 1.2 fps
704x396p@25/30 0.6 0.8 0.9 fps
640x480p@25/30 0.7 0.8 1 fps
640x360p@25/30 0.6 0.7 0.8 fps
480x320p@25/30 0.4 0.5 0.6 fps
480x270p@25/30 0.4 0.5 0.5 fps
400x300p@25/30 0.4 0.4 0.5 fps
400x224p@25/30 0.3 0.4 0.4 fps
320x240p@25/30 0.3 0.3 0.4 fps
320x180p@25/30 0.3 0.3 0.4 fps
Electra VS - Version 05.10 405 User Manual - Rev. A Chapter 3 ’Web User Graphical Interface’ — Recommended Settings
Recommended H.265 Settings in Live UHD
Assuming the following settings:
I Period and P Period = 48 (2160p50) I Period can be reduced to 32 or 24 to reduce zapping time.
P Period = 8
GOP Type = IB
Adaptive GOP = true
Temporal Scalability = false
Close GOP Period = 0
Deblocking = true
Decoder delay = 1000
For Simple/Movie Contents (2160p50/60): 10 to 16 Mbit/s
For All/Complex Contents (2160p50/60): 18 to 27 Mbit/s
406 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 Servicing
In this Chapter
’Common’ ...... page 408
’Hardware Delivery’ ...... page 413
’Software Only Delivery’ ...... page 439
’Virtualization Delivery’ ...... page 444
Electra VS - Version 05.10 407 User Manual - Rev. A Chapter 4 ’Servicing’ — Common
Common
Managing the Recovery Points
Overview
A recovery point is a file which contains all the components required to the recover the status of the system at a specific time:
Software version (including OS)
License file
Setup configuration
List of workflows
List of jobs
Logs
Database
Periodic recovery points are automatically performed and purged.
You can store up to ten manual recovery points. They will not be removed automatically.
Recovery Points Management
In the GUI, click Download on the Setup page. The Recovery Point tab is displayed:
Figure 4-1. Recovery Points tab
The Recovery Points table lists the recovery points on your Electra VS and their main characteristics.
The table contains the following processing components:
Recovery Points: name of the recovery point file. This name is automatically set when creating the recovery point.
Type:
Factory: the recovery point has been generated in the factory and can not be erased.
408 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Common
Periodic: the recovery point has been generated automatically. A recovery point is generated daily at 12:00 (UTC). These recovery points are automatically erased. The only ones kept are those from: - The 1st Sunday of the last 3 months - The last 3 Sundays - The last 3 days
Manual: the recovery point has been generated manually. The maximum number allowed is 10. They are not purged automatically.
Date: recovery point date creation.
Version: software version associated with the recovery point.
Status:
: the recovery point is available on all nodes and can be restored.
: the recovery point creation is «in progress».
: the recovery point creation failed in at least one node. A recovery point in error can be restored if it is copied at least on the two masterisable nodes.
Unavailable Nodes: the list of nodes in which the recovery point has not been created.
In progress Nodes: the list of nodes in which the recovery point is on-going.
Add, Delete or Restore a Recovery Point
Figure 4-2. Recovery Point management
To add a Manual recovery point click New. Up to 10 Manual recovery points can be stored in the device.
To delete a recovery point select it and click Delete.
To restore a recovery point select it, click Restore and confirm.
The creation of a recovery point (manual or periodic) has no effect on the operation of the system: the jobs are not disturbed. Restoring a recovery point interrupts the processing of jobs, and involves a reboot of the system. If you add new nodes in the system, restoring an old recovery point will remove the new nodes from the system as the old license file will be restored.
Electra VS - Version 05.10 409 User Manual - Rev. A Chapter 4 ’Servicing’ — Common
Upgrading the Software Release
To upgrade the software: 1. Read carefully chapter 6 "Interoperability & Limitations" of the Release Note of the new version you want to install. 2. Go to the Setup tab and choose the Download category. 3. Refer to section ’Setup/Download’ on page 180.
When you apply a new software version, a smooth upgrade mechanism applies, for each job: 1. The job is created in the new version, in mute mode. 2. Once the job is properly running, it is unmuted and the job in the old version is muted. 3. The job in the old version is deleted.
The smooth upgrade mechanism is not available for jobs that use a virtual IP address, for instance TS over IP unicast inputs or Web TV outputs when the stream is available on the local Web server. Those jobs are stopped and recreated in the version. Note that TS over IP outputs do not use a virtual IP address, and thus the smooth upgrade can be used.
The smooth upgrade can be used only if the system CPU and memory resources are sufficient to duplicate the jobs. Otherwise, jobs are stopped and recreated in the new version.
410 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Common
Requesting a new license File
A new license file has to be generated by Harmonic in the following cases:
You want to add processing licenses to your Electra VS.
You want to add a new slave node in your Electra VS and you have reach the maximum number of nodes allowed by the license (ELC-VS-SW-VOSFLEX).
You have replaced the hardware platform of one of your two masterisable nodes.
The licensing mechanism has change since Electra VS V04.00.00 version. It is now possible to purchase licenses for slave nodes that will be added later in the Electra VS (ELC-VS-SW-VOSFLEX). It is not anymore mandatory to generate a new license file each time a slave node is added or each time a slave hardware platform is changed. However if your license has been generated before V04.00.00 version you may have to request a new license file the first time you perform a node addition.
Harmonic may needs technical information on your Electra VS to be able to answer your request. To facilitate this, the GUI lets you generate a file that contains all the information that Harmonic needs to identify your Electra VS and to generate a new license file for you, proceed as follows: 1. In the GUI, point to the Hardware tab and click the Nodes category. 2. Click New license request.
Figure 4-3. Export license request dialog
Electra VS - Version 05.10 411 User Manual - Rev. A Chapter 4 ’Servicing’ — Common
3. Enter a name for the resulting file (without the extension) and validate. 4. Send this file to your Harmonic sales representative with your request.
Declaring a new License File
Once you have received your new license file, proceed as follows: 1. In the GUI, point to the Download tab. 2. On the upper-right corner, click Download new license.
Figure 4-4. Downloading a new license file
3. Select the new license file that Harmonic sent to you and click Open. Enter *.LIC in the file name in order to see the list of license files.
If you have requested additional processing licenses: Check that the licenses have correctly been updated in the license tab.
If you have added or replaced masterisable nodes or increased the number of slave nodes: Check that the number of nodes accepted in the Electra VS has been updated (ELC-VS-SW-VOSFLEX) in the license tab.
412 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Hardware Delivery
Managing the Recovery Points
Refer to section ’Managing the Recovery Points’ on page 408.
Upgrading the Software Release
Refer to section ’Upgrading the Software Release’ on page 410.
Requesting a New License File
Refer to section ’Requesting a new license File’ on page 411.
Declaring a New License File
Refer to section ’Declaring a new License File’ on page 412.
Unmounting the Front Panel on a 1RU Server
To add or replace a disk or access the slide-out display, you need to remove the front panel. To do so, proceed as follows: 1. Pull the left side of the front panel to unlock it.
Figure 4-5. Unmounting the front panel – Pull the left side of the front panel
1
Electra VS - Version 05.10 413 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
2. Disengage the right side of the front panel from the notches of the server. 3. Remove the front panel.
Figure 4-6. Unmounting the front panel – Disengaging the left side
2
3
414 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Adding a Diskless Node to Electra VS
If you want to expand your system by adding diskless nodes, you first need to purchase the physical nodes and rack them. You then need to enable, configure and finally declare them in the system. This section explains how to perform these operations for the 1RU, 6RU, and 10RU systems. Install the new blades in the blade center or the 1RU device in the rack as explained in the ’Installation and Startup’ chapter. In the case of a 1RU device, connect it like the other devices in the system.
Enabling the New Diskless Node (6RU and 10RU)
Once you have racked a new node, you need to enable it. To do so, follow the procedures below.
Connecting to the ILO Interface 1. Launch Internet Explorer 2. Enter the IP address of the ILO interface of the blade center. For more information, see section ’Connecting to the HP Monitoring Tools’ on page 473. 3. Enter the user name and the password indicated on the asset tag.
Figure 4-7. Connection to the ILO interface
The HP OnBoard Administrator interface is displayed.
Electra VS - Version 05.10 415 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Enabling the Node 1. In the HP OnBoard Administrator page, point to Enclosure Information, Enclosure Settings and select Enclosure Bay IP Addressing. 2. Select the new node you have just racked and check the box in the Enabled column.
Figure 4-8. Enabling the new diskless node
Configuring the BIOS of a Diskless Node
Once the new node is enabled, follow the procedures below to configure it.
For a 6RU or 10RU blade: Accessing the BIOS
In the HP BladeSystem Onboard Administrator, click the Rack Overview link in the tree on the left.
416 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Figure 4-9. HP OnBoard Administrator interface
1. Click the Front View. 2. Select a node.
Figure 4-10. Selecting a node from the HP OA interface
Electra VS - Version 05.10 417 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Setting the Boot Options of the Blade 1. Still from the OnBoard Administrator interface Front View, select the Boot Options tab.
Figure 4-11. Accessing the Boot options
2. From the One Time Boot from drop-down list, choose RBSU (ROM-Based setup utility). This option lets the server reboot directly on the BIOS parameters without any particular action.
Figure 4-12. Setting the boot option
3. Apply the change. 4. Select the Virtual Devices tab.
Figure 4-13. Selecting the Virtual Devices tab
418 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
5. Click the Cold Boot button.
Figure 4-14. Clicking the Cold Boot button
The blade center boots on the BIOS parameters.
Accessing the System KVM 1. Select the Status tab.
Figure 4-15. Accessing the Status
2. Choose ILO.
Figure 4-16. Selecting the ILO
Electra VS - Version 05.10 419 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
3. Click Integrated Remote Console.
Figure 4-17. Accessing the Integrated Remote Console
4. Run the application.
For the ILO3 firmware version 1.20, the framework .net 3.5 must be installed on the machine on which Internet Explorer is launched. If the PC has an Internet connection, the installation is automatically suggested. This installation is only necessary the first time the PC is used, for integration.
420 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
For 1RU Devices: Accessing the BIOS 1. Connect a mouse and screen to your Electra VS device. 2. Start the device and launch the BIOS configuration.
Setting the BIOS Parameters
Figure 4-18. BIOS parameters
In the BIOS parameters, use the following commands:
To move, use the up and down arrows. To go back to the previous screen, press Esc. To validate, press Enter.
Electra VS - Version 05.10 421 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Enabling the Network Boot Support on NIC 2 (Blade Centers Only) 1. From the main menu of the BIOS, choose System Options.
Figure 4-19. Accessing the system options
2. Select Embedded NICs.
Figure 4-20. Selecting the embedded NICs
422 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
3. Select NIC 2 Boot Options.
Figure 4-21. Accessing the NIC boot options
A warning message is displayed.
Figure 4-22. Warning message when setting the NIC boot options
4. Press Enter to continue. 5. Choose Network Boot.
Figure 4-23. Enabling the network boot
Electra VS - Version 05.10 423 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Modifying the HP Power Profile 1. Go back to the main menu of the BIOS.
2. Select Power Manager Options and press Enter twice. 3. Select Maximum Performance.
Figure 4-24. Selecting the HP power profile
4. Press Enter to apply the change.
Setting the Advanced Power Management Options 1. Select Advanced Power Management Options.
On G7 blades and servers: 2. Select the Memory Interleaving submenu. 3. Choose the Full Interleaving option.
Figure 4-25. Setting the memory interleaving on G7 blades and servers
424 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
On G8 blades and servers: 2. Select the Channel Interleaving submenu. 3. Choose the Enabled option.
Figure 4-26. Setting the memory interleaving on G8 blades and servers
Setting the Advanced Performance Tuning Options 1. Go back to the main menu. 2. Select Advanced Options. 3. Select Advanced Performance Tuning Mode.
Figure 4-27. Accessing the advanced performance tuning options
Electra VS - Version 05.10 425 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
4. Press Enter. 5. Select Node Interleaving.
Figure 4-28. Setting the node interleaving
6. Press Enter to access the parameters. A warning message is displayed.
Figure 4-29. Warning message when setting the node interleaving
7. Press Enter to continue. 8. Select Enabled.
Figure 4-30. Enabling the node interleaving
426 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Rebooting the Node 1. Go back to the main menu of the BIOS.
2. Press Esc several times until reaching the menu shown in Figure 4-31.
Figure 4-31. Exiting the BIOS menu
3. Press F10 to reboot the node with the new BIOS parameters.
Requesting a New License File
Refer to section ’Requesting a new license File’ on page 411.
Declaring a New License File
Refer to section ’Declaring a new License File’ on page 412.
Adding a 1RU Diskless Node to Electra VS
If you want to expand your system by adding an additional server, you first need to purchase the physical diskless nodes. 1. Plug them in the same way as the other system nodes. 2. Check that your license allow the addition of new node a. In the GUI, point to the Download tab.
b. In the license table check that you have the right to add new nodes. The quantity used of ELC-VS-SW-VOSFLEX shall be lower than the quantity maximum allowed.
c. If it is not the case ask additional license to Harmonic. Refer to section ’Requesting a new license File’ on page 411. and section ’Declaring a new License File’ on page 412.
Electra VS - Version 05.10 427 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
3. Add the node in the Electra VS a. Point to the Hardware tab and click the Nodes category.
b. Click Add Nodes
The new node shall be detected and proposed to be added in Electra VS.
If it is not the case check that your node is correctly plugged in the System Private LAN
c. Click Next
4. The node shall be automatically added in your Electra VS. If it is not the case check your license right (refer to section ’Requesting a new license File’ on page 411).
428 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Replacing a Hot Swappable Part
6RU and 10RU Server
The hot swappable parts are listed below.
Table 4-1. 6RU/10RU - Hot swappable parts
Code Description
ELC-VS-OPT-6U-BLA-PRO Hot-swappable processing blade for Electra VS 6RU platform.
ELC-VS-OPT-10U-BLA-PRO Hot-swappable processing blade for Electra VS 10RU platform.
ELC-VS-OPT-6U-AC Hot-swappable AC power supply unit for Electra VS 6RU platform.
ELC-VS-OPT-6U-DC Hot-swappable DC power supply unit for Electra VS 6RU platform.
ELC-VS-OPT-10U-AC Hot-swappable AC power supply unit for Electra VS 10RU platform. Fits all single phase and triple phase platforms.
ELC-VS-OPT-10U-DC Hot-swappable DC power supply unit for Electra VS 10RU platform. Fits 48V DC platform only.
ELC-VS-OPT-6U-FAN Hot-swappable fan unit for Electra VS 6RU platform.
ELC-VS-OPT-6U-MNG Hot-swappable chassis manager board for Electra VS 6RU platform.
ELC-VS-OPT-10U-FAN Hot-swappable fan unit for Electra VS 10RU platform.
ELC-VS-OPT-10U-MNG Hot-swappable chassis manager board for Electra VS 10RU platform.
ELC-VS-OPT-10GIGE-SWI Hot-swappable 10GigE internal IP switch for Electra VS 6RU and 10RU platforms.
ELC-VS-OPT-HDD Hot-swappable hard-disk drive for Electra VS 1RU, 6RU and 10RU platforms.
To diagnose or confirm part failure and prepare on-site hardware service provider maintenance, you may be requested to provide the following information:
Active Health System log
In the HP OnBoard Administrator page, point to Enclosure Information, Active On Board Administrator, System log.
Save the logs from before the failure was detected to a text file.
Onboard Administrator SHOW ALL report
In the HP OnBoard Administrator page, point to Enclosure Information, Enclosure Settings, Click the SHOW ALL link.
Save the configuration to a text file.
Product serial number.
Electra VS - Version 05.10 429 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Product model name and number.
Product identification number.
Add-on boards or hardware.
Third-party hardware or software.
In the HP OnBoard Administrator page, point to Enclosure Information and select the Information tab. Save a screen shot of the Part Information table.
Figure 4-32. HP OnBoard Administrator page – Part Information table
In the HP OnBoard Administrator page, point to Enclosure Information and select Component Firmware. Save a screen shot of the Firmware Information table.
Figure 4-33. HP OnBoard Administrator page – Firmware Information table
430 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
In the HP OnBoard Administrator page, point to Enclosure Information and select Device Bay. Save a screen shot of the Device Bay status view.
Figure 4-34. HP OnBoard Administrator page – Device bay status
Applicable error messages (IML)
In the HP OnBoard Administrator page, point to Enclosure Information, Device Bay and select the erroneous blade if any. Save the log to a text file.
Operating system type and revision level. The information will be provided by Harmonic.
1RU Server
The hot swappable parts are listed below.
Table 4-2. 1RU - Hot swappable parts
Code Description
ELC-VS-OPT-1U-AC Hot-swappable power supply unit for Electra VS 1RU platform.
To diagnose or confirm part failure and prepare on-site hardware service provider maintenance, you may be requested to provide the following information:
System Information / Health Summary
Connect to the server HP iLO page as follows: 1. Plug an Ethernet cable on the active iLO port on the rear panel and connect it to your Ethernet network.
Electra VS - Version 05.10 431 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
2. On a remote computer, type the DNS name in the address bar of a Web browser. 3. Enter the user name and password indicated on the asset tag. You are now connected to the HP configuration interface.
In the HP iLO page, point to Information, System information. Save a screen shot of the subsystems and device status. Save a screen shot of the failed subsystems by selecting the corresponding tab.
Technical support registration number (if applicable).
Product serial number.
Product model name and number.
Product identification number.
In the HP iLO page, point to Information, Overview. Save a screen shot of the iLO overview.
Figure 4-35. HP iLO page – iLO overview
The serial number and product ID information are also available on the slide out information stick on the platform front panel.
Applicable error messages (IML)
In the HP iLO page, point to Integrated Management Log. Save the log to a text file.
Add-on boards or hardware.
Third-party hardware or software.
Operating system type and revision level. The information will be provided by Harmonic.
432 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Replacing a Diskless Node in Electra VS
To replace a diskless node, you need to configure the BIOS of the new node. After that, the process is basically the same as for declaring a new node.
Contact your Harmonic sales representative to buy a new node.
Configuring the BIOS of the New Node
The process is exactly the same as when adding a new diskless node. Follow all steps of the procedure described in section ’Configuring the BIOS of a Diskless Node’ on page 416.
Replacing a Node
To replace a node, proceed as follows: 1. Put the node in maintenance Select the node and click Maintenance.
Figure 4-36. Set the node in maintenance mode
2. Confirm the operation
Figure 4-37. Set in maintenance mode confirmation
3. Remove the node from Electra VS Select the node and click Remove.
Electra VS - Version 05.10 433 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Figure 4-38. Remove node
4. Remove physically the node
For a 1RU server: switch off the front panel and power the device off.
For a blade server: remove the blade (no specific precautions to take). 5. Insert the new node at the old one’s location
For a 1RU server: cable the device and start it using the front panel.
For a blade server: insert the new blade and start it using the front panel. 6. Add the new node to Electra VS
Click Add nodes.
Figure 4-39. Add nodes
The new node is displayed.
Check Add, enter the node id and click Next.
434 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Figure 4-40. Add node and Node id
The new node is added.
Figure 4-41. Node added
Electra VS - Version 05.10 435 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Blade Center - Upgrading OnBoard Administrator firmware
To upgrade the version of your OnBoard Administrator software, follow the procedure below.
Connecting to the ILO Interface 1. Run Internet Explorer. 2. Enter the IP address of the blade center ILO interface. For more information, see section ’Connecting to the HP Monitoring Tools’ on page 473. 3. Enter the user name and password indicated on the asset tag.
The HP OnBoard Administrator interface is displayed. 4. To upgrade the OA firmware, select Enclosure Settings, Active OnBoard Administrator, Upgrade setting view.
Figure 4-42. HP configuration interface – Firmware Update page
5. Check the current firmware version in the Firmware information table. 6. Select the new firmware and click upload.
Before performing any upgrade, read the Compatibilities section in the Electra VS-ReleaseNotes-vxx.xx.00-edx document on the DVD-ROM supplied with the equipment and check that there is no limitation on the type of firmware version supported with your version.
436 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
Blade Center - Upgrading Flex10 firmware
First, you may want to check the Flex10 firmware version. To do so, follow the procedure below.
Connecting to the ILO Interface 1. Run Internet Explorer. 2. Enter the IP address of the blade center ILO interface. For more information, see section ’Connecting to the HP Monitoring Tools’ on page 473. 3. Enter the user name and password indicated on the asset tag.
The HP OnBoard Administrator interface is displayed. 4. To upgrade the Flex10 firmware, select Enclosure Settings, Virtual Connect Manager view.
Figure 4-43. HP configuration interface – Virtual Connect Manager selection
The Virtual Connect Manager is opened. The firmware version is displayed.
Figure 4-44. HP configuration interface – Virtual Connect Manager page
To upgrade the Flex10 version, follow the procedure below.
Electra VS - Version 05.10 437 User Manual - Rev. A Chapter 4 ’Servicing’ — Hardware Delivery
1. Install the HP Virtual Connect Support Utility Set (VCSU) available on the DVD-ROM in the FLEX10 directory on your remote desktop. 2. Open a windows console. 3. Go to the VCSU directory Type cd C:\Program Files\Hewlett-Packard Company\Virtual Connect Support Utility 4. Type the following command: vcsu.exe -a update -i XXX.XXX.XXX.XXX -u Administrator -p pwdOA -vcu Administrator -vcp pwdFlex10 -l "C:\Integrati on-VS7000\vcfwall370.bin" XXX.XXX.XXX.XXX: Target OA IP address pwdOA: OA password pwdFlex10: Flex10 password C:\Integration-VS7000\vcfwall370.bin: path of the Flex10 firmware upgrade
5. Type Y to confirm the operation when requested. The upgrade may take up to 1 hour for the upgrade of the two Flex 10. 6. Check that all the modules have successfully been updated in the windows console and again perform a Flex10 firmware version check through the OA.
Upgrade trace example: ------ HP BladeSystem c-Class Virtual Connect Support Utility Version 1.5.2 (Build 173) Build Date: Jan 6 2011 11:26:43 Copyright (C) 2007-2010 Hewlett-Packard Development Company, L.P. All Rights Reserved ------The following modules will be updated: ======Enclosure Bay Module Current Version New Version ======CZ3126JYDP 1 HP VC Flex-10 3.18 3.30 Enet Module 2011-04-01T22:57:39Z 2011-08-16T02:29:46Z ------CZ3126JYDP 2 HP VC Flex-10 3.18 3.30 Enet Module 2011-04-01T22:57:39Z 2011-08-16T02:29:46Z ------
During the update process, modules being updated will be temporarily unavailable. In addition, the update process should NOT be interrupted by removing or resetting modules, or by closing the application. Interrupting the update or the modules being updated may cause the modules to not be updated properly. Please verify the above report before continuing. Would you like to continue with this update? [YES/NO]: YES The following modules were updated successfully: ======Enclosure Bay Module New Version ======CZ3126JYDP 1 HP VC Flex-10 Enet Module 3.51 2011-08-16T02:29:46Z CZ3126JYDP 2 HP VC Flex-10 Enet Module 3.51 2011-08-16T02:29:46Z
438 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Software Only Delivery
Software Only Delivery
Managing the Recovery Points
Refer to section ’Managing the Recovery Points’ on page 408.
Upgrading the Software Release
Refer to section ’Upgrading the Software Release’ on page 410.
Requesting a New License File
Refer to section ’Requesting a new license File’ on page 411.
Declaring a New License File
Refer to section ’Declaring a new License File’ on page 412.
Creating a Bootable USB Flash Drive
Refer to Chapter 2 ’Installation and Startup’, section ’Creating the Bootable USB Flash drive’ on page 58.
Installing the Version on the First Node (Master node)
Refer to Chapter 2 ’Installation and Startup’, section ’Installing the Version on the First Node (Master Node)’ on page 58.
Adding Masterisable Node to Electra VS
Refer to Chapter 2 ’Installation and Startup’, section ’Adding the Second Masterisable Node in Electra VS’ on page 65.
Adding Non Masterisable Node(s) to Electra VS
If you want to expand the Electra VS by adding an additional server, you first need to purchase the physical slave nodes. 1. Plug them in the same way as the other nodes.
You then need to declare them in Electra VS.
Electra VS - Version 05.10 439 User Manual - Rev. A Chapter 4 ’Servicing’ — Software Only Delivery
2. Check that your license allow the addition of a new node a. In the GUI, point to the Download tab.
b. In the license table check that you have the right to add new nodes, i.e. that all the ELC-VS-SW-VOSFLEX are not currently used.
c. If it is not the case ask additional license to Harmonic. Refer to section ’Requesting a new license File’ on page 411. and section ’Declaring a new License File’ on page 412. 3. Install the Electra VS software version in the node Install the version from a USB Flash drive on the new node. Refer to Chapter 2 ’Installation and Startup’, section ’Creating the Bootable USB Flash drive’ on page 58 and section ’Installing the Version on the First Node (Master node)’ on page 439. Reboot the node. 4. Add the node in Electra VS a. Go to the Nodes category.
b. Select Add Nodes.
440 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Software Only Delivery
The IP address of the new node in the management network will be processed according to the ip address of the first node + node id. For example: nodeId 1 - 198.18.70.30 nodeId 4 - 198.18.70.33 You can change the node id, the ip address will be change at the same time. If it is not the case: - retry several times, the detection may take several minutes. - check the interface configuration and the switch connection.
c. Click Next.
5. The node shall be automatically added in your system. 6. Configure the processing capacity of your node. Refer to Chapter 7 ’Tools’, section ’NodeBench’ on page 466. 7. Check the status of the node a. Select the Hardware tab. b. Go to the Nodes category.
c. Check that the status of the node is OK. 8. Finalize the network configuration of your node.
Electra VS - Version 05.10 441 User Manual - Rev. A Chapter 4 ’Servicing’ — Software Only Delivery
Replacing a Masterisable Node in Electra VS
If you want to replace one of your masterisable node, you first need to purchase a physical node with disk. This section explains how to perform these operations. 1. Shutdown the original master node. a. Check that you have another masterisable node You shall always have a master node in your Electra VS, if you want to replace one of the two master nodes be sure that the other one is operational. b. Put the node in maintenance mode. Refer to section ’Replacing a Diskless Node in Electra VS’ on page 433 step 1 and 2.
c. Shutdown the masterisable node If it is the master node, the second masterisable node shall become master. 2. Request a new license without the old masterisable node. There is only two masterisable nodes in a Electra VS. You must request to remove the old node from the system before adding the new one. Contact Harmonic to generate a new license file, don't forget to indicate the node Id of the node to remove from the license. Refer to section ’Requesting a new license File’ on page 411. 3. Apply the new license file and check that the old node has effectively been removed from the Electra VS. Refer to section ’Declaring a new License File’ on page 412. 4. You can now add your new masterisable node. a. Install the version from the USB Flash drive on a second node with disk (Refer to steep 1 to 6 in the section ’Installing the Version on the First Node (Master node)’ on page 439. b. Connect the physical interface of the new node as the old one node.
442 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Software Only Delivery
5. Add the node in Electra VS a. Select the Hardware tab.
b. Go to the Nodes category.
c. Select Add Nodes.
The node should be detected and displayed in the list.
d. Select it and click Next. The node is added to the Electra VS. 6. Contact Harmonic to generate a new license file with the new masterisable node. Refer to section ’Requesting a new license File’ on page 411. The new masterisable node will be selected between the slave nodes with disk declared in Electra VS. 7. Apply the new license file. Refer to section ’Declaring a new License File’ on page 412. Check that a node is now declared slave (can be master).
Electra VS - Version 05.10 443 User Manual - Rev. A Chapter 4 ’Servicing’ — Virtualization Delivery
Virtualization Delivery
Managing the Recovery Points
Refer to section ’Managing the Recovery Points’ on page 408.
Upgrading the Software Release
Refer to section ’Upgrading the Software Release’ on page 410.
Requesting a New License File
Refer to section ’Requesting a new license File’ on page 411.
Declaring a New License File
Refer to section ’Declaring a new License File’ on page 412.
Adding a Masterisable Node to Electra VS
Refer to Chapter 2 ’Installation and Startup’, section ’Adding the Second Masterisable Node in Electra VS’ on page 65.
444 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Virtualization Delivery
Adding a Slave Node to Electra VS
If you want to expand your Electra VS by adding an additional server, you first need to download the virtual machine on the node using the ESXI
Follow steps section ’Installing the First Node (Master Node)’ on page 69 to section ’Installing the OVA on the first Node (Master Node)’ on page 72 describe in the Chapter 2 ’Installation and Startup’.
You then need to declare it. 1. Check that your license allow the addition of a new node a. In the GUI, point to the Download tab.
b. In the license table check that you have the right to add new nodes. The quantity used of ELC-VS-SW-VOSFLEX shall be lower than the quantity maximum allowed.
c. If it is not the case Ask additional license to Harmonic. Refer to section ’Requesting a new license File’ on page 411 and section ’Declaring a new License File’ on page 412. 2. Add the node a. Go to the Nodes category.
b. Select Add Nodes. The new node shall be detected and proposed to be added in Electra VS. If it is not the case check the network mapping
c. Click Next. 3. The node shall be automatically added in your Electra VS. 4. Configure the processing capacity of your node. Refer to Chapter 7 ’Tools’, section ’NodeBench’ on page 466, 5. Check the status of the node a. Select the Hardware tab.
b. Go to the Nodes category.
c. Check that the status of the node is OK. 6. Finalize the network configuration of your node.
Electra VS - Version 05.10 445 User Manual - Rev. A Chapter 4 ’Servicing’ — Virtualization Delivery
Replacing a Masterisable Node in Electra VS
If you want to replace one of your masterisable node, you first need to purchase a physical node with disk. This section explains how to perform these operations. 1. Shutdown the original master node. a. Check that you have another masterisable node You shall always have a master node in your Electra VS, if you want to replace one of the two master nodes be sure that the other one is operational. b. Put the node in maintenance mode. Refer to section ’Replacing a Diskless Node in Electra VS’ on page 433 step 1 and 2.
c. Shutdown the masterisable node If it is the master node, the second masterisable node shall become master. 2. Request a new license without the old masterisable node. There is only two masterisable nodes in a Electra VS. You must request to remove the old node from the system before adding the new one. Contact Harmonic to generate a new license file, don't forget to indicate the node Id of the node to remove from the license. Refer to section ’Requesting a new license File’ on page 411. 3. Apply the new license file and check that the old node has effectively been removed from the Electra VS. Refer to section ’Declaring a new License File’ on page 412. 4. You can now add your new masterisable node. a. Refer section ’Adding the Second Node in Electra VS (Masterisable Node)’ on page 76.
b. Connect the physical interface of the new node as the old one node.
446 Electra VS - Version 05.10 User Manual - Rev. A Chapter 4 ’Servicing’ — Virtualization Delivery
5. Add the node in Electra VS a. Select the Hardware tab.
b. Go to the Nodes category.
c. Select Add Nodes.
The node should be detected and displayed in the list.
d. Select it and click Next. The node is added to the Electra VS. 6. Contact Harmonic to generate a new license file with the new masterisable node. Refer to section ’Requesting a new license File’ on page 411. The new masterisable node will be selected between the slave nodes with disk declared in Electra VS. 7. Apply the new license file. Refer to section ’Declaring a new License File’ on page 412. Check that a node is now declared slave (can be master).
Electra VS - Version 05.10 447 User Manual - Rev. A Chapter 4 ’Servicing’ — Virtualization Delivery
448 Electra VS - Version 05.10 User Manual - Rev. A Chapter 5 Troubleshooting
Introduction
If you face any problem with the equipment, follow the procedures described in this section.
In this Chapter
’Troubleshooting Procedures’ ...... page 450
’Frequently Asked Questions’ ...... page 453
Electra VS - Version 05.10 449 User Manual - Rev. A Chapter 5 ’Troubleshooting’ — Troubleshooting Procedures
Troubleshooting Procedures
Exporting Information for Customer Support
If you have problems with workflows or jobs, there is a simple way to export the information and send it to the customer support: 1. In the lower-right corner of the GUI, click Export. 2. Select the folder where you want to store the file and give it a name.
A zip file is created and contains the workflows configuration, the list of jobs as well as the system configuration. 3. Send the resulting zip file to the customer support for analysis, indicating the workflows or jobs that cause trouble.
The customer support might also need the following information:
Network topology: provide the diagram.
For a blade center:
Flex10 configuration: export the Flex10 configuration as follows: a. Open an SSH connection with the active Flex10 module, for example using Putty. b. Enter your login and password.
c. Type the following command: show config The whole configuration is displayed. d. Save the configuration to a text file.
e. Send the file to the support team.
Enclosure information: to get this information, proceed as follows: a. From the HP OA interface, choose Enclosure Settings.
b. Select Configuration scripts.
c. Click the SHOW ALL link.
d. Save the configuration to a text file.
e. Send the file to the support team.
450 Electra VS - Version 05.10 User Manual - Rev. A Chapter 5 ’Troubleshooting’ — Troubleshooting Procedures
Modifying a Workflow from a Text Editor
If needed, you may perform some changes in the code, and then import them back in the GUI to apply your changes. To do so: 1. Follow the steps described above to export the workflows configuration to a zip file. 2. Find the XML file corresponding to the workflow you wish to modify and extract it from the zip. 3. Open the XML file in a text editor. 4. Perform your changes. 5. Re-include the XML file of the workflow in the original ZIP file. 6. In the lower-right corner of the GUI, click Import and select the ZIP file.
The modified workflow is now available in the list of workflows.
Exporting Logs
To export logs, proceed as follows: 1. From the GUI, open the Setup tab. 2. Select the Logs category. 3. From the Export area, click the Export now button to export the logs immediately.
A text file is generated with all the logs stored in the database.
For more information on the export feature, refer to section ’Export’ on page 181.
Using the Console
The Console tab is available only if you are logged with an administrator account. To display / hide the Console tab press CTRL+D keys. The Console tab is described in section ’Console Tab’ on page 227.
This tab should be used only under the customer support’s supervision. If needed, the customer support team will indicate the commands to send.
Electra VS - Version 05.10 451 User Manual - Rev. A Chapter 5 ’Troubleshooting’ — Troubleshooting Procedures
Providing Remote Access to the Electra VS
The remote access must accept remote access of SSH type and Web type, for example via a VPN.
452 Electra VS - Version 05.10 User Manual - Rev. A Chapter 5 ’Troubleshooting’ — Frequently Asked Questions
Frequently Asked Questions
Why cannot I instantiate my job whereas there is space on the Electra VS?
Perform the following verifications:
Check the coherence messages: there might be an explanation why you cannot instantiate the job.
Check that there is no license restriction. You may have reached the maximum number of jobs you are authorized to instantiate.
Check that the job is properly configured. If in a TS audio video extractor item you have set an HD 1080i video when the source is actually an SD video, the system will nevertheless allocate resources for an HD video. The system will this be underused.
Check that there is no Ethernet "link down" alarms. Indeed, if the job is using a LAN for which the interface is disconnected, then the job will not be instantiated.
I do not see my workflow in the list when I want to create a job. Why?
Your workflow is probably non-instantiable. This might be because the workflow contains no source. For instance, an encoding workflow in which the input is not linked is not instantiable.
I cannot create a workflow. Why?
This is probably because you are not authorized to do so. If you have an administrator account, you can modify the user account settings (refer to section ’Setup/User Accounts’ on page 178). Otherwise, contact your administrator.
I cannot create a job. Why?
This is probably because you are not authorized to do so. If you have an administrator account, you can modify the user account settings (refer to section ’Setup/User Accounts’ on page 178). Otherwise, contact your administrator.
Electra VS - Version 05.10 453 User Manual - Rev. A Chapter 5 ’Troubleshooting’ — Frequently Asked Questions
When I want to launch a job, I get a "Job is waiting: license not available" message. What should I do?
The "Job is waiting: license not available" message indicates that you are already using all the licenses you own for this feature. You can check this from the Setup tab, Download category by viewing the Quantity used / Quantity max values.
In this case, the job stays in Waiting state until a license becomes available.
I cannot modify the system parameters. Why?
This is probably because you are not authorized to do so. If you have an administrator account, you can modify the user account settings (refer to section ’Setup/User Accounts’ on page 178). Otherwise, contact your administrator.
I modified a workflow parameter, but it was not applied to the currently running jobs. Why?
When modifying the default value of a private parameter of a workflow, the value is applied for currently running jobs that are based on this workflow. However, modifying the default value of a public parameter does not affect running jobs based on this workflow. Indeed, the value that is used is the value specified when creating the job, and not the default value of the workflow.
My Windows network storage directory is not accessible. What should I do?
If the Electra VS fails to access a destination storage location, the following error will be raised: “Unreachable destination: Network storage XXXXX on server XXX.XXX.XXX.XXX protocol CIFS”.
Check that you have declared the mount point with the CIFS protocol.
Check your shared folder rights. Your Windows user must be allocated permission on both the Security and Sharing tabs.
The issue may also be with Windows. You may have to modify windows registry keys to allocate more memory to share folders.
Check the following registry key values and change them if they are not correctly set.
454 Electra VS - Version 05.10 User Manual - Rev. A Chapter 5 ’Troubleshooting’ — Frequently Asked Questions
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache = 1 This key tells Windows to set aside enough system cache for sharing large files. HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\P arameters\Size = 3 This value tells Windows to prioritize file sharing over reducing memory usage. Reboot your Windows server after key modification.
The SNMP agent does not work. What should I do?
In the Setup tab, SNMP category, check that the Read and Read/Write communities are entered.
It takes a long time to launch the GUI. Why?
Before launching the signed GUI application, the client station checks through Java (starting in version 1.7.xx) that the related certificate has not been revoked by the issuing authority.
If the Java setting does not allow internet access, the certificate revocation check attempt will fail after about 1 minute. The starting applet will be run but only after this time.
You have two solutions to reduce this startup time:
Solution 1: Allow internet access from the client station so that the certification authority revocation check request can run normally. Java should be configured with the proxy settings.
Solution 2: Disable certification authority revocation checking in Java. Java should be set to disable this check.
Procedure 1. Run the Java Control Panel as follows:
Run the Windows Start menu
Click Programs
Select the Java directory
Click Configure Java to run the Java Control Panel
Electra VS - Version 05.10 455 User Manual - Rev. A Chapter 5 ’Troubleshooting’ — Frequently Asked Questions
Figure 5-1. Run the Java Control Panel
2. Choose one of the following 2 solutions:
Solution 1: Allow internet access from the client station.
Click the General tab, open Network Settings, and enter the proxy settings to enable internet access:
Figure 5-2. Proxy settings to enable internet access
456 Electra VS - Version 05.10 User Manual - Rev. A Chapter 5 ’Troubleshooting’ — Frequently Asked Questions
Solution 2: Disable revocation checking on the client station.
Click the Advanced tab and check the Do not check (not recommended) option.
Figure 5-3. Disable revocation checking
3. Restart Internet Explorer to apply the changes.
I want to remove the bonding of one interface on my 1RU platform. How can I do this?
You can remove the bond between network interfaces on two 1RU Electra VS platforms. By removing a bond, you add a new logical interface, which you must associate with a new LAN. 1. From the Setup tab, select IP, and then click Edit in the top right corner to activate editing mode. 2. Select the Thomson server 1RU profile and then click Duplicate selected profile. 3. In the Profile Thomson server 1RU_1 dialog, move the corresponding nodes from the Other nodes profiles column to the Nodes list for this profile, and then click OK. The new profile is added to the list of Network interfaces profiles.
Electra VS - Version 05.10 457 User Manual - Rev. A Chapter 5 ’Troubleshooting’ — Frequently Asked Questions
Figure 5-4. Move the corresponding nodes to the Nodes list for this profile column
4. In the profile information table to the right, do the following: a. For the bond you wish to remove, change the Bonded with interface value to Blank. The bond is removed and the Logical interface name for the unbonded NIC changes to “unused.”
Figure 5-5. Removing the bond between two NICs (NIC1 and NIC5)
b. In the Logical interface name column, enter a new name for the independent NIC.
c. In the Raise an interface-down log column, select Logical interface down. 5. Click Apply to validate your changes. 6. Add a new LAN and associate it with the new Logical interface name you created in Step 4.
458 Electra VS - Version 05.10 User Manual - Rev. A Chapter 6 Customer Service
Introduction
This chapter indicates what you should do if you have a problem with an equipment, whether you need to repair it or to return it.
In this Chapter
’Support Center Contacts’...... page 460
’Warranty’ ...... page 461
’Services’...... page 462
’Spare Parts’ ...... page 462
’Returning Equipment’...... page 462
’Repackaging for Shipment’ ...... page 462
’Long Term Product Support’ ...... page 463
’Recycling the Product’ ...... page 463
Electra VS - Version 05.10 459 User Manual - Rev. A Chapter 6 ’Customer Service’ — Support Center Contacts
Support Center Contacts
Harmonic Global Service and Support has many Technical Assistance Centers (TAC) located globally, but virtually co-located where our customers can obtain technical assistance or request on-site visits from the Regional Field Service Management team. The TAC operates a Follow-The-Sun support model to provide Global Technical Support anytime, anywhere, through a single case management and virtual telephone system. Depending on time of day, anywhere in the world, we will receive and address your calls or emails in one of our global support centers. The Follow-the-Sun model greatly benefits our customers by providing continuous problem resolution and escalation of issues around the clock.
Report an issue online at: http://harmonicinc.com/webform/report-issue-online
Table 0–1: Technical Support Phone Numbers and Email Addresses
Region Telephone Technical Support E-mail
Americas 888.673.4896 [email protected] (888.MPEG.TWO) or +1.408.490.6477
Europe, Middle +44.1252.555.450 [email protected] East, and Africa
India +91.120.498.3199 [email protected]
Russia +7.495.926.4608 [email protected]
Mainland China +86.10.6569.5580 [email protected]
Japan +81.3.5565.6737 [email protected]
Asia Pacific – +852.3184.0045 [email protected] Other Territories or 65.6542.0050
The Harmonic Inc. support website is:
http://www.harmonicinc.com/content/technical-support
To contact the Harmonic support center by email please write to us at: [email protected] To ensure fast customer service please include the following information when contacting Harmonic by email:
Your contract number
Your geographical location (i.e. country you are in)
The name of your product
Any additional system configuration information relating to your product
460 Electra VS - Version 05.10 User Manual - Rev. A Chapter 6 ’Customer Service’ — Warranty
Warranty
Harmonic guarantees that the product will be free from defects in materials and workmanship, and that the product and/or software will conform to the applicable specifications, within the duration of the warranty.
The product is under warranty for a period of twelve (12) months.
The software is under warranty for a period of ninety (90) days.
Concerning the software warranty, Harmonic guarantees that, for a period of 90 days, after the product’s delivery date, or after a system’s Site Acceptance Test, the physical media will be free from defects and viruses and the embedded software will conform to applicable specifications. There is no warranty that Harmonic software will be error-free. The purchase of a software license entitles the customer to use the Harmonic software release shipped at the time the license is purchased. Rights to new releases (upgrades) are only provided through a Harmonic OneCare service level agreement or can be priced upon request.
Concerning third party firmware & software (e.g. Java, SunMicrosystems, etc.), when supplied with a Harmonic product, Harmonic is not responsible for supplying any support or information regarding said software.
Concerning Harmonic products based on HP Servers, Hardware is covered by the 1-year and Software by the 90-day Harmonic Warranty policy. During the Harmonic Warranty period, Harmonic should serve as the primary point of contact for support. In addition to the contractual Harmonic Warranty, when included free as part of the HP Global Limited Warranty program, the HP services available locally should be used as much as possible by the local Harmonic support team to maximize customer satisfaction. After the Harmonic Warranty period, the remainder of the HP Server Hardware warranty period (generally 2 years) is automatically transferred (linked to part and serial number) to the Customer. The local HP Terms and Conditions then apply to the product warranty.
The Distributor Warranty Policy described in the individual distributorship agreement applies.
For details on the Harmonic warranty policy, please contact your Harmonic sales representative (list of sales representatives available on the Harmonic website at: http://www.harmonicinc.com
Electra VS - Version 05.10 461 User Manual - Rev. A Chapter 6 ’Customer Service’ — Services
Services
Training and assistance service offers are available and can be quoted for upon request.
Harmonic OneCare service level agreement offers apply to this product.
Spare Parts
The spare parts are listed in Table A-71 ’Ordering references for Electra VS’ on page 544, in the Spare Parts category.
Returning Equipment
Please contact the call center with questions about the process for returning Harmonic equipment. Within the standard Harmonic warranty period, there is a 30 day turnaround (factory in/out) guarantee for repairs. Unless specifically agreed, cost and risks for return shipment of equipment are borne by the Customer. The faulty device must be packed where possible in its original packaging (protective corners and boxes) If you no longer have the packaging, the faulty device must be protected against shocks during the transportation. The company may not be held liable for any consequence resulting from non-observance of this return procedure. The company will not be able to guarantee a repair time for any RMA request for which we do not have a clear and complete fault description. If no fault is found, a fixed price will be raised to cover shipping and testing of the unit.
Repackaging for Shipment
Retain original packaging — Unless specifically agreed, cost and risks for return shipment of equipment are borne by the Customer. The faulty device must be packed where possible in its original packaging (protective corners and boxes) If you no longer have the packaging, the faulty device must be protected against shocks during the transportation. The company may not be held liable for any consequence resulting from non-observance of this return procedure. The Harmonic Customer Service Department will examine packaging on arrival and can refuse to carry out repairs if the packaging has been visibly damaged during transportation and this has led to further damage in addition to the fault originally noted. For a blade center, the nodes and the SFP couplers must be removed from the blade center for transport. The front panel must be removed from 1RU servers before repackaging.
462 Electra VS - Version 05.10 User Manual - Rev. A Chapter 6 ’Customer Service’ — Long Term Product Support
Long Term Product Support
Long-Term Product Support (LTPS) is the Harmonic support provided during the product life cycle, starting at the announcement of the end of product manufacture and ending at the announcement of the end of services.
After product phase-out announcement, LTPS data is provided by the Harmonic Regional Sales and Field Services organizations.
The Harmonic OneCare SLA commitment concerning LTPS data and associated services may differ from those included as part of the general Harmonic LTPS policy. In such cases, LTPS data and associated services governed by the terms and conditions of OneCare contracts override the general LTPS policy.
Recycling the Product
Harmonic has developed a comprehensive end-of-life product take back program for recycling or disposal of end-of-life products. Our program meets the requirements of the European Union’s WEEE Directive and, in the United States, those of the Environmental Protection Agency, individual state or local agencies. Harmonic guarantees the proper disposal of your end-of-life products. A Certificate of Recycling or a Certificate of Destruction, depending on the ultimate disposition of the product, can be sent upon request. Harmonic will be responsible for all costs associated with recycling and disposal, including freight, however you are responsible for the removal of the equipment from your facility and packing the equipment ready for pickup. For further information on the Harmonic product take back system, please visit our website’s Environmental Policy page: http://www.harmonicinc.com
Electra VS - Version 05.10 463 User Manual - Rev. A Chapter 6 ’Customer Service’ — Recycling the Product
464 Electra VS - Version 05.10 User Manual - Rev. A Chapter 7 Tools
Introduction
This chapter describes the Equipment Set-up tool delivered in the DVD-ROM with the product, the monitoring tools delivered by HP for the blade centers configuration, as well as the NodeBench tool.
In this Chapter
’NodeBench’ ...... page 466
’Equipment Setup’...... page 469
’HP Monitoring Tools (6RU and 10RU Devices)’...... page 473
Electra VS - Version 05.10 465 User Manual - Rev. A Chapter 7 ’Tools’ — NodeBench
NodeBench
Overview
Deploying Electra VS on off-the-shelf servers or on a virtualized infrastructure offers a lot of flexibility: the number of potential hardware configurations expands dramatically, with a direct impact on solution performances.
Before deploying Electra VS solution (virtualized or not) on a customer’s hardware platform, a benchmark is required to assess the level of performances which can be expected from the target servers. This is the purpose of the VOS Flex NodeBench.
VOS Flex NodeBench gathers information on the hardware resources and measures the performances of the target servers. This performance measurement must be performed for every different hardware targets.
Operation
This section explain:
How to launch VOS Flex NodeBench in a platform not integrated in a Electra VS.
How to use VOS Flex NodeBench.
Launching VOS Flex NodeBench on New Hardware Resource 1. Creating the bootable USB Flash drive Refer to Chapter 2 ’Installation and Startup’, section ’Creating the Bootable USB Flash drive’ on page 58. 2. Starting Electra VS for evaluation a. Launch VOS Flex NodeBench from the USB flash drive - Power down the server - Plug the USB Flash drive in your server - Power up the server - At restart select the BOOT menu (F11 for HP platform) - Boot from the key
RUN VS7000 Electra VS (for evaluation using NodeBench tool) Install VS7000 Electra VS on Local host
466 Electra VS - Version 05.10 User Manual - Rev. A Chapter 7 ’Tools’ — NodeBench
- Select Run Electra VS (for evaluation using NodeBench tool)
b. Configure the management IP address - Connect in Guest mode (User = THVNguest Pwd =THVNpwd0) - Execute the following command: setIP -l bond<> -l lannumber -a @IP/mask <-t if tagged> -g @IPgateway: configure the management IP address, after configuration you can access the Web interface using the address configured Example : setIP -a 198.18.76.244/21 -g 198.18.64.1 -l 3064 -d eth0 The management IP address will be set to 198.18.76.244 in LAN 3064 in the first network interface.
c. Connect a PC to the configured management interface You can now connect to the Electra VS Web Interface using the PC. Refer to Chapter 2 ’Installation and Startup’, section ’Accessing the Web Interface for the First Time’ on page 63.
Using VOS Flex NodeBench
VOS Flex NodeBench analyzes can be executed
On a hardware platform not integrated in a Electra VS, in order to assess the level of performances which can be expected from the target servers and perform accurate simulation.
On a new hardware platform added in a already existing Electra VS.
On a hardware platform already integrated in a Electra VS, in order to check if its real processing capacity corresponds to the configured one.
To launch NodeBench analyze, proceed as follows: 1. Select the Hardware tab. 2. Go to the Nodes category. 3. Select the Node to analyze. Note: If jobs are running on the target node the NodeBench analyze will be refused. If it is the case you can stop the job running on the node or reboot it to force them to be restart on another node if available.
Electra VS - Version 05.10 467 User Manual - Rev. A Chapter 7 ’Tools’ — NodeBench
4. Click the Start NodeBench button to launch the analyze.
5. Import the NodeBench zipped files if requested. The files are stored in the DVD-ROM in the Software / VOS Flex-Nodebench files directory. The analyze may take up to five hours.
When the NodeBench analyze is complete, the resulting processing capacity is indicated between brackets in the interface.
Figure 7-1. Processing capability .
6. Click the Export NodeBench result button to upload the result file on your PC.
You can download it on another node with the same characteristics (exactly the same hardware and exactly the same configuration of the BIOS parameters) or send it to Harmonic is requested.
You can apply it on the current node by clicking the Set Processing Capacity button. If you reduce a capacity and if jobs are running on the node they may be stopped and may be restarted on another nodes. If the capacity is higher than the real capacity of the node the jobs may not work correctly.
468 Electra VS - Version 05.10 User Manual - Rev. A Chapter 7 ’Tools’ — Equipment Setup
Equipment Setup
Overview
The Equipment Set-up tool provided by Harmonic lets you perform the setup of the equipment through the network. It also lets you discover the equipment that is present on the local network, and this even if their IP address is not configured.
This tool works only on interface 1 (System private LAN) of the system.
Operation
This section explains:
How to launch the Equipment Set-up
How to connect to a device
How to set the system private LAN parameters
Launching Equipment Setup 1. Insert the DVD-ROM supplied with your Electra VS product into your DVD-ROM drive.
2. Double-click the EquipmentSetup.jar file to launch the application.
Electra VS - Version 05.10 469 User Manual - Rev. A Chapter 7 ’Tools’ — Equipment Setup
Connecting to a Device
Figure 7-2. Equipment set-up
To connect to a device: 1. Choose a mode of connection:
If the IP address of the equipment is known and can be reached, check the first option: IP address is known and reachable. This method must be used if the equipment is not on the local network, but can however be reached through routers.
If the equipment is physically connected to the local network, whatever its IP address, check the second option: IP address is unknown or unreachable. When choosing this option, the list of detected equipment on the local network is displayed (see Figure 7-3 ). Criteria may be given, such as serial number and/or part number. 2. Click Connect in the menu bar on the left.
470 Electra VS - Version 05.10 User Manual - Rev. A Chapter 7 ’Tools’ — Equipment Setup
Figure 7-3. List of detected equipment
For each piece of equipment, the following information is provided:
Equipment name
IP address (LAN1)
Serial number
Product type
Version 3. Select one piece of equipment from the list and click Select to reach its setup.
Electra VS - Version 05.10 471 User Manual - Rev. A Chapter 7 ’Tools’ — Equipment Setup
Setting Device Parameters
Figure 7-4. Equipment set-up settings
Once you are connected to a device, you can set a number of parameters regarding the system private LAN:
LAN number: number of the LAN, used to identify the LAN in logs.
Address
Mask
Supervision address: this is a virtual IP address allocated to the master node, allowing supervision of the Electra VS on this LAN. It allows to connect to the Electra VS without knowing which node is currently the master one.
Addresses range
When the parameters are set, click Send to apply them to the equipment.
If the supervision PC is in DHCP, unplug and replug it so as to force it to get a new address. Number of necessary addresses = number of blades + 2.
472 Electra VS - Version 05.10 User Manual - Rev. A Chapter 7 ’Tools’ — HP Monitoring Tools (6RU and 10RU Devices)
HP Monitoring Tools (6RU and 10RU Devices)
Connecting to the HP Monitoring Tools
To perform the IP configuration of a blade center, there are several steps. The Electra VS device is delivered with a preconfiguration that you may need to adapt to your needs and to complete.
There are several ways to connect to the device, depending on your network configuration. All possibilities are described in the coming sections.
Before you start, on the rear panel of the blade center, locate the Active OnBoard Administrator module. Pull the tag attached to the OnBoard Administrator and write down the DNS name, the user name and the password indicated. You will need this information to connect to the device.
Method #1: Connecting via the iLO Port in DHCP
The easiest way to connect to the device is using the iLO port. In this case you need to have a DHCP server and a DNS server.
Proceed as follows: 1. Plug an Ethernet cable on the active iLO port on the rear panel and connect it to your Ethernet network. 2. On a remote computer, type the DNS name in the address bar of a Web browser.
Figure 7-5. HP configuration interface – login page
Electra VS - Version 05.10 473 User Manual - Rev. A Chapter 7 ’Tools’ — HP Monitoring Tools (6RU and 10RU Devices)
3. Enter the user name and password indicated on the asset tag.
You are now connected to the HP configuration interface.
Figure 7-6. HP configuration interface – welcome page
Method #2: Connecting on the DHCP Network using the IP Address of the Device
If you have a DHCP server but you do not have a DNS server, you can retrieve the IP address of the blade center from the front panel and use it to connect to the equipment via the DHCP network.
To do so: 1. On the front panel of the Electra VS device, press OK to activate the display.
Figure 7-7. Electra VS front panel screen – Main menu
474 Electra VS - Version 05.10 User Manual - Rev. A Chapter 7 ’Tools’ — HP Monitoring Tools (6RU and 10RU Devices)
2. Select Enclosure Info and press OK.
Figure 7-8. Electra VS front panel screen – Enclosure information
3. Note the IP address indicated in the Active OA field. 4. From a remote computer, type the IP address in the address bar. 5. Enter the user name and password indicated on the asset tag.
You are now connected to the HP configuration interface.
Method #3: Connecting After Manually Configuring the IP Address of the Device
If you do not have a DHCP server nor a DNS server, you can configure the IP address manually using the front panel.
To do so: 1. On the front panel of the Electra VS device, press OK to activate the display.
Figure 7-9. Electra VS front panel screen – Main menu
Electra VS - Version 05.10 475 User Manual - Rev. A Chapter 7 ’Tools’ — HP Monitoring Tools (6RU and 10RU Devices)
2. Select Enclosure Settings and press OK.
Figure 7-10. Electra VS front panel screen – Enclosure settings
3. Select the OA1 IPv4 field and press OK.
Figure 7-11. Electra VS front panel screen – Onboard Administrator selection
4. Once again, select the OA1 IPv4 field and press OK.
Figure 7-12. Electra VS front panel screen – Onboard Administrator network mode
476 Electra VS - Version 05.10 User Manual - Rev. A Chapter 7 ’Tools’ — HP Monitoring Tools (6RU and 10RU Devices)
5. Set the Network Mode to static and press OK. 6. Select Accept and press OK.
Figure 7-13. Electra VS front panel screen – Onboard Administrator IP address setting
7. Use the arrows to enter the IP address in the OA1 IP field. 8. Select Accept and press OK.
Once the IP address is set, you can access the equipment remotely. 1. From a remote computer, type the IP address in the address bar. 2. Enter the user name and password indicated on the asset tag.
You are now connected to the HP configuration interface.
Performing the IP Configuration from the HP Interface
Once you are connected to the HP configuration interface, you can perform a variety of settings, and particularly the settings of the interconnect bays. What we call interconnect bays are the HP VC Flex-10 Enet Modules.
Accessing the Interconnect Bays’ Management Console
Before configuring the interconnect bays, make sure you write down the user name and password of each module. They are indicated on the label on the rear panel of the blade center.
To connect to the interconnect bay: 1. From the tree menu on the left, select Enclosure Information, Interconnect Bays and select a bay.
Electra VS - Version 05.10 477 User Manual - Rev. A Chapter 7 ’Tools’ — HP Monitoring Tools (6RU and 10RU Devices)
Figure 7-14. HP configuration interface – Interconnect bay
2. Click the Management Console link on the right.
You are redirected to a dedicated HP configuration interface.
478 Electra VS - Version 05.10 User Manual - Rev. A Chapter 7 ’Tools’ — HP Monitoring Tools (6RU and 10RU Devices)
Figure 7-15. Accessing the HP Virtual Connect Manager interface
3. Enter the user name and password of the interconnect bay and click Sign in.
Configuring the Interconnect Bays
Interconnect bays are delivered with a default configuration. If you need to modify it, read the information below.
The Electra VS product requires an internal system network for communication between the blades. This network must be linked to the first interface of each blade. You must perform the first IP configuration via this network.
Once you are logged in, perform the following global steps: 1. In the Ethernet networks category, define the LANs. 2. Assign the LANs to the output ports. 3. Modify the server profiles so that they see these networks.
When your configuration is complete, connect the Ethernet cables to the interconnect bays.
Saving your Configuration
When your configuration of the interconnect bays is complete, you may want to save it to a file for backup purposes. To do so: 1. From the HP Management Console, in the tree menu on the left, under Domain Settings, choose Backup/Restore.
Electra VS - Version 05.10 479 User Manual - Rev. A Chapter 7 ’Tools’ — HP Monitoring Tools (6RU and 10RU Devices)
Figure 7-16. HP Virtual Connect Manager interface – Domain settings
2. If you wish to encrypt your backup, enter an encryption key in the field. 3. In the Backup Domain Configuration area, click the Backup Configuration button. 4. Save your file.
If you need to restore this configuration, proceed as follows: 1. In the same configuration panel, click Browse in the Restore Domain Configuration area and select your backup file. 2. Click the Restore Configuration button.
You can also use the Import/Export feature in script format, as described in section ’Exporting Information for Customer Support’ on page 450, in the Enclosure information paragraph.
More Information
For more information on the HP configuration interface, refer to the HP documentation available on the HP Website and on the DVD-ROM.
480 Electra VS - Version 05.10 User Manual - Rev. A Appendix A Technical Specifications
Introduction
This chapter gives:
Specifications
Standard compliance
Ordering guide
In this Chapter
’Hardware Delivery Specifications’ ...... page 482
’Software Only Requirements Specifications’ ...... page 512
’Virtualization Requirements Specifications’ ...... page 512
’Common Specifications’ ...... page 513
’Standard Compliance’ ...... page 540
’Ordering Guide’ ...... page 544
Electra VS - Version 05.10 481 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Hardware Delivery Specifications
Electrical, Thermal and Mechanical Specifications
For all specifications of your equipment, please refer to the HP Technical Specifications provided on the DVD-ROM.
Values in the tables in this section are based on N + N redundancy mode for the power supply, unless specified otherwise.
Electra VS 10RU
Electra VS 10RU (AC 200-240V single phase)
Electra VS 10RU fitted with 16 system storage and processing blades
Table A-1. Electra VS G7 10RU fitted with 16 blades (AC 200-240V single phase), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current Total Input Power (W) 2268 4429 5443 Total Input VA 2314 4519 5554 Total Input Current (A)t 10.06 19.65 24.15 Input Current per cord 1.68 3.27 4.02 (A) Total Airflow (CFM) 180 352 560 Total Airflow (CMM) 51016 Heat Dissipating 7734 15102 18561 Power (BTU)
Table A-2. Electra VS G8 10RU fitted with 16 blades (AC 200-240V single phase), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current Total Input Power (W) 1604 5035 6328 Total Input VA 1637 5137 6457 Total Input Current (A)t 7.12 22.34 28.07
482 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Table A-2. Electra VS G8 10RU fitted with 16 blades (AC 200-240V single phase), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Input Current per cord 1.186 3.723 4.679 (A) Total Airflow (CFM) 128 386 628 Total Airflow (CMM) 41118 Heat Dissipating 5470 17168 21577 Power (BTU)
Table A-3. Electra VS G9 10RU fitted with 16 blades (AC 200-240V single phase), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current Total Input Power (W) 1821 5565 6692 Total Input VA - 5678 - Total Input Current (A)t - 24.69 - Heat Dissipating - 18976 - Power (BTU)
Table A-4. Electra VS G9v2 10RU fitted with 16 blades (AC 200-240V single phase), Electrical and Thermal specifications
@100% Idle Utilization Max Circuit
Total system Inrush ------<210A @ 230V, < 2ms>------Current
Total Input Power (W) 1611 5221 6218
Total Input VA - 5328 -
Total Input Current (A)t - 23.17 -
Heat Dissipating Power - 17805 - (BTU)
Table A-5. Electra VS 10RU fitted with 16 blades (AC 200-240V single phase), Dimensions and Weight
Dimensions (H x W x D) 17.4 x 17.6 x 32 in / 442 x 447.04 x 813 mm
Weight 471 lbs / 213 kg
Electra VS - Version 05.10 483 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Electra VS 10RU fitted with 8 system storage and processing blades
Table A-6. Electra VS G7 10RU fitted with 8 blades (AC 200-240V single phase), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current Total Input Power (W) 1299 2535 3131 Total Input VA 1326 2587 3195 Total Input Current (A)t 5.77 11.25 13.89 Input Current per cord 0.96 1.87 2.31 (A) Total Airflow (CFM) 106 210 347 Total Airflow (CMM) 36 10 Heat Dissipating 4431 8645 10672 Power (BTU)
Table A-7. Electra VS G8 10RU fitted with 8 blades (AC 200-240V single phase), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current Total Input Power (W) 973 2853 3574 Total Input VA 993 2911 3647 Total Input Current (A)t 4.32 12.66 15.86 Input Current per cord 0.720 2.109 2.643 (A) Total Airflow (CFM) 80 236 381 Total Airflow (CMM) 27 11 Heat Dissipating 3320 9728 12188 Power (BTU)
Table A-8. Electra VS G9 10RU fitted with 8 blades (AC 200-240V single phase), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current Total Input Power (W) 1050 3075 3730
484 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Table A-8. Electra VS G9 10RU fitted with 8 blades (AC 200-240V single phase), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total Input VA -3137- Total Input Current (A)t - 13.64 - Heat Dissipating - 10484 - Power (BTU)
Table A-9. Electra VS G9v2 10RU fitted with 8 blades (AC 200-240V single phase), Electrical and Thermal specifications
@100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current
Total Input Power (W) 947 2899 3485
Total Input VA - 2958 -
Total Input Current - 12.86 - (A)t
Heat Dissipating - 9886 - Power (BTU)
Table A-10. Electra VS 10RU fitted with 8 blades (AC 200-240V single phase), Dimensions and Weight
Dimensions (H x W x D) 17.4 x 17.6 x 32 in / 442 x 447.04 x 813 mm
Weight 357 lbs / 162 kg
Electra VS - Version 05.10 485 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Electra VS 10RU (AC NA Triple Phase @ 208VAC)
Electra VS 10RU fitted with 16 system storage and processing blades
Table A-11. Electra VS G7 10RU fitted with 16 blades (AC NA Triple Phase @ 208VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 208V, < 2ms ------Current per Branch Total Input Power (W) 2298 4425 5443 Total Input VA 2344 4515 5554 Total Input Current (A)t 6.51 12.53 15.42 Input Current per cord 3.25 6.27 7.71 (A) Total Airflow (CFM) 183 352 560 Total Airflow (CMM) 51016 Heat Dissipating 7834 15088 18561 Power (BTU)
Table A-12. Electra VS G8 10RU fitted with 16 blades (AC NA Triple Phase @ 208VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 208V, < 2ms ------Current per Branch Total Input Power (W) 1676 5066 6342 Total Input VA 1710 5170 6472 Total Input Current (A)t 4.75 14.35 17.96 Input Current per cord 2.374 7.175 8.982 (A) Total Airflow (CFM) 133 388 630 Total Airflow (CMM) 41118 Heat Dissipating 5715 17277 21627 Power (BTU)
486 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Table A-13. Electra VS G9 10RU fitted with 16 blades (AC NA Triple Phase @ 208VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 208V, < 2ms ------Current per Branch Total Input Power (W) 1905 5575 6707 Total Input VA - 5690 - Total Input Current (A)t - 15.79 - Heat Dissipating -19014- Power (BTU)
Table A-14. Electra VS G9 v210RU fitted with 16 blades (AC NA Triple Phase @ 208VAC), Electrical and Thermal specifications
@100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 208V, < 2ms ------Current per Branch
Total Input Power (W) 1712 5231 6231
Total Input VA - 5338 -
Total Input Current (A)t - 14.82 -
Heat Dissipating Power - 17839 - (BTU)
Table A-15. Electra VS 10RU fitted with 16 blades (AC NA Triple Phase @ 208VAC), Dimensions and Weight
Dimensions (H x W x D) 17.4 x 17.6 x 32 in / 442 x 447.04 x 813 mm
Weight 471 lbs / 213 kg
Electra VS - Version 05.10 487 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Electra VS 10RU fitted with 8 system storage and processing blades
Table A-16. Electra VS G7 10RU fitted with 8 blades (AC NA Triple Phase @ 208VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 208V, < 2ms ------Current per Branch Total Input Power (W) 1389 2555 3130 Total Input VA 1418 2608 3194 Total Input Current (A)t 3.94 7.24 8.86 Input Current per cord 1.97 3.62 4.43 (A) Total Airflow (CFM) 114 211 347 Total Airflow (CMM) 36 10 Heat Dissipating 4735 8710 10670 Power (BTU)
Table A-17. Electra VS G8 10RU fitted with 8 blades (AC NA Triple Phase @ 208VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 208V, < 2ms ------Current per Branch Total Input Power (W) 1073 2869 3582 Total Input VA 1095 2927 3655 Total Input Current (A)t 3.04 8.12 10.15 Input Current per cord 1.519 4.062 5.073 (A) Total Airflow (CFM) 88 237 382 Total Airflow (CMM) 27 11 Heat Dissipating 3658 9782 12214 Power (BTU)
488 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Table A-18. Electra VS G9 10RU fitted with 8 blades (AC NA Triple Phase @ 208VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 208V, < 2ms ------Current per Branch Total Input Power (W) 1198 3084 3736.64 Total Input VA -3147- Total Input Current (A)t -8.73- Heat Dissipating - 10515 - Power (BTU)
Table A-19. Electra VS G9v2 10RU fitted with 8 blades (AC NA Triple Phase @ 208VAC), Electrical and Thermal specifications
@100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 208V, < 2ms ------Current per Branch
Total Input Power (W) 1099 2914 3490
Total Input VA - 2974 -
Total Input Current (A)t -8.25-
Heat Dissipating Power - 9937 - (BTU)
Table A-20. Electra VS 10RU fitted with 8 blades (AC NA Triple Phase @ 208VAC), Dimensions and Weight
Dimensions (H x W x D) 17.4 x 17.6 x 32 in / 442 x 447.04 x 813 mm
Weight 357 lbs / 162 kg
Electra VS - Version 05.10 489 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Electra VS 10RU (AC INTL Triple Phase @ 230VAC)
Electra VS 10RU fitted with 16 system storage and processing blades
Table A-21. Electra VS G7 10RU fitted with 16 blades (AC INTL Triple Phase @ 230VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current per Branch Total Input Power (W) 2249 4363 5373 Total Input VA 2295 4452 5483 Total Input Current (A)t 3.33 6.45 7.95 Input Current per cord 1.663 3.226 3.973 (A) Total Airflow (CFM) 179 347 553 Total Airflow (CMM) 51016 Heat Dissipating 7668 14877 18322 Power (BTU)
Table A-22. Electra VS G8 10RU fitted with 16 blades (AC INTL Triple Phase @ 230VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current per Branch Total Input Power (W) 1673 5055 6328 Total Input VA 1707 5158 6457 Total Input Current (A)t 2.47 7.48 9.36 Input Current per cord 1.237 3.738 4.679 (A) Total Airflow (CFM) 133 387 628 Total Airflow (CMM) 41118 Heat Dissipating 5704 17238 21577 Power (BTU)
490 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Table A-23. Electra VS G9 10RU fitted with 16 blades (AC INTL Triple Phase @ 230VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current per Branch Total Input Power (W) 1901 5565 6692 Total Input VA - 5677 - Total Input Current (A)t -8.23- Heat Dissipating - 18977 - Power (BTU)
Table A-24. Electra VS G9v2 10RU fitted with 16 blades (AC INTL Triple Phase @ 230VAC), Electrical and Thermal specifications
@100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current per Branch
Total Input Power (W) 1709 5221 6218
Total Input VA - 5328 -
Total Input Current (A)t -7.72-
Heat Dissipating Power - 17805 - (BTU)
Table A-25. Electra VS 10RU fitted with 16 blades (AC INTL Triple Phase @ 230VAC), Dimensions and Weight
Dimensions (H x W x D) 17.4 x 17.6 x 32 in / 442 x 447.04 x 813 mm
Weight 471 lbs / 213 kg
Electra VS - Version 05.10 491 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Electra VS10RU fitted with 8 system storage and processing blades
Table A-26. Electra VS G7 10RU fitted with 8 blades (AC INTL Triple Phase @ 230VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current per Branch Total Input Power (W) 1353 2512 3081 Total Input VA 1381 2564 3144 Total Input Current (A)t 2 3.72 4.56 Input Current per cord 1.001 1.858 2.278 (A) Total Airflow (CFM) 111 208 341 Total Airflow (CMM) 36 10 Heat Dissipating 4615 8568 10505 Power (BTU)
Table A-27. Electra VS G8 10RU fitted with 8 blades (AC INTL Triple Phase @ 230VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current per Branch Total Input Power (W) 1071 2862 3574 Total Input VA 1093 2921 3647 Total Input Current (A)t 1.58 4.23 5.29 Input Current per cord 0.792 2.117 2.643 (A) Total Airflow (CFM) 88 237 381 Total Airflow (CMM) 27 11 Heat Dissipating 3652 9761 12188 Power (BTU)
492 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Table A-28. Electra VS G9 10RU fitted with 8 blades (AC INTL Triple Phase @ 230VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current per Branch Total Input Power (W) 1197 3078 3729 Total Input VA -3141- Total Input Current (A)t -4.55- Heat Dissipating - 10497 - Power (BTU)
Table A-29. Electra VS G9v2 10RU fitted with 8 blades (AC INTL Triple Phase @ 230VAC), Electrical and Thermal specifications
@100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 230V, < 2ms ------Current per Branch
Total Input Power (W) 1097 2909 3483
Total Input VA - 2968 -
Total Input Current (A)t -4.3-
Heat Dissipating Power - 9920 - (BTU)
Table A-30.
Dimensions (H x W x D) 17.4 x 17.6 x 32 in / 442 x 447.04 x 813 mm
Weight 356 lbs / 161 kg
Electra VS - Version 05.10 493 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Electra VS 10RU (AC JPN Triple Phase @ 200VAC)
Electra VS 10RU fitted with 16 system storage and processing blades
Table A-31. Electra VS G7 10RU fitted with 16 blades (AC JPN Triple Phase @ 200VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 200V, < 2ms ------Current per Branch Total Input Power (W) 2256 4376 5390 Total Input VA 2302 4465 5500 Total Input Current (A)t 6.64 12.89 15.88 Input Current per cord 3.322 6.445 7.938 (A) Total Airflow (CFM) 179 348 554 Total Airflow (CMM) 51016 Heat Dissipating 7691 14921 18379 Power (BTU)
Table A-32. Electra VS G8 10RU fitted with 16 blades (AC JPN Triple Phase @ 200VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 200V, < 2ms ------Current per Branch Total Input Power (W) 1678 5071 6348 Total Input VA 1712 5174 6478 Total Input Current (A)t 4.94 14.94 18.70 Input Current per cord 2.471 7.468 9.349 (A) Total Airflow (CFM) 133 388 630 Total Airflow (CMM) 41118 Heat Dissipating 5721 17291 21647 Power (BTU)
494 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Table A-33. Electra VS G9 10RU fitted with 16 blades (AC JPN Triple Phase @ 200VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 200V, < 2ms ------Current per Branch Total Input Power (W) 1905 5582 6714 Total Input VA - 5695 - Total Input Current (A)t - 16.44 - Heat Dissipating - 19302 - Power (BTU)
Table A-34. Electra VS G9v2 10RU fitted with 16 blades (AC JPN Triple Phase @ 200VAC), Electrical and Thermal specifications
@100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 200V, < 2ms ------Current per Branch
Total Input Power (W) 1712 5236 6238
Total Input VA - 5343 -
Total Input Current (A)t - 15.42 -
Heat Dissipating Power - 17856 - (BTU)
Table A-35. Electra VS 10RU fitted with 16 blades (AC JPN Triple Phase @ 200VAC), Dimensions and Weight
Dimensions (H x W x D) 17.4 x 17.6 x 32 in / 442 x 447.04 x 813 mm
Weight 470 lbs / 213 kg
Electra VS - Version 05.10 495 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Electra VS 10RU fitted with 8 system storage and processing blades
Table A-36. Electra VS G7 10RU fitted with 8 blades (AC JPN Triple Phase @ 200VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 200V, < 2ms ------Current per Branch Total Input Power (W) 1357 2520 3090 Total Input VA 1385 2571 3153 Total Input Current (A)t 4.00 7.42 9.10 Input Current per cord 1.999 3.712 4.551 (A) Total Airflow (CFM) 111 209 342 Total Airflow (CMM) 36 10 Heat Dissipating 4628 8593 10537 Power (BTU)
Table A-37. Electra VS G8 10RU fitted with 8 blades (AC JPN Triple Phase @ 200VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 200V, < 2ms ------Current per Branch Total Input Power (W) 1074 2871 3585 Total Input VA 1096 2930 3658 Total Input Current (A)t 3.16 8.46 10.56 Input Current per cord 1.582 4.228 5.280 (A) Total Airflow (CFM) 88 238 382 Total Airflow (CMM) 27 11 Heat Dissipating 3662 9790 12224 Power (BTU)
496 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Table A-38. Electra VS G9 10RU fitted with 8 blades (AC JPN Triple Phase @ 200VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 200V, < 2ms ------Current per Branch Total Input Power (W) 1197 3087 3740 Total Input VA -3150- Total Input Current (A)t -9.09- Heat Dissipating - 10527 - Power (BTU)
Table A-39. Electra VS G9v2 10RU fitted with 8 blades (AC JPN Triple Phase @ 200VAC), Electrical and Thermal specifications
@100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 200V, < 2ms ------Current per Branch
Total Input Power (W) 1097 2918 3493
Total Input VA - 2977 -
Total Input Current (A)t -8.59-
Heat Dissipating Power - 9949 - (BTU)
Table A-40. Electra VS 10RU fitted with 8 blades (AC JPN Triple Phase @ 200VAC), Dimensions and Weight
Dimensions (H x W x D) 17.4 x 17.6 x 32 in / 442 x 447.04 x 813 mm
Weight 357 lbs / 162 kg
Electra VS 10RU (DC 48V)
Electra VS 10RU fitted with 16 system storage and processing blades
Table A-41. Electra VS G7 10RU fitted with 16 blades (DC 48V), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------No Inrush current------Current
Electra VS - Version 05.10 497 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Table A-41. Electra VS G7 10RU fitted with 16 blades (DC 48V), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total Input Power (W) 1950 3934 4829 Total Input VA 1950 3934 4829 Total Input Current (A)t 40.63 81.96 100.6 Total Airflow (CFM) 155 313 497 Total Airflow (CMM) 49 14 Heat Dissipating 6650 13414 16466 Power (BTU)
Table A-42. Electra VS G8 10RU fitted with 16 blades (DC 48V), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------No Inrush current------Current Total Input Power (W) 1368 4532 5677 Total Input VA 1368 4532 5677 Total Input Current (A)t 28.49 94.42 118.28 Total Airflow (CFM) 112 347 564 Total Airflow (CMM) 31016 Heat Dissipating 4664 15455 19360 Power (BTU)
Table A-43. Electra VS G9 10RU fitted with 16 blades (DC 48V), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------No Inrush current------Current Total Input Power (W) 1930 5802 7009 Total Input VA - 5802 - Total Input Current (A)t -121- Heat Dissipating - 19784 - Power (BTU)
498 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Table A-44. Electra VS G9v2 10RU fitted with 16 blades (DC 48V), Electrical and Thermal specifications
@100% Idle Utilization Max Circuit
Total system Inrush ------No Inrush current------Current
Total Input Power (W) 1716 5449 6491
Total Input VA - 5449 -
Total Input Current -114- (A)t
Heat Dissipating - 18582 - Power (BTU)
Table A-45. Electra VS 10RU fitted with 16 blades (DC 48V), Dimensions and Weight
Dimensions (H x W x D) 17.4 x 17.6 x 32 in / 442 x 447.04 x 813 mm
Weight 458 lbs / 208 kg
Electra VS 10RU fitted with 8 system storage and processing blades
Table A-46. Electra VS G7 10RU fitted with 8 blades (DC 48V), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------No Inrush current------Current Total Input Power (W) 1078 2214 2724 Total Input VA 1078 2214 2724 Total Input Current (A)t 22.46 46.12 56.74 Total Airflow (CFM) 88 191 302 Total Airflow (CMM) 25 9 Heat Dissipating 3676 7549 9288 Power (BTU)
Table A-47. Electra VS G8 10RU fitted with 8 blades (DC 48V), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------No Inrush current------Current
Electra VS - Version 05.10 499 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Table A-47. Electra VS G8 10RU fitted with 8 blades (DC 48V), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total Input Power (W) 1078 2214 2724 Total Input VA 1078 2214 2724 Total Input Current (A)t 22.46 46.12 56.74 Total Airflow (CFM) 88 191 302 Total Airflow (CMM) 25 9 Heat Dissipating 3676 7549 9288 Power (BTU)
Table A-48. Electra VS G9 10RU fitted with 8 blades (DC 48V), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------No Inrush current------Current Total Input Power (W) 1159 3240 3902 Total Input VA - 3240 - Total Input Current (A)t -68- Heat Dissipating - 11047 - Power (BTU)
Table A-49. Electra VS G9 v210RU fitted with 8 blades (DC 48V), Electrical and Thermal specifications
@100% Idle Utilization Max Circuit
Total system Inrush ------No Inrush current------Current
Total Input Power (W) 1057 3064 3654
Total Input VA - 3064 -
Total Input Current (A)t -64-
Heat Dissipating Power - 10448 - (BTU)
Table A-50. Electra VS 10RU fitted with 8 blades (DC 48V), Dimensions and Weight
Dimensions (H x W x D) 17.4 x 17.6 x 32 in / 442 x 447.04 x 813 mm
Weight 345 lbs / 156 kg
500 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Electra VS 6RU
Electra VS 6RU (AC 100-240V single phase @ 115VAC)
Electra VS 6RU fitted with 8 system storage and processing blades
Table A-51. Electra VS G7 6RU fitted with 8 blades (AC 100-240V single phase @ 115VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 140A @ 115V, < 2ms ------Current Total Input Power (W) 1458 2751 3330 Total Input VA 1488 2807 3398 Total Input Current (A)t 12.94 24.41 29.55 Input Current per cord 2.16 4.07 4.92 (A) Total Airflow (CFM) 119 228 369 Total Airflow (CMM) 36 10 Heat Dissipating 4972 9381 11355 Power (BTU)
Table A-52. Electra VS G8 6RU fitted with 8 blades (AC 100-240V single phase @ 115VAC), Electrical and Thermal specifications in Power Supply Redundancy mode N +1 @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 115V, < 2ms ------Current Total Input Power (W) 1109 3030 3821 Total Input VA 1132 3092 3899 Total Input Current (A)t 9.84 26.89 33.90 Input Current per cord 1.640 4.481 5.651 (A) Total Airflow (CFM) 91 251 408 Total Airflow (CMM) 37 12 Heat Dissipating 3781 10333 13030 Power (BTU)
Electra VS - Version 05.10 501 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Table A-53. Electra VS 6RU fitted with 8 blades (AC 100-240V single phase @ 115VAC), Dimensions and Weight
Dimensions (H x W x D) 10.4 x 19.1 x 32.977 in / 265 x 485 x 835 mm Weight G7: 279 lbs / 126 Kg G8: 252 lbs / 114 kg
Electra VS 6RU (AC 100-240V single phase @ 230VAC)
Electra VS 6RU fitted with 8 system storage and processing blades
Table A-54. Electra VS G7 6RU fitted with 8 blades (AC 100-240V single phase @ 230VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 140A @ 115V, < 2ms ------Current Total Input Power (W) 1418 2688 3271 Total Input VA 1447 2743 3338 Total Input Current (A)t 6.29 1.93 14.51 Input Current per cord 1.05 1.99 2.42 (A) Total Airflow (CFM) 116 222 362 Total Airflow (CMM) 36 10 Heat Dissipating 4835 9168 11154 Power (BTU)
Table A-55. Electra VS G8 6RU fitted with 8 blades (AC 100-240V single phase @ 230VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------< 210A @ 115V, < 2ms ------Current Total Input Power (W) 1076 3027 3704 Total Input VA 1097 3089 3779 Total Input Current (A)t 4.77 13.43 16.43 Input Current per cord 0.795 2.238 2.739 (A) Total Airflow (CFM) 88 250 395 Total Airflow (CMM) 27 11
502 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Table A-55. Electra VS G8 6RU fitted with 8 blades (AC 100-240V single phase @ 230VAC), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Heat Dissipating 3668 10321 12630 Power (BTU)
Table A-56. Electra VS 6RU fitted with 8 blades (AC 100-240V single phase @ 230VAC), Dimensions and Weight
Dimensions (H x W x D) 10.4 x 19.1 x 32.977 in / 265 x 485 x 835 mm Weight 281 lbs / 127 kg
Electra VS 6RU (DC 48V)
Electra VS 6RU fitted with 8 system storage and processing blades
Table A-57. Electra VS G8 6RU fitted with 8 blades (DC 48V), Electrical and Thermal specifications @100% Idle Utilization Max Circuit
Total system Inrush ------No Inrush current------Current Total Input Power (W) 1771 4348 5392 Total Input VA 1771 4348 5392 Total Input Current (A)t 36.89 90.58 112.34 Input Current per cord -- - (A) Total Airflow (CFM) 141 346 555 Total Airflow (CMM) 41016 Heat Dissipating 6038 14826 18387 Power (BTU)
Table A-58. Electra VS 6RU fitted with 8 blades (DC 48V), Dimensions and Weight Dimensions (H x W x D) 17.4 x 17.6 x 32 in / 442 x 447.04 x 813 mm Weight 381 4lbs / 174 kg
Electra VS - Version 05.10 503 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Electra VS 1RU
Electra VS 1RU (AC 100-240V single phase)
G7 Total Input Power: 295 W
G8 Total Input Power: 350 W
G9 Total Input Power:
Mono processor: 240 W
Dual processor: 405 W
G9v2 Total Input Power:
Mono processor: 220 W
Dual processor: 370 W
Dimensions and Weight:
Table A-59. Electra VS 1RU (AC 100-240V single phase), Dimensions
Dimensions (H x W x D) - 1.70 x 16.78 x 27.25 in / 43.2 x 426.2 x 692.2 mm G7
Dimensions (H x W x D) - 1.7 x 17.1 x 27.5 in / 43.2 x 434.7 x 698.5 mm G8
Dimensions (H x W x D) - 1.69 x 17.11 x 27.5 in / 42.9 x 434.6 x 699 mm G9
Max Weight 42.6 lbs / 19 kg
504 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
Blade Center Physical Interface Specifications
Supported modules:
SFP+ transceiver module - 10GBase-SR (optical) - 850nm - LC multi-mode - plug-in module - up to 980 ft.
SFP (mini-GBIC) transceiver module - 1000Base-SX (optical) - plug-in module
SFP (mini-GBIC) transceiver module - 1000Base-T (electrical) - plug-in module
Electra VS - Version 05.10 505 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
HP 1RU Hardware available Configurations
Refer to section ’Ordering Guide’ on page 544.
1RU G8 Hardware available configurations
The following 1-RU platforms may be ordered
ELC-VS-1U-2AC-SYS/ ELC-VS-1U-2AC-PRO + ELC-VS-HW-GIGE-4: Server with 8 IP network connectors
Figure A-1. G8 server with 8 IP network connectors
ELC-VS-1U-2AC-SYS/ ELC-VS-1U-2AC-PRO + ELC-VS-HW-GIGE-4 (mandatory) + ELC-VS-HW-HDSDI-4: Server with 8 IP network connectors and 4 SD-SDI/HD-SDI inputs
Figure A-2. G8 server with 8 IP network connectors and 4 SD-SDI/HD-SDI inputs
ELC-VS-1U-2AC-SYS/ ELC-VS-1U-2AC-PRO + ELC-VS-HW-GIGE-4 (mandatory) + ELC-VS-HW-HDSDI-2: Server with 8 IP network connectors and 2 SD-SDI/HD-SDI inputs
Figure A-3. G8 server with 8 IP network connectors and 2 SD-SDI/HD-SDI inputs
506 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
ELC-VS-1U-2AC-SYS/ ELC-VS-1U-2AC-PRO + ELC-VS-HW-GIGE-4 (mandatory) + ELC-VS-HW-SDI-8 Server with 8 IP network connectors and 8 SD-SDI inputs
Figure A-4. G8 server with 8 IP network connectors and 8 SD-SDI inputs
ELC-VS-1U-2AC-SYS/ ELC-VS-1U-2AC-PRO + 2 * ELC-VS-HW-SDI-8: Server with 4 IP network connectors and 16 SD-SDI inputs
Figure A-5. G8 server with 4 IP network connectors and 16 SD-SDI inputs
In this configuration only 2 IP interfaces are available.
Electra VS - Version 05.10 507 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
1RU G9 Hardware available configurations
The following 1-RU platforms may be ordered
ELC-VS-1U-2AC-SYS/ELC-VS-1U-2AC-SYS-MONO/ ELC-VS-1U-2AC-PRO/ELC-VS-1U-2AC-PRO-MONO: Server with 8 IP network connectors
Figure A-6. G9 server with 8 IP network connectors
ELC-VS-1U-2AC-SYS/ELC-VS-1U-2AC-SYS-MONO/ ELC-VS-1U-2AC-PRO/ELC-VS-1U-2AC-PRO-MONO + ELC-VS-HW-HDSDI-4: Server with 8 IP network connectors and 4 SD-SDI/HD-SDI inputs
Figure A-7. G9 server with 8 IP network connectors and 4 SD-SDI/HD-SDI inputs
ELC-VS-1U-2AC-SYS/ELC-VS-1U-2AC-SYS-MONO/ ELC-VS-1U-2AC-PRO/ELC-VS-1U-2AC-PRO-MONO + ELC-VS-HW-HDSDI-2: Server with 8 IP network connectors and 2 SD-SDI/HD-SDI inputs
Figure A-8. G9 server with 8 IP network connectors and 2 SD-SDI/HD-SDI inputs
508 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
ELC-VS-1U-2AC-SYS/ELC-VS-1U-2AC-SYS-MONO/ ELC-VS-1U-2AC-PRO/ELC-VS-1U-2AC-PRO-MONO + ELC-VS-HW-SDI-8 Server with 8 IP network connectors and 8 SD-SDI inputs
Figure A-9. G9 server with 8 IP network connectors and 8 SD-SDI inputs
ELC-VS-1U-2AC-SYS/ELC-VS-1U-2AC-SYS-MONO/ ELC-VS-1U-2AC-PRO/ELC-VS-1U-2AC-PRO-MONO + 2 * ELC-VS-HW-SDI-8: Server with 8 IP network connectors and 16 SD-SDI inputs
Figure A-10. G9 server with 8 IP network connectors and 16 SD-SDI inputs
ELC-VS-1U-2AC-SYS/ELC-VS-1U-2AC-SYS-MONO/ ELC-VS-1U-2AC-PRO/ELC-VS-1U-2AC-PRO-MONO + ELC-VS-HW-UHD: Server with 8 IP network connectors and additional hardware accelerator board for UHD encoding
Figure A-11. G9 server with 8 IP network connectors and additional hardware accelerator board for UHD encoding
UHD accelerator board
Electra VS - Version 05.10 509 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
ELC-VS-1U-2AC-SYS/ELC-VS-1U-2AC-PRO + 2*ELC-VS-HW-UHD
Figure A-12. G9 server with 8 IP network connectors and 2 additional hardware accelerator board for UHD encoding
UHD accelerator boards
ELC-VS-1U-2AC-SYS/ELC-VS-1U-2AC-SYS-MONO/ELC-VS-1U-2AC-PR O/ELC-VS-1U-2AC-PRO-MONO + ELC-VS-HW-3GSDI-4
Server with 8 IP network connectors and 4 3G-SDI inputs
Figure A-13. G9 server with 8 IP network connectors and 4 3G-SDI inputs
3G-SDI quad board
ELC-VS-1U-2AC-SYS/ELC-VS-1U-2AC-SYS-MONO/ELC-VS-1U-2AC-PRO/ ELC-VS-1U-2AC-PRO-MONO + ELC-VS-HW-3GSDI-4 + ELC-VS-HW-UHD
Server with 8 IP network connectors and 4 3G-SDI inputs and additional hardware accelerator board for UHD encoding
Figure A-14. G9 server with 8 IP network connector, 4 3G-SDI inputs and additional hardware accelerator board for UHD encoding
3G-SDI quad board UHD accelerator board
510 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Hardware Delivery Specifications
ELC-VS-1U-2AC-SYS/ELC-VS-1U-2AC-PRO + ELC-VS-HW-3GSDI-4 + 2* ELC-VS-HW-UHD
Server with 8 IP network connectors and 4 3G-SDI inputs and 2 additional hardware accelerator boards for UHD encoding
Figure A-15. G9 server with 8 IP network connector, 4 3G-SDI inputs and 2 additional hardware accelerator boards for UHD encoding
3G-SDI quad board UHD accelerator boards
Electra VS - Version 05.10 511 User Manual - Rev. A Appendix A ’Technical Specifications’ — Software Only Requirements Specifications
Software Only Requirements Specifications
The minimum and recommended requirements are described in the Electra VS-Checklist documentation delivered in the DVD-ROM with the product.
Virtualization Requirements Specifications
The minimum and recommended requirements are described in the Electra VS-Checklist documentation delivered in the DVD-ROM with the product.
512 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Common Specifications
Input Specifications
Live TS Over IP Inputs
MPEG-2 TS MPTS/SPTS over IP (CBR & VBR)
Bitrate range: 10 kbit/s - 100 Mbps
Supported protocols: TS/UDP/IP or TS/RTP/UDP/IP
Packet sizes: 188/204
Unicast and multicast, IGMP v2, IGMP v3, SSM
IPV4 support
Live RTMP Inputs
Bitrate range : 10kbps - 50 Mbps
Protocols: RTMP protocol 1.0 RTMPS, RTMPE, RTMPT or RTMPTE protocols are not supported
Supported video formats: H264
Supported audio formats: AAC-LC, AAC-HE v1, AAC-HE v2 RTMP Streams are identified per stream name, only one stream per connection is supported. Multi-bitrate is not supported.
SDI Inputs (Depending on Server Type)
Standards:
SMPTE 259M (SD-SDI) (see ’SMPTE 259M-2008’)
SMPTE 272M (Embedded audio in SD) (see ’SMPTE 272M-2004’)
SMPTE 292M (HD-SDI) for dual and quad cards (see ’SMPTE ST 292-1:2011’)
SMPTE 299M (Embedded audio in HD) (see ’SMPTE 299M-2004’)
SMPTE 424M (3G-SDI) Level A, Level B Dual Link (B-DL). Level B Dual Stream (B-DS) is not supported. (see ’SMPTE ST 424:2012’)
Electra VS - Version 05.10 513 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
SMPTE-425-5 (UHD 4x3G-SDI) Quadrant and 2 Sample Interleave (2SI) modes (see '’SMPTE ST 425-5:2015’)
Supported video formats:
SD: NTSC [email protected] fps, PAL 576i@25 fps
HD For dual, quad and 3G-SDI boards only: - 1080p@25/29.97/30 fps - 1080i@25/29.97/30 fps - 720p@50/59.94/60 fps For 3G-SDI board only: - 1080p@50/59.94/60 fps
UHD - 2160p@25/30/50/60 fps
4:2:2, 10 bits
Supported audio formats:
PCM: - 48 kHz, 16 bits - Mono, stereo, 5.1 - Up to 16 channels per SDI input on new dual or quad boards or octo boards (e.g. 16 mono or 8 stereo components). Up to 8 channels per SDI input on former dual or quad boards.
Compressed audio: - Dolby Digital/Dolby Digital Plus - Dolby E (from dual or quad boards). - Up to 4 Dolby streams on a dual or a quad board, and to 8 Dolby streams on an octo board.
Subtitles:
Closed captions extraction: CEA-608-B & CEA-708-B, line 21 & CDP/VANC, OP-42
Teletext extraction: - Teletext in DVB/SCTE VBI: ITU-R BT 653.3 system B. - SMPTE-2031 Carriage of DVB/SCTE VBI Data in VANC - OP-47 Subtitling Distribution Packet (SDP) format (the Vertical Ancillary Multi-Packet format is not supported) - Teletext is not extracted from VBI lines 6 and 7 on the Dual or Quad SD-HD boards.
514 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Aspect ratio: WSS, AFD (RP186), AFD Ready (SMPTE 2016), Manual
Connectors:
For ELC-VS-HW-HDSDI-2: BNC connectors.
For ELC-VS-HW-HDSDI-4: DIN 1.0/2.3 rather than larger BNC connectors. 4 SDI female BNC cables are delivered with the board.
For ELC-VS-HW-SDI-8: DIN 1.0/2.3 rather than larger BNC connectors. 8 SDI female BNC cables are delivered with the board.
For ELC-VS-HW-3GSDI-4: DIN 1.0/2.3 rather than larger BNC connectors. 4 SDI female BNC cables are delivered with the board.
Extraction of the following SCTE 104 over SMPTE2010 requests and creation of corresponding SCTE 35 sections (not available on former dual or quad cards):
Alive_request_data
Splice_request_data : - spliceStart_normal - spliceStart_immediate - spliceEnd_normal - spliceEnd_immediate - splice_cancel
Splice_null_request
Insert_avail_descriptor_request_data
Insert_descriptor_request_data
Supported splice modes are:
immediate
VITC
UTC
SDI Matrices
The supported SDI matrices all support the Grass Valley protocol.
Table A-60. List of supported SDI matrices Type Reference Name
8x8 SDI SL-SD0808-N-CP Nevion - VikinX Sublime 8x8 HD-SDI SL-HD0808-N-CP Nevion - VikinX Sublime 16x16 SDI SL-SD1616-N-CP Nevion - VikinX Sublime
Electra VS - Version 05.10 515 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Table A-60. List of supported SDI matrices Type Reference Name
16x16 HD-SDI SL-HD1616-N-CP Nevion - VikinX Sublime 32x32 SDI SL-SD3232-N-CP Nevion - VikinX Sublime 32x32 HD-SDI SL-HD3232-N-CP Nevion - VikinX Sublime 64x64 or more Concerto SDI matrix
File Formats
MPEG-2 TS input:
Bitrate: 10 kbps - 50 Mbps
Bitrate auto-detection (PCR based)
SPTS/MPTS - SPTS in CBR or VBR (i.e. TS without stuffing packets) mode - MPTS in CBR mode only (VBR not supported).
MP4/MOV input
Video: H.264, Apple ProRes, MPEG-2
Audio: AAC-LC, AAC-HE v1, AAC-HE v2, MPEG-1 layer 2, Dolby
MPEG-2 PS input
MXF
OP1a including D-10 (IMX30, IMX 40, IMX50), XAVC (AVC intra only), XDCAM 422 50 Mbps - Video: AVC-I, MPEG2 - Audio: PCM S8, PCM S16LE, PCM S16BE, PCM S24LE, PCM S24BE, PCM S32LE, PCM S32BE, MPEG-1 Audio Layer 2, AAC - Subtitle: Closed captions extraction: -transmitted in video -CEA-608-B & CEA-708-B, CDP/VANC if presence of Closed Captions in video and in a separate track, only the second ones are transmitted. XML metadata (mount point) are not taken in account.
YUV input:
P010: 4:2:0,10 bits (coded on 16 bits, little endian), planar (different from Microsoft definition)
516 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
I420: 4:2:0, 8 bits, planar (different from Microsoft definition) Planar standard definition The luma "luminance" plane Y appears first, then the U chroma and last the V chroma planes as shown in the following diagram:
YYYYYY YYYYYY YYYYYY YYYYYY U U U U U U V V V V V V
Supported image file formats:
Gif (fixed and animated)
Jpeg
Png
Tiff
Bmp (windows bitmap)
Tga (targa)
Remote file storage:
NFS v3
CIFS
Electra VS - Version 05.10 517 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Decoding Specifications
Video Decoding
MPEG-2 Video (Refer to Table A-61 ’MPEG-2 video decoding specifications’ on page 518)
H.264 AVC (Refer to Table A-62 ’H.264 and H.265 decoding specifications’ on page 519)
H.265 AVC (Refer to Table A-62 ’H.264 and H.265 decoding specifications’ on page 519)
AVC-I
File: AVC-Intra 50, AVC-Intra 100
Live: AVC-Intra 100
Apple ProRes (file input only)
Input format - Apple ProRes 4444 - Apple ProRes 4444 (XQ) - Apple ProRes 422 (HQ) - Apple ProRes 422 - Apple ProRes 422 (LT) - Apple ProRes 422 (Proxy)
Internal format - 4:2:0, 8 or 10bits
Resolution - up to 2160p@60 fps
Table A-61. MPEG-2 video decoding specificationsa
MPEG-2b
Input Format 4:2:0, 8 bits 4:2:2, 8 bits
Maximum bitrates Standard (4:2:0, 8 bits): 20 Mbps Contribution 4:2:0/4:2:2, 8 bits: 100 Mbps
Profiles Simple, Main, High
Levels Low, Main, High
518 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Table A-61. MPEG-2 video decoding specificationsa
MPEG-2b
Resolution up to 720p@60 fps, 1080i@30 fps or 1080p@30 fps (live and file inputs)
Implemented tools 3:2 pull-down support
Closed captions extraction (CEA-608, CEA-708)
a The decoding output format is always 4:2:0. The output bit depth depends on both the input video bit depth and the value of the Output video bit depth parameter. It will be 10 bits if the input video is 10 bits and if the Output video bit depth parameter is set to ‘same as input’. It will be 8 bits in all the other cases. b DigiCipher II is supported.
Table A-62. H.264 and H.265 decoding specificationsa
H.264 H.265
Input Format 4:2:0, 8 bits 4:2:0, 8 bits 4:2:2, 8 bits 4:2:0, 10 bits 4:2:0, 10 bits 4:2:2, 10 bits AVC-Intra Class 50, Class 100
Maximum bitrates Standard (4:2:0, 8 bits): 12 Mbps 40 Mbps Contribution 4:2:0, 8 bits and CABAC: 50 Mbps 4:2:0, 10 bits and CABAC: 50 Mbps 4:2:2, 8 bits and CABAC: 50 Mbps 4:2:2, 10 bits and CABAC: 30 Mbps 4:2:0/4:2:2, 8/10 bits and CAVLC: 100 Mbps
Profiles Baseline, Main, High Main, Main 10
Levels up to 4.2 N/A
Resolution up to 1080p@60 fps, 1080i@30 fps (live input) up to 1080i@30 fps up to 720p@60 fps, 1080i@30 fps, up to 3840x2160p@60 fps 2160p@60 fps (file input)
Implemented tools 3:2 pull-down support
Closed captions extraction (CEA-608, CEA-708)
a The decoding output format is always 4:2:0. The output bit depth depends on both the input video bit depth and the value of the Output video bit depth parameter. It will be 10 bits if the input video is 10 bits and if the Output video bit depth parameter is set to ‘same as input’. It will be 8 bits in all the other cases.
Electra VS - Version 05.10 519 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Audio Decoding
MPEG-1 layer 2, MPEG-2 layer 2
MPEG-2 / MPEG-4 AAC-LC, AAC-HE v1 / v2
Dolby Digital / Dolby Digital Plus
Dolby E The Dolby E source carries up to 8 audio tracks which may be combined to carry surround (5.1), stereo (2.0) or mono (1.0) audio programs depending on the program number. It is possible to decode up to 4 audio programs from the same Dolby E source. Refer toTable A-64 ’Dolby E program configurations’ on page 521.
Table A-63. Audio decoding specifications
Dolby Digital/ MPEG-1 Layer II AAC Dolby MPEG-2 Layer II Digital Plus
Profiles AAC-LC AAC-HE v1 -- AAC-HE v2
Modes AAC-LC: Mono, Stereo, 5.1 Mono, Stereo, Joint Mono, Stereo, 5.1 AAC-HE v1: Mono, Stereo, Stereo, Dual Channel 5.1 AAC-HE v2: Stereo
Sampling All: 7.35, 8.09, 11.025, 12, 16, 24, MPEG-1 LII and 48 kHz rates 32, 44.1, 48, 64, 88, 96 kHz MPEG-2 LII: 32 kHz, 44.1 kHz or 48 kHz MPEG-2 LII only: 16 kHz, 22.05 kHz or 24 kHz
Transpor t ADTS ADTS - LOAS
520 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Table A-64. Dolby E program configurations
Program Number
1234
0 5.1 2.0
1 5.1 1.0 1.0
6 2.0 2.0 2.0 2.0
7 2.0 2.0 2.0 1.0
9 2.0 1.0 1.0 1.0 Program Configuration 10-17-21 1.0 1.0 1.0 1.0 11 5.1
14 2.0 2.0 2.0
15 2.0 2.0 1.0 1.0
16 2.0 1.0 1.0 1.0
19 2.0 2.0
20 2.0 1.0 1.0
Electra VS - Version 05.10 521 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Processing Specifications
Video Processing
Smart de-interlacing
Interlacing
Predefined conversion The following conversions are predefined:
PAL 576i @ 25 fps to HD 720p @ 50 fps
PAL 576i @ 25 fps to HD 1080i @ 25 fps
PAL 576i @ 25 fps to NTSC 480i @ 29.97 fps
PAL 576i @ 25 fps to HD 720p @ 59.94/60 fps
PAL 576i @ 25 fps to HD 1080i @ 29.97/30 fps
NTSC 480i @ 29.97 fps to HD 720p @ 59.94 fps
NTSC 480i @ 29.97 fps to HD 1080i @ 29.97 fps
NTSC 480i @ 29.97 fps to PAL 576i @ 25 fps
NTSC 480i @ 29.97 fps to HD 720p @ 50 fps
NTSC 480i @ 29.97 fps to HD 1080i @ 25 fps
HD 720p @ 50 fps to PAL 576i @ 25 fps
HD 720p @ 50 fps to HD 1080i @ 25 fps
HD 720p @ 50 fps to NTSC 480i @ 29.97 fps
HD 720p @ 50 fps to HD 720p @ 59.94/60 fps
HD 720p @ 50 fps to HD 1080i @ 29.97/30 fps
HD 720p @ 50 fps to HD 1080p
HD 720p @ 50 fps to UHD 3840x2160
HD 720p @ 59.94 fps to NTSC 480i @ 29.97 fps
HD 720p @ 59.94/60 fps to HD 1080i @ 29.97/30 fps
HD 720p @ 59.94/60 fps to PAL 576i @ 25 fps
HD 720p @ 59.94/60 fps to HD 720p @ 50 fps
HD 720p @ 59.94/60 fps to HD 1080i @ 25 fps
HD 720p @ 59.94/60 fps to HD 1080p
HD 720p @ 59.94/60 fps to UHD 3840x2160
HD 1080i @ 25 fps to PAL 576i @ 25 fps
HD 1080i @ 25 fps to HD 720p @ 50 fps
HD 1080i @ 25 fps to NTSC 480i @ 29.97 fps
HD 1080i @ 25 fps to HD 720p @ 59.94/60 fps
522 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
HD 1080i @ 25 fps to HD 1080i @ 29.97/30 fps
HD 1080i @ 25 fps to HD 1080p
HD 1080i @ 25 fps to UHD 3840x2160
HD 1080i @ 29.97 fps to NTSC 480i @ 29.97 fps
HD 1080i @ 29.97/30 fps to HD 720p @ 59.94/60 fps
HD 1080i @ 29.97/30 fps to PAL 576i @ 25 fps
HD 1080i @ 29.97/30 fps to HD 720p @ 50 fps
HD 1080i @ 29.97/30 fps to HD 1080i @ 25 fps
HD 1080i @ 29.97/30 fps to HD 1080p
HD 1080i @ 29.97/30 to UHD 3840x2160
HD 1080p to PAL 576i @ 25 fps
HD 1080p to NTSC 480i @ 29.97 fps
HD 1080p to HD 720p
HD 1080p to HD 1080i
HD 1080p to UHD 3840x2160
UHD 3840x2160 to PAL 576i @ 25 fps
UHD 3840x2160 to NTSC 480i @ 29.97 fps
UHD 3840x2160 to HD 720p
UHD 3840x2160 to HD 1080i
UHD 3840x2160 to HD 1080p
Picture resizing: to UHD 3840x2160
AFD conversion
Picture cropping/clipping
Mosaic generation
Thumbnail export in jpeg
Animated/static logo insertion Animated logos are limited to 200 image files.
DVB Subtitle burn-in video
Static/crawling text insertion: Manual or file source. Supported file types: UTF-8, UTF-16, UTF-32, BIG-5, GB18030, TIS-620, SHIFT_JIS
Frame-rate adaptation (from 5 to 60 fps)
Audio Processing
Re-sampling: 8 to 48 kHz (8, 11.025, 12, 16, 22.05, 24, 32, 44.1, 48 kHz)
Audio Mute
Electra VS - Version 05.10 523 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
5.1 / Stereo / mono conversions
Stereo to mono
Mix
Left (for dual channel input)
Right (for dual channel input)
Dolby stereo down-mixing
Static gain adjustment: -30 to +30 dBFS
Automatic Loudness Control:
Modes: Flat, EBU R128, A-Weighting
Noise level: -90 to 0 dBFS
Loudness target: -40 to 0 dBFS
Compression ratio: 1 to 100
Peak limiter: -40 to 0 dBFS
Delay Adjustment from -3 s to + 3 s by step of 1 ms
Encoding Specifications
Video Encoding
H.264 AVC
H.265 HEVC HDR signaling: HLG, HDR-10 and PQ-10.
MPEG-2 Video
Table A-65. H.264 AVC, H.265 HEVC Video encoding specifications
Video Encoding Specifications
Bitrate: 10 kbps - 12 Mbps High bit rate, low density mode (not recommended for 720p50/60): up to 20 Mbps CBR, Capped VBR, statmux H264 AVC Live 4:2:0 - 8 bits Resolution: up to 1080i @ 30fps 720p @ 60fps 1080p @ 60fps
Bitrate: 10 kbps - 80 Mbps CBR, Capped VBR, statmux H264 AVC File 4:2:0 - 8 bits Resolution up to 2160p @ 60fps
524 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Table A-65. H.264 AVC, H.265 HEVC Video encoding specifications
Video Encoding Specifications
Resolution max: up to 720p @ 60 fps - up to 1080p @ 60 fps min: down to 64x64 horizontal and vertical resolutions have to be a multiple of 2 Interlace support (1080i & SD) H265 HEVC Live CBR, Capped VBR, statmux Frame-rate: from 5 to 60 fps Bitrate: 10 kbps - 8 Mbps 4:2:0 - 8/10 bits Main & Main10 profiles
Resolution: 3840x2160 (QFHD) Frame-rate: 25 fps, 29.97 fps, 30 fps, 50 fps, 59.94 fps, 60 fps Progressive only H.265 HEVC Live Bitrate: 4 - 40 Mbps (with UHD accelerator) CBR 4:2:0 - 8/10 bits Main & Main10 profiles
Resolution max: up to 3840x2160 @ 60 fps min: down to 64x64 horizontal and vertical resolutions have to be a multiple of 2 "Interlace support (1080i & SD) H.265 HEVC File "CBR, Capped VBR "Frame-rate: from 5 to 60 fps "Bitrate: 10 kbps - 80 Mbps "4:2:0 - 8/10 bits "Main & Main10 profiles
Table A-66. MPEG-2 Video encoding specifications
MPEG-2 Video Encoding Specifications
Format 4:2:0 – 8 bits
Rate 1 – 20 Mbps
Bit rate control CBR, Capped VBR, Statistical multiplexing
Electra VS - Version 05.10 525 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Table A-66. MPEG-2 Video encoding specifications
MPEG-2 Video Encoding Specifications
Maximum: up to 1080i@30 fps, 720p@60 fps or 1080p@30 fps. Minimum: down to 64x64. Resolution Frame-rate minimum: 5 fps. Horizontal and vertical resolutions have to be a multiple of 2.
Profile Main Profile
Level Main Level, High Level
I, P, B slices Scene-cut detection Implemented tools Interlace support Open GOP
526 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Audio Encoding
MPEG-1 layer 2 Mono/Stereo/Joint Stereo/Dual Channel
MPEG-4 AAC-LC, AAC-HE v1 / v2
Dolby Digital / Dolby Digital Plus
Table A-67. Audio encoding specifications
Supported Preferred Mono/Stereo/ Codec Bit range [bits/s] sampling rate sampling rate 5.1 [kHz] [kHz]
MPEG-1 layer 2 Mono 32, 48, 56, 64, 80, 96, 32, 44.1, 48 32, 44.1, 48 112, 128, 160, 192
Stereo/Joint 64, 96, 112, 128, 160, 32, 44.1, 48 32, 44.1, 48 Stereo/Dual 192, 224, 256, 320, 384 Channel
Electra VS - Version 05.10 527 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Table A-67. Audio encoding specifications
Supported Preferred Mono/Stereo/ Codec Bit range [bits/s] sampling rate sampling rate 5.1 [kHz] [kHz]
AAC-LC Mono 8-15.999 8, 11.025,12, 16 12
16-23.999 16 16
24-31.999 16, 22.05, 24 24
32-55.999 32 32
56-127.999 32, 44.10, 48 44.10
128-192 32, 48, 96 48
192.001-264.6 44.10, 48, 96 96
264.601-288 48, 88.2, 96 96
Stereo 16-23.999 11.025,12, 16 12
24-31.999 16 16
32-39.999 16, 22.05, 24 22.05
40-95.999 32 32
96-111.999 32, 44.10, 48 32
112-255.999 32, 44.10, 48 44.10
256-384 32, 48, 96 48
384.002-529.200 44.10, 48, 96 96
529.202-576 48, 88.20, 96 96
5.1 160-239.999 32 32
240-279.999 32, 44.1, 48 32
280-639.999 32, 44.1, 48 44.1
640-800 32, 48, 96 48
Dual mono not available
528 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Table A-67. Audio encoding specifications
Supported Preferred Mono/Stereo/ Codec Bit range [bits/s] sampling rate sampling rate 5.1 [kHz] [kHz]
AAC-HE v1 Mono 8-11.999 22.05, 24 24
12-17.999 32 32
18-39.999 32, 44.10, 48 44.10
40-64 32, 44.10, 48 48
Stereo 16-27.999 32, 44.10, 48 32
28-95.999 32, 44.10, 48 44.10
96-128 32, 48, 96 48
5.1 64-69.999 32, 44.10, 48 32
70-159.999 32, 44.10, 48 44.10
160-319.999 32, 44.10, 48 48
320-640 64, 88.20, 96 96
AAC-HE v2 Stereo 8-11.999 22.05, 24 24
12-17.999 32 32
18-39.999 32, 44.10, 48 44.10
40-64 32, 44.10, 48 48
Dolby Digital Mono 56, 64, 80, 96, 112, 128, 32, 44.1, 48 48 160, 192, 224, 256, 320, 384, 448, 512, 576, 640
Stereo 96, 112, 128, 160, 192, 224, 256, 320, 384, 448, 512, 576, 640
5.1 224, 256, 320, 384, 448, 512, 576, 640
Dolby Digital Plus Mono 32, 40, 48, 56, 64, 80, 48 48 96, 112, 128, 160, 192, 224, 256, 320, 384, 448, 512, 576, 640
Stereo 96, 112, 128, 160, 192, 224, 256, 320, 384, 448, 512, 576, 640
5.1 192, 224, 256, 320, 384, 448, 512, 576, 640
Electra VS - Version 05.10 529 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Teletext, Subtitles and Closed Captions Processing
Table A-68. Teletext, Subtitles and Closed Captions Processing
Output Format HLS MPEG Dash Burn-in video Smoothstreaming Smoothstreaming DVB-Subtitle/TS/IP DVB-Subtitle/TS/IP DVB teletext /TS/IP teletext DVB Closed Caption/TS/IP Caption/TS/IP Closed Pass-through DVB-teletext Transcoding with Transcoding Transcoding program to DFXP resynchro to WebVtt to SMPTE TT component/TS/IP (TTML) nization
DVB-Subtitling Pass-through program with Transcoding Transcoding Transcoding Yes component/TS/IP resynchro to SMPTE TT to SMPTE-TT to SMPTE-TT (bitmap) nization
Pass-through Pass-through Pass-through Pass-through Closed-Captions with with with with video resynchro resynchro resynchro resynchro stream/TS/IP nization nization nization nization Input Teletext Extraction and Transcoding Format (SMPTE-2031) Transcoding Transcoding conversion to to DFXP over SDI & to WebVtt to SMPTE TT DVB teletext (TTML) HD-SDI
Teletext (ITU-R Extraction and Transcoding Transcoding Transcoding BT 653.3 System conversion to to DFXP to WebVtt to SMPTE TT B) over SDI DVB teletext (TTML)
Pass-through Pass-through Pass-through Pass-through Closed-Captions with with with with over SDI & resynchro resynchro resynchro resynchro HD-SDI nization nization nization nization
Extraction and Transcoding OP47 teletext Transcoding Transcoding conversion to to DFXP over HD-SDI to Webvtt to SMPTE TT DVB teletext (TTML)
530 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Output Specifications
Live Output
MPEG-2 TS MPTS/SPTS over UDP/IP or RTP/UDP/IP:
Bitrate range: 10 kbps - 100 Mbps
Packet size: 188
CBR, VBR (i.e. without stuffing packets)
Multicast / Unicast
IP v4
Video encapsulation: H.264 AVC, H.265 HEVC, MPEG-2 Video
Audio encapsulation: AAC-LC, AAC-HE v1/v2, MPEG-1 Layer 2, Dolby Digital / Dolby Digital Plus
Pass-through: DVB-Teletext, DVB-Subtitles, SCTE 35, audio, video, data, descriptors
Subtitles: Extraction and conversion to DVB teletext from SDI Teletext (SMPTE-2031, ITU-R BT 653.3 System B over SDI, OP47 teletext over HD-SDI).
Adobe Flash / RTMP:
RTMP push
Adaptive bitrate
Authentication: in FMS URL, adapted to - Akamai server, - Level3 server - Adobe method
IP v4
Video encapsulation: H.264 AVC
Audio encapsulation: AAC-LC, AAC-HE v1, AAC-HE v2
Radio program support
Apple HTTP Live Streaming (HLS):
Adaptive bitrate
Segmentation: chunks from 1 to 10 seconds, by steps of 1 second
Protocol version 2, 3, 4 and 5 (see document ’draft-pantos-http-live-streaming-11’)
Encryption: - HLS encryption (AES-128, SAMPLE-AES, Apple fairplay) - Fixed key manually defined
Electra VS - Version 05.10 531 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
- Fixed or rotating key provided by key server - Nagravision - Verimatrix - Novel DRM - HLS using PlayReady by Irdeto v1.0 and v2.0 Fixed key provided by key server - HLS using PlayReady by Viaccess Fixed key provided by key server - HLS using PlayReady by PolyMedia Fixed key provided by key server - HLS using PlayReady by Cisco Fixed key manually defined - HLS using PlayReady by Huawei Fixed or rotating key provided by key server - HLS using PlayReady by Harmonic (KMS Minimum Implementation) Fixed or rotating key provided by key server - HLS using PlayReady by ZTE Fixed or rotating key provided by Microsoft PlayReady LiveTv key server
2 modes: - Push: http PUT to a Web server - Origin server: Apache Web server1 IP v4
Video encapsulation: H.264 AVC, HEVC
Audio encapsulation (up to 5.1): AAC-LC, AAC-HE v1, AAC-HE v2, Dolby Digital / Dolby Digital Plus
Multi audio: multi languages, multi bitrates
Radio program support
Subtitles: - Closed caption (pass-through with resynchronization) - WebVTT - SMPTE-TT (including PNG images)
Microsoft HTTP Smooth Streaming (HSS):
Adaptive bitrate
Segmentation
Encryption:
1. This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
532 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
- Portable encoding of audio/video objects and Protected Interoperable File Format (PIFF) -AES-CBC -AES-CTR - Fixed key provided by key server/PlayReady DRM -BuyDRM -Irdeto -PolyMedia -Technicolor -Viaccess -Nagravision -Verimatrix - Rotating key provided by key server: -Microsoft PlayReady LiveTv, Huawei, Harmonic (KMS Minimum Implementation)
2 modes: - Push: http POST to an IIS server - Origin server: Apache Web server1
IP v4
Video encapsulation: H.264 AVC
Audio encapsulation (up to 2.0): AAC-LC, AAC-HE v1, AAC-HE v2
Radio program support
Subtitles: - DFXP - SMPTE-TT (including PNG images)
MPEG-DASH:
Adaptive bitrate
Segmentation
IPV4
Video encapsulation: H.264 AVC, H.265 HEVC
Audio encapsulation (up to 5.1): AAC-LC, AAC-HE v1, AAC-HE v2, Dolby Digital Plus
Encryption - Encryption scheme -MPEG-CENC (AES-CTR)/PlayReady DRM -MPEG-CENC (AES-CTR)/Widevine
Electra VS - Version 05.10 533 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
-MPEG-CENC (AES-CTR)/Verimatrix DRM - Key management -Fixed key manually defined -Fixed key provided by key server: Piksel -Fixed key or rotating key provided by key server: Widevine, Microsoft PlayReady LiveTv, Huawei, Harmonic (KMS Minimum Implementation), Verimatrix
Compatibility with HbbTV: generation of a specific manifest for this format
Mode: ISO base media file format (see ’ISO/IEC 14496-12’)
2 modes: - Push: http PUT to a Web server - Origin server: Apache Web server1
Subtitles: - Closed caption (pass-through with resynchronization) - SMPTE-TT (including text or PNG images)
File Output
MPEG-2 TS:
CBR, packet size = 188
Video: H.264, H.265, MPEG-2
Audio: AAC-LC, AAC-HE v1, AAC-HE v2, MPEG-1 layer 2, Dolby Digital, Dolby Digital Plus
Subtitles: - DVB subtitles (pass-through with resynchronization) - DVB teletext (pass-through with resynchronization) - Closed caption (pass-through with resynchronization)
MP4\3GP:
Supported tracks: - Video: H.264, H.265, MPEG-2 - Audio: AAC-LC, AAC-HE v1, AAC-HE v2, MPEG-1 layer 2, Dolby Digital, Dolby Digital Plus
Progressive download
1. This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
534 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Apple HTTP Live Streaming (HLS):
Adaptive bitrate
Segmentation: chunks from 1 to 10 seconds, by steps of 1 second
Protocol version 2, 3, 4 or 5 (see document ’draft-pantos-http-live-streaming-11’)
Encryption: - HLS encryption (AES-128) - Fixed key manually defined - Fixed or rotating key provided by key server - Nagravision - Verimatrix - Novel DRM - HLS using PlayReady by Irdeto v1.0 and v2.0 Fixed key provided by key server - HLS using PlayReady by PolyMedia Fixed key provided by key server - HLS using PlayReady by Cisco Fixed key manually defined - HLS using PlayReady by Huawei Fixed key provided by key server - HLS using PlayReady by Harmonic (KMS Minimum Implementation) Fixed key provided by key server - HLS using PlayReady by ZTE Fixed key provided by ZTE key server
Video encapsulation: H.264 AVC, HEVC
Audio encapsulation: AAC-LC, AAC-HE v1, AAC-HE v2, Dolby Digital / Dolby Digital Plus
Multi audio: multi languages, multi bitrates
Radio program support
Subtitles: - Closed caption (pass-through with resynchronization) - WebVTT - SMPTE-TT (including PNG images)
Microsoft HTTP Smooth Streaming (HSS):
Adaptive bitrate
Segmentation
File format: disk file format, wire file format
Electra VS - Version 05.10 535 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Encryption: - Portable encoding of audio/video objects and Protected Interoperable File Format (PIFF) -AES-CBC -AES-CTR - Fixed key provided by key server/PlayReady DRM -BuyDRM -Irdeto -PolyMedia -Technicolor -ViaAccess -ZTE -Verimatrix
Video encapsulation: H.264 AVC
Audio encapsulation: AAC-LC, AAC-HE v1, AAC-HE v2
Radio program support
Subtitles: - Closed caption (pass-through with resynchronization) - SMPTE-TT (including PNG images) - DFXP
MPEG-DASH:
Adaptive bitrate
Video encapsulation: H.264 AVC, H.265 HEVC
Audio encapsulation: AAC-LC, AAC-HE v1, AAC-HE v2, Dolby Digital Plus
Encryption - Encryption scheme -MPEG-CENC (AES-CTR)/PlayReady DRM -MPEG-CENC (AES-CTR)/Widevine -MPEG-CENC (AES-CTR)/Verimatrix DRM - Key management -Fixed key manually defined -Key provided key server: Huawei, Harmonic (KMS Minimum Implementation), Widevine, Piksel, ZTE
536 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Compatibility with HbbTV: generation of specific manifest for this format (see ’HbbTV Version 1.5’)
Mode: ISO base media file format (see ’ISO/IEC 14496-12’)
File format: disk file format, wire file format
Subtitles: - Closed caption (pass-through with resynchronization) - SMPTE-TT (including text or PNG images)
Control-Command Specifications
IP v4
HTTP or HTTPS (over secure TLSv1.2)
Web services (SOAP)1
1. For more information on the Web services control-command, refer to the Web Services SOAP API document.
Electra VS - Version 05.10 537 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
IP TV Latency
The formula to obtain the latency is as follows:
Latency = +
With:
Input latency:
SDI input: 0.64 second.
TS/IP input: 1.3 second.
Coder delay: this is the value configured in the encoders (see section ’H.264 AVC Encoder’ on page 311, section ’H.265 HEVC Encoder’ on page 315, section ’MPEG-2 Encoder’ on page 309). The values are identical for the three encoders:
Standard: 55 frames.
Short: 41 frames.
Ultra-short: 26 frames.
Decoder delay: this is the value configured in the encoders (see section ’H.264 AVC Encoder’ on page 311, section ’H.265 HEVC Encoder’ on page 315, section ’MPEG-2 Encoder’ on page 309). The value is fixed to 1 second for MPEG-2 encoding.
Output frame rate: it depends on the input frame rate, and on the optional frame rate adaptation you may have added.
Optional processing latency: it depends on the video processing you have configured. It is null if there is no preprocessing.
Examples (without any video processing):
SDI input, H264, 25 fps, delay set to Standard: 4.3 seconds.
SDI input, H264, 25 fps, delay set to Short: 3.3 seconds.
SDI input, H264, 25 fps, delay set to Ultra-short: 2.5 seconds.
SDI input, H264, 60 fps, delay set to Standard: 3.1 seconds.
TS/IP input, H264, 60 fps, delay set to Standard: 3.7 seconds. In Statmux mode, the formula to obtain the latency is as follows: Latency = + 61 /
Audio transcoding (radio, or TV with pass-through video), TS/IP input / TS/IP output:
Latency is approximately 2 seconds.
538 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Security Specifications
The following Control-Command specifications are supported:
Web GUI (https)
Web Services (http/SOAP)
SNMP v1, v2c
IP v4
NTP v4 for NTP server connection
PTP v2
For remote connections, only SSHv2 is supported.
For authentication, LDAP and LDAPS are supported.
In the following table, note the open TCP/UDP ports according to the LAN protocol access configuration. The xxxx ports are dynamic ports. The port values may vary between 512 and 1023, and may change on each platform.
Table A-69. Security specifications
Port Service Master node Slave node
22/tcp SSH Remote Login Protocol If Allow SSH checked If Allow SSH checked
68/udp BOOTP client (Equipment Setup Open Open connection)
80/tcp World wide Web HTTP Apache port If Allow HTTP checked If Allow HTTP checked 80
111/tcp SUN Remote Procedure Call Open Open
111/udp SUN Remote Procedure Call Open Open
123/udp Network Time Protocol Open
161/udp net-SNMP If Allow SNMP checked
201/tcp rpc status Open Open
201/udp rpc status Open Open
443/tcp HTTP protocol over TLS/SSL If Allow HTTPS checked If Allow HTTPS checked
xxxxx/udp Rpcbinf Open Open
Electra VS - Version 05.10 539 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Standard Compliance
Table A-70. Standard compliance
Standards Title
MPEG-2. ISO/IEC 13818-1 Information Technology - Generic Coding of Moving Pictures and Associated Audio information - Part 1: Systems- June 2013
MPEG-2. ISO/IEC 13818-1 Draft Amendment 3 -Transport of HEVC video over MPEG-2 Systems. 2013
MPEG-2. ISO/IEC 13818-2 Information Technology - Generic Coding of Moving Pictures and Associated Audio information - Part 2: Video - February 2000
MPEG-2. ISO/IEC 13818-3 Information Technology - Generic Coding of Moving Pictures and Associated Audio information - Part 3: Audio
MPEG-4. ISO/IEC 14496-10 Information technology - Coding of audio-visual objects Part 10: Advanced video coding
MPEG-4. ISO/IEC 14496-15 Advanced Video Coding (AVC) file format. First edition, April 2004
HEVC. ITU/T H.265 Infrastructure of audiovisual services - Coding of moving video High Efficiency Video Coding April 2013
ETSI EN 300 468 Specification for Program Information (SI) in DVB system
ETSI TR 101 162 Allocation of Service Information (SI) codes for DVB systems
ETSI TR 101 211 Guidelines on implementation and usage of Service Information (SI)
ETR 289 V1 Support for use the scrambling and conditional access (CA) within DVB systems
ETSI TS 103 197 Head-End Implementation of DVB Simulcrypt
ETSI TR 101 154 Implementation Guidelines for the use of MPEG-2 Systems, Video and Audio in Satellite, Cable and Terrestrial Broadcasting Applications
ETSI ETR 289 Digital Video Broadcasting (DVB); Support for use of scrambling and Conditional Access (CA) within digital broadcasting systems
ETSI TR 102 135, DVB Implementation Guidelines of the DVB Simulcrypt Standard
ETSI TR 101 162, DVB Allocation of Service Information (SI) codes for DVB systems
540 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Table A-70. Standard compliance
Standards Title
ETSI TS 103 197 DVB SimulCrypt Head-end implementation of DVB SimulCrypt
ATSC-Mobile DTV Standard, Part 7 AVC and SVC Video System Characteristics, Document A/153 Part 7:2009, 15 October 2009
The Protected Interoperable File Portable encoding of audio-video objects, Revised Format (PIFF) 2010-03-09
draft-pantos-http-live-streaming-11 HTTP Live Streaming, April 16, 2013
IEEE 802.1Q IEEE Standard for Local and metropolitan area networks--Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks
ISO/IEC 23009-1:2012 Information technology - Dynamic adaptive streaming over HTTP (DASH) - Part 1: Media presentation description and segment formats
RFC 4918 HTTP Extensions for WEb Distributed Authoring and Versioning (WebDAV) June 2007
ISO/IEC 639-2:1998 Codes for the representation of names of languages - Part 2: Alpha-3 code. Oct 1998
HbbTV Version 1.5 HbbTV Specification 6th March 2012
MS-SSTR v20120705 Smooth Streaming Protocol Specification
ETSI EN 300 472 Digital Video Broadcasting (DVB); Specification for conveying ITU-R System B Teletext in DVB bitstreams
ETSI EN 300 743 DVB Subtitling systems Version 1.3.1, November 2001
ETSI EN 300 706 Enhanced Teletext Specification. Version 1.2.1, April 2004
ETSI EN 301 775 Digital Video Broadcasting (DVB); Specification for the carriage of Vertical Blanking Information (VBI) data in DVB bitstreams, May 2003
ITU-R BT.653-3 Teletext systems. April 2009
SMPTE ST 2052-1:2010 Timed Text Format. 2010
DFXP Distribution format exchange profile, version 24 September 2013 http://www.w3.org/TR/2013/REC-ttml1-20130924/
WEBvTT W3C The Web Video Text Tracks Format https:// dvcs.w3.org/hg/text-tracks/raw-file/default/webvtt/Ov erview.html
SMPTE-2031 Carriage of DVB/SCTE VBI Data in VANC (SD et HD SDI)
Electra VS - Version 05.10 541 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Table A-70. Standard compliance
Standards Title
SMPTE 2010-2008 Vertical Ancillary Data Mapping of ANSI/SCTE 104 Messages (Revision of RP 2010-2007)
SCTE 104 2014 Automation System to Compression System Communications Applications Program Interface (API)
OP-47 Storage and distribution of teletext subtitles and VBI data for high definition TV (HD-SDI 10 bits)
OP-42 FREE TV AUSTRALIA OPERATIONAL PRACTICE OP42 DISTRIBUTION, TRANSMISSION, AND MONITORING OF CLOSED CAPTIONS ON LINE 21/334, issue 4 December 2012
ETSI EN 300 294 Television systems; 625-line television Wide Screen Signalling (WSS). Version 1.4.1, April 2004
IEEE Std 1588TM IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, March 2008
AES67-2015 AES standard for audio applications of networks - High-performance streaming audio-over-IP interoperability, 2015
ISO/IEC 14496-12 ISO Base Media File Format
3GPP TS 26.244 3GPP file format, Release 12, April 2014
SMPTE 259M-2008 SMPTE STANDARD for Television — SDTV Digital Signal/Data — Serial Digital Interface Revision of SMPTE 259M-2006
SMPTE 272M-2004 SMPTE STANDARD for Television — Formatting AES/EBU Audio and Auxiliary Data into Digital Video Ancillary Data Space
SMPTE ST 292-1:2011 SMPTE STANDARD for Television — 1.5 Gb/s Signal/Data Serial Interface Revision of SMPTE 292-2008
SMPTE 299M-2004 SMPTE STANDARD for Television — 24-Bit Digital Audio Format for SMPTE 292M Bit-Serial Interface
SMPTE ST 425-5:2015 SMPTE STANDARD for Television — Image Format and Ancillary Data Mapping for the Quad Link 3 Gb/s Serial Interface
SMPTE ST 424:2012 SMPTE STANDARD for Television — 3-Gbps SDI Video
IRTF RFC2250 RTP Payload Format for MPEG1/MPEG2 Video, January 1998
A/85 Techniques for Establishing and Maintaining Audio Loudness for Digital Television, July 2011
542 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Common Specifications
Table A-70. Standard compliance
Standards Title
Recommendation ITU-R BS.1770-3 Algorithms to measure audio programme loudness and true-peak audio level, August 2012
EBU Recommendation R 128 Loudness normalisation and permitted maximum level of audio signals, August 2011
CableLabs Encoder Boundary Point Specification. OC-SP-EBP-I01-130118 Version I01, January 2013
CableLabs Real-time Event Signaling and Management API, OC-SP-ESAM-API-I01-120910 October 2013
CableLabs Adaptive Transport Stream Specification, February 2014 OC-SP-ATS-I01-140214
RTMP specification Adobe's Real Time Messaging Protocol , December 2012 http://wwwimages.adobe.com/www.adobe.com/conte nt/dam/Adobe/en/devnet/rtmp/pdf/rtmp_specification_ 1.0.pdf
Recommendation ITU-R BT.2020-2 Parameter values for ultra-high definition television systems for production and international programme exchange Oct 2015
SMPTE ST 2084 High Dynamic Range Electro-Optical Transfer Function of Mastering Reference Displays (2014)
ARIB STD-B67 Essential parameter values for the extended image dynamic range television (EIDRTV) system for programme production (version 1.0 - July 2015)
IEEE 1588-2008 Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems (version 2)
GIF89a Graphics Interchange Format Version 89a (1990)
Electra VS - Version 05.10 543 User Manual - Rev. A Appendix A ’Technical Specifications’ — Ordering Guide
Ordering Guide
Table A-71. Ordering references for Electra VS
Code Description
Chassis
1RU
ELC-VS-1U-2AC-SYS Electra VS 1RU platform for system storage & processing. Equipped with dual HDD in RAID 1 configuration and dual PSU.
ELC-VS-1U-2AC-PRO Electra VS 1RU platform for processing. Equipped with dual PSU, no HDD.
ELC-VS-1U-2AC-SYS-MONO Electra VS 1RU mono-processor platform for system storage & processing. Equipped with dual HDD in RAID 1 configuration and dual PSU.
ELC-VS-1U-2AC-PRO-MONO Electra VS 1RU mono-processor platform for processing. Equipped with dual PSU, no HDD.
10RU
ELC-VS-10U-AC Electra VS 10RU platform. Hosts up to 16 blades. Equipped with AC 200-240V single phase power feeding. Includes 10 fans and 6 PSUs. Includes redundant internal 10GiGE switches. Includes redundant chassis manager boards.
ELC-VS-10U-ACT-INT Electra VS 10RU platform. Hosts up to 16 blades. Equipped with AC 380V triple phase power feeding with IEC 309 16A cables (international). Includes 10 fans and 6 PSUs. Includes redundant internal 10GiGE switches. Includes redundant chassis manager boards.
ELC-VS-10U-DC Electra VS 10RU platform. Hosts up to 16 blades. Equipped with DC 48V power feeding. Includes 10 fans and 6 PSUs. Includes redundant internal 10GiGE switches. Includes redundant chassis manager boards.
ELC-VS-10U-ACT-US Electra VS 10RU platform. Hosts up to 16 blades. Equipped with AC 208V triple phase power feeding with NEMA L15-30P cables (US, Japan). Includes 10 fans and 6 PSUs. Includes redundant internal 10GiGE switches. Includes redundant chassis manager boards.
Built-to-order hardware Option
1RU
ELC-VS-HW-HDSDI-2 Additional dual-port SDI/HD-SDI interface board for Electra VS 1RU platforms.
ELC-VS-HW-HDSDI-4 Additional Quad-port SDI/HD-SDI interface board for Electra VS 1RU platforms.
544 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Ordering Guide
Table A-71. Ordering references for Electra VS (...)
Code Description
ELC-VS-HW-SDI-8 Additional octo-port SDI interface board for Electra VS 1RU platforms.
ELC-VS-HW-3GSDI-4 Additional quad-port 3G-SDI interface board for Electra VS 1RU platforms.
ELC-VS-HW-UHD Additional hardware accelerator board for UHD encoding in 1RU platform. This option requires the ELC-VS-LIC-ENC-HEVCUHD license.
Field Upgradable Hardware Option
1RU
ELC-VS-OPT-1U-AC Hot-swappable power supply unit for Electra VS 1RU platforms.
10RU
ELC-VS-OPT-10U-BLA-SYS Hot-swappable system storage and processing blade for Electra VS 10RU platforms. Equipped with dual HDD in RAID 1 configuration.
ELC-VS-OPT-10U-BLA-PRO Hot-swappable processing blade for Electra VS 10RU platforms.
ELC-VS-OPT-10U-AC Hot-swappable AC power supply unit for Electra VS 10RU platform. Fits all single phase and triple phase platforms.
ELC-VS-OPT-10U-DC Hot-swappable DC power supply unit for Electra VS 10RU platform. Fits 48V DC platform only.
ELC-VS-OPT-10U-FAN Hot-swappable fan unit for Electra VS 10RU platform.
ELC-VS-OPT-10U-MNG Hot-swappable chassis manager board for Electra VS 10RU platform.
Common
ELC-VS-OPT-SFP-O-GIGE GigE optical SFP coupler for Electra VS internal IP router for Electra VS 10RU platform.
ELC-VS-OPT-SFP-O-10GIGE 10GigE optical SFP coupler for Electra VS internal IP router for Electra VS 10RU platform.
ELC-VS-OPT-SFP-E-GIGE GigE copper SFP coupler for Electra VS internal router, RJ45 connection for Electra VS 10RU platform.
ELC-VS-OPT-10GIGE-SWI Hot-swappable 10GigE internal IP switch for Electra VS 10RU platform.
ELC-VS-OPT-HDD Hot-swappable hard-disk drive for Electra VS 1RU and 10RU platforms.
Accessories
Electra VS - Version 05.10 545 User Manual - Rev. A Appendix A ’Technical Specifications’ — Ordering Guide
Table A-71. Ordering references for Electra VS (...)
Code Description
ELC-VS-CAB-10U-EUR CEE7-VII European power cord for Electra VS 10RU platform. Fits AC 200-240V single phase platform only.
Software options
Software release
ELC-VS-SW-VOSFLEX This option enables the Electra VS VOSFlex video system on 1 server. This license is required for every 1RU platform or blade in the Electra VS.
ELC-VS-SW-SOFT-ONLY Electra VS delivery as software-only. One item is required per Electra VS delivered.
ELC-VS-SW-VIRTUALIZED Electra VS delivery for virtualized environments. One item is required per virtualized Electra VS delivered.
Video Encoding
ELC-VS-LIC-ENC-MP4QVGA This option enables 1 live QVGA video channel encoding using H.264 baseline & main profiles. It can be used to encode up to 320x240@30fps pixels.
ELC-VS-LIC-ENC-MP4SD This option enables 1 live SD video channel encoding using H.264 baseline, main & high profiles. It can be used to encode up to 720x576 pixels@25fps or 720x480@30fps pixels
ELC-VS-LIC-ENC-MP4HD This option enables 1 live HD video channel encoding using H.264 baseline, main & high profiles. It can be used to encode up to 1920x1080@30fps pixels.
ELC-VS-LIC-ENC-MP2SD This option enables 1 live SD video channel encoding using MPEG-2 MP@ML format. It can be used up to 720x576 output resolution.
ELC-VS-LIC-ENC-MP2HD This option enables 1 live HD video channel encoding using MPEG-2 MP@HL format. It can be used up to 1920x1080@30fps pixels.
ELC-VS-LIC-ENC-HEVCQVGA This option enables 1 live QVGA video channel encoding using HEVC main profile. It can be used to encode up to 320x240@30fps pixels.
ELC-VS-LIC-ENC-HEVCSD This option enables 1 live SD video channel encoding using HEVC main profile. It can be used to encode up to 720x576@25fps or 720x480@30fps pixels.
ELC-VS-LIC-ENC-HEVCHD This option enables 1 live HD video channel encoding using HEVC main profile. It can be used up to encode up to 1920x1080@30fps pixels.
ELC-VS-LIC-ENC-HEVCUHD This option enables 1 live UHD video channel encoding using HEVC main profile (4:2:0). This option is only valid with the ELC-VS-HW-UHD hardware option.
546 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Ordering Guide
Table A-71. Ordering references for Electra VS (...)
Code Description
ELC-VS-LIC-FLX This option is valid for one H.264 encoding channel. This option allows one video encoder (SD/HD) to be assigned within a pool of encoders that are located on the SAME SITE and that are sharing the bandwidth in LOCAL statistical multiplexing.
Scrambling
ELC-VS-LIC-SCR-OTT This option enables WebTV/OTT scrambling output. It performs AES-128 encryption. One license is required per WebTV output.
ELC-VS-LIC-FILE-SCR-OTT This option enables WebTV scrambling for file encoding.
Audio Encoding
ELC-VS-LIC-ENC-AUD20 This option enables 1 live stereo audio channel encoding using MPEG-1 L2, AAC-LC, HE-AAC V1 or HE-AAC V2 formats.
ELC-VS-LIC-ENC-DD51 This option enables 1 live multichannel audio channel encoding using AC3 or E-AC3 formats. It can be used to encode 1 multichannel 5.1 audio or up to 3 stereo audios.
ELC-VS-LIC-ENC-AAC51 This option enables 1 live multichannel audio channel encoding AAC. It can be used to encode 1 multichannel 5.1 audio or up to 3 AAC/MPEG-1L2 stereo audios.
ELC-VS-LIC-ALC20 This option allows Automatic Loudness Control on one stereo pair.
ELC-VS-LIC-ALC51 This option allows Automatic Loudness Control on one multichannel 5.1 audio or for 3 stereo audios.
Audio Transmission
ELC-VS-LIC-TX-AES67 This option enables the transmission of an audio channel using AES-67 standard. Video Decoding
ELC-VS-LIC-DEC-SD This option enables 1 live SD video channel decoding using MPEG-2 or H.264. It can decode up to 720x576@25fps pixels or 720x480@30fps pixels.
ELC-VS-LIC-DEC-HD This option enables 1 live HD video channel decoding using MPEG-2 or H.264. It can decode up to 1920x1080@30fps pixels.Two licenses are needed for decoding up to 1080p@60fps.
ELC-VS-LIC-DEC-HEVCSD This option enables 1 live SD video channel decoding using HEVC Main Profile (4:2:0 8/10bit). It can be used to decode up 720x576 pixels@25fps pixels or 720x480@30fps pixels.
ELC-VS-LIC-DEC-HEVCHD This option enables 1 live HD video channel decoding using HEVC Main Profile (4:2:0 8/10bit). It can be used to decode up 1920x1080 pixels@30fps pixels.
Electra VS - Version 05.10 547 User Manual - Rev. A Appendix A ’Technical Specifications’ — Ordering Guide
Table A-71. Ordering references for Electra VS (...)
Code Description
ELC-VS-LIC-DEC-HEVCUHD This option enables 1 live UHD video channel decoding using HEVC Main Profile (4:2:0 8/10bit). It can be used to decode up 3840x2160 pixels@60fps pixels.
ELC-VS-LIC-DEC-SD-MEZZA This option enables 1 live SD video channel decoding using MPEG-2/H.264 (4:2:2/4:2:0, 8/10bits) at high bit rate. It can decode up to 720x576pixels@25fps or 720x480pixels@30fps.
ELC-VS-LIC-DEC-HD-MEZZA This option enables 1 live HD video channel decoding using MPEG-2/H.264 (4:2:2/4:2:0, 8/10bits) at high bit rate. It can decode up to 1920x1080 pixels@30fps. Two licenses are needed for decoding up to 1080p@60fps.
From version 02.20 upwards, H.264 decoding licenses let you decode MPEG-2 or H.264. In addition, the decoding and encoding licenses now allow operators to use all bought licenses. For instance, a 1920x1080@30fps encoding license allows you to encode: 1 x (1920x1280)@30fps or 1 x (1280x720)@30 fps and 5 x (640x360)@30fps
ELC-VS-LIC-HDR-HLG This option enables processing of HDR HLG signals for one video source.
ELC-VS-LIC-HDR-PQ This option enables processing of HDR SMPTE 2084 PQ signals for one video source. Audio Decoding
ELC-VS-LIC-DEC-AUD20 This option enables 1 live audio stereo channel decoding using MPEG-1 L2, AAC-LC, HE-AAC V1 or HE-AAC V2 formats.
ELC-VS-LIC-DEC-DD51 This option enables 1 multichannel audio decoding using AC3 or E-AC3 formats. It can be used to decode 1 multichannel 5.1 audio or up to 3 stereo audios.
ELC-VS-LIC-DEC-AAC51 This option enables 1 multichannel audio decoding using AAC. It can be used to decode 1 multichannel 5.1 AAC audio or up to 3 stereo AAC/MPEG-1L2 audios.
ELC-VS-LIC-DEC-DE This option enables 1 Dolby E audio decoding channel.
Audio Reception
548 Electra VS - Version 05.10 User Manual - Rev. A Appendix A ’Technical Specifications’ — Ordering Guide
Table A-71. Ordering references for Electra VS (...)
Code Description
ELC-VS-LIC-RX-AES67 This option enables the reception of an audio channel using AES-67 standard.
Software License
ELC-VS-LIC-FILE This option enables file-based encoding on 1 server. It supports MPEG-2 TS input format. It supports MPEG-2 TS, mp4, HLS, Smooth Streaming & MPEG-Dash output formats.
ELC-VS-LIC-FILE-PRE This option enables file-based encoding on 1 server. It supports MPEG-2 TS format or mp4 file format input. It supports up to 4k H.264/HEVC encoding over MPEG-2 TS, mp4, HLS, Smooth Streaming & MPEG-Dash output formats.
Electra VS - Version 05.10 549 User Manual - Rev. A Appendix A ’Technical Specifications’ — Ordering Guide
550 Electra VS - Version 05.10 User Manual - Rev. A Appendix B SNMP Management
Introduction
This chapter gives all information required to monitor Electra VS via SNMP.
It gives a description of the Electra VS MIB.
It explains how to register the SNMP Manager(s) on the GUI of the Electra VS.
It also indicates how to enable the HP Blade Center SNMP Agent.
In this Chapter
’MIB Description’ ...... page 552
’Registering SNMP Manager on the GUI’ ...... page 557
’Enabling HP Blade Center SNMP Agent’...... page 558
Electra VS - Version 05.10 551 User Manual - Rev. A Appendix B ’SNMP Management’ — MIB Description
MIB Description
Electra VS can be monitored via SNMP (v1 or v2). The parameters may be consulted at any time. You may then check its status and get the lists of active and closed logs (alarms and events).
Furthermore, SNMP TRAPs are used to send notification of logs of the equipment. On the DVD-ROM provided with Electra VS, you will find a MIB file in the MIB directory. The MIB details how to monitor the equipment.
Figure B-1. Electra VS MIB
The Electra VS MIB is composed of a number of parts:
Traps (see Paragraph ’Trap Descriptions’ on page 553 for more details),
Objects:
Description: containing the equipment serial number and version (these elements are also available in the About box).
Supervision: containing the current status, the active log list and the closed log list.
Agent Settings: containing the SNMP agent configuration (Trap addressee).
Conformance.
The MIB contains useful information in the description of each field.
The Electra VS equipment can send notifications to SNMP managers when the status of the equipment changes (each time an alarm appears or disappears or an event occurs).
552 Electra VS - Version 05.10 User Manual - Rev. A Appendix B ’SNMP Management’ — MIB Description
Trap Descriptions
Table 1. Description of the alarm trap: VOS FlexTraps(0).supTrapLog(100)
Parameter Description
supLastTrapIdLog Counter that is incremented each time a trap is sent. Thanks to this counter, you can track the loss of logs. In the MIB, look at the supLastTrapIdLog field. If there is a gap between this value and the supLastTrapIdLog value received in the last trap, you can deduce that a trap has been lost. For example, if the supLastTrapIdLog contained in the last trap you received is equal to 3 and the supLastTrapIdLog you get from the MIB is equal to 4, you can deduce the trap number 4 has been lost.
supLogId Log identifier. It is a unique ID that remains the same whether it is an active log or a closed log.
supLogCode Code of the log. This code is used to get the description of the log.
supLogType Type of the log. This code is used to get the type of the log (event, alarm).
supLogNodeId Node identifier of the associated log.
supLogRaisingDateMs UTC time of the log in milliseconds from 1/1/1970.
supLogClearingDateMs UTC time of the log ending in milliseconds from 1/1/1970. It is equal to zero if the log appears.
supLogJobId Job identifier. It is equal to zero if system log.
supLogJobName Job name.Significant if supLogJobId is not equal to zero.
supLogJobRaisingDate Optional, can be significant only for file-to-file jobs (off-line jobs). Time in milliseconds from the beginning of the file.
supLogJobClearingDate Optional, can be significant only for file-to-file jobs (off-line jobs). Time in milliseconds from the beginning of the file.
supLogSeverity Log severity.
supLogCategory Log category.
supLogProbableCause Log probable cause.
supLogProbableCauseText Log probable cause text.
Electra VS - Version 05.10 553 User Manual - Rev. A Appendix B ’SNMP Management’ — MIB Description
Table 1. Description of the alarm trap: VOS FlexTraps(0).supTrapLog(100)
Parameter Description
supLogSpecificProblem Specific problem text (can be empty).
supLogXMLResource Optional XML resource (format is described by resource.xsd file).
supLogNbParam Number of log parameters.
supLogParam1 Parameter 1.
supLogParam2 Parameter 2.
supLogParam3 Parameter 3.
supLogParam4 Parameter 4.
supLogParam5 Parameter 5.
supLogParam6 Parameter 6.
supLogParam7 Parameter 7.
supLogParam8 Parameter 8.
supLogParam9 Parameter 9.
supLogParam10 Parameter 10.
554 Electra VS - Version 05.10 User Manual - Rev. A Appendix B ’SNMP Management’ — MIB Description
Register/Unregister a Manager to Receive Traps
Figure B-2. MIB trap addressee table
To register or unregister a trap receiver, add or remove the agtStgTrDstTable table lines. For example:
To add an snmpV2 trap receiver with the 178.3.2.10 IP address:
SET agtStgTrDstEvalRowStatus.178.3.2.10 integer 4 (Create and go)
SET agtStgTrDstSnmpVersion.178.3.2.10 integer 2 (snmp v2) To add a snmpV1 trap receiver with the 178.3.2.20 IP address:
SET agtStgTrDstEvalRowStatus.178.3.2.20 integer 4 (Create and go)
SET agtStgTrDstSnmpVersion.178.3.2.20 integer 1 (snmp v1) To remove a trap receiver with the 178.3.2.10 IP address:
SET agtStgTrDstEvalRowStatus.178.3.2.10 integer 6 (Remove)
Electra VS - Version 05.10 555 User Manual - Rev. A Appendix B ’SNMP Management’ — MIB Description
Get the Active Log List or Closed Log List
Figure B-3. MIB log list and closed log list
To retrieve the active log list or the closed log list, walk either the supActiveLogTable or the supClosedLogTable. For example:
To retrieve the active log list:
WALK supActiveLogTable To retrieve the closed log list:
WALK supClosedLogTable
Each time a change occurs in one of these two lists, the supLogVersion variable is updated. To find out if there has been a change in one list: GET supLogVersion.0 If the result value is not the same as the previous one, a change has occurred.
556 Electra VS - Version 05.10 User Manual - Rev. A Appendix B ’SNMP Management’ — Registering SNMP Manager on the GUI
Registering SNMP Manager on the GUI
To register a Manager to receive the traps, proceed as follows: 1. Open the GUI as described in section ’Workflows and Jobs Concept’ on page 80. 2. Select the Setup tab. 3. Select the SNMP category. 4. Click the Edit button on the top-right corner to be able to modify the values. 5. Fill in the SNMP Port, the Read Community and Read/Write Community fields.
By default, two community strings are declared: xxxxPublic associated with R/O access level xxxxPrivate associated with R/W access level
6. In the table, add the IP addresses and ports of the SNMP Managers so that they can receive the traps.
To know how to use a table, see Paragraph ’Tables’ on page 91.
Electra VS - Version 05.10 557 User Manual - Rev. A Appendix B ’SNMP Management’ — Enabling HP Blade Center SNMP Agent
Enabling HP Blade Center SNMP Agent
In addition to the Electra VS SNMP agent, the HP blade center provides an SNMP agent that can be used to monitor the hardware.
To use it, you need to enable SNMP and to set a number of parameters.
This configuration is made through the HP configuration interface of the device. Proceed as follows: 1. Open the HP configuration interface, as explained in section ’Connecting to the HP Monitoring Tools’ on page 473. 2. From the tree menu on the left, under Enclosure Information, select Enclosure Settings and then SNMP Settings. 3. Check the Enable SNMP box. 4. Fill in the System Location, System Contact, Read Community and Write Community fields. 5. In the Community String field, enter the IP addresses of the SNMP Managers so that they can receive the system alerts and click Add. 6. Repeat this step for each trap addressee to add.
For further details on SNMP management of the HP blade center, refer to the HP documentation.
558 Electra VS - Version 05.10 User Manual - Rev. A Appendix C Safety Instructions
The safety instructions, provided by HP, are available in printed format in your equipment packaging.
Electra VS - Version 05.10 559 User Manual - Rev. A Appendix C ’Safety Instructions’
560 Electra VS - Version 05.10 User Manual - Rev. A Appendix D Regulatory Notices
Refer to the documentation provided by HP in your equipment packaging.
Electra VS - Version 05.10 561 User Manual - Rev. A Appendix D ’Regulatory Notices’
562 Electra VS - Version 05.10 User Manual - Rev. A Appendix E Logs
Introduction
This chapter provides the list of logs visible in the Logs panel.
In this Chapter
’Log Categories’...... page 564
’List of Logs’ ...... page 565
Electra VS - Version 05.10 563 User Manual - Rev. A Appendix E ’Logs’ — Log Categories
Log Categories
A category is indicated for each log. This may be:
Communications
Quality of service
Processing error
Equipment
Environmental
Other
564 Electra VS - Version 05.10 User Manual - Rev. A Appendix E ’Logs’ — List of Logs
List of Logs
The logs listed below concern several Harmonic products. Not all of the logs listed are necessarily raised by the product.
Code Type Levela Text
0 Alarm Critical Instantiation error RTSP server %s
1 Alarm Undefined (Info) Node in maintenance
2 Alarm Undefined (Critic) Unreachable node
3 Alarm Major Bitrate overflow: LAN overload (%d bps used instead of %d bps)
4 Event Major Job deleted incompatible with configuration
5 Event Undefined (Info) Log database purged by %s
6 Event Undefined (Info) Log database exported by %s to %s
7 Event Minor Log database export failure by %s to %s, cause %s
8 Event Minor Log database purge failure by %s, cause %s
9 Event Undefined (Info) Workflow operation %s %s by %s
10 Event Undefined (Info) Job operation %s by %s
11 Alarm Undefined (Major) File error: Could not open file %s on folder %s
12 Alarm Critical Loss of TS synchro
13 Alarm Undefined (Major) Unreachable destination: Network storage %s on server %s protocol %s
14 Alarm Undefined (Info) Master node
15 Event Undefined (Info) Master change previous master node %d, cause %s
16 Alarm Undefined (Info) Main disk
17 Event Undefined (Info) Main disk change previous disk node %d, cause %s
18 Event Undefined (Info) License file download
19 Event Undefined (Info) License expiration %s
20 Event Undefined (Info) Version download version %s, actual version %s
21 Event Undefined (Info) Version activation version %s, actual version %s
22 Alarm Warning No source clock available: %s
23 Event Undefined (Info) Configuration change System parameters %s by %s
24 Alarm Major Output overflow
25 Alarm Undefined (Info) Active input %s
26 Event Undefined (Info) Active input switch %s is active
Electra VS - Version 05.10 565 User Manual - Rev. A Appendix E ’Logs’ — List of Logs
27 Alarm Critical Configuration inconsistency: received video format (%s) higher than configured maximum one (%s)
28 Alarm Minor Stream discontinuity: continuity counter error on PID %d
29 Alarm Major No component: %s
30 Alarm Major No component: %s
31 Alarm Critical Configuration inconsistency: audio sampling rate (%d Hz) should be in the range [%d-%d] for %s encoding at %d bps
32 Event Critical Software error: workflow %s has been modified without update of its version number
33 Alarm Critical Configuration inconsistency: TS bitrate is higher than configured maximum one (%s bps)
34 Alarm Critical Configuration inconsistency: number of audio channels (%d) is higher than configured maximum one (%d)
35 Alarm Critical Configuration inconsistency: format %s is not the configured one (%s)
36 Alarm Warning Job is waiting: %s
37 Alarm Minor Configuration inconsistency: %s is out of the picture boundaries
38 Alarm Undefined (Major) File error: format not supported
39 Event Undefined (Info) Job is running on node(s) %s
40 Event Undefined (Info) Job deletion from node(s) %s
41 Alarm Major No component: PID %d not referenced in program %d
42 Alarm Major No component: PID %d missing
43 Alarm Major Unsupported frame format: %s
44 Alarm Critical Configuration inconsistency: audio format %s is not compatible with %s encoding
45 Alarm Warning Version mismatch: a new %s version is required, please reboot the node to activate it
46 Alarm Undefined (Major) Loss of synchronization: %s
47 Alarm Undefined (Major) Loss of synchronization: %s
48 Alarm Undefined (Major) Connection establishment error
49 Alarm Major ServiceId not present: %d in PAT
50 Alarm Warning No component: program number %d, %s
51 Event Undefined (Info) Job restarted detection of new input component(s)
52 Alarm Undefined (Major) File error: cannot write file %s on folder %s
53 Event Warning File error: output file renamed %s (file %s already exists)
54 Event Major File error: cannot rename output file %s into %s on folder %s
566 Electra VS - Version 05.10 User Manual - Rev. A Appendix E ’Logs’ — List of Logs
55 Alarm Undefined (Major) File error: cannot create output file %s on folder %s
56 Event Major Unreachable network storage: %s
57 Alarm Major Input overflow
58 Alarm Minor No AFD in signal
59 Alarm Minor No WSS in signal
60 Alarm Minor Configuration inconsistency: PCR PID is not defined for output program %d
61 Alarm Major Link down: interface %d
62 Alarm Major Configuration inconsistency: PMT PID %d is not the configured one (%d)
63 Alarm Warning Link down: %s NIC of interface %d
64 Event Undefined (Info) Job completed
65 Alarm Critical Configuration inconsistency: audio bitrate (%d bps) should be in the range [%d-%d] for %s encoding
66 Alarm Warning Job modification is waiting: %s
67 Alarm Major No component: Track Id %d missing
68 Alarm Major Component processing problem: unsupported format (%s)
69 Alarm Minor Fallback mode: component %s uses fallback bitrate (%d bps)
70 Alarm Minor Configuration inconsistency: configured component bitrate range [%d-%d] should be in the range [%d-%d] for PID %d
71 Alarm Warning Software error: database incorrect version (%s)
72 Alarm Warning Software error: current software version integrity is not verified (%s)
73 Alarm Major Output overflow: %s
74 Alarm Undefined (Info) Version activation installation of version %s in progress
75 Alarm Undefined (Info) Version activation job upgrade in progress
76 Alarm Critical Database inconsistency: please contact [email protected]
77 Event Major Job restarted: database inconsistency detected and corrected
78 Event Critical Database inconsistency: data (setup, workflows, jobs, logs) from %s (UTC) are restored
79 Alarm Warning Signaling information not present: no Closed Caption descriptor in PMT of program number %d
80 Alarm Warning Software error: %s
81 Event Undefined (Info) Master change: %s
Electra VS - Version 05.10 567 User Manual - Rev. A Appendix E ’Logs’ — List of Logs
82 Event Warning Database inconsistency: %s data have been repaired
83 Alarm Major Bitrate overflow: %s bandwidth group %d overload (%d Mbps used instead of %d Mbps)
84 Alarm Major Link down: Switch %d (%s), NIC %s
85 Alarm Critical Provisioning error %s %s %s asset
86 Alarm Major Provisioning error %s %s %s asset
87 Alarm Critical Harware failure Switch %d (%s) is unreachable
88 Alarm Major Configuration inconsistency: configured decoder delay for the splicer (%d ms) is too low, the received video requires %d ms at least
89 Alarm Critical Buffer underflow
90 Event Undefined (Info) DNS resolution changed from %s to %s 91 Alarm Undefined (Info) Version activation: upgrade in progress for job %lu 92 Event Undefined (Info) Connection established RTMP client %s is connected 93 Alarm Major Stream error: stream name %s is not the configured one, the %s stream is refused 94 Alarm Warning Bypass mode: bypass relay activated in job configuration 95 Alarm Major Configuration inconsistency: bypass relay unavailable on this output 96 Alarm Major Performance degraded: insufficient resource '%s'. %s 97 Alarm Major Configuration inconsistency: level name %s does not exist (playlist files will not be imported by %s) 98 Alarm Major File error: file generation aborted due to key server connection timeout (%d seconds)
99 Alarm Critical Stream error: RTMP multi-stream inputs are not supported
100 Event Critical Software error: a component is blocked, job is aborted
101 Event Major Video standard mismatch: %s level changed from %s to %s, risk of overflow
102 Event Major Video standard mismatch: %s profile changed from %s to %s, risk of overflow
103 Alarm Warning Card fragmentation: no new UHD encoding could be started on this node. It could be resolved by restarting jobs %s or %s 104 Alarm Undefined Configuration inconsistency: input dynamic range (%s) is (Warning) not the configured one (%s)%s 105 Alarm Critical Stream error: audio input (%s)
106 Alarm Warning Network Element Report: %s
107 Event Warning Other %s
568 Electra VS - Version 05.10 User Manual - Rev. A Appendix E ’Logs’ — List of Logs
108 Event Warning File error: maximum number of logo files (%d) reached in %s folder
1000 Event Undefined (Info) ECM channel crypto period %d s, channel %d, stream %d
1001 Alarm Warning Scrambling in degraded mode: ECM channel extended crypto period for channel %d, stream %d
1002 Alarm Warning Connection establishment error
1003 Alarm Warning Communications protocol error: %s
1004 Alarm Warning Scrambling error: %s (stream could not be decrypted)
2000 Alarm Critical Hardware failure: %s
2001 Alarm Critical Ventilation failure: %s
2002 Alarm Undefined (Major) High temperature: %s
2003 Alarm Critical Power supply failure: %s
2004 Alarm Critical Hardware failure: %s
2005 Alarm Critical Disk failure: %s
2006 Alarm Critical Hardware failure: accessing problem
3000 Alarm Critical Connection establishment error
3001 Alarm Critical Communications protocol error: %s
3002 Alarm Critical Connection establishment error: %s
4000 Event Critical Hot folder job operation error %s by %s: %s
5000 Alarm Major Component processing problem: %s
5001 Alarm Major Configuration inconsistency: %s
5002 Event Critical Erroneous workflow version description of workflow %s has been modified but not its version %s
5003 Event Undefined (Info) Job deleted maximum number (%d) of completed jobs reached, %d have been automatically deleted
6000 Alarm Undefined (Info) Simulation running %s by %s
7000 Event Undefined (Info) Recovery point operation %s %s by ’%s’
7001 Event Warning Recovery point operation error %s %s by ’%s’
7002 Alarm Warning Recovery point operation error periodic, recovery point cannot be generated
7003 Alarm Warning Recovery point operation %s restoration in progress
7004 Alarm Warning Software error: database recovery unavailable, please contact support
7005 Alarm Warning Recovery point operation: partition is full, remove useless manuals RPs if possible 8000 Event Undefined (Info) Manual switch on backup job %lu
Electra VS - Version 05.10 569 User Manual - Rev. A Appendix E ’Logs’ — List of Logs
8001 Event Critical Manual switch failure SDI sync_loss on backup job %lu 8002 Event Undefined (Info) Automatic switch on backup job %lu (main job cannot run) 8003 Event Undefined (Info) Automatic switch on backup job %lu (SDI sync_loss on main job) 8004 Event Undefined (Info) Manual switch‐back main job is active 8005 Event Critical Manual switch‐back failure SDI sync_loss on main 8006 Event Undefined (Info) Automatic switch‐back on main job (SDI sync_loss on backup job %lu) 8007 Event Undefined (Info) Automatic switch‐back on main job (backup job %lu cannot run) 8008 Event Undefined (Info) Automatic switch‐back main job is active 8009 Event Undefined (Info) Job deletion from node(s) %s in order to create/update
8010 Event Undefined (Info) Automatic switch-back on main job (resource of backup job %lu required for another job) 9000 Alarm Warning Inconsistent media: frame rate (%s fps) different from configured one (%s fps), segment %s will be skipped if problem not fixed 9001 Event Critical Segment skipped frame rate (%s fps) different from configured one (%s fps), segment %s skipped 9002 Alarm Warning Inconsistent media: codec (%s) different from configured one (%s), segment %s will be skipped if problem not fixed 9003 Event Critical Segment skipped codec (%s) different from configured one (%s), segment %s skipped 9004 Alarm Warning Inconsistent media: video size (%s) greater than configured one (%s), segment %s will be skipped if problem not fixed 9005 Event Critical Segment skipped video size (%s) greater than configured one (%s), segment %s skipped 9006 Alarm Warning Configuration inconsistency: overlay template '%s' referenced by overlay '%s' not found. Overlay will be skipped if problem not fixed 9007 Event Critical Overlay skipped overlay template '%s' referenced by overlay '%s' not found. 9008 Alarm Warning Missing media: %s '%s' missing in %s, segment %s will be skipped if problem not fixed 9009 Event Critical Segment skipped missing media %s '%s' in %s, segment %s is skipped 9010 Alarm Warning Duplicated media: %s '%s' duplicated in %s, segment %s will be skipped if problem not fixed
570 Electra VS - Version 05.10 User Manual - Rev. A Appendix E ’Logs’ — List of Logs
9011 Event Critical Segment skipped duplicated media %s '%s' in %s, segment %s is skipped 9012 Alarm Warning Media in error: %s '%s' in error %s, segment %s will be skipped if problem not fixed 9013 Event Undefined Segment skipped media %s '%s' in error %s, segment %s is skipped 9014 Alarm Undefined (Info) Software error: splicer '%s' not found %s 9015 Event Undefined (Info) Software error: splicing information not found '%s' 9016 Event Undefined (Info) Configuration inconsistency: segment '%s' invalid (%s) and discarded 9017 Event Warning Splice precision %s for segment %s. %s 9018 Alarm Warning Configuration inconsistency: duration (%s) is different from expected one (%s) for %s %s 10000 Event Undefined (Info) Configuration change network interfaces profile '%s'
10001 Event Undefined (Info) Configuration change network interfaces profile '%s' has been replaced by '%s' 10002 Alarm Warning Resource at or nearing capacity: no more internal DHCP address available in order to add new node in system 10003 Alarm Warning Loss of redundancy: synchronization with Master node in progress, node not yet ready to become Master 10004 Alarm Warning Loss of redundancy: failure of synchronization with Master node (%s)
10005 Event Undefined (Info) Configuration change node is added by %s
10006 Event Undefined (Info) Configuration change node is removed by %s
a values in parentheses are default values
Event type log: Log raised and cleared immediately allowing an event to be monitored. Undefined level: The level will be determined according to the context.
Electra VS - Version 05.10 571 User Manual - Rev. A Appendix E ’Logs’ — List of Logs
572 Electra VS - Version 05.10 User Manual - Rev. A Appendix F Network Settings
Introduction
This chapter provides detailed information on the network configuration for different deliveries of the Electra VS.
In this Chapter
’Hardware Delivery - 6RU and 10RU devices’...... page 574
’Internal Switches & Software Configuration Consistency’..page 575
’Flex10’ ...... page 576
’Multicast Management’...... page 579
’Heterogeneous System Configuration’ ...... page 579
’Interface Bitrates’ ...... page 580
’Hardware Delivery - 1RU device’ ...... page 582
’Network Configuration’ ...... page 582
’Software Only Delivery’ ...... page 583
’Virtualization Delivery’ ...... page 583
Electra VS - Version 05.10 573 User Manual - Rev. A Appendix F ’Network Settings’ — Hardware Delivery - 6RU and 10RU devices
Hardware Delivery - 6RU and 10RU devices
Blades
Internal Switches (Flex10)
Each blade has two physical 10 Gbps interfaces, also called pNIC. The use of Flex10 modules, i.e. the internal switches of the blade center, allows to demultiply these interfaces to reach a number of 8 interfaces, or FlexNIC: 4 by physical interface.
The allocation of the 10 Gbps of a physical interface between the 4 FlexNIC is customizable. To make this bitrate allocation, you must use the HP interface to configure the Flex10:
10RU device: one physical interface is on the first Flex10, the other is on the second Flex10.
6RU device: both physical interfaces are on the first Flex10. We add a mezzanine to the blade so as to have also two physical interfaces on the second Flex10. In total, there are consequently 16 FlexNIC.
To know how to use the HP interface, refer to the HP Virtual Connect for c-Class BladeSystem - User Guide provided on the DVD-ROM.
Interface Bonding
Interfaces are grouped in bonds, in fail-over mode, with the main interface always being on the first Flex10.
The currently active NIC remains active while it is up, there is no automatic restore when the other NIC becomes up again.
10RU Device
Each blade has 8 network interfaces. On the Flex10, they are named LOM:1-a to LOM:4-a and LOM:1-b to LOM:4-b; a blades being on the first Flex10 and b blades on the second one.
On the 10RU device, interfaces are defined as follows:
Interface 1: LOM:1-a & LOM:2-a
Interface 2: LOM:1-b & LOM:2-b
Interface 3: LOM:1-c & LOM:2-c
Interface 4: LOM:1-d & LOM:2-d
574 Electra VS - Version 05.10 User Manual - Rev. A Appendix F ’Network Settings’ — Hardware Delivery - 6RU and 10RU devices
6RU Device
Each blade has 16 network interfaces. On the Flex10, they are named LOM:1-a to LOM:8-a and LOM:1-b to LOM:8-b; a blades being on the first Flex10 and b blades on the second one.
On the 6RU device, associations between interfaces in the software application and the FlexNIC in the Flex10 are defined as follows:
Interface 1: LOM:1-a & MEZZ1:1-a
Interface 2: LOM:2-a & MEZZ1:2-a
Interface 3: LOM:1-b & MEZZ1:1-b
Interface 4: LOM:2-b & MEZZ1:2-b
Interface 5: LOM:1-c & MEZZ1:1-c
Interface 6: LOM:2-c & MEZZ1:2-c
Interface 7: LOM:1-d & MEZZ1:1-d
Interface 8: LOM:2-d & MEZZ1:2-d
VLAN Tagging
When using VLAN tagging to have more than four interfaces in total in the 10RU device, or eight interfaces in total in the 6RU device, it is imperative that the configuration be consistent with the Flex10 configuration.
Internal Switches & Software Configuration Consistency
The configuration of the blade internal switches (Flex10) must be consistent with the network configuration in the software application
Here are the main configuration principles:
Interfaces 1 are reserved to the system network of the blade center, for management.
In the software application, it is possible to define networks of internal data and external data.
On the Flex10:
A private network forbids the dialog between two blades of the blade center.
Internal data networks and the System network must never be set as private network.
Electra VS - Version 05.10 575 User Manual - Rev. A Appendix F ’Network Settings’ — Hardware Delivery - 6RU and 10RU devices
External data networks must be set as private networks. For example in an IP TV configuration in which blades generate multicast, this prevents the multicast from affecting the blades. Otherwise, if an external data network is not set as a private network, as long as no client has sent an IGMP request to receive the stream, the network is flooded by the Flex10 on all interfaces.
Flex10
External Connector Description
FLEX10
X1 to X6, used with SFP couplers, can be Gbps copper/optical interfaces or 10 Gbps optical interfaces. X1 can also be used as a link between several blades. It is not recommended for Electra VS needs to use the specific stacking cable (see section ’Heterogeneous System Configuration’ on page 579).
FLEX10-D
X1 to X10, used with SFP couplers, can be Gbps copper/optical interfaces or 10 Gbps optical interfaces. X1 can also be used as a link between several blades (see section ’Heterogeneous System Configuration’ on page 579).
Grouping Possibilities
It is possible to group:
several LANs on one unique external connector. To do so, you must create a Shared uplink set using VLAN tagging.
several external connectors on one unique LAN (trunk): this lets you increase the bandwidth.
For more information on these aspects, refer to the HP Virtual Connect - Ethernet Networking Scenario Cookbook.
Flex10 Configuration
On the DVD-ROM, you will find a folder named Flex10. This folder contains configuration files for the Flex10 modules.
The format of these files is CLI.
How to Use a Configuration File 1. Open an SSH session with the active Flex10 (for such a session, you can use for example the free tool "putty").
576 Electra VS - Version 05.10 User Manual - Rev. A Appendix F ’Network Settings’ — Hardware Delivery - 6RU and 10RU devices
Login and password are required to establish the connection. 2. When the SSH session is established, open the configuration file with MS Wordpad. 3. Copy all the content of the configuration file (using CTRL-A then CTRL-C, for example), and copy it into the SSH session. 4. Check that all the instructions are correctly executed (reports are given on the SSH session).
The configuration file is also applied to the other Flex10 of the enclosure.
Description of Configuration Files
Factory Configuration Files
Factory_config_Flex10_C3000_10.txt
Factory_config_Flex10_C3000_10D.txt
Factory_config_Flex10_C7000_10.txt
Factory_config_Flex10_C7000_10D.txt
When you received the Electra VS, the Flex10 was configured with a default configuration.
The configuration files listed above contain this factory configuration.
There is two files for the HP C3000 enclosure and for the HP C7000 enclosure depending on flex10 type (Flex10 or Flex10D).
Files to Help You Apply your Own Configuration
First_part_config_Flex10_CX000.txt
Last_part_config_Flex10_CX000.txt
When you want to configure the Flex10, it can be easier to reset the configuration at first and then build your own configuration.
These files will help you do this.
The steps are:
Preliminary: you shall know exactly the network topology you want to apply:
Which Shared Uplink Sets (SUS)?
Which LANs? Using VLAN tagging?
Which connectors on the Flex10 panel, for which usage?
Which blade interfaces, for which LANs? Using VLAN tagging?
Electra VS - Version 05.10 577 User Manual - Rev. A Appendix F ’Network Settings’ — Hardware Delivery - 6RU and 10RU devices
Step 1: Reset the Flex10 configuration. To do this, open an SSH session to the active Flex10, and enter successively the following commands: poweroff server * remove profile * delete domain import enclosure UserName=Administrator Password=xxxxxxx (replace xxxxxxx by the password of the on-board administrator). Step 2: Apply the first part configuration file (use either C7000 or C3000 one, depending on your enclosure). This step automatically:
Creates the 2 LANs that are absolutely necessary to the Electra VS: System private LAN, and Internal data LAN.
Creates a server profile that contains only these 2 LANs.
Applies this server profile to the first blade of the enclosure.
Step 3: Open the Web interface on the Flex10, and perform the following actions: 1. Create the Shared Uplink Sets (SUS) you need. 2. Create the LANs you need: Control, data, etc.
A LAN can be associated to an SUS at creation, but not after.
3. Do not forget to configure correctly the external LANs: SmartLink and Private Network feature shall be activated, and a LAN shall be accessible by a blade on both NICs of a bond. 4. Edit the server profile, and configure it with the LANs you created.
Step 4: Apply the last part configuration file. This step automatically:
Creates new profiles identical to the first profile.
Assigns these profiles to the other blades of the enclosure.
As usual, when the configuration is finished, save it carefully in a file (you can use the "show config" command).
578 Electra VS - Version 05.10 User Manual - Rev. A Appendix F ’Network Settings’ — Hardware Delivery - 6RU and 10RU devices
Multicast Management
IGMP snooping is enabled on the two Flex10, with the default time-out of 260 seconds.
IGMP snooping must not be disabled as it is mandatory on the Internal data network. If disabled, the system will not be operational.
To ensure a proper multicast management, the network must contain an IGMP Querier. You must thus ensure that one of your switches acts as such (the Flex10 cannot have this role).
External LANs are configured as private networks, which forbids any traffic between blades. In an IP TV environment, this prevents from flooding a multicast stream in output of a blade towards all the other blades.
Heterogeneous System Configuration
It is possible to link blade centers and 1RUs via an external 1 Gbps switch, at least considering the system private LAN.
To ensure a proper multicast management in the system private LAN, it must contain an IGMP Querier. You must thus ensure that one of your switches acts as such. The IP source of the IGMP querier shall exist in the system private LAN.
Figure F-1. Linking blade centers via an external 1 Gbps switch
Electra VS - Version 05.10 579 User Manual - Rev. A Appendix F ’Network Settings’ — Hardware Delivery - 6RU and 10RU devices
Table 1. ‘Linking 10RU or 6RU blade centers via an external switch’ diagram key
Item Description
1 and 2 Link between switch 1 and switch 2
3 Enclosure 1 (10RU)
4 Enclosure 2 (10RU)
5 Enclosure 3 (10RU)
6 Enclosure 4 (10RU)
8 Link to switch 2
9 Internal Dual 10Gb Stacking links
An internal data LAN must not be shared on several blade centers: each blade center must have its own internal data LAN.
Interface Bitrates
You may adjust the bitrates for the interfaces.
Bitrate Allocation on 10RU Interfaces
You may adjust the bitrates of the four interfaces, for a total of 10 Gb/s.
The factory configuration is as follows:
Interface 1: 2 Gb/s
Interface 2: 3 Gb/s
Interface 3: 1 Gb/s
Interface 4: 4 Gb/s
Bitrate Allocation on 6RU Interfaces
You may adjust the bitrates of the eight interfaces, for a total of 20 Gb/s.
The factory configuration is as follows:
Interface 1: 2 Gb/s
Interface 2: 3 Gb/s
Interface 3: 1 Gb/s
Interface 4: 2.4 Gb/s
Interface 5: 3.5 Gb/s
Interface 6: 2.3 Gb/s
580 Electra VS - Version 05.10 User Manual - Rev. A Appendix F ’Network Settings’ — Hardware Delivery - 6RU and 10RU devices
Interface 7: 3.5 Gb/s
Interface 8: 2.3 Gb/s
Bitrate Allocation Rules
You can allocate these bitrates differently provided you respect the following principles:
Avoid reducing the System private LAN bitrate as it has a primary role in the blade center’s proper functioning.
If the Internal data bitrate is too much reduced, this creates additional restrictions for the load-balancer. The blade center risks being under-used, or it will be impossible to create some jobs that need to be allocated on several nodes.
Electra VS - Version 05.10 581 User Manual - Rev. A Appendix F ’Network Settings’ — Hardware Delivery - 1RU device
Hardware Delivery - 1RU device
Network Configuration
On 1RU devices, the factory network configuration is as follows:
Interface 1: LAN 10, System private LAN.
Interface 2: LAN 20, Management LAN.
Interface 3: LAN 30, Data LAN.
Interface 4: LAN 40, Data LAN.
Additional LANs, with VLAN tagging, are available: VLAN 11 (resp. 21, 31, 41) on interface 1 (resp. 2, 3, 4).
For a Electra VS made of several 1RU server, it is possible to add an Internal data network if you need to start jobs that can be split over several nodes. It is also necessary for a statmux that is split over several nodes.
By default each logical interface is composed of 2 physical interfaces that work in fail-over (bond): logical Interface INTF_1 is composed of the first NIC of each board, logical Interface INTF_2 is composed of the second NIC of each board, etc.
You can modify the Electra VS setup to remove the bonding. For example, NICi of first card can be independent from NICi of second card. Each time you remove a bond, you add one more logical interface.
In G8, when there are 2 octo SDI boards, there is only one network board. Bonding is configured to have physical interfaces linked per 2, so 2 logical interfaces. That means you have: logical Interface INTF_1 is composed of the first two NICs of the board logical Interface INTF_2 is composed of the last two NICs of the board.
You can remove the second bounding, in this case you have: logical Interface INTF_1 is composed of the first two NICs of the board logical Interface INTF_2 is linked to the third NIC of the board logical Interface INTF_3 is linked to the last NIC of the board.
582 Electra VS - Version 05.10 User Manual - Rev. A Appendix F ’Network Settings’ — Software Only Delivery
Software Only Delivery
The network recommendations are described in the IP architecture documentation delivered in the DVD-ROM with the product.
Virtualization Delivery
The network recommendations are described in the IP architecture documentation delivered in the DVD-ROM with the product.
Electra VS - Version 05.10 583 User Manual - Rev. A Appendix F ’Network Settings’ — Virtualization Delivery
584 Electra VS - Version 05.10 User Manual - Rev. A Appendix G ESAM
Introduction
This chapter provides information on how Electra VS is implementing CableLabs® ESAM (Event Signaling and Management).
In this Chapter
’ESAM Implementation’ ...... page 585
Electra VS - Version 05.10 585 User Manual - Rev. A Appendix G ’ESAM’ — ESAM Implementation
ESAM Implementation
The Electra VS is implementing the API Signal Confirmation and Conditioning for CableLabs® ESAM (Event Signaling and Management). Such standard has been developed to facilitate ad-insertion, black out management and slate insertion on WebTV applications.
The following picture provides a typical architecture for OTT with a POIS (Placement Opportunity Information System) and an external packager.
Figure G-1. Typical architecture for OTT with a POIS and an external scrambler
Step 1 a. Electra VS is sending a message indicating an SCTE command in the input stream to the POIS.
b. The POIS is notifying the Electra VS of the action to be taken: - Keep the SCTE 35 command as it is. - Replace the SCTE command by another one. - Delete the SCTE 35 command.
Even if there is no SCTE 35 in input of the Electra VS, the POIS can ask the Electra VS to insert an SCTE 35 command in the MPEG-2 TS stream.
Step 2 a. Electra VS inserts an SCTE 35 command according to the POIS request. b. Electra VS ensures that all the profiles are synchronized (EBP standard) in the output. In addition, it also inserts an IDR frame on the right temporal timing (according to the SCTE command) to authorize a frame accurate insertion of advertisement, black out, etc. by the external packager.
Please note that all interfacing with POIS are requiring dedicated adjustments.
586 Electra VS - Version 05.10 User Manual - Rev. A Appendix H Aspect Ratio Conversions
Introduction
This chapter provides the default conversions performed and the AFD value set according to the input AFD and aspect ratio.
In this Chapter
’Conversions according to input AFD and output display aspect ratio’ ...... page 588
’Conversions according to default strategies and output display aspect ratio’ ...... page 590
’Specific output AFD according to source or output display aspect ratio’...... page 591
Electra VS - Version 05.10 587 User Manual - Rev. A Appendix H ’Aspect Ratio Conversions’
Conversions according to input AFD and output display aspect ratio
Table H-1. Conversion according to input AFD and output display aspect ratio
Input AFD Conversion according to output display aspect ratio
16:9 4:3
2 < 16:9 16:9 > 16:9 Box 16:9 Top
AFD 10 (16:9 centre) 3 < 14 :9 14 :9 > 14 :9 Box 14:9 (Top)
AFD 11 (14:9 centre) 4 < 16 :9 16:9 > 16 :9 Box > 16:9 (Centre)
AFD 4 (Box > 16:9 centre) 8 < Input DAR Input DAR > Input DAR As the coded frame
AFD according to source display AFD 8 (As the coded AFD according to source display aspect ratio (see table below) frame) aspect ratio (see table below) 9 < 4 :3 4 :3 > 4 :3 4:3 (Centre)
AFD 9 (4:3 centre) 10 < 16 :9 16 :9 > 16 :9 16:9 (Centre)
AFD 10 (16:9 centre)
588 Electra VS - Version 05.10 User Manual - Rev. A Appendix H ’Aspect Ratio Conversions’
11 < 14:9 14:9 > 14:9 14:9 (Centre)
AFD 11 (14:9 centre) 13 < 4:3 4:3 > 4:3 4:3 (14:9 centre)
AFD 13 (4:3 with 14:9 centre) 14 < 16 :9 16 :9 > 16 :9 16:9 (14:9 centre)
AFD 14 (16:9 with 14:9 centre) 15 < 4:3 4:3 4:3 < < 16:9 16:9 > 16:9 16:9 (4:3 centre)
AFD according to output AFD 9 (4:3 centre) display aspect ratio (see AFD 15 (16:9 with 4:3 centre) table below)
Electra VS - Version 05.10 589 User Manual - Rev. A Appendix H ’Aspect Ratio Conversions’
Conversions according to default strategies and output display aspect ratio
Table H-2. Conversion according to default strategies and output display aspect ratio
Default conversion to narrower display aspect ratio Input frame Letter box Center cut Full screen
AFD according to source AFD according to output display aspect ratio (see table display aspect ratio (see Referbelow) to Table H-4 below tableRefer below)to Table H-3 below
Default conversion to wider display aspect ratio Input frame Pillar box Full screen
AFD according to source display aspect AFD according to output display aspect ratio (seeRefer table to Table below) H-3 below ratio Refer(see table to Table below) H-4 below
590 Electra VS - Version 05.10 User Manual - Rev. A Appendix H ’Aspect Ratio Conversions’
Specific output AFD according to source or output display aspect ratio
Table H-3. Specific output AFD according to source display aspect ratio
Output AFD according to source display aspect ratio
Display aspect ratio 4:3 14:9 16:9 > 16:9 Other
AFD 911104No AFD
Table H-4. Specific output AFD according to output display aspect ratio
Output AFD according to output display aspect ratio
Display aspect ratio 4:3 14:9 16:9 > 16:9 Other
AFD 911104 8
Electra VS - Version 05.10 591 User Manual - Rev. A Appendix H ’Aspect Ratio Conversions’
592 Electra VS - Version 05.10 User Manual - Rev. A Glossary
100/1000Base-T An Ethernet standard designed to generate, monitor and capture 100/1000 Ethernet traffic.
4:2:0 A chrominance sub-sampling system in which the difference signals are sampled on alternate lines at half the luminance rate.
4:2:2 A chrominance sub-sampling system in which the difference signals are sampled on all lines at half the luminance rate.
AAC Advanced Audio Compression algorithm that has been ratified for both MPEG-2 (ISO/IEC 11818-7) and MPEG-4 (ISO/IEC 14496-3).
AAC-LC Low Complexity-Advanced Audio Coding.
AC-3 Audio Coding 3. AC-3 is a digital audio encoding, also called Dolby Digital, technique developed by Dolby® for multi-channel sound applications.
AFD Active Format Descriptor. Standard set of codes that can be sent in the MPEG video stream or in the baseband SDI video signal that carries information about their aspect ratio and active picture characteristics.
AGC Automatic Gain Control.
API Application Programming Interface Specification intended to be used as an interface by software components to communicate with each other.
AVC Advanced Video Coding.
BISS Basic Interoperable Scrambling System. BISS is a satellite signal scrambling system developed by the European Broadcasting Union and a consortium of hardware manufacturers.
Buffer A memory store used to provide a consistent rate of data flow.
BW Bandwidth: a measure of the width of a range of frequencies, measured in hertz.
CA Conditional Access. System to control subscriber access to services, programs and events.
CABAC Context-based Adaptive Binary Arithmetic Coding CABAC is a form of entropy coding used in H.264 video encoding. It is notable for providing much better compression than CAVLC but is more computationally expensive. CABAC is not supported in Baseline and Extended profiles.
Electra VS - Version 05.10 593 User Manual - Rev. A Glossary
CAT Conditional Access Table CAT table is used for conditional access to the streams. It provides association with the EMM stream.
CAVLC Context Adaptive Variable Length Coding. CAVLC is a form of entropy coding used in H.264 video encoding. CAVLC has lower coding efficiency than CABAC but is less computationally expensive.
CBR Constant Bitrate. The bit-rate of the bitstream is constant.
CC Close Caption.
Chrominance Chrominance (chroma or C for short) is the signal used in video systems to convey the information of the picture, separately from the accompanying luma signal (or Y for short).
CIF Common Intermediate Format. A format used to standardize the horizontal and vertical resolutions in pixels of YCbCr sequences in video signals, commonly used in video teleconferencing systems (video size: 352p x 288p).
Closed Caption A TV picture subtitling system used with 525-line analog transmissions.
Codec Compressor-Decompressor. A codec is a device or computer program capable of encoding and/or decoding a digital data stream or signal.
Compression The process of removing redundant data from audio or video streams to reduce the amount of data transferred or stored.
CPU Central Processing Unit.
CrCb Digital difference signals. These signals, in combination with the luminance signal (Y), define the and brightness of each picture element (pixel) on a TV line. See: Chrominance.
CW Control Word.
CWG Control Word Generator.
DAR Display Aspect Ratio
DASH Dynamic Adaptive Streaming over HTTP
dB Decibel The decibel is a logarithmic unit that indicates the ratio of a physical quantity (usually power or intensity) relative to a specified or implied reference level. A ratio in decibels is ten times the logarithm to base 10 of the ratio of two power quantities. A decibel is one tenth of a bel, a seldom-used unit.
dBFS Decibel Full Scale
De-blocking Filter An in-loop de-blocking filter is designed to smooth out artifacts introduced by the compression process in the reconstructed image in both the encoder and decoder.
Decoder The device containing the electronic circuitry necessary to decode encrypted signals. Some Decoders features a receiver.
DNS Domain Name Server
594 Electra VS - Version 05.10 User Manual - Rev. A Glossary
DRC Dynamic Range Control.
DTS Decoding Time Stamp A field that may be present in a PES packet header that indicates the time that an access unit is to be decoded in the system target Decoder.
DTVCC Digital Television Closed Captioning.
DVB Digital Video Broadcasting The Digital Video Broadcasting Project (DVB) is an industry-led consortium of around 250 broadcasters, manufacturers, network operators, software developers, regulatory bodies and others in over 35 countries committed to designing open technical standards for the global delivery of digital television and data services. Services using DVB standards are available on every continent with more than 500 million DVB receivers deployed.
EBU European Broadcast Union.
ECM Entitlement Control Message. Private Conditional Access information that specifies control words and possibly other stream-specific, scrambling, and/or control parameters.
ECMG ECM Generator
Elementary Stream A generic term for a coded bit-stream, be it video, audio or other.
EMC Electromagnetic Compatibility.
EMM Entitlement Management Message. Private Conditional Access information that specifies the authorization level or services of specific decoders.
Encryption Encoding of a transmission to prevent access without the appropriate decryption equipment and authorization.
EPG Electronic Program Guide. Provides users of television, radio, and other media applications with continuously updated menus displaying scheduling information for current and upcoming programming.
ES Elementary Stream A generic term for a stream of data of one particular type. Typically these streams are of Video or Audio Types.
ESAM (Real-time) Event Signaling and Management API specification from CableLabs®.
Ethernet The most widely used local area network (LAN) defined by the IEEE as the 802.3 standard.
FEC Forward Error Correction. A system of error control for data transmission, whereby the sender adds systematically generated redundant data to its messages. The carefully designed redundancy allows the receiver to detect and correct a limited number of errors occurring anywhere in the message without the need to ask the sender for additional data. FEC enables the receiver to correct errors without the need for a reverse channel to request retransmission of data, but this advantage is at the cost of a fixed higher forward channel bandwidth
Electra VS - Version 05.10 595 User Manual - Rev. A Glossary
Field For an interlaced video signal, a "field" is the assembly of alternate lines of a frame. Therefore, an interlaced frame is composed of two fields, a top field and a bottom field.
Frame A frame contains lines of spatial information of a video signal. For progressive video, these lines contain samples starting from one time instant and continuing through successive lines to the bottom of the frame. For interlaced video a frame consists of two fields, a top field and a bottom field. One of these fields will commence one field later than the other.
FTP File Transfer Protocol. It is a standard network protocol used to copy a file from one host to another over a TCP-based network.
GPI General Purpose Interface.
GUI Graphical User Interface It is a type of user interface that allows users to interact with electronic devices with images rather than text commands. A GUI represents the information and actions available to a user through graphical icons and visual indicators such as secondary notation, as opposed to text-based interfaces, typed command labels or text navigation.
H.264 ITU/ETSI name for MPEG-4 Part-10 (ISO/IEC 14496-10).
H.265 ITU/ETSI name for MPEG-H Part-2 (ISO/IEC 23008-2).
HbbTV Hybrid Broadcast Broadband TV Both an industry standard and promotional initiative for hybrid digital TV to harmonize the broadcast, IPTV, and broadband delivery of entertainment to the end consumer through connected TVs (Smart TVs) and set-top boxes.
HD High Definition.
HD-SDI 1.5 Gbps High-Definition Serial Digital Interface.
HDTV High Definition Television.
HE-AAC High-Efficiency Advanced Audio Encoding. A lossy data compression scheme for digital audio defined as a MPEG-4 Audio profile in ISO/IEC 14496-3. There are two types of HE-AAC: - HE-AAC = AAC+ = AAC-LC + SBR (Spectral Band Reconstitution) - HE-AACv2 = eAAC+ = AAC-LC + SBR + PS (Parametric Stereo)
HEVC High Efficiency Video Coding. Refer to H.265
HTML Hyper Text Markup Language. HTML is the predominant markup language for web pages. That is the basic building-blocks of web pages.
HTTP Hyper Text Transfer Protocol.
HTTPS Hyper Text Transfer Protocol Secure.
I-Frame Intracoded Frame. A frame, which is coded using purely intracoding with reference to no other field or frame information. I frames provide a reference point for dependent P and B frames and allow random access into the compressed video stream.
596 Electra VS - Version 05.10 User Manual - Rev. A Glossary
I-Picture Refer to I-Frame.
ID Identifier
IDR Instantaneous Decoding Refresh. IDR pictures can be decoded without reference to previous frames.
IEC International Electrotechnical Committee.
IGMP Internet Group Management Protocol. IGMP is a communication protocol used by hosts and adjacent routers on IP networks to establish multicast group memberships. There are three versions of IGMP, as defined by "Request for Comments" (RFC) documents of the Internet Engineering Task Force (IETF). IGMPv1 is defined by RFC 1112, IGMPv2 is defined by RFC 2236 and IGMPv3 was initially defined by RFC 3376 but has since been superseded by RFC 4604.
IIS Internet Information Services. Web server application and set of feature extension modules created by Microsoft for use with Microsoft Windows. IIS 7.5 supports HTTP, HTTPS, FTP, FTPS, SMTP and NNTP.
IP Internet Protocol.
IP Address A 32-bit (IPv4) or 128-bit (IPv6) numerical identifier for a specific TCP/IP host device on a network, that represents the sender or receiver of information sent across the network.
IRD Integrated Receiver Decoder. The IRD is the official name for the satellite receiver, which has a built-in decoder for unscrambling subscription channels. It is also known as Set-Top Box for the cable.
ISO International Standards Organization.
ITU-R International Telecommunications Union - Radio. Formerly CCIR. Deals with the standardization of wireless communication.
ITU-T International Telecommunications Union - Telecommunications. Formerly CCITT. Produces global telecommunication standards, and defines tariff and accounting principles.
Joint Stereo An audio mode in which the left and right channels of audio are encoded into one channel. This mode is used to reduce bandwidth needs, and thus improve compression efficiency.
JPEG Joint Photographic Experts Group. Name of the committee that created the JPEG standard (and also other standards). The JPEG standard specifies the codec, which defines how a still image is compressed into a stream of bytes and decompressed back into an image.
LAN Local Area Network. A local area network is a network that connects computers and devices in a limited geographical area such as home, school, computer laboratory or office building.
LATM Low-overhead Audio Transport Multiplex. LATM is part of the method to encapsulate HE-AAC audio into transport stream.
Electra VS - Version 05.10 597 User Manual - Rev. A Glossary
LC-AAC Low Complexity-Advanced Audio Coding.
LCD Liquid Crystal Display.
LED Light Emitting Diode.
LFE Low Frequency Effects
LOAS Low-overhead Audio Stream LOAS is part of the method to encapsulate HE-AAC audio into a transport stream.
LUFS Loudness Unit relative to Full Scale
M In a GOP (Group Of Picture), M is the distance between successive P-Frames.
Macroblock A area of the TV picture. Macroblocks are usually composed of two or more blocks of pixels. The size of a block depends on the codec and is usually a multiple of 4. In MPEG-2 the size is fixed at blocks of 8x8 pixels. In H264 the overarching macroblock size is fixed at 16x16 pixels, but this is broken down into smaller blocks or partitions which are either 4, 8, 12 or 16 pixels by 4, 8, 12 or 16 pixels.
MBAFF MacroBlock Adaptive Frame Field coding. Use a macroblock pair structure for pictures coded as frames.
MIB Management Information Base. SNMP collects management information from devices on the network and records the information in a management information base. The MIB information includes device features, data throughput statistics, traffic overloads, and errors.
MPTS Multiple Programs Transport Stream
MTU Maximum Transmission Unit: The size of the largest packet that a network protocol can transmit.
Multicast Process where a single stream is served from one source to multiple receivers. The multicast address range is: 224.0.0.0 - 239.255.255.255.
NMS Network Management System.
NTP Network Time Protocol.
Packet - In networks, a unit of data transmitted over a packet-switching network. A packet consists of a header followed by a number of contiguous bytes from an elementary data stream. - In transport streams, a packet is a small, fixed-size data quantum.
PAFF Picture Adaptive Frame Field coding. Allows a freely selected mixture of pictures coded either as complete frames where both fields are combined together for encoding or as individual single fields.
PCM Pulse Code Modulation PCM is a modulation technique. It is a digital representation of an analog signal where the magnitude of the signal is sampled regularly at uniform intervals. Every sample is quantized to a series of symbols in a digital code, which is usually a binary code.
598 Electra VS - Version 05.10 User Manual - Rev. A Glossary
PCR Program Clock Reference. A time stamp used in digital video compression that indicates the system time clock’s (STC) value the instant the time stamped packet leaves the encoder. In the Moving Pictures Experts Group 2 (MPEG-2) system the digital video source is clocked at 27 MHz and the decoder must generate the same 27 MHz clock so that the encoder and decoder clocks are synchronized. These clocks are called System Time Clocks (STC). To synchronize the decoder, the encoder sends a PCR to the decoder. The decoder receives the packet and compares the STC value with its own STC counter value. If the values are the same then no adjustment is needed but if the two values are different, the decoder must either reset, speed up, or slow down its STC.
PES Packetized Elementary Stream A specification in the MPEG-2 Part 1 (Systems) (ISO/IEC 13818-1) and ITU-T H.222.0[1][2] that defines carrying of elementary streams in packets within MPEG program streams and MPEG transport streams [3]. The elementary stream is packetized by encapsulating sequential data bytes from the elementary stream inside PES packet headers.
PID Packet Identifier A unique integer value used to identify the contents of an MPEG-2 Transport Stream packet (Video component PID, Audio component PID, etc.).
Profile A defined subset of the syntax specified in the MPEG-2 or MPEG-4 video coding specification.
PMT Program Map Table. A mandatory MPEG-2 PSI table. Each service has a PMT. It lists the service component parts (elementary streams of video, audio, location of the PCR fields, etc.).
POIS Placement Opportunity Information System. POIS is defined in the Real-time Event Signaling and Management API specification (ESAM) from CableLabs®.
PSU Power Supply Unit.
QCIF Quarter Common International Format. To have one fourth of the area as "quarter" implies the height and width of the frame are halved (video size: 176p x 144p).
QSIF Quarter Screen International Format. To have one fourth of the area as "quarter" implies the height and width of the frame are halved (video size:160 x 120 pixels (NTSC) or 192 X 144 pixels (PAL).
QVGA Quarter Video Graphics Array. QVGA is a popular term for a computer display with 320×240 display resolution.
R, G, B Red, Green, Blue.
Resolution Determined by the number of pixels displayed per line or for a given area.
RTP Real Time Transport Protocol. This Protocol defines a standardized packet format for delivering audio and video over IP networks.
Electra VS - Version 05.10 599 User Manual - Rev. A Glossary
RU Rack Unit. It is a unit of measure used to describe the height of equipment intended for mounting in a 19-inch rack or a 23-inch rack. One rack unit is 1.75 inches (44.45 mm) high.
Scrambling Alteration of the characteristics of a television signal in order to prevent unauthorized reception of the information in clear form.
SBR Spectral Band Replication. SBR is a tool used in HE-AAC for broadcast transmissions.
SD Standard Definition.
SD-SDI 270 Mbps Standard-Definition Serial Digital Interface.
SDI Serial Digital Interface.
SDTV Simple Definition Television.
SID Slide-out System Insight Display. Active Health Indicator provided by HP on the front panel of their 1RU server to indicate equipment status.
SMPTE Society of Motion Picture and Television Engineers. A Standards Organization devoted to advancing theory and application in motion imaging, including film, television, video, computer imaging, and telecommunications.
SNMP Simple Network Management Protocol. SNMP provides a means to monitor and control network devices, and to manage configurations, statistics collection, performance, and security. SNMP network management is based on the client and server model. Each managed host runs a process called an agent. The agent is a server process that maintains the Management Information Base (MIB) database for the host. SNMP uses ports 161 and 162.
SPTS Single Program Transport Stream
StatMux Statistical Multiplexing Statistical multiplexing is a proven technique used to dynamically assign compression bitrates based upon video complexity and motion requirements of individual channels. The principle of statistical multiplexing is that a group or “pool” of encoders shares a fixed quantity of bandwidth. The bandwidth is allocated on a frame by frame basis by a centralized controller so the encoder with the most complex video is allowed to borrow more bandwidth from the pool of encoders with less difficult video.
STB Set-Top Box. A device that provides access to the Broadband broadcast or Internet and displays information on a TV screen.
TCP Transmission Control Protocol. One of the main protocols in TCP/IP networks. TCP enables two hosts to establish a connection and exchange streams of data. TCP guarantees delivery of data and packets, and will be delivered in the same order in which they were sent. While IP takes care of handling the actual delivery of the data, TCP takes care of keeping track of the individual units of data (called packets) that a message is divided into for efficient routing through the Internet.
600 Electra VS - Version 05.10 User Manual - Rev. A Glossary
TCP/IP Transmission Control Protocol/Internet Protocol Two interrelated protocols that are part of the Internet protocol suite. TCP operates on the OSI transport layer and breaks data into packets. IP operates on the OSI network layer and routes the packets. While IP takes care of handling the actual delivery of the data, TCP takes care of keeping track of the individual units of data (called packets) that a message is divided into for efficient routing through the Internet. TCP/IP allows the construction of very large networks with little central management.
TS Transport Stream. A multiplex of several Elementary Stream that are contained in packets.
UDP User Data Protocol. A connectionless protocol, like TCP, that runs on top of IP networks. Unlike TCP/IP, UDP/IP provides very few error recovery services, offering instead a direct way to send and receive datagrams over an IP network without acknowledgements for guaranteed delivery.
Unicast Unicast is communication between a single sender and a single receiver over a network.
UTC Coordinated Universal Time. UTC is the time standard by which the world regulates clocks and time. In casual use, UTC corresponds to Greenwich Mean Time (or GMT).
VBI Vertical Blanking Interval. In analog video, the interval after the last displayed line of video in a field and before the first displayed line of video in the next field, during which a television receiver will synchronize vertically.
VBR Variable Bit-Rate. VBR is an encoding method that is designed to achieve a better video quality vs. bitrate ratio than CBR (Constant Bit-Rate) encoding. This is achieved by continuously changing the bit rate during the encoding process depending on the picture complexity. Refer to Statmux.
VBV Video Buffering Verifier The video buffering verifier is a theoretical MPEG video buffer model used to ensure that an encoded video stream can be correctly buffered and played back at the decoder device.
VGA Video Graphics Array (640x480 pixels).
VLAN Virtual Local Area Network. A local area network with a definition that maps workstations on some other basis than geographic location (for example, by department, type of user, or primary application). The virtual LAN controller can change or add workstations and manage load balancing and bandwidth allocation more easily than with a physical picture of the LAN. Network Management System software keeps track of relating the virtual picture of the local area network with the actual physical picture. VLANs are based on logical instead of physical connections.
Electra VS - Version 05.10 601 User Manual - Rev. A Glossary
WSS Wide Screen Signalling. WSS is digital information embedded in the TV signal describing the qualities of the broadcast, in particular the intended aspect ratio of the image. This can be used by a widescreen TV to switch to the correct display mode. The WSS signal is placed in line 23 (PAL) and lines 20/283 (PAL-M and NTSC) and has 14 data bits.
Y (Luminance) Defines the brightness of a TV picture.
602 Electra VS - Version 05.10 User Manual - Rev. A Glossary
Electra VS - Version 05.10 603 User Manual - Rev. A www.harmonicinc.com Copyright 2017 Harmonic Inc. All rights reserved.