4400 Family User Manual

Transcription

1 4400 Family User Manual Inca Networks Inc Family User Manual Revision 2

2 Copyright 2016 Inca Networks, Inc. The information contained in this document is subject to change without notice. All rights reserved. The information contained in this document is proprietary and is protected by copyright. No part of this document may be reproduced in any form without the prior written consent of Inca Networks, Inc. Inca Networks and product model names are trademarks of Inca Networks, Inc. Inca Networks Inc Family User Manual Revision 2 2

3 IMPORTANT SAFETY INFORMATION WARNING REFER SERVICING TO QUALIFIED PERSONNEL. CAUTION TO REDUCE THE RISK OF ELECTRICAL SHOCK, OBSERVE STANDARD GROUNDING AND SAFETY PROCEDURES WHEN HANDLING AND OPERATING ELECTRICAL EQUIPMENT. CAUTION TO REDUCE THE RISK OF ELECTRICAL SHOCK, DO NOT REMOVE COVERS FROM THIS UNIT. THERE ARE NO USER-SERVICEABLE PARTS INSIDE. REFER SERVICING TO QUALIFIED PERSONNEL. CAUTION TO REDUCE THE RISK OF ELECTRICAL SHOCK, DO NOT EXPOSE THIS PRODUCT TO RAIN OR MOISTURE. CAUTION THE 4420 AND 4430 ARE HEAVY. USE TWO OR MORE PEOPLE WHEN HANDLING AND WHEN INSTALLING IN A RACK. INSTALLATION IN A RACK REQUIRES USE OF THE INCLUDED RAIL KIT OR OPTIONAL REAR BRACKETS. WARNING INTERNAL COMPONENTS ARE SENSITIVE TO STATIC ELECTRICITY (ESD). OBSERVE STANDARD ESD PROTECTION PRACTICES WHENEVER SERVICING MODULES, POWER SUPPLIES OR FANS. AN ESD GROUND POINT IS PROVIDED AT THE REAR OF THE UNIT. Inca Networks Inc Family User Manual Revision 2 3

4 Contents IMPORTANT SAFETY INFORMATION... 3 INTRODUCTION... 6 OVERVIEW... 7 HARDWARE... 8 The 4400 Family... 8 Hardware Descriptions... 8 Modules and Video Transcoding Licenses Module Installation GETTING STARTED Connect to the Management Network Connect to the Video Network Start the Parent and Child Devices Configure Sources and Outputs VIDIOS USER INTERFACE Overview Device Hierarchy User Interface Mechanics VidiOS Stream Analysis View Stream Analysis VidiOS Service Failover VIDIOS USER REFERENCE Accessing the VidiOS User Interface The Main Page and Device Control Shortcuts and the Maintenance Menu Parent Device System Tab Video Network Interface Settings SNMP Tab Alarms Tab Event Log Tab Parent Device Alarms Inca Networks Inc Family User Manual Revision 2 4

5 The Child Device Sources Tab IP Outputs Tab Profiles Tab Report Tab Administration Tab Service Failover Introduction to Service Failover Service Failover Description Service Failover Configuration Configure Service failover Maintenance Menu System Maintenance Tab Links Tab TROUBLESHOOTING Confirming Video Output Using VLC CONCLUSION APPENDIX A: THE INCA NETWORKS BOOT MENU GOVERNMENT STANDARDS COMPLIANCE United States Canada Inca Networks Inc Family User Manual Revision 2 5

6 Introduction This manual describes the features and configuration options of the Inca Networks 4400 family of digital video processors. The family includes the 4410, 4420 and QUICK START Refer to the Inca Networks 4400 Family Quick Start Guide for a less technical step-by-step description of the initial setup and configuration of the device. The Inca 4400 Modular Series features flexibility with processing modules and high-capacity network interfaces. The 4400 series optimizes the format, resolution and bitrate of large numbers of live satellite, IP and off-air digital sources for delivery to set-top-boxes or multi-screen devices. Options include modular platforms with up to three bays that can transcode, trans-rate or downscale HD programs to and from MPEG-2 and MPEG-4, with integrated grooming and monitoring of all streams. The 4400 series can transcode up to 36 HD or 90 SD linear programs to MPEG- 4 or up to 72 adaptive bitrate profiles, in just one rack unit of space. Optional front-end input modules include the Inca Receiver 4400, enabling reception and transcoding of ATSC off-air and QAM sources in a single box, and the Inca ASI 4400, for interfacing with existing head-end equipment. Optional ABR licensing enables transcoding to frame-aligned outputs, which can then be received by a packager and delivered at the most appropriate bitrate for the end consumer. Packaging solutions include Inca s 5420 Multiscreen Package & Origin Server, which packages and delivers frame-aligned outputs using HTTP Live Streaming (HLS). Major features introduced with firmware version include service failover and audio transcode for linear services. Both features are described in detail in this user manual. The Inca 4400 Modular Series modularity makes it easy to scale infrastructure and easily add capacity as business grows, reducing capital and operating expenses. This manual describes the operation of the 4400 family of products as of firmware version If you have questions or would like a personal tour of the 4400 user interface, please let us know. It will be our pleasure to show you around the interface and highlight its features. The best way to reach us is through our support system at support@incanetworks.com. Inca Networks Inc Family User Manual Revision 2 6

7 Figure 1 VidiOS IP Outputs tab showing processors and transcodes Overview This manual provides detailed information about the 4400 series of Inca products. The subjects presented include: Hardware features Getting started network connections and configuration The VidiOS web-based user interface A VidiOS user reference describing video processing configuration The Inca Networks Boot Menu, which provides serial console access to management network interface and admin user password settings, as well as a reset to factory defaults function. Inca Networks Inc Family User Manual Revision 2 7

8 Hardware The 4400 Family The 4400 family of products is available in three chassis models, the 4410, 4420 and 4430, with one, two or three video processing modules, respectively. Hardware Descriptions Network Interfaces Each member of the 4400 family is equipped with multiple gigabit Ethernet (GigE) video network interfaces: 4410, 4420, 4430 Port 1, labeled MGMT on the front panel, is always the management network interface 4410 Five video network interfaces labeled Seven video network interfaces labeled Eight video network interfaces, numbered ports 2-9 in the user interface, are located in the rightmost module bay. Ports 2-5 are on the bottom row and ports 6-9 are on the top row, numbered from left-to-right, as shown in the illustration below. Figure LAN Interface Port Numbering While it is possible transport video traffic through the management network interface, it is recommended that video be transported through a dedicated LAN or VLAN, separate from the management network. To maintain operational margin, it is recommended to operate the GigE ports up to a maximum average GigE saturation of 80%, or 800 Mbps. Power Supplies All 4400 series power supplies are auto-ranging and automatically adjust to source voltages within their range of operation, nominally 100 to 240 volts AC at 50 to 60 Hz, without the need for manual voltage selection. The 4420 and 4430 default configurations feature dual redundant hot-swappable power supplies that can be connected to different independent power circuits, such that if one source circuit fails, the unit will continue to operate from the remaining circuit. Inca Networks Inc Family User Manual Revision 2 8

9 If power is supplied to only one of the power inputs or if one of the two power sources fails, a high-pitched alarm will sound. The alarm will not sound when power is applied to both inputs. To temporarily silence the alarm, momentarily depress the button located to the left of the power entry connectors at the rear of the unit. Figure 3 Rear power inputs of the 4420 Figure 4 Rear power inputs of the 4430 Hotswap Power Supplies In the event of a single power supply failure, the 4420 and 4430 power supplies can be hot-swapped, allowing a system to remain in operation while the failed power supply is replaced. If a power supply unit fails, a high-pitched alarm will sound and the LED on the rear of the failed unit will flash (4420) or turn off (4430). The LED on the remaining working power supply unit will remain on. To remove a power supply unit from the chassis, remove the power source from the rear of the unit, then push the retaining latch down (4420) or to the right (4430), and pull the unit out of the chassis using the provided handle. To install a replacement power supply unit, gently slide the replacement into the chassis until its latch locks it in place, then insert the source power cable. Cooling Fans The 4400 series chassis utilize up to four chassis fans capable of spinning at over 11,000 RPM. If a fan speed falls below a threshold, a warning will be displayed in the system s user interface, under the parent device. The 4400 family s chassis fan configurations are as follows: 4410 Two chassis fans 4420 Three chassis fans 4430 Four chassis fans, hot swappable Hotswap Fans If a chassis fan in the 4430 fails, it can be replaced while the unit remains in service. Inca Networks Inc Family User Manual Revision 2 9

10 To remove a failed fan, loosen its retaining screw and grasp the fan assembly to remove it from the chassis. To install a new fan, slide the replacement fan into the opening left by the removed fan and gently tighten its retaining screws. Rack Mounting All members of the 4400 product family can be mounted in a standard 19 rack, occupying one unit of rack space. CAUTION The 4420 and 4430 are heavy and require at least two people to handle. Always use appropriate safety precautions when handling heavy equipment. The 4420 and 4430 are heavy and require use of the included mounting rail kit in a four-post rack. The 4410 can be mounted using only front rack ears. The mounting rail kit included with the 4430 requires a minimum rack depth of 24.4 (620 mm) from the front vertical rail to the rear vertical rail. An optional rear bracket kit is available for racks that are less than 24.4 deep. CAUTION Use of a mounting rail kit is required for the 4420 and These units are heavy and front rack ears on their own do not provide sufficient mechanical support. Attempting to rack-mount the units without sufficient support is a safety hazard and can result in bodily harm and damage to the unit. Cooling air flow is from front to back and empty rack space is not required above or below the unit. Inca Networks Inc Family User Manual Revision 2 10

11 Modules and Video Transcoding Licenses The 4400 is shipped with identifying labels on the front of all occupied module bays to help identify the video transcode licensing specifications of each module. Identifying labels must be removed during operation to permit the flow of cooling air. The Inca Modular Series 4400 is available with a variety of module and video transcoding license options, as detailed in the following tables. Inca Modular Series 4400 Modules Model Number of Video Transcode Processors Inputs ASI 1 8VSB/QAM 1 VMA-XC VMA-XC VMA-XC VMA-ASI-XC VMA-ASI-XC VMA-8VSB-XC 1-4 VMA-8VSB-XC2 2-4 Notes: 1. ASI and 8VSB/QAM inputs are licensed in single port increments. Inca Modular Series 4400 Processor Video Transcoding Densities Source Resolution Output Codec MPEG-4 AVC MPEG-2 HD 4 2 SD 10 4 Inca Networks Inc Family User Manual Revision 2 11

12 Inca Modular Series Video Transcode Processor Licensing License Sources (MPEG-4 or MPEG-2) Outputs HD 1 SD MPEG-4 MPEG-4 PIP MPEG-2 2 4x HD xSD x MPEG-2 HD x MPEG-2 SD x HD ABR 2 2 x x SD ABR 4 4 x x HD + PIP x SD + PIP x PIP from HD x PIP from SD Notes: 1. SD sources can be processed in HD-licensed processors. 2. MPEG-2 outputs can be configured in processors licensed for MPEG-4 output at a reduced transcode density. 3. Up to four adaptive bitrate profiles from each of two HD sources. 4. Up to two adaptive bitrate profiles from each of four SD sources. Module Installation CAUTION Ensure that the 4400 chassis is powered down before removing or installing modules. Modules are not hot swappable and installing or removing modules while the unit is powered up can result in damage to the module or chassis. CAUTION Transcoder and front-end modules are sensitive to static electricity. Standard ESD protection practices should be observed whenever handling modules. Inca s Modular Series 4400 supports user installation and removal of modules at the front of the unit. When handling modules it is important to take precautions against damage from electrostatic discharge (ESD) by observing standard ESD protection practices. Modules should always be stored in ESD protective bags. When installing or removing modules, it is important that the unit be powered down. The modules are not hot swappable and installing or removing modules while the unit is powered up can result in damage to the module or chassis. Inca Networks Inc Family User Manual Revision 2 12

13 Modules can be removed by loosening the two thumbscrews on either side of the module s front cover. When loosened, the thumbscrews release the module from the chassis, but do not come out of the module itself. After the screws have been loosened, the module can be removed by gently pulling on the thumbscrews to detach it from the motherboard. The module will then slide out with little resistance. Unpopulated module bays are fitted with a blank cover, which must be removed before a new module can be installed. The blank cover is removed by following the same removal procedure as described above. A blank cover can be identified by the absence of text on its front surface. When installing a module, the edges of the PCB must be aligned with the card guides in the chassis bay. The module will slide freely until it reaches the motherboard connector, where it will encounter some resistance, and slightly more pressure will seat the module in the connector. When the module is seated, the thumbscrews can be tightened until they are just snug. Getting Started All day-to-day configuration and control of the 4400 is performed using Inca s VidiOS web browser based user interface, which is accessed through the management LAN interface. This sections introduces the configuration steps needed to configure the unit for networking and video processing. Each section provides links to the relevant detailed discussion in the user reference. CLI Except for the boot menu setup functions there is no console or command line interface (CLI) to Inca Networks products. Connect to the Management Network The 4400 is shipped with DHCP enabled for the management network interface. If the unit will be managed using a network with a DHCP server, it can be used with its default configuration. Static settings can be assigned using the webbased user interface or using the Inca Networks Boot Menu. To use the web-based user interface to configure static settings in a unit configured for DHCP, boot it with its management network interface, labeled MGMT, connected to a network with an active DHCP server. Note that when configured for DHCP, an active DHCP server is required in order for the unit to complete its boot process. If a DHCP server is present IP settings will automatically be assigned to the management interface during the boot process. The assigned IP address will be Inca Networks Inc Family User Manual Revision 2 13

14 displayed on the unit s front panel LCD display; the unit will also appear in the Windows Network Neighborhood. To access the unit s web-based user interface, navigate to its IP address using a standards compliant web browser and enter the unit s admin username and password. The admin username is admin and the default admin password is admin. Static IP settings can be assigned to the management network interface in the System Maintenance tab of the Maintenance menu, as detailed in Management Network Interface Configuration, below. A reboot is required in order to bring changes to the management interface settings into effect. If a network with an active DHCP server is not available, it is necessary to assign static settings using the Inca Networks Boot Menu, as described in Appendix A. USERNAME AND PASSWORD The default username and password for the web-based user interface are: Username: admin Password: admin NOTE The default admin password can be changed using the Maintenance section of the web-based user interface, as of firmware version , or the Inca Networks Boot Menu. A reboot is required to bring an admin password change made using the web-based user interface into effect. Connect to the Video Network Connect a video network interface to the video network and configure the interface. It is recommended that video be transported on a dedicated LAN or VLAN, separate from the management network. To prevent un-requested traffic from flooding the video network, it is strongly recommended that an IGMP querier and IGMP snooping are enabled on the video network. Video network interfaces are configured using the web-based user interface, in the System tab of the parent device. See Device Hierarchy below for help finding the parent device. See Video Network Interface Settings below for an explanation of video network configuration. Each video network interface is capable of full duplex gigabit Ethernet rates. In order to maintain operational margin, especially in the presence of variable bitrate streams, it is recommended to keep port bitrates below 800 Mbps. Inca Networks Inc Family User Manual Revision 2 14

15 Several advanced network settings are available for the video network interfaces, in the form of port pairing for automatic failover, round robin and LACP link aggregation. Configuration details can be found in Advanced Network Options, below. Port 2 is selected by default when creating sources and outputs; for efficiency during configuration, it is convenient to use port 2 for at least one video network interface. Any other connected and configured interface can also be selected. UDP MULTICAST The primary method for networking video streams within the head end is UDP multicast. To prevent multicast traffic from flooding the network, it is important to ensure that an IGMP querier is active in all VLANs through which multicast traffic will flow and that IGMP snooping is enabled in each network switch/vlan. It is recommended that video be transported on a dedicated LAN or VLAN, separate from the management network. VidiOS User Interface Start the Parent and Child Devices If they are not already running, start the parent and child devices, as described in The Main Page and Device Control, below. The parent and child devices must be running in order to process video. Configure Sources and Outputs Video sources and outputs are configured in the Sources and IP Outputs tabs of the child device. IP video sources are supported by all 4400 products. Optional 8VSB/QAM tuner and ASI modules are also available. See Sources Tab for source configuration details outputs are always IP, either multicast or unicast. Output streams can be transcoded or demultiplexed versions of source video streams. The 4400 can also be used as a video analyzer, serving a probe function for the Inca Networks All Seeing Eye monitoring product. See IP Outputs Tab for output configuration details. Overview With the exception of a number of boot menu functions, all 4400 configuration and control is performed using the VidiOS web-based user interface. The user interface can be accessed using any current standards-compliant web browser with access to the management network. This section provides an introduction Inca Networks Inc Family User Manual Revision 2 15

16 to the features of the VidiOS web-based user interface. Configuration details are provided in the following chapter, VidiOS User Reference. Device Hierarchy Inca s VidiOS user interface employs a hierarchical structure, with systemlevel controls and notifications at the top of the hierarchy in a parent device, and video processing functions in one or more child devices beneath the parent. The child device in the 4400, for example, is named Inca Networks TS Processor by default and provides access to source, transcode, demultiplexing and probe configurations. This structure can be seen in the Device Status section at the top of the user interface. Names can be assigned to the parent and child devices; these names then appear as the titles of web browser windows and tabs. Device names are for convenience and do not affect video processing functions. Parent and child devices are accessed and controlled from the Device Status section of the user interface. Devices can be started, stopped and restarted using the graphic icons at the right of the display. Devices must be in their running state in order to perform their functions. Devices at a higher level in the hierarchy must be running in order for devices lower in the hierarchy to start. That is, the parent device must be running in order for child device(s) to start. Active system level alarms and warnings are displayed beneath the parent device name. Figure 5 The parent-child hierarchy Inca Networks Inc Family User Manual Revision 2 16

17 User Interface Mechanics Hover Help Extensive help information has been included in the user interface through the use of hover help, which can be accessed by hovering the mouse pointer over fields and labels. Figure 6 Hover help describing a parameter Hovering over input boxes reveals more information about the expected input. Figure 7 Hover help describing expected input Hovering over user interface elements provides more detailed information, if available. Figure 8 Hover help displaying additional information about a processor Save Changes Edits to some fields are saved automatically when the user clicks outside an edited textbox while changes to other fields need to be saved by the user. Inca Networks Inc Family User Manual Revision 2 17

18 If the Save Changes option does not appear under the left navigation menu after clicking outside an edited field, the changes have been saved and take effect automatically. If the Save Changes option appears under the left navigation menu after the user has clicked outside an edited field, Save Changes must be clicked for the edits to be saved and take effect. If the user attempts to leave the page without clicking on Save Changes, a dialog box appears to remind the user that there are unsaved changes and asking the user to confirm their action or stay on the page. Figure 9 Dialog box alerting the user of unsaved changes Figure 10 Location of the Save Changes button Saved settings are applied immediately and persist across system reboots. VidiOS Stream Analysis The VidiOS Input and Output Monitors display a wealth of information about the video transport streams being processed in the system, including a detailed view of the transport stream structure, payload descriptors, average and peak bitrates, and errors. Input and Output Monitors include controls for view customization, stream sample download and access to the stream s audit trail. An audit trail is a view of the system event log filtered to display events related to the monitored stream. Inca Networks Inc Family User Manual Revision 2 18

19 View Stream Analysis VidiOS stream analysis can be viewed by hovering the mouse cursor over a stream s configuration or by clicking its configuration. In the case of IP inputs, the configuration area is its row in the source area; for other inputs and all outputs, the stream s configuration area is called a tile. Hovering over the source section of a tile brings up details of the source stream and hovering over an output section of a tile, if present, brings up details of the output stream. Clicking on the tile causes the VidiOS analysis of both the input and output to display on the left of the page. Hovering over the source section of a tile opens a pop-up window displaying source stream details: Figure 11 Hover monitor view of detailed Source Stream analysis Hovering over the output section of a tile opens a pop-up window showing output stream details: Figure 12 Hover monitor view of detailed Output Stream analysis Inca Networks Inc Family User Manual Revision 2 19

20 Clicking a tile displays both source and output stream details in the Input and Output Monitors at the left of the page: Figure 13 Source and Output Stream for selected processor tile Hovering the mouse pointer over Program and PID bitrates pops up additional details, as shown in the figure below. For example, over short periods a program s bitrate may burst higher than the average bitrate reported in the monitor. Hovering the mouse over the program s average bitrate pops up additional information, including the program s 15 second peak bitrate, which can be an important factor in demultiplexing applications. Bitrates reported in the Input and Output Monitors are averages and include packet overhead, representing the actual bitrates carried by the network. The payload carried in each Program or PID can be accessed by hovering the mouse pointer over the reported bitrate. Inca Networks Inc Family User Manual Revision 2 20

21 Figure 14 Hover over bitrates to view additional detail Customize the Input and Output Monitor Views The Input and Output Monitor views can be adjusted to the user s preference using controls located at the top of the Input and Output Monitors, as described below. Shows/Hides Scrambled programs, Default: Show Shows/Hides Programs. Default: Show Shows/Hides Tables. Default: Show Shows/Hides Other PIDs. Default: Hide Other PIDs, included in the transport stream by the broadcaster but not part of a program or table, are displayed at the bottom of the transport stream monitor, but are normally hidden. Display of Other PIDs, if present, can be toggled on and off by clicking on the control or on Other PIDs. Controls with blue backgrounds indicated that the related content is being displayed. Greyed out controls indicates that the related content is not present in the transport stream. Download Stream Samples Each Input Monitor and Output Monitor tile contains a icon, which, when clicked, downloads a 10 second sample of the MPEG transport stream to the user s workstation. The downloaded file can be found in the web browser s Downloads folder and can then be played using a media player that supports the MPEG-TS format, such as VLC. Inca Networks Inc Family User Manual Revision 2 21

22 Download Sample Figure 15 Download a Stream Sample Access Stream Audit Trails Stream audit trails are dialog windows into the system s event log that display all events related to the monitored stream. Audit trails can be accessed throughout the user interface, wherever a icon is seen such as in the Input and Output Monitors, output configuration drop-downs and the system Event Log. The top of the audit trail window displays a block diagram showing the progress of the stream through the system. Audit trails for source streams display a single input block. Audit trails for transcoded outputs display four blocks, including the input, as the stream enters the system; the demux, before the program is sent to the transcode hardware; the remux of the transcoded program, as it is received back from the transcode hardware; and the output, as the transcoded program is sent out a network interface. An analysis of the stream is performed at each stage of its journey through the system and the stage is identified in the event log. Additional information available in the audit trail view can be accessed by hovering the mouse pointer over the blocks in the block diagram, as illustrated in the figures below. Hovering over the top portion of a block displays the stream s VidiOS analysis. Hovering over the bottom portion of a block displays the stream s dependencies. Inca Networks Inc Family User Manual Revision 2 22

23 Figure 16 Audit trail for a source Figure 17 Audit trail block diagram for a transcoded output Figure 18 Audit trail hover for VidiOS analysis Inca Networks Inc Family User Manual Revision 2 23

24 Figure 19 Audit trail hover to display dependencies VidiOS Service Failover Service failover enables the operator to configure a secondary, or backup, source for an output that the system can automatically bring into service if the output s primary source fails. The primary source is monitored for up to six user-configurable trigger conditions. When an active trigger threshold is met on the primary source, the system can be configured to automatically bring the secondary source into service in place of the primary source. When the trigger condition on the primary source clears, the system automatically returns service to the primary source. In the Modular Series 4400 family, service failover is available for any configured transcoded or direct output, up to the number of available service failover licenses. Service failover for transcoded outputs can take place either before or after the transcode operation. Service failover is a licensed feature. Licenses can be purchased per service and can be installed in the field, if remote SSH or VPN access is provided. Contact Inca sales at sales@incanetworks.com for more information about purchasing service failover licenses. Detailed service failover configuration information is provided below, in the VidiOS User Reference. VidiOS User Reference Accessing the VidiOS User Interface Access the VidiOS web-based user interface by entering the unit s management IP address in the address bar of a PC connected to the management network. Alternatively, double click the unit s icon in the PC s network neighborhood. Inca Networks Inc Family User Manual Revision 2 24

25 Login Authentication The VidiOS web-based user interface is protected by a username and password. Visiting the device s management IP in a web browser will produce an HTTP authentication dialog box. Figure 20 Login prompt for username and password USERNAME AND PASSWORD The default username and password for the web-based user interface are: Username: admin Password: admin The admin password can be changed in the Administration tab of the Maintenance section of the web-based user interface. The admin password can also be changed using the Inca Networks Boot Menu, which is accessed using the serial console port. The Main Page and Device Control Parent and child devices are accessed and controlled from the Device Status section of the user interface. Active system level alarms and warnings are displayed beneath the parent device name. System level configuration and control takes place in the parent device. Video processing functions are configured and controlled in the child device. Figure 21 Parent and child devices Device Start/Stop control is provided using icons to the right of each device. The parent device must be running in order for a child device to start. When booted, the 4400 will return to its last running state. Key Controls are: Inca Networks Inc Family User Manual Revision 2 25

26 Start Device Stop Device Restart Device Reboot System Shortcuts and the Maintenance Menu The Shortcuts navigation menu at the left of the display is always available to provide quick access to commonly used tabs in the parent and child devices and the Maintenance page. Figure 22 Location of the Shortcuts menu Parent Device The Parent Device section provides information about the chassis hardware, configuration of system level settings, access to active alarms and the system event log. System Tab The System tab is where Parent Device settings such as video network interfaces, timeserver settings and user defined device information are configured. Inca Networks Inc Family User Manual Revision 2 26

27 Figure 23 System tab of the Parent Device The System tab also provides network traffic and environment monitors: Inca Networks Inc Family User Manual Revision 2 27

28 Chassis level stream and license utilization: And details of installed modules, their licenses and license utilization: Device Name The Device name is a user-defined field to help identify the unit. Time Settings Inca recommends setting the Time Zone to the local time zone and employing an NTP timeserver to synchronize the clocks of all systems on the network. This will provide a common time base for comparing event logs. NTP Server IP Address The 4400 is configured by factory default to query a number of Internet time servers. If a timeserver IP address is not specified, the 4400 will attempt to use its pre-configured Internet timeserver settings. The IP addresses of one or more alternate timeservers can be specified in the NTP Time Server IP Address field. Access to Internet timeservers requires that an Internet gateway be available on the network and that its IP address be configured in the management interface settings. A list of NTP timeservers can be found at: If an Internet gateway is not available, local timeservers can be specified by IP address. If the local timeserver is on the same subnet as the 4400, a gateway is not required. Multiple timeserver IP addresses can be configured and should be separated by a single space. Inca Networks Inc Family User Manual Revision 2 28

29 Time Zone The local time zone is specified in the Time Zone field in the System Tab of the parent device. The time zone format follows the IANA time zone database: Common examples include: Canada/Pacific US/Eastern Europe/Berlin Europe/Stockholm America/Anchorage Figure 24 NTP Server Configuration Administrator Contact and Location Administrator Contact and Location are user-defined fields provided for convenience. Video Network Interface Settings All available video network interfaces will be listed under the heading Video Network Interface. This section provides details of basic video network interface configuration. Advanced video network settings are configured in the System Maintenance tab of the Maintenance menu, detailed in Video Port Aggregation Mode. Each video interface is configured in its own row of the Video Network Interface configuration table. The configurable parameters are described below. Inca Networks Inc Family User Manual Revision 2 29

30 Enabled [ Yes No ] This field allows video network interfaces to be enabled and disabled. Other settings are not affected when an interface is disabled. Default: No Type [ Static DHCP ] This field defines how the video interface IP settings will be assigned. Static Video network interfaces are typically assigned static IP addresses. Statically configured IP addresses do not change; they are manually entered and must be unique on the network to which the interface is connected. DHCP DHCP is a networking protocol that allows for the automatic negotiation and allocation of IP addresses. Successful DHCP operation requires the presence of an active DHCP server on the network to which the interface is connected. The allocated IP address may be subject to change, though some routers and switches can be configured to map a specified IP address to the port s MAC address. Default: Static Name [ Textbox ] The Name field defines the video interface s alias that will appear throughout the user interface. Inca recommends assigning a name that describes the use of the port, e.g., Video 1, Network A. IP Address [ Textbox ] This field defines the static IP address to be used. This field is ignored if the IP settings are assigned by a DHCP server. Network Mask [ Textbox ] This field defines the range of IP addresses, or subnet, which will be considered part of the internal network using a bitmask. IP addresses outside the subnet will be considered external to the network and routed through the gateway, if configured. This field is ignored if the IP settings are assigned by a DHCP server. Speed [ Auto ] The Speed field defines the port speed of the network interface in megabits per second. For most applications this setting should be left on Auto. Default: Auto Inca Networks Inc Family User Manual Revision 2 30

31 IGMP Version [ 2 3 ] The IGMP Version field defines which version of IGMP will be used. This field is set to 2 by default to ensure compatibility with existing infrastructure. Default: 2 Multicast TTL [ Textbox ] The Multicast TTL field defines the maximum number of hops a multicast packet may travel before it is dropped by the network. Each router the packet passes through decrements the TTL by one; when the TTL reaches zero, the packet is dropped. This field allows fine control over multicast network penetration, which may be used to ensure multicast data does not flood outside networks. The default setting of 255 is interpreted by the network as unlimited hops. Default: 255 Gateway [ Textbox ] The Gateway defines which network router will be used when an IP address outside the subnet defined by the network mask is requested. This field is optional, and is often left blank. A gateway is required if an output is sent to and IP address outside the interface s subnet. Default: <Blank> Click Save Changes to apply changes to the settings. SNMP Tab VidiOS includes limited support for SNMP, or Simple Network Management Protocol, in the form of a set of Inca transport stream MIBs and video related SNMP trap forwarding. SNMP is configured and enabled in the SNMP tab of the parent device. Inca products cannot be managed using SNMP. SNMP MIBs are available for download in the Links tab of the Maintenance page. A MIB, or Management Information Base, is required to define the scope and context of SNMP data and traps. Inca Networks Inc Family User Manual Revision 2 31

32 Figure 25 SNMP tab with example configuration Management server/network This field defines the IP address of the management server or network and should be set to the base address of the management subnet, or the IP address of the SNMP server to restrict access to a single host. Management network mask This field can be set to the subnet mask of the management network, or to , to restrict access to a single host. Community String This field defines a string that SNMP clients must use to access the SNMP interface; it is analogous to a password. SNMP clients and servers use the string public by default. This field applies to management only, and is therefore unused. Default: public Trap Server This field defines the IP address of the Trap Server. This is the server that will receive trap reports from the Trap Community String This field defines a string that will be used when sending traps to a trap server; it is analogous to a password. SNMP clients and servers will use the string public by default. The 4400 must be configured with the same community string as the SNMP trap server. Default: public Event Log Size This field defines the number of event logs to keep in memory. This field is deprecated and is no longer used. Default: 200 Inca Networks Inc Family User Manual Revision 2 32

33 Alarms Tab Alarms are active high-priority event log errors for both system and stream events. To view the Alarms tab from anywhere in the user interface, click Alarms in the Shortcuts navigation bar at the left of the user interface. Alarms that have cleared are automatically removed from the Alarms list. Figure 26 Alarms tab with multiple alarms Event Log Tab The Event Log contains information about the parent and children devices. Information, warnings and errors regarding network interfaces and transcoding operations are all logged and accessible within the Event Log tab. The type of each event log entry is identified using an icon, as defined in the below table: Event Log Legend: Alarm Raised Alarm Cleared Error Notice Warning Information Inca Networks Inc Family User Manual Revision 2 33

34 Event Log Actions: Refresh Audit Refresh the event log View the stream s audit trail Figure 27 Event Log tab with typical information, warnings and errors. Types of Errors Continuity errors Continuity errors occur when packets in the MPEG transport stream arrive out of sequential order. This error will occur when one or more packets are missing, arrive out of order, or are duplicated. Continuity errors often indicate corrupted or missing data in the transport stream and can result from a variety of causes, such as a weak input signal, interference, or network errors. Transmission errors Transmission errors occur when one or more packets contained in a transmitted MPEG-2 transport stream fail the Cyclic Redundancy Check (CRC), an errorchecking mechanism in the receiver. Transmitted MPEG-2 transport streams contain checksums corresponding to the data being transmitted. The receiver verifies the integrity of the received data by independently computing the checksum of the received data and comparing it to the transmitted checksum. CRC will fail if any data, including the checksum, has been corrupted. Transmission errors often coincide with Continuity errors, as both are indicative of data corruption in the transport stream. Inca Networks Inc Family User Manual Revision 2 34

35 In the 4400, transmission error indicators are only set in the receiver hardware of the optional 8VSB and QAM receiver module and indicate corruption of the received signal at the module s input port. Multiplex may be oversubscribed Multiplex may be oversubscribed errors are usually indicated when an MPEG-2 transport stream s payload exceeds the Transport Rate allocated to it; in other words, when the combined video and audio bitrates and overhead are higher than the configured transport rate. The Transport Rate must always be configured high enough to contain all of the video, including the peak video bitrate, and audio payloads of the video stream. For a discussion of how to set bitrates, see the section below on Transcode Profile Settings. Multiplex over-subscription is determined by analysis of stream timing parameters, thus errors in stream timing during restarts and other streaming transients can also be reported as Multiplex may be oversubscribed errors, even if the configured bitrates are adequate. Low bitrate in source Low bitrate errors occur in response to an abnormally low bitrate in the source stream for a time that exceeds a factory-defined period. This can indicate excessive packet loss, but can also occur when a configured source is not receiving any data at all. Typical causes for low bitrates are network errors and radio frequency interference in off-air signals. Low bitrate alarms on outputs can indicate that an output network was selected which has not been configured or does not have network link. Reference clock timeout The Program Clock Reference (PCR) in each stream is used to synchronize the System Time Clocks (STC) of the decoder and encoder. Reference clock timeout errors indicate that a PCR has not been received within the required time period. Reference clock timeout errors often coincide with continuity and transmission errors, as they are all related to packet loss or corruption in the transport stream. Source failed (<List of errors>) Indicates that one or more of the configured and enabled service failover monitored parameters has triggered the configured threshold. This error is displayed if the automatic failover mechanism is disabled. List of errors lists the parameters which have exceeded the configured threshold. Auto failover (<List of errors>) Indicates that one or more of the configured and enabled service failover monitored parameters has exceeded the configured threshold and the service has Inca Networks Inc Family User Manual Revision 2 35

36 failed over to the configured backup service. List of errors lists the parameters which have exceeded the configured threshold. Parent Device Alarms In addition to active streaming alarms displayed in the alarms tab, system alarms are displayed in below the parent device as illustrated below. Ethernet Link Loss Alarm The video port interfaces are continually monitored for a valid Ethernet link. Loss of video port connectivity will trigger an alarm visible in the Alarms tab as well as under the parent device in the Device status heading. The alarm will be cleared within 60 seconds of re-establishing Ethernet connectivity to the affected video port. Figure 28 Loss of Ethernet connectivity Alarm on a configured video port. Temperature Alarm The 4400 monitors its CPU and system temperatures using temperature sensors. Under normal conditions in an air-conditioned data center, the unit operates at modest temperature levels. The system temperature alarm threshold is 60 degrees Celsius and the CPU temperature alarm threshold is 65 degrees Celsius. When a temperature exceeds these thresholds an over-temperature alarm is displayed. Over-temperature alarms clear automatically when the temperature falls 7 degrees Celsius below the threshold. Fan Speed Alarm The 4400 series contains up to four chassis fans, which can spin at over 11,000 RPM. The fan speeds are automatically increased or decreased to maintain the chassis temperature at factory-defined levels. If a fan speed falls below its factory-defined speed threshold, a warning will be displayed in the user interface under the parent device. Fan speed warnings clear automatically when the fan speed rises above its alarm threshold. The Child Device All video processing functions are configured and controlled in the Child Device. Clicking on the child device opens its Sources tab, in which all video sources are configured. Details of the selected source are displayed in at the left of the tab. Sources are configured at the right of the tab, with IP sources at the top. ASI or 8VSB/QAM ports, if available, are displayed below IP sources. Inca Networks Inc Family User Manual Revision 2 36

37 Figure 29 The 4400 Child Device Sources Tab Input Monitor The transport stream analysis of a selected source stream appears in the Input Monitor, at the left of the Sources tab. When a new source is configured, the system will start to receive it and display its source analysis. Initial warnings and bitrate fluctuations will settle down after a few seconds as VidiOS collects information about the stream. If a source is selected that is not available to the 4400, the Input Monitor will not have a stream analysis to display or will indicate that an error has occurred. Figure 30 Input Monitor stream details for an IP Source Inca Networks Inc Family User Manual Revision 2 37

38 Configure a New IP Source To configure an IP source, open the Sources tab, click Add a new source, and enter the source s parameters as detailed below. Figure 31 IP Sources Name [ Textbox ] This is a user-defined field for identification of the source throughout the system. The name is used for source selection when configuring outputs and in logging. Default: <Blank> Network Port [ Listbox ] The Network Port defines the GigE interface used to receive the source stream, identified by Ethernet port number or an alias, if set. Hovering the mouse pointer over this field will display the available network interfaces and the traffic level on each interface. Default: Port 2 or Port 2 s alias, if set Multicast Group [ Textbox ] This field defines the address of the source stream. The Multicast Group should be an address in the /4 ( to ) range. If configuring a unicast source, this field can be left blank or configured with the IP address of the source device. UDP Port [ Textbox ] The UDP Port defines the port on which the transport stream is received. If a UDP port is not defined, the system will use Default: 1234 Configure an ASI Input If an ASI input module is installed in the system, ASI input configuration can be found near the bottom of the Source Streams section of the Sources tab, below the IP sources. Each ASI port control panel is referred to as a tile. To receive an ASI source, connect an ASI source cable to an ASI input at the front of the unit, then edit the port s configuration in the user interface to enable the port and optionally assign a name to the source stream. Modules are numbered starting from 1, from left to right when facing the unit. Inca Networks Inc Family User Manual Revision 2 38

39 Figure 32 ASI stream configuration All that is required after connecting an ASI source to the 4400 s ASI input is to enable the input. It is recommended that each ASI input be assigned a unique name to aid in configuring outputs. Name [ Textbox ] This is a user-defined field for identification of the stream throughout the system. The name is used for source selection when configuring outputs and in logging. Default: <Blank> Enabled [ Checkbox ] Click the checkbox to toggle the enable control. Default: Disabled Configure an 8VSB or QAM Input If an 8VSB/QAM receiver is installed in the system, its configuration can be found at the bottom of the Source Streams section of the Sources tab, beneath IP and ASI sources, if present. Each receiver control panel is referred to as a tile. To receive an 8VSB source, connect an RF source to an RF input port at the front of the unit, then edit the port s configuration in the user interface to select the source modulation and carrier frequency, enable the stream, and optionally assign a name to the source stream. The source modulation will be 8VSB for ATSC off-air sources and either 64 or 256 QAM for North American Annex B QAM sources. Inca Networks Inc Family User Manual Revision 2 39

40 Figure 33 8VSB/QAM source configuration Name [ Textbox ] This is a user-defined field for identification of the stream throughout the system. The name is used for source selection when configuring outputs and in logging. Default: <Blank> System [ ATSC 64 QAM 256QAM ] This field defines the type of modulation used in the source. ATSC is used for off-air 8VSB sources and either 64 or 256 QAM for North American Annex B QAM sources. Default: ATSC Frequency [ Combobox ] This field configures the frequency to which the receiver will be tuned. The drop-down menu contains a list of channels and their corresponding frequencies, which then are automatically converted to their value in Hertz when selected. Frequencies can also be entered manually. While the receiver operates over the full ATSC specification, best results are obtained with a source signal-to-noise ratio (SNR) of at least 22 db and source power between -60 dbm and 0 dbm. Enabled [ Checkbox ] Click the checkbox to toggle the enable control. Default: Disabled IP Outputs Tab Output streams and VidiOS probes are configured in the IP Outputs tab of the child device. Output streams can be transcoded source programs or direct outputs. Direct outputs are streams that are passed through or turned around and can be full or Inca Networks Inc Family User Manual Revision 2 40

41 partial multiplexes. Direct outputs are often used to demultiplex multi-program source multiplexes (MPTS) into single program transports (SPTS), strip padding or bridge streams between networks. VidiOS probes make it possible to realize the benefits of the deep analytics included in the VidiOS analysis engine to monitor the outputs of other transport stream sources. Probes analyze sources and provide analytics to Inca s All Seeing Eye monitoring system but do not generate output streams. ANALYZE ANY STREAM VidiOS can be used to analyze the outputs of other vendors equipment during troubleshooting, even if not using the All Seeing Eye. Simply configure a source stream in the Sources tab and the analysis will be available. The IP Outputs tab is arranged with VidiOS input and output stream analysis on the left of the display and output controls on the right. Output controls are arranged into transcode processors at the top and direct outputs and probes at the bottom. Figure 34 Input and Output Monitor displaying detailed VidiOS analytics for the selected transcode processor tile Stream processing controls are grouped in tiles. A tile is created for each source being processed and supports one or more transcoded outputs, direct outputs or probes. Inca Networks Inc Family User Manual Revision 2 41

42 Output Tiles Outputs are generated using tiles, which define a source and one or more outputs or probes. In order to generate an output stream or probe analysis, a tile must be configured with both a source and one or more outputs. A tile s source can be any source in the Sources tab. Figure 35 Tiles, on the left with one and on the right with zero outputs For transcodes, the tile s Source Filter selects the source program to be processed. A tile for a transcoded output can be used to generate one or more transcoded outputs from the selected source. In a single tile, for example, an HD MPEG-2 source can be transcoded to MPEG-4 HD, MPEG-4 SD downscale and picture-in-picture (PIP) outputs. Up to four transcoded outputs can be added per source tile. In adaptive bitrate streaming applications, all bitrate profiles for the source must be processed in the same tile or frame alignment will not be achieved. See below under Transcoding for Adaptive Bitrate Streaming Applications for more details. In direct output tiles, a source multiplex of one or more programs can be selected and up to 16 demultiplexed outputs or probes can be configured per tile using Output Filters, as detailed below. The Source Filter is usually not used for direct outputs. Each output consumes a single transcode or direct output license. Details instructions for configuring sources and outputs are provided below. Transcoded Outputs Transcoding is performed by processors, which are shown in the child device IP Outputs tab. Processors can be licensed for a variety of transcode operations. The license installed for each processor is displayed to the right of the processor for example, Quad HD Transcoder, 10 x SD Transcoder. Inca Networks Inc Family User Manual Revision 2 42

43 HD sources require HD licensed processors. SD sources can be transcoded using both HD and SD licensed processors. Refer to Modules and Licenses for details of available transcode module and licensing options. Available processors are displayed under Output Streams in the IP Outputs tab of the child device. Figure 36 Processors available for transcoding, under Output Streams Configure a Transcode Source New output tiles are created by clicking the add stream icon. Each output tile can contain one or more transcoded outputs. Transcode settings are defined using transcode profiles, as described below. For transcoded outputs, the source program selection and program and PID filtering and remapping are made using a source filter. Multiple outputs can be configured in a tile. For convenience, tabs for the configuration of the first output are included in the Create a stream dialog. Output configuration is discussed in the following section. Figure 37 Source configuration for an Output Stream Inca Networks Inc Family User Manual Revision 2 43

44 Name [ Textbox ] This is a user-defined field for identification of the stream throughout the system. The name is used for source selection when configuring outputs and in logging. Default: <Blank> Source [ Listbox ] This dropdown menu selects the source that will be used to generate the transcoded output. The drop-down menu lists all sources that are configured in the Sources tab. Source Filter [ Textbox ] The Source Filter field is used to select programs or portions of programs from source multiplexes for transcoding, and to optionally remap source programs and PIDs. A typical application is to demultiplex a single program from a source multi-program transport stream (MPTS) using a simple program filter such as P3, where 3 specifies the program number in the source multiplex. Details of Inca s filter expressions are available in a separate guide, Inca Networks Filter Language Quick Reference. If no filter is entered, the first program in the source multiplex will be selected. Filtering for direct outputs and probes is done in the output configuration. Default: <Blank> FILTER EXPRESSIONS Filter expressions are a feature of VidiOS and provide a powerful mechanism for filtering and remapping programs and PIDs. See the Inca Networks Filter Expression Reference guide for details. Adding a Transcoded Output A transcoded output is added to the tile by selecting Add an output from the tile s drop-down menu. When Add an output is selected a dialog will appear, as shown below. The Add an output dialog presents three tabs for the configuration of video transcode, audio transcode and service failover. Video and audio Inca Networks Inc Family User Manual Revision 2 44

45 transcoding are described in the following sections. Service failover is described below, in the Service Failover chapter. Figure 38 Adding a transcoded output to a processor tile Transcoding Video The leftmost tab in the Add an output dialog configures the output transport stream settings and applies a video transcode profile. Figure 39 Configuration of a transcoded output stream Inca Networks Inc Family User Manual Revision 2 45

46 Name [ Textbox ] This is a user-defined field for identification of the stream throughout the system. The name is used for source selection when configuring outputs and in logging. Default: <Blank> Transcode Profile [ Listbox ] This is a drop-down list of available transcode profiles. The 4400 ships with a library of preconfigured transcode profile examples. The creation and editing of transcode profiles are discussed in the section Profiles Tab. Network Port [ Checkbox ] The Network Port can be any configured and enabled video network interface with a network connection. Up to two output ports can be selected for transcoded outputs. If two ports are selected, the output stream is mirrored out both ports. Note that if the selected port is not configured or does not have link, a low bitrate error will be reported and no output will be generated. Default: Port 2 Output Address [ Textbox ] This field defines the multicast or unicast address for the output. For a systematic approach to multicast addressing that reinforces efficient head end management, see Inca s application note IPTV Best Practices for Multicast Group Assignment. UDP Port [ Textbox ] This field defines the UDP port used for the output transport stream. Default: 1234 Protocol [ Listbox ] Protocol defines the protocol that will be used for the output transport stream. The most commonly used setting in the head end is UDP Transport Stream. Alternatives to UDP Transport Stream are RTP, Real Time Protocol, and RTP+FEC. FEC, or Forward Error Correction, adds redundancy to the transmitted stream which downstream devices can use to correct a limited amount of data corruption through the transmission path. FEC settings are configured in Advanced Network Options in the Administration tab of the Maintenance menu. See FEC Settings for configuration details. Default: UDP Transport Stream Transport Mode [ Listbox ] The Transport Mode will override the profile settings, allowing per-output adjustments to the output transport stream, if desired. This setting is rarely used for transcoded outputs, for which alternate and re-usable transcode profiles are readily created. The Default transport mode uses the transport mode specified in the transcode profile. Default: Default (use the transport mode specified in the transcode profile) Inca Networks Inc Family User Manual Revision 2 46

47 Transport Rate [ Textbox ] The Transport Rate will override the profile settings, allowing per-output adjustments to the output bitrate, if desired. This setting is rarely used for transcoded outputs. When left in its default state, <Blank>, the transport rate specified in the transcode profile will be used. Default: <Blank> Output Filter [ Textbox ] The Output Filter can be used to remap the program and PIDs for a transcoded output but for transcoded outputs these functions normally take place in the Source Filter. Output Filters are rarely used for transcoded outputs. Default: <Blank> TRANSCODE PROFILES Transcode profiles contain predefined transcode configurations to simplify managing a large number of streams. The 4400 has been preconfigured with a library of example profiles. See the sections Add or Edit a Transcode Profile and Transcode Profile Settings for more details about managing profiles. After the desired output settings have been entered, click Save to save the settings and start the video transcode. It is not necessary to configure the Audio and Monitor/Failover tabs in order to start a transcode. The Audio and Monitor/Failover tabs are discussed in following sections. After a transcode has been configured, if the selected source stream is present and stable and the selected network ports are configured and connected to a network, the transcode operation will start and the Output Monitor will begin to display details of the output stream. As the transcode operation begins, several warnings may appear; these will clear after a few seconds as the process converges and as VidiOS collects information about the output stream. It may be necessary to scroll down the page to view the Output Monitor. Output stream details can also be viewed by hovering the mouse cursor over the output portion of the tile. Inca Networks Inc Family User Manual Revision 2 47

48 Figure 40 Hover view of output stream analysis. HOVER MONITOR View the details of any stream by hovering over its configuration tile. MOVE TO A DIFFERENT PROCESSOR To move a tile to a different processor, click on the Edit icon at the top of the tile to open the tile for editing, then select the destination processor from the Processor drop-down menu and click Save to make the change take effect. Transcoding for Adaptive Bitrate Streaming Applications In ABR (Adaptive Bit-Rate) streaming applications, the 4400 with ABR licensing transcodes sources to groups of multiple frame-aligned output streams at a variety of bitrates. The groups of frame-aligned outputs can then be ingested by a packager and origin server, such as the Inca Multiscreen Package and Origin 5420, and delivered to players using HLS (HTTP Live Streaming). The availability of multiple versions of the stream at a variety of bitrates allows HLS players to adapt to varying network transport conditions by seamlessly switching between versions of the stream. Seamless switching between streams at different bitrates is made possible by the alignment-in-time of the key frames in each member of the group. Since HLS streaming requires AAC audio encoding, 4400 processors licensed for ABR transcoding automatically transcode source audio encoded in Dolby Digital or Dolby Digital Plus to AAC LC stereo at 128 kbps. The 4400 Inca Networks Inc Family User Manual Revision 2 48

49 transcodes the first audio stream in the source. Source audio containing more than two channels is downmixed to stereo. Other audio transcode options are available for ABR outputs in firmware or higher; see Transcoding Audio below for details. ABR output configuration is the same as any other 4400 transcode except that frame-aligned groups of outputs must be configured within the same tile. Other than grouping the outputs in a single tile and using the profile recommendations provided below, no additional settings are required to achieve frame-alignment. It is important to note that the first output stream in a tile must be enabled in order for other outputs in the tile to function. ABR transcode profiles must be developed to work within the capabilities of the targeted player(s) and the delivery network. While many profile settings are specific to players or the carrying network, a few settings are consistent: Transport Mode: Constant Interlacing: Progressive Frame Rate: 30 Same GOP closure period for each bitrate Including padding in the transport is acceptable since the packager later removes it when breaking the stream into chunks for HLS delivery. The transcode profile library included in the 4400 firmware contains a set of example HLS transcode profiles. HD licensed ABR transcode processors can generate up to four frame-aligned outputs from each of two HD sources. The set of outputs for each HD source should be limited to two frame size reductions from the source. For example, if the source frame size is 1920x1080, the operator may configure output frame sizes of 1280x720 and 720x480; configuring more frame sizes in the output set may result in unstable operation. Likewise, each set of two outputs from an SD licensed transcode processor should be limited to include at most one frame size reduction from the source. DOWNSCALES Limit downscales per set of ABR outputs to two for HD sources and one for SD sources. Audio and Data PID Processing Firmware version introduces audio transcoding and the version two, or V2, audio signal path for linear applications. This section describes the audio transcode features and the V2 pathway. To minimize changes during the upgrade to new firmware versions, linear applications continue to use the original audio and data PID signal path by Inca Networks Inc Family User Manual Revision 2 49

50 default. The V2 pathway is enabled for the service when an audio pass-through or transcode is configured in the Audio tab of the Add an output dialog. ORIGINAL AUDIO PATHWAY REMAINS THE DEFAULT For linear services, the original audio and data PID pathway is used by default. The V2 pathway is enabled whenever an Audio setting is configured in the Audio tab of the Add an output dialog. The V2 pathway is used by default in ABR applications. V2 Audio and Data PID Pathway Overview A new audio pathway, referred to as the V2 pathway, is introduced with firmware version Prior to firmware version , all audio and data PID content for linear video transcodes passed through the video transcode processor. With the V2 pathway, only the video elementary stream passes through the transcode processor; audio and data PIDs bypass the transcode processor and are processed in software by the system CPU, as shown in the block diagrams below. The V2 pathway has been used in ABR transcode applications for several years and is a proven technology. Source MPEG-2 TS SPTS/MPTS Host CPU Demultiplex MPEG-2 TS SPTS Transcode Processor Output MPEG-2 TS SPTS Figure 41 Original audio and data PID signal path. Video Transcode Processor Video Source MPEG-2 TS SPTS/MPTS Host CPU Demultiplex Audio Host CPU Audio Transcode Audio Host CPU Multiplex Output MPEG-2 TS SPTS Audio Passthrough Subtitle PIDs Teletext and data PIDs Figure 42 V2 audio and data PID signal path. Inca Networks Inc Family User Manual Revision 2 50

51 As noted in the introduction to this section, to minimize the number of changes introduced during the firmware upgrade, the system will continue to use the original audio and data PID signal path for linear applications unless the V2 pathway is enabled by configuring an audio pass-through or transcode in the Audio tab of the Add an output dialog. ENABLE THE V2 AUDIO AND DATA PID SIGNAL PATH The V2 audio and data PID signal path is enabled whenever a setting is made in the Audio tab of the Add an output dialog. A benefit of the V2 audio and data PID signal path is that it reduces the processing load on the video transcoder hardware. The video transcode hardware can process multiple audio and data PIDs. Except in the 10x SD case when each service includes multiple audio and data PIDs, the processor can become overloaded; in this case, enabling the V2 pathway for each service reduces processor load and stabilizes transcode performance. USE V2 FOR 10X SD Improve performance when transcoding 10x SD services by enabling the V2 audio and data PID signal path for each service. Add Audio Outputs Default audio and data PID operations are listed in the following table. Alternative audio and data PID operations can be configured using the Audio tab in the Add an output dialog. To enable the V2 signal path operation in linear applications, click Add an audio output in the Audio tab of the output configuration dialogue. Clicking Add an audio output automatically enables V2 pathway functionality for the service, as described in the table below. Clicking Add an audio output in ABR applications has different behavior, as described in the table further below. Inca Networks Inc Family User Manual Revision 2 51

52 Figure 43 The Audio tab in the Add an output dialog. Linear Transcode Audio and Data PID Processing In the Default and V2 Pathways Transcode Type Default Default Audio and Data PID Outputs Audio and data PIDs are automatically passed through to the output using the same PID numbers as the source, unless filtered or remapped using a Source Filter. Audio and data PIDs pass through the transcode processor. If an audio output is configured in the Audio tab of the output configuration, the V2 pathway is in effect. V2 Pathway One audio service in the source is passed through or transcoded for each audio output configured in the Audio tab. All data PIDs in the source are included in the output unless removed using a Source Filter. Inca Networks Inc Family User Manual Revision 2 52

53 ABR Transcode Audio and Data PID Processing Transcode Type Default Default Audio and Data PID Outputs The first audio service in the source is automatically transcoded to AAC and included in the output. An alternate audio service can be selected using a Source Filter. Data PIDs included in the source are passed through to the output through the system CPU. All audio and data PIDs are processed using the V2 signal path. One audio service in the source is passed through or transcoded for each audio output configured in the Audio tab. Adaptive Bitrate Audio is no longer automatically transcoded to AAC. If AAC output audio is required, the audio transcode must be configured. All data PIDs in the source are passed through to the output unless removed using a Source Filter. All audio and data PIDs are processed using the V2 signal path. Figure 44 Audio configuration tab with outputs added. Click Add an audio output for each audio stream in the source to be included in the output. Audio outputs are passed through by default. To transcode the audio to a different codec or bitrate, select the desired audio transcode profile from the drop-down menu for the output. Refer to the following section for details about transcoding audio. Audio Transcoding Audio transcoding for linear applications and configurable audio transcode for ABR applications were introduced in firmware version Inca Networks Inc Family User Manual Revision 2 53

54 To transcode an audio stream to a different audio codec or bitrate, add audio outputs using the Audio tab in the output configuration, as described in the previous section, then select the desired audio transcode profile in the drop down menu for the output. The audio output configuration drop-down menu includes options for passthrough and several default audio transcode profiles based on standard bitrate for the available output codecs. User customized audio transcode profiles can be added to the system in the Profiles tab of the child device. Customized audio transcode profiles are discussed in more detail below, under Profiles. Figure 45 Select an audio transcode profile. Audio Transcode Licensing Audio transcoding is a licensed function. The system must contain enough audio transcode licenses for the configured number of audio transcodes. Details of the installed audio transcode licenses are found in the Hardware Modules section of the parent device, under Installed Options. The table shows the number of installed audio transcode licenses and the number of licenses in use. Figure 46 Audio transcode license details. Inca Networks Inc Family User Manual Revision 2 54

55 For backward compatibility, ABR licensed transcode processors have a VSL- AUX-A3D-DM audio transcode license installed in the module for each source the module can process. For example, a module containing three video transcode processor (VMA-XC3), each licensed for 2x HD ABR video transcodes will also have six VSL-AUX-A3D-DM audio transcode licenses installed in it. If a module with installed audio transcode licenses is removed from the chassis, its audio transcode licenses are no longer available in the chassis. Audio transcode licenses not installed in an ABR licensed module are installed in the chassis itself and remain with the chassis, even when the module is removed. All audio transcode licenses in the chassis, both those installed in the chassis, as well as any installed modules with ABR licensed processors, form a pool of available audio transcode licenses that are used as audio transcodes are configured in the system. The VSL-AUX-A3D-DM license enables transcoding functions, as described in the following tables. Audio Transcode License Capability Audio Transcode License MP2/AAC Stereo Decode MP2/AAC 5.1 Decode & Downmix Dolby Stereo Decode Dolby 5.1 Decode & Downmix MP2/AAC Stereo Encode VSL-AUX-A3D-DM-LIC VSL-AUX-DM-LIC Audio Transcode Codec Support Source Codecs MPEG-Audio AAC ADTS AAC LATM Dolby AC-3 / EC-3 Output Codecs MPEG-Audio AAC ADTS AAC LATM Direct Outputs and Probes Each 4400 chassis includes licensing for ten direct outputs or VidiOS probes from IP sources. Direct output and probe licensing is also included for streams received using the optional 8VSB/QAM and ASI interfaces. Optional licenses Inca Networks Inc Family User Manual Revision 2 55

56 are available to increase the number of direct outputs and probes from IP sources to 48 (4410, 4420, 4430) or 96 (4420, 4430). Direct outputs are streams that are passed through or turned around and can be full or partial multiplexes. Direct outputs are often used to demultiplex multiprogram source multiplexes (MPTS) into single program transports (SPTS), remove padding or bridge streams from one network or VLAN to another. VidiOS probes analyze streams that are generated by third party sources and can provide analysis results to Inca s All Seeing Eye monitoring system. Probes are like direct outputs but do not generate output streams. Direct outputs and probes are configured in the Direct Outputs section of the IP Outputs tab. Configure a Direct Output Tile Clicking on the icon in the Direct Outputs section will produce a dialog, as shown. The Source and Output tabs are described below; the Monitor/Failover tab is described in the Service Failover section, below. Figure 47 Direct output source configuration dialog Name [ Textbox ] This is a user-defined field for identification of the stream throughout the system. The name is used for source selection when configuring outputs and in logging. Default: <Blank> Source [ Listbox ] This field defines the stream that will be used as the source for the output. The drop-down menu lists all sources that are configured in the Sources tab. Source Filter [ Textbox ] This field defines the program filter to be used on the source stream. This field can be used to select programs and remaps and filter out programs and PIDs. Even though source filters are available for direct outputs, they are seldom used because program selection and filtering is normally done using output filters. Default: <Blank> Inca Networks Inc Family User Manual Revision 2 56

57 Configure a Direct Output Each tile has a drop-down menu located at its top right corner. Selecting Add an output will open an output configuration menu dialog, as shown below. Up to 16 direct outputs or probes can be added per direct output tile. Figure 48 Direct output; output configuration dialog. Name [ Textbox ] This is a user-defined field for identification of the stream throughout the system. The name is used for source selection when configuring outputs and in logging. Default: <Blank> Transcode Profile [ Listbox ] Transcode profiles are not used for direct outputs or probes. Default: No Transcode Network Port [ Checkbox ] The Network Port can be any configured and enabled network interface with a network connection. Note that only one output port can be selected for direct outputs; output port mirroring does not apply to direct outputs. Selection of more than one network port will result in an output configuration error. Default: Port 2 Inca Networks Inc Family User Manual Revision 2 57

58 Protocol [ Listbox ] Protocol defines the protocol that will be used for the output transport stream. The most commonly used setting in the head end is UDP Transport Stream. Alternatives to UDP Transport Stream are RTP, Real Time Protocol, and RTP+FEC. FEC, or Forward Error Correction, adds redundancy to the transmitted stream which downstream devices can use to correct a limited degree of data corruption through the transmission path. FEC settings are configured in Advanced Network Options in the Administration tab of the Maintenance menu. See FEC Settings for configuration details. Default: UDP Transport Stream Output Address [ Textbox ] This field defines the multicast or unicast address for the output. For a systematic approach to multicast addressing that reinforces efficient head end management, see Inca s application note IPTV Best Practices for Multicast Group Assignment. Default: <Blank> UDP Port [ Textbox ] This field defines the UDP port used for the output transport stream. Default: 1234 Transport Mode [ Listbox ] The Transport Mode controls aspects of the output transport stream. The available modes are described below. Constant mode, or CBR, is generally recommended for direct outputs. Default: Same as Constant if a Transport Rate is specified, otherwise the same as Variable. Constant This is the recommended transport mode and generates a groomed constant bitrate (CBR) stream. The Transport Rate must be specified and high enough to contain the selected program, including its peak burst bitrate, plus overhead for system tables. For constant bitrate sources, include at least 50 to 100 kbps of padding in the output to allow for fluctuations in the source bitrate. For variable bitrate sources, include at least 50 to 100 kbps above the highest burst bitrate of the source. The source program burst rate is measured by the system and can be observed by hovering the mouse pointer over the program s bitrate in the Source Monitor. The burst rate may vary over time and the measurement is updated every five seconds. The amount of padding included in the constant bitrate output can be observed in the Output Monitor. Inca Networks Inc Family User Manual Revision 2 58

59 Setting the Transport Rate too low will result in Multiplex Oversubscribed errors. Constant transport mode is a preferred mode that takes full advantage of Inca s VidiOS stream grooming technology. Peak Same as Constant mode except that padding is not included in the output stream. Refer to the Constant mode section for a discussion of Transport Rate considerations. Variable Pass-through without padding. Preserve original timing without grooming. Rarely used. Bypass Pass the source directly to output, bypassing stream grooming. Filter and PID remap are active but not PMT re-write. Rarely used. SI Only Same as Bypass except elementary streams are not inspected for alarm purposes. Rarely used. Suspend Suspend output. No output stream is generated. Rarely used. Transport Rate The Transport Rate field defines the maximum transport data transmitted per second, measured in bits per second. Required for Constant and Peak mode transport. Default: <Blank> Output Filter The Output Filter field is used to select all or part of the source multiplex for output and to remap source programs and PIDs. A typical application is to demultiplex a single program from a multi-program source multiplex using a simple program filter such as P3, where 3 specifies the program number in the source multiplex. Details of Inca s filter expressions are available in a separate guide, Inca Networks Filter Language Quick Reference. When demultiplexing programs from a multi-program source multiplex, programs can be dragged to the direct output tile directly from the source multiplex. This shortcut automatically populates the Name and Output Filter with the channel descriptor and program filter. Clicking Save will add the output to the tile. If Enable this stream is left checked, the output will start automatically. Default: <Blank> Enable [ Checkbox ] Toggle the output stream on or off. Default: Enabled Inca Networks Inc Family User Manual Revision 2 59

60 Configure a VidiOS Probe VidiOS probes analyze streams that are not generated by another Inca product and provide analysis results to Inca s All Seeing Eye monitoring system. Probes are like direct outputs but do not generate output streams. Probes are added to direct output tiles. Refer to Configure a Direct Output Tile for information about creating a direct output tile. Each tile has a drop-down menu button in the top right corner. Selecting Add a probe creates a configuration dialog as shown: Figure 49 VidiOS Probe configuration dialog. Name [ Textbox ] This is a user-defined field for identification of the probe throughout the system. This name will identify the probe in the Output Monitor as well as in the All Seeing Eye. Default: <Blank> Output Filter [ Textbox ] The Output Filter field is used to select the program in the source multiplex that will be analyzed by the probe, e.g. P8. The filter is specified using Inca s filter expressions. Details of Inca s filter expressions are available in a separate guide, Inca Networks Filter Language Quick Reference. Default: <Blank> Enable [ Checkbox ] Toggle the probe on or off. Default: Enabled Clicking Save will create a new probe entry under the selected tile. Profiles Tab Transcode profiles simplify the management of a large number of streams by enabling the creation of a library of standard settings for use with multiple sources. Editing a profile to change a setting updates all of the transcode operations using the profile, providing an efficient way to make changes. Transcode profiles are managed in the Profiles tab of the child device. Inca Networks Inc Family User Manual Revision 2 60

61 Add or Edit a Transcode Profile Figure 50 Transcode profiles shown in the Profiles tab of the child device Clicking Add a transcode profile opens a selection box from which one or more pre-defined transcode profiles can be copied from a library of example profiles. Once copied from the library, new or existing profiles can be customized to meet specific requirements by clicking the Edit icon, which results in an edit dialog. It is always possible to add a fresh copy of an example profile from the library. Figure 51 Adding a new video transcode profile from the library Inca Networks Inc Family User Manual Revision 2 61

62 Figure 52 Editing a video transcode profile Video Transcode Profile Settings This section provides detailed descriptions of the VidiOS transcode profile settings. A number of profile parameters are considered advanced settings. These include settings like PSI Interval, GOP Structure, GOP Closure Period, H.264 Profile and H.264 Level and require technical knowledge of MPEG encoding. Auto settings can be used in most cases. Certain applications, such as multi-screen may require specific settings in these fields. Short Name [ Text, up to 10 Characters ] Short Name is a brief descriptive name used to identify the transcode profile in the user interface in places where space is limited. The short name is limited to ten characters. Description [ Text ] Description provides space a description of the profile and is often used to describe key features like frame size, codec type, transport mode, and video bitrate. E.g., AVC 480i VBR 1.8 Mbps. Transport Mode [ Constant Peak Variable ] The Transport Mode field defines the type of MEG-2 transport stream that will be generated, either Constant bitrate or Peak Variable bitrate. Constant In Constant Transport Mode the encoder will add null packets to the transport stream to achieve a constant Transport Rate. Peak Variable Peak Variable mode provides network bandwidth efficiency by using only the bandwidth needed to transmit the transport stream payload, without adding the null packet padding used to generate a constant bitrate stream. From a stream timing perspective, Peak Variable mode is the similar to Inca Networks Inc Family User Manual Revision 2 62

63 Constant mode except that null packets are not transmitted. In Peak Variable mode the output bitrate will fluctuate, but will not exceed the Transport Rate. Note that Peak Variable is not the same as variable bitrate and a transport rate must be set. Transport Rate [ bits per second ] The Transport Rate field defines the maximum bitrate of the output transport stream in bits per second. This setting differs from the Video Bitrate setting, as the transport stream carries all of the video, audio and data PIDs along with transport overhead. Set the Transport Rate to the sum of the video elementary stream bitrate plus 5% plus the audio and data PID bitrates plus 100,000 to 200,000 bits per second for padding. Transport Rate = Video ES Rate + 5% + Total Audio Bitrate + Data PIDs + ~150,000 bps For example, if the CBR Video Bitrate is set to 8,000,000 bps (8 Mbps) and there are two audio streams at 192,000 bps (192 kbps) and 384,000 bps (384 kbps) and no data PIDs, start with a CBR transport rate of: Transport Rate = 8,000, , ,920, , ,000 9,150,000 bps Setting too low a Transport Rate will result in the transport container being too small to contain the content and will result in the loss of data and Multiplex may be oversubscribed errors. The transport rate can be adjusted up or down as needed in the application. Encoding [ H.264 CBR H.264 VBR MPEG-2 VBR MPEG-2 CBR ] The Encoding field defines the MPEG encoding standard, or codec, and video bitrate mode. MPEG-2 The MPEG-2 standard was first released in 1996 and continued to be developed until Although it has been succeeded by the more efficient H.264 standard, it remains a popular choice for backward compatibility with existing infrastructure. H.264 (MPEG-4 AVC) The H.264 standard was introduced in 2003 as the successor to MPEG-2 video encoding. As a general rule, H.264 offers a 40% encoding efficiency improvement compared to MPEG-2. In other words, H.264 requires only 60% of the bitrate needed to achieve the equivalent picture quality in MPEG-2. H.264 is widely used in IPTV applications but may not be compatible with some legacy infrastructure. CBR (Constant Bitrate) In constant bitrate mode the output video will be encoded at the constant bitrate defined in the Video Bitrate field. An advantage of CBR mode is predictability of the output bitrate. Inca Networks Inc Family User Manual Revision 2 63

64 VBR (Variable Bitrate) In variable bitrate mode the encoder will vary the encoded bitrate depending on the video content, reserving higher bitrates for large scene changes or high action. VBR encoding targets the average Video Bitrate in normal circumstances, but can burst to a defined Peak Video Bitrate when needed. VBR encoding only uses as much data as needed to encode the video frames, even if it is well below the target average. When VBR encoding is selected, the Video Bitrate becomes the target average and Peak Video Bitrate becomes the maximum. Video Bitrate [ bits per second ] The Video Bitrate field defines the output video bitrate in bits per second. This field acts as a maximum when the Encoding is set to MPEG-2 CBR or H.264 CBR. In VBR encoding Video Bitrate defines the target average bitrate. The Video Bitrate should always be set lower than the Transport Rate and leave room for audio streams and transport overhead. See the Transport Rate discussion above for a more detailed discussion. Peak Video Bitrate [ bits per second ] When the Encoding field is set to MPEG-2 VBR or H.264 VBR, this field defines the maximum encoded bitrate. In CBR encoding this parameter is ignored. To create room for the VBR encoder to do its work, set the Peak Video Bitrate to at least 1.5 times the Video Bitrate. BURSTING A sudden short duration increase in the Video Bitrate is known as bitrate Bursting. Bursting occurs in VBR encoding due to rapid changes in the video picture, such as in sports or action scenes. Bursting is temporary and is defined as a peak in the Video Bitrate. PSI Interval [ milliseconds ] Program-Specific Information (PSI) contains tables which store metadata describing the programs in the transport stream. VidiOS displays two PSI tables in the Input and Output Monitor sections of the user interface, the Program Allocation Table (PAT) and Program Map Table (PMT). The PAT indexes the programs contained in the transport stream while the PMT indexes the Packet Identifiers (PIDs) making up each of the programs. The PSI Interval specifies the interval, in milliseconds, at which these tables are inserted in the output transport stream. The default PSI Interval is suitable in the majority of applications. Default: 150 Frame Size [ Drop-down menu ] The Frame Size drop-down menu specifies the frame size of the transcoded output. Selecting Auto preserves the Frame Size of the video source. Inca Networks Inc Family User Manual Revision 2 64

65 Transcoded outputs can be encoded to the same size as the source video or lower. Upscaling to a frame size that is larger than the source frame size is not supported. Specifying a frame size that is larger than the source is the same as specifying Auto; the output will use the same frame size as the source. The maximum frame size is restricted by the H.264 Level setting discussed below. If an H.264 Level is explicitly defined, see the table of H.264 Levels and respective constraints below, specify a Frame Size that is supported for the desired level. Default: Auto Interlacing [ Auto Progressive Interlaced ] The Interlacing field defines whether the output video will be interlaced or progressive. If Auto is selected, the output video will follow the source. Interlaced Interlacing is a method of drawing video data introduced in the 1930s with the aim of saving bandwidth and reducing flicker, a problem inherent to progressive scanning at the time. This method also allowed the doubling of the perceived frame rate by interleaving two consecutive frames, using odd lines of the first and the even lines of the second. Progressive Progressive video draws sequential frames in order, similar to a film strip. Each image is drawn line by line, top to bottom. Nearly all digital displays use this method of video representation. Interlaced video must first be deinterlaced for proper playback on progressive displays. Default: Auto Aspect Ratio [ Drop-down menu ] The aspect ratio of the output is defined by its active format descriptor. By default, the transcoded output will follow the source s aspect ratio. The source s aspect ratio can be over-ridden using the Aspect Ratio setting in the transcode profile. Note that the aspect ratio is independent of frame size. Default: Auto Frame Rate [ Drop-down menu, Frames per second ] Frame Rate field specifies the number of full frames that will be encoded in the output video stream per second. In interlaced mode, the field rate will be twice the frame rate. When Frame Rate is set to Auto, the output frame rate will be the same as the source frame rate. The maximum supported frame rate for a frame size of 1920x1080 is thirty frames per second. The maximum frame rate may be limited by the H.264 level. If an H.264 Level is explicitly defined, see the table of H.264 Levels and respective constraints below, specify a Frame Rate that is supported for the desired level. Default: Auto Inca Networks Inc Family User Manual Revision 2 65

66 GOP Structure and GOP Closure Period MPEG encoding uses a group of pictures, or GOP, as a basic building block. GOP Structures describe how the MPEG video encoder calculates deltas, or differences, between I-Frames, or keyframes. A GOP is a repeated pattern of three types of frame, I, B and P. The number of frames from one I-frame to the next is the GOP Length. The duration of a standalone GOP that doesn t depend on other frames for picture data is the GOP Closure Period. Each of these parameters is described in more detail below. Some GOP Structures can encode video more efficiently, but at the expense of increased computational load. Conversely, other GOP Structures are less computationally intensive, but result in less efficient encoding and require a higher bitrate to achieve equivalent picture quality. Although a large number of GOP structures are available, the most common setting for linear applications is Auto with the default GOP length of 1500 milliseconds. Certain middleware systems or advanced applications may require specific GOP structures and lengths. Inca Networks Inc Family User Manual Revision 2 66

67 GOP Structure [ Drop-down menu ] The following table describes the different types of frames used in a GOP. Frame Type I P B Description Intra or I-Frames are the only self-sufficient frames in MPEG encoding. They contain all the data necessary to create an accurate representation of the current frame. They are the least computationally intensive type of frame, but also the least efficiently compressed. In Closed GOPs, I-Frames mark the beginning of a GOP sequence. I-Frames are also known as keyframes. See the GOP Closure Period section below for additional discussion about open and closed GOPs. P-Frames rely on the calculation of deltas between the current frame and the previously decoded frame(s). Beyond merely calculating differences, P-Frames also attempt to predict the content of the current frame based on motion patterns in previous frames. This is an effective technique, as many of the differences across frames can be eliminated by performing relatively simple transformations on previous frames. This motion compensation mimics common camera movements in TV and cinema, such as vertical and horizontal translations, pan, tilt and roll. B-Frames are similar to P-Frames, but can also use future frames as predictive elements. This means B-Frames contain less data than P-Frames, but require greater computational resources and more decoder buffer memory. In Open GOPs, B-Frames mark the beginning of a GOP Sequence. Figure 53 Description of frame types used in MPEG encoding GOP Structures supported by the 4400 The 4400 GOP Structure is selected from a drop-down list and is made up of a number, the GOP Length, followed by a frame sequence consisting of an I- Frame followed by zero or more B and P frames. Examples include: Auto 30 IBBPBBP 90 IBBPBBP 32 IBBBPBBBP 32* IBBBPBBBP Inca Networks Inc Family User Manual Revision 2 67

68 Where denotes that the sequence of B and P frames following the initial I-Frame repeats a number of times up to the GOP length. For example, the GOP structure 90 IBBPBB specifies a GOP structure with 89 frames between successive I-Frames, for a GOP length of 90 frames. At a frame rate of 30 frames-per-second, a GOP length of 90 represents three seconds of video. For most linear transcoding applications Inca recommends setting the GOP structure to Auto, which allows the transcode processor to select a suitable GOP structure. In the above example, the GOP structure 32* IBBBPBBBP is a simplified structure that does not use B frames as reference for other frames. Longer GOPs compress video data more efficiently, as the encoded data contains fewer of the lower-efficiency I-Frames, but may allow transcoding errors to accumulate during the period of the GOP. GOP length can also affect trick play features, which use a special type of I- Frame called an IDR, or Instantaneous Decoder Refresh, frame for random access features like pause, fast forward and rewind. In these applications, longer GOP lengths can reduce the granularity of control available to the consumer. See the discussion below on GOP Closure Period for additional details. A consideration when specifying the GOP Structure is that some structures may prove too resource intensive for older playback devices. If in doubt consult the device specifications to determine its capabilities. GOP Structures are often described using two numbers, M and N. Inca Networks Inc Family User Manual Revision 2 68

69 M N Denotes the distance between anchor frames (I-Frames and P- Frames). The gaps between anchor frames are bridged with B- Frames. Denotes the number of frames between successive I-Frames. This value corresponds exactly to the GOP Size. For example: M N GOP Sequence 2 15 I B P B P B P B P B P B P B P I 4 13 I B B B P B B B P B B B P I 1 15 I P P P P P P P P P P P P P P I 0 12 I I I I I I I I I I I I I Figure 54 Examples of GOP Sequences being represented by M and N GOP Closure Period [ milliseconds ] The GOP Closure Period sets the interval at which Instantaneous Decoder Refresh (IDR) frames are sent. An IDR frame is a type of I-Frame which indicates to the encoder that no frame preceding it may be used as a reference. IDR frames are completely self-referential, and can be decoded independent of any other frame. Video playback controls such as pause, rewind and fast-forward often use IDR frames as stop points. Seeking between IDR frames is not always supported, as it is more computationally intensive and therefore impractical for less capable playback devices. Setting the GOP Closure Period to 0 will forgo any closure period. This is known as an Open GOP. When the GOP is open, the GOP Structure begins with a B-Frame rather than an I-Frame. Using an Open GOP generally results in slightly more efficient compression than a Closed GOP of the same size, as the data-laden I-Frame has been replaced with the more efficient B-Frame. The Closure Period is defined in milliseconds. The default setting can be used in most cases. Default: 1500 Inca Networks Inc Family User Manual Revision 2 69

70 H.264 Profile [ Drop-down Menu ] The H.264 Profile field defines the complexity of the encoding features used by the encoder. Generally, there is a positive correlation between efficiency, encoding complexity and the computational resources required in the decoder. H.264 Profiles allow encoding settings to be tailored to the capabilities of the target playback device. The 4400 supports the following profiles: Baseline Main High Baseline profile is the simplest and does not support the use of B-Frames or interlaced video. Each profile becomes increasingly more efficient and resource intensive to encode and decode. The Main profile is used for SD TV broadcasts using the MPEG-4 format. The High profile is used for broadcast and disc applications, especially for HDTV - DVB HDTV and Blu-ray, for example. The default setting can be used in most cases. Default: Auto H.264 Level H.264 encoding levels define a series of encoding constraints. Each level controls maximums such as decoding speed, frame size, bitrate and resolution. The encoder includes this information as metadata which precedes the actual MPEG data. This allows playback devices to quickly determine if the data can be decoded effectively with the available resources. Refer to the table below for H.264 levels and their respective constraints. Inca Networks Inc Family User Manual Revision 2 70

71 Max decoding speed Max Frame Size Max VCL kbit/s Max resolution Level Luma samples/s Macroblocks per second Luma samples Macroblocks Baseline & Main Profiles High Max frame rate (FPS) 1 380,160 1,485 25, b 380,160 1,485 25, ,000 3, , ,536,000 6, , x240@ ,041,280 11, , ,041,280 11, , ,000 2, ,068,800 19, , ,000 5, ,184,000 20, ,720 1,620 4,000 5, ,368,000 40, ,720 1,620 10,000 12, ,648, , ,600 3,600 14,000 17, ,296, ,000 1,310,720 5,120 20,000 25, ,914, ,760 2,097,152 8,192 20,000 25, ,914, ,760 2,097,152 8,192 50,000 62, ,693, ,240 2,228,224 8,704 50,000 62, ,994, ,824 5,652,480 22, , , ,658, ,040 9,437,184 36, , , ,841,600 2,073,600 9,437,184 36, , , Figure 55 Table of H.264 Levels and respective constraints The Luma Samples/s column is roughly equivalent to the maximum number of pixels per second that can be decoded. For example, H.264 Level 3.1 has a maximum resolution and frame rate of 1280 by 720 at 30 fps. In this case, the product of is exactly equivalent to the Luma Samples/s column, 27,648,000. This number of pixels can be factored into any three numbers, each one representing the width, height and frame rate, given that they are supported. The product of the frame dimensions and frame rate do not have to equal the Luma Samples/s, but they should not exceed it by a large margin. The default setting can be used in most cases. Default: Auto Inca Networks Inc Family User Manual Revision 2 71

72 Video Only [ Checkbox ] Video Only is used in applications such as PIP, or picture-in-picture, generation, in which the output transport stream includes only a video PID, without audio. Default: <Unchecked> Audio Transcode Profile Settings This section describes the VidiOS audio transcode profile settings. Most audio transcode configurations are addressed by the fixed default audio transcode settings available in the output configuration. User defined audio transcode profiles can also be added in the Profiles tab. To create a new audio transcode profile, click Add an audio profile in the Profiles tab. Figure 56 Add an audio profile Short Name [ Text, up to 10 Characters ] Short Name is a brief descriptive name used to identify the transcode profile in the user interface in places where space is limited. The short name is limited to ten characters. Description [ Text ] Description provides space for a description of the profile and is often used to describe key features like codec type, transport mode, and audio bitrate. Codec [ Drop-down menu ] The Codec drop-down menu offers a list of supported output audio codecs. Transport [ Default ADTS LOAS/LATM ] The Transport drop-down menu offers a selection of audio transport modes. Default applies in most cases. ADTS and LOAS/LATM apply only to AAC outputs. In the case of AAC output, the default transport mode is ADTS. Default: Default Bitrate [ Drop-down menu ] The Bitrate drop-down menu offers a selection of audio output bitrates. Inca Networks Inc Family User Manual Revision 2 72

73 Default: The default bitrate is codec dependent and follows the default audio transcode profiles. Report Tab The report tab provides a tabular overview of the video output configuration, as shown below. The view is read-only and it is not possible to change the configuration in the Report tab. Figure 57 Tabular view of video outputs in the Report tab Administration Tab Export, Backup or Restore Video Settings Backup and restoration of the video setting in the child device is available below the Direct Outputs section of the IP Outputs tab. The following configurations can be backed up and restored. A human readable backup of the configuration is also available. IP Sources Local Sources (ASI, 8VSB, QAM) IP Outputs Transcode Profiles System level settings such as Device Names, NTP, SNMP, and network interface settings are not included in the child device video settings backup. Export Settings Human Readable Backup In the IP Outputs tab of the Child Device clicking the Export button below the heading Output Streams downloads the device s video settings to the local computer s Downloads folder in spreadsheet format. The downloaded spreadsheet is for viewing only and cannot be read back into the unit. Inca Networks Inc Family User Manual Revision 2 73

74 Export button Figure 58 Export video configuration in human readable form Backup and Restore Settings The backup and restore options are accessed in the IP Outputs tab of the child device, under the Direct Outputs heading. The Backup button generates an XML backup file, which can be used to restore device settings. The Restore button opens a dialog box, which can be used to select a previously saved XML backup, as shown below. A message is displayed to indicate successful restoration. Figure 59 Dialog box prompting the user for a backup file Inca Networks Inc Family User Manual Revision 2 74

75 Figure 60 Dialog box indicating a successful configuration restore Service Failover Introduction to Service Failover Service failover enables the operator to configure a secondary, or backup, source for an output that the system can automatically bring into service if the output s primary source fails. The primary source is monitored for up to six user-configurable trigger conditions. When an active trigger threshold is met on the primary source, the system can be configured to automatically bring the secondary source into service in place of the primary source. When the trigger condition on the primary source clears, the system automatically returns service to the primary source. In the Modular Series 4400 family, service failover is available for any configured transcoded or direct output, up to the number of available service failover licenses. Service failover for transcoded outputs can take place either before or after the transcode operation. Service Failover Description In service failover, the system monitors up to sixteen PIDs in the primary source used to generate an output. Up to six parameters can be monitored, with userconfigurable thresholds. The system can be configured to automatically fail over to a user specified secondary source when any of the trigger conditions are met. The secondary source can be any source in the system, and filter expressions can be used to remap the secondary source programs and PIDs to match the primary stream. This section describes service failover functionality. The following section describes service failover configuration. For the following discussion please refer to the screen shot of the failover configuration tab provided below. Inca Networks Inc Family User Manual Revision 2 75

76 Figure 61 Service Failover Configuration Tab for a 4400 Transcode Primary and Secondary Sources Any active source in the system can be a primary or secondary source. It is the responsibility of the operator to ensure that the selected secondary source and the failover settings meet the requirements of downstream equipment. For example, it may be necessary to remap program and PID numbers to match those of the primary source. Program and PID remapping is accomplished using filter expressions. Program and PID Filtering and Remapping Program and PID filtering and remapping is accomplished using filter expressions. Details of Inca Networks filter expressions can be found in the Inca Networks - Filter Expression Quick Reference. Examples of filter expressions are included below, under Configure Service failover. Source Monitor For transcoded outputs, monitoring can take place either before or after the transcode, using Watch the source or Watch the transcoder output, respectively. The selected monitor mode determines where in the signal flow the secondary source will be substituted in the event of a failover. Inca Networks Inc Family User Manual Revision 2 76

77 In Watch the source mode, source monitoring and secondary source substitution take place before the transcode processor. The substituted secondary source will be transcoded using the same transcode profile that was applied to the primary source. It is the operator s responsibility to ensure that the transcode processor license and transcode profile are compatible with the secondary source. Trigger Conditions Primary Source VidiOS Analysis Output Filter VidiOS Analysis Output Secondary Source VidiOS Analysis Secondary Filter Figure 62 Direct Outputs Watch the Source Trigger Conditions Primary Source VidiOS Analysis Source Filter Transcode Processor Output Filter VidiOS Analysis Output Secondary Source VidiOS Analysis Secondary Filter Figure 63 Transcoded Outputs Watch the Source In Watch the transcoder output mode, monitoring and secondary source substitution take place after the transcode processor. The substituted secondary source is output directly, without being transcoded. Trigger Conditions Primary Source VidiOS Analysis Source Filter Transcode Processor Output Filter VidiOS Analysis Output Secondary Source VidiOS Analysis Secondary Filter Figure 64 Transcoded Outputs Watch the Transcoder Output For ABR transcoded outputs, in which multiple outputs are derived from one source, only Watch the Source mode should be used. In the event of source failure, it is important that the substitute output pass through an ABR transcode process to ensure that the multi-bitrate outputs are frame aligned. For direct outputs, Watch the source mode should be used. Watch the transcoder output mode is not applicable unless a transcode operation is taking place. Inca Networks Inc Family User Manual Revision 2 77

78 Monitor Settings Triggers Up to six parameters in up to 16 selected PIDs in the primary source can be monitored. Failover to the secondary source is triggered if any of the user configurable trigger thresholds is exceeded. The six monitored parameters relate to PIDs or to the program. PID level monitors include Low Bitrate, Continuity Errors and Encrypted stream errors. Program level monitors include PAT loss, PMT loss and Video frame loss. Figure 65 Monitor Settings One or more monitored PIDs are specified in the Monitor PIDs field using filter expressions. The first specified PID determines the monitored program. For example, if the first specified PID is the first audio PID in the second program or the source multiplex program level monitoring will be performed on the second program in the source multiplex. Monitored parameters are specified using per second units. Parameters are sampled in five second intervals. Alarm and failover decisions are made within the five second sampling interval framework. The Duration parameter to the right of PAT loss applies to the PAT loss, PMT loss, Video frame loss and Encrypted stream errors parameters. Whenever a Threshold and Duration threshold is exceeded, an alarm is displayed in the Output Monitor. If Failover mode is set to Automatic Failover, the system will fail over to the configured secondary source. PID Level Monitors PID level monitors are monitored for each specified PID. Low Bitrate Low bitrate monitoring compares each monitored PID s bitrate to the specified threshold. If a PID s bitrate falls below the specified threshold for the specified duration, an alarm is raised; if automatic failover is enabled, the output fails over to the secondary source. Continuity Errors Continuity errors detects continuity error rates in each monitored PID. If the continuity error rate in any monitored PID exceeds the specified threshold for Inca Networks Inc Family User Manual Revision 2 78

79 the specified duration, an alarm is raised; if automatic failover is enabled, the output fails over to the secondary source. Encrypted Stream Errors Encrypted stream errors detects the presence of encryption in each monitored PID. If encryption is detected on any monitored PID for the specified Duration, an alarm is raised, and, if enabled, a failover event is triggered. This parameter is especially useful for the detection of regional service blackouts. Transport and Program Level Monitors Program level monitoring is performed at the level of MPEG-2 transports and programs. The system monitors the program associated with the first PID specified in the Monitor PIDs field. For example, if the first monitored PID is associated with program number three in the source transport stream, the system will use Program 3 for program level parameters. PAT Loss PAT loss is a transport level monitor that detects loss of the program association table, or PAT, in the primary source transport stream. If the PAT is not detected in the source transport stream for the specified Duration, an alarm is raised; if automatic failover is enabled, the output fails over to the secondary source. PMT Loss PMT loss detects the loss of the primary source program s program map table. If the PMT is not detected for the specified Duration, an alarm is raised; if automatic failover is enabled, the output fails over to the secondary source. Video Frame Loss Video frame loss detects loss of video frame header information in the associated program s video PID. If the video frame information is not detected for the specified Duration, an alarm is raised; if automatic failover is enabled, the output fails over to the secondary source. Failover Modes The action that is taken after a monitored parameter exceeds its threshold is configured in the Failover section at the bottom of the failover configuration tab. Three options are available: Automatic failover causes the system to automatically fail over to the secondary source after a trigger threshold has been exceeded. Force secondary allows the operator to manually force a failover to the secondary source. Disable disables the failover function while continuing to monitor the source PIDs. In all cases, alarms are generated when monitored parameters are exceeded. Inca Networks Inc Family User Manual Revision 2 79

80 Figure 66 Failover Modes Alarms When one or more monitor settings are exceeded, an alarm is generated for the output stream. The alarm message indicates the failover type and lists the triggered parameters. Examples of the alarm triggers are shown below. Figure 67 Output Alarm with Failed Primary Source Automatic Failover Enabled Figure 68 Output Alarm with Failed Primary Source Automatic Failover Disabled Inca Networks Inc Family User Manual Revision 2 80

81 Figure 69 Output Alarm Force Secondary Service Failover Configuration Where to Find Service Failover Configuration Service failover is configured in the output configuration tile in the child device s IP Outputs tab. Service failover is accessed by selecting Edit in the drop-down menu in the source or output section of the desired output tile, then selecting the Monitor/Failover tab, as shown in the screenshots below. Monitor/Failover configuration in the source region of the tile applies to the tile s first output. If more than one output is generated in the tile, and if using Watch the transcoder output monitor mode, configure service failover for each output individually. If using Watch the source monitor mode, service failover can be configured in either the source or output sections of the tile and will affect all of the tile s outputs. Figure 70 Select Edit in the Source Portion of the Tile Inca Networks Inc Family User Manual Revision 2 81

82 Figure 71 Select Edit for an Output Configure Service failover Configure the Source Monitor Source Monitor Monitor mode [ Disable Watch the source Watch the transcoder output ] This menu enables or disables source monitoring and selects whether the source or transcoded output is monitored. In the Inca Networks Modular Series 4400, each monitored source uses one service failover license. Disable Primary source monitoring is disabled for this output. Watch the source Primary source monitoring is performed on the specified PIDs. Watch the transcoder output Monitoring is performed on the specified PIDs in the transcoded output. This option applies to transcoded outputs and should not be used for direct outputs. In failover, the secondary source replaces the transcoded output and the secondary source is not transcoded. Default: Disable Monitor PIDs [ Textbox ] This field specifies one or more PIDs to monitor in the source selected in Monitor mode. Up to sixteen PIDs can be specified. PIDs are specified using Inca Networks filter expressions, separated by commas. Several example expressions are provided below. For more information about filter expressions, please see Inca Networks - Filter Language Quick Reference. Example PID filters P@1.A1 The first audio PID in the first program in the source multiplex. P@3.A1 The first audio PID in the third program. P@1.V1 The first video PID in the first program. 52 PID number , P@1.A1 PID number 49 and the first audio PID in the first program. Inca Networks Inc Family User Manual Revision 2 82

83 Default: Configure the Monitored Parameters Monitor Settings Monitor parameters [ Checkboxes ] Up to six parameters can be selected using checkboxes. All parameters with checkmarks are monitored. All six parameters are selected by default. Click the checkboxes to select or de-select parameters. Thresholds and durations can be configured for low bitrate and continuity errors. The duration setting to the right of PAT loss applies to all other parameters. If Automatic failover is selected in the Failover mode section, the threshold and duration settings are used as both the failover trigger and recovery rules. For example, if a duration of 15 seconds is specified, the primary source must be clear of the error for 15 seconds before the system cancels the failover. Default: All parameters monitored Low bitrate Monitor the bitrate of all specified PIDs. Trigger an alarm and failover, if enabled, if the bitrate of any selected PID falls below the bits per second specified in Threshold for the number of seconds specified in Duration. Default Threshold: 50,000 (50 kbps) Default Duration: 15 seconds Continuity errors Monitor all specified PIDs for continuity errors. Trigger an alarm and failover, if enabled, if the rate of continuity errors in any selected PID exceeds the number of errors per second specified in Threshold for the number of seconds specified in Duration. Default Threshold: 5 Default Duration: 15 seconds PAT loss Monitor the source transport stream for the loss of its PAT, or program association table. Trigger an alarm and failover, if enabled, if the PAT is not detected for the number of seconds specified in Duration. Default Duration: 5 seconds PMT loss Monitor the source transport stream for the loss of the PMT, or program map table, associated with the first specified PID. Trigger an alarm and failover, if enabled, if the PMT is not detected for the number of seconds specified in the Duration field to the right of PAT loss. Inca Networks Inc Family User Manual Revision 2 83

84 Video frame loss Monitor the source transport stream for the loss of video frame header information in the program associated with the first specified PID. Trigger an alarm and failover, if enabled, if the video frame information is not detected for the number of seconds specified in the Duration field to the right of PAT loss. Encrypted stream errors Monitor all specified PIDs for an active encryption flag. Trigger an alarm and failover, if enabled, if an encryption flag is present for the number of seconds specified in the Duration field to the right of PAT loss. This parameter is especially useful for the detection of regional service blackouts. Configure Failover Failover Failover mode [ Disable Force Secondary Automatic Failover ] This dropdown menu selects or disables a failover mode. Disable Failover is disabled for this monitor. Force Secondary Force failover to the secondary source specified in Secondary source. Monitored results are reported in the resulting failover alarm but do not affect the failover state. Automatic failover If the threshold and duration are exceeded for any monitored parameter on any monitored PID, automatically fail over to the specified secondary source. Automatically revert to the primary source after the error condition clears. If a failover is triggered, an alarm is displayed in the Output Monitor; the alarm message lists all triggered parameters. Default: Disable Secondary source [ Dropdown menu ] Select the desired secondary source from the dropdown menu; all available sources are listed. It is the operator s responsibility to ensure that the secondary source is compatible with downstream equipment. A Secondary filter can be used to remap programs and PIDs for compatibility with the primary source. Secondary filter [ Textbox ] Specify a filter to select the desired secondary program from the selected Secondary source. If necessary, remap programs and PIDs as required to make the secondary output compatible with the primary source. Remapping example: Inca Networks Inc Family User Manual Revision 2 84

85 This example refers to the primary and secondary source example shown below, in which the primary source is on the left. To select program three in the secondary source and to remap its program number and PIDs to match the primary source, the following secondary filter can be used: 120:52. Note that in this example, the secondary source has fewer audio PIDs than the primary. Figure 72 Example Primary and Secondary Sources Figure 73 Remapped Program and PID Configuration Inca Networks Inc Family User Manual Revision 2 85

86 Figure 74 Failover with Remapped Program and PID Maintenance Menu The Maintenance menu, located under Shortcuts at the left of the web-based user interface, provides access to a number of system level controls and information. System level settings available in the maintenance menu include: Management network interface IP configuration, Advanced network options, Admin user password, Reboot and power down controls, Package manager for firmware updates, SNMP MIB download, and Chassis level configuration download. Inca Networks Inc Family User Manual Revision 2 86

87 System Maintenance Tab Management Network Interface Configuration Management network interface settings can be changed using the web-based user interface in the System Maintenance tab of the Maintenance menu. The Maintenance menu is accessed by clicking Maintenance, under Shortcuts at the left of the web-based user interface. To configure the management network interface, select Configure the management network interface in the drop-down menu under Administration. NOTE Changes to management network interface settings come into effect after the next chassis reboot. Management network interface configuration through the web-based user interface requires that an IP address has already be assigned to the management network interface, either through DHCP or a previous static configuration, and that the user has logged in to the web-based user interface using the admin user password. USERNAME AND PASSWORD The default username and password for the web-based user interface are: Username: admin Password: admin Use caution when changing management network settings as misconfiguration can result in loss of access to the web-based user interface. If access to the management network interface is lost, check the unit s front panel LCD display for the management IP address. All active IP addresses are displayed on the LCD, so it is important to look specifically for the management interface. The Inca networks boot menu can always be used to re-configure the management interface network settings using a serial cable. A serial cable is included with unit. See The Inca Networks Boot Menu for details. CAUTION Use care when changing management network interface settings. Incorrect or forgotten network settings can result in loss of access to the unit. The 4400 will display the current management IP address on its front panel LCD. If the unit cannot be accessed using the displayed management IP address, management network settings may be reconfigured using a serial cable and the Inca Networks Boot Menu. Inca Networks Inc Family User Manual Revision 2 87

88 The figures below show the Administration drop-down menu in a system configured to use DHCP Management DHCP is shows as Active and a system configured to use static network settings. Figure 75 System administration menu with Management DHCP Active Figure 76 Management network interface static settings Name [ Textbox ] This field defines the alias for Port 1. Examples of names that clearly reflect the nature of the port include MGMT, Admin and Management. Default: Port 1 Inca Networks Inc Family User Manual Revision 2 88

89 IP Address [ Static DHCP ] This field defines how the management interface will obtain its IP settings, either using static settings, or from a DHCP server. DHCP is the default configuration to simplify initial access to the user interface, but static settings are used in most applications. Static Statically configured IP addresses are fixed and must not conflict with existing addresses on the network. DHCP DHCP is a networking protocol that allows for the automatic negotiation and allocation of IP addresses. Successful DHCP operation requires that the nearest upstream router run a DHCP server. The IP addresses allocated may be subject to change, though some DHCP servers can be configured to map a specified IP address to the port s MAC address. Default: DHCP IP Address [ Textbox ] This field defines the static IP address to be used; the address is entered without leading zeroes. This field can be left empty if the interface is being configured using DHCP, as the DHCP server will allocate IP address automatically. Entries in this field are ignored if DHCP is enabled. Default: <Blank> Network Mask The network mask defines the scope of IP addresses or subnet that will be considered part of the internal network using a bitmask. IP addresses outside the range defined by the Network Mask will be considered external to the network and routed through the gateway, if configured. Entries in this field are ignored if DHCP is enabled. Default: <Blank> Gateway The Gateway, if available, defines the address of the network router that will be used when an IP address outside the subnet defined by the assigned IP address and network mask is requested. Although this field is optional, Inca recommends setting a gateway, if present, to avoid connection issues with timeservers, or in the event remote access to the system is required. Default: <Blank> Advanced Network Options Advanced video interface network options are configured in the System Maintenance tab of the Maintenance menu, accessed under Shortcuts at the left of the web-based user interface. Advanced network options include port aggregation and forward error correction, or FEC. To configure advance network options, select Advanced network options under Administration. Inca Networks Inc Family User Manual Revision 2 89

90 Note that changes to Advanced network options come into effect after the next chassis boot. NOTE Changes to management network interface settings come into effect after the next chassis reboot. Figure 77 Advanced network options Video Port Aggregation Mode Video port aggregation groups video ports into pairs to provide redundancy and link aggregation functions. Three pairing modes are available: active failover, round robin and LACP, as detailed below. In its default state port aggregation is disabled and each video port operates independently of all others. A chassis reboot is required to bring changes to the video port aggregation mode into effect. Active video port aggregation is indicated in the System tab of the parent device under Network Traffic Monitor. When port aggregation is active, a is displayed to the left of the secondary ports, as shown in the figure below. NOTE Changes to the video port aggregation mode come into effect after the next chassis reboot. Port Pairing Port pairings are chassis dependent and are fixed. The lower numbered port in each pair is the primary port and the higher numbered is the secondary port. Inca Networks Inc Family User Manual Revision 2 90

91 When video port aggregation is active, configurations of secondary ports in the parent device System tab are ignored. In the 4430, each video port is paired with its above neighbor as follows: 2/6, 3/7, 4/8, and 5/9. Paired ports are listed here in the order primary/secondary. In the 4420, the port pairings are: 2/6, 3/7, and 4/8. Port 5 is not paired and remains independent of all other ports. In the 4410, the port pairings are: 2/5 and 3/6. Port 4 is not paired and remains independent of all other ports. Video Port Aggregation Mode [ Disabled Round Robin Active Failover LACP Aggregation ] Disabled Port aggregation is disabled and each video port operates independently of all others. Round Robin Outputs assigned to the primary port alternate between the primary and secondary port. For example, if three streams are transmitted, the first and third streams may be transmitted through the primary port and the second stream through the secondary port. Active Failover Inputs and outputs will be received and transmitted through the primary port. If communication on the primary port fails, the system will attempt to reestablish communication on the secondary port. LACP Link Aggregation Control Protocol Traffic will be shared evenly between the primary and secondary ports, effectively creating a two gigabit interface. This mode requires that the corresponding switch ports also be configured for link aggregation using LACP. Default: Disabled Figure 78 Network traffic monitor in a 4430 with port aggregation enabled Inca Networks Inc Family User Manual Revision 2 91

92 FEC Settings Forward Error Correction, or FEC, adds extra information to an RTP stream that can be used to recover data lost due to transmission errors. FEC redundancy is added to output RTP data flow when RTP+FEC is selected in the Protocol dropdown menu of an output configuration. See Configure a Transcoded Output and Configure a Direct Output. FEC Settings are configured in the Advanced Network Options section of the Maintenance menu, shown in the figure above, where the desired number of rows and columns are defined. One FEC packet is added for each row and column. Change Password Clicking Change password allows configuration of the system s admin user password. If the password is forgotten or lost, the Inca Networks Boot Menu can be used to configure a new password or reset it to the factory default. The factory default admin user password is admin. System Power Control The system can be remotely rebooted or powered down using the options in the drop-down menu under Administration in the System Maintenance tab of the Maintenance menu. Note that once the system has been powered down, it can only be restarted by momentarily depressing the power switch on the rear of the chassis. CAUTION Once the system has been powered down using the web-based user interface, it can only be restarted by momentarily depressing the power switch on the rear of the chassis, requiring physical access to the chassis. Package Manager The package manager is used to install firmware updates, which are provided in the form of packages. Packages are first uploaded to the system and then installed. Installation can be performed while the unit is in service. A system reboot is required to bring firmware updates into effect. Inca recommends rebooting the system immediately following installation. Uploading Packages Packages are installed in the Package manager tab of the Maintenance menu. VidiOS package files can be identified by their.ip (Inca Package) filename extension. Note that the VidiOS Package manager will only accept packages certified by Inca Networks. Successfully uploaded packages will be listed under the Available packages heading, as shown in the figure below. Inca Networks Inc Family User Manual Revision 2 92

93 Figure 79 The package manager Uploaded packages can be saved to the system s local flash storage. To save the package, click Save. Saving packages is not required. Unsaved packages will be deleted when the system is next booted or when Delete is clicked. BACKUP SYSTEM SETTINGS Inca recommends backing up system settings before installing firmware upgrades. Backing up video processing settings is discussed in Export, Backup or Restore Sources, Outputs and Profiles. A non-restorable reference backup of all system settings is also available in the Links Tab. Click Install to install the uploaded package on the system s flash storage device. The system will pop up a confirmation dialog, and if the user clicks yes will continue with installation of the package. After the installation process has begun, an Installation status tile will appear adjacent to the Available packages tile. The installation process takes less than a minute and the system will inform the user when the process is completed with an instruction to reboot the system to apply the update, as shown in the figure below. An information message indicating that the package was successfully installed with also be displayed under the parent device name at the top of the display. The message will be displayed until the system is rebooted. CAUTION Loss of power to the system during a firmware upgrade can cause the device to cease functioning. Ensure that the device is not powered down or rebooted during the installation process. Figure 80 Firmware upgrade installation status. Inca Networks Inc Family User Manual Revision 2 93

94 Links Tab The Links tab contains links to SNMP MIBs and a full chassis configuration file. Figure 81 The links tab populated with download links Troubleshooting Information about SNMP can be found in the SNMP Tab section of this document. The chassis configuration file is in XML format and contains a full backup of the parent and child device settings, including the video network interface settings. This backup is for reference only. There is presently no facility for the operator to use this file to restore the system to a previous state. For a restorable backup of the video configuration see the discussion above, Export, Backup or Restore Video Settings. Confirming Video Output Using VLC If system has been successfully configured, is running and has a valid input signal, the resulting video output can be viewed on the network using a set top box or a computer running the VLC client software (available free from NOTE Ensure the playback device used to test the video is wired to the video network, not the management network. If the playback device has multiple network interfaces, ensure that its multicast routes are configured to the video network interface. Ensure that the playback device has a valid IP address on the playback network. To view an MPEG-2 TS stream over UDP using the VLC Player, start VLC and select Media Open Network Stream (or press <CTRL>-N). For VLC versions below 1.1.0: Under protocol select UDP and enter the multicast address configured as the output destination. e.g If a unicast output destination was configured, view the stream on the destination device. The format is udp:// :1234 Inca Networks Inc Family User Manual Revision 2 94

95 VLC version and higher use a different URL format, in the form udp://@multicast:port, e.g. udp://@ :1234 After the address is entered, VLC should immediately start buffering and then display the video at its default resolution, as shown in Figure 82. NOTE SD streams are often interlaced and may display artifacts if de-interlacing is not enabled in VLC. NOTE When viewing HD content, keep in mind that many laptops and some desktop PCs lack the processing power to play HD video smoothly, especially at the 1080i resolution commonly used in North American digital broadcasts. Figure 82 VLC confirming video output NOTE When watching video in VLC it is recommended that the 1:1 Original Zoom level be used. Viewing in full screen mode requires that the video be scaled to match the monitor resolution, which may cause it to appear slightly distorted. If a larger image is desired, the 2:1 Zoom option can be used to scale the image without distortion. Inca Networks Inc Family User Manual Revision 2 95

96 NOTE Playback of digital video on any device, be it VLC on a PC or on a set top box often involves de-interlacing, re-scaling, or both. As such, the quality of the de-interlacer and scaler, as well as the resolution of the display device and the resolution of the input source are all factors in determining the perceived quality of the resulting video. When troubleshooting, try viewing the same source using various playback devices on multiple monitors to help isolate where an issue is being introduced. Conclusion For help, please contact Inca Networks at support@incanetworks.com. Inca Networks Inc Family User Manual Revision 2 96

97 Appendix A: The Inca Networks Boot Menu The Inca Networks Boot Menu provides a way to change the management network settings and administration password and to reset the unit to the default factory settings. The boot menu provides a safety net for occasions when these settings cannot be changed using the web-based user interface. The 4400 was shipped with an included RJ-45 to DB-9 serial cable for serial console access. The RJ-45 connector plugs into the RJ-45 port labeled SERIAL on the front of the unit (the RJ-45 port without LED indicators). The DB-9 connector is plugged into a computer running VT100 serial terminal emulation software. If the computer does not have a DB-9 serial port, a DB-9 to USB adapter can be used to convert the serial interface signals. SERIAL PORT SETTINGS The console serial port settings are: Baud: Parity: none Data Bits: 8 Stop Bits: 1 Flow Control: none TERMINAL EMULATION Inca Networks boot menu layout relies on VT100 style control codes and for best results VT100 terminal emulation should always be used. The use of other terminal emulations may result in unexpected behavior. PuTTY is a suitable terminal emulator and is available for free. It can be downloaded from the following website: The boot menu is accessible for a short time after the unit is powered on. Pressing the down arrow key within this period will halt the boot process. Pressing the <enter> key will load the boot menu, as shown below: Inca Networks Inc Family User Manual Revision 2 97

98 The boot menu is navigated using the arrow keys, <tab> and <enter>. Pressing <tab> will shift the focus between the inner frame and outer frame. Management Interface, Use a Static Network Address If the 4400 loses network connectivity, the management network interface settings can be re-configured using Use a static network address in the Inca Networks Boot Menu. IP address This field defines the static IP address of management network interface. Network Mask This field defines the scope of IP addresses, or subnet, which will be considered part of the internal network using a bitmask. Other IP addresses will be considered external to the network and routed through the gateway. Inca Networks Inc Family User Manual Revision 2 98

99 Gateway (optional) The Gateway defines which network router will be used when an IP address outside the subnet defined by the network mask is requested. Although this field is optional, Inca recommends setting a gateway, if present, to avoid connection issues with timeservers, or in the event VPN access is required. DNS Server (optional) This field defines the DNS server used to resolve domain names and can be helpful in cases where remote ssh access is provided to Inca Networks via an ssh port forward. Management Interface, Configure the Network Using DHCP The 4400 is configured by default to obtain management network settings automatically using DHCP. Management network settings can be configured to use DHCP by selecting Configure the network using DHCP in the Inca Networks Boot Menu. Pressing <enter> will confirm the changes. Set the Web Administration Password The serial console is the only way to regain access to the VidiOS web-based user interface if the administration password is lost. A new web administration password can be set by selecting Set the web administration password in the Inca Networks Boot Menu, as shown below: Inca Networks Inc Family User Manual Revision 2 99

100 Configure IPMI Access Intelligent Platform Management Interface (IPMI) is not available in the Reset the Configuration to Factory Defaults The 4400 can be reset to factory default settings by selecting Reset configuration to factory defaults. Settings can be reset with or without retaining existing network settings: Selecting Keep network settings will preserve previously configured management and IPMI network settings, if applicable. The reset process will exit the boot menu and take effect immediately. Save the Settings and Exit Changes to the system configuration using the boot menu will not take effect until Save the settings and exit is selected. The device will then resume the boot process using the specified changes. Inca Networks Inc Family User Manual Revision 2 100

101 Exit Without Changing the Settings Selecting Exit without changing the settings will exit the boot menu. The device will resume the boot process without the changes taking effect and any changes made during the session will be discarded. Inca Networks Inc Family User Manual Revision 2 101

102 Manufactured under license from Dolby Laboratories. Dolby and the double-d symbol are registered trademarks of Dolby Laboratories. Inca Networks Inc Family User Manual Revision 2 102

103 Government Standards Compliance United States FCC DECLARATION OF CONFORMITY Responsible Party Name: Address: Telephone: Inca Networks Inc Airport Way Pitt Meadows, BC, V2Y 0G4, Canada (604) Declares that product: Inca Modular Series 4400, models 4420, 4430 Complies with Part 15 of the FCC Rules. This device complies with Part 15 of the FCC Rules. Operations are subject to the following two conditions: (1) This device must not be allowed to cause harmful interference; (2) This device must accept any interference received, including interference that may cause undesired operation. Modifying the equipment without Inca Networks authorization may result in the equipment no longer complying with FCC requirements for Class A or Class B digital devices. In that event, your right to use the equipment may be limited by FCC regulations, and you may be required to correct any interference to radio or television communications at your own expense. For Class A Equipment This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense. Canada This Class A digital apparatus complies with Canadian ICES-003. Avis de conformité à la réglementation d Industrie Canada. Cet appareil numérique de la classe A est conforme à la norme NMB-003 Inca Networks Inc Family User Manual Revision 2 103