1. RELEASE OVERVIEW .................................................................................................... 3 1.1 Envivio Halo, v2.13 (Build 2.13.00(012)) ................................................................................. 3 1.2 Envivio Halo, v2.12 (Build 2.12.10(008)) ................................................................................. 3 1.3 Envivio Halo, v2.12 (Build 2.12.00(005)) ................................................................................. 3 1.4 Envivio Halo, v2.05 (Build 2.05.00(002)) ................................................................................. 3 1.5 Envivio Halo, v2.00 (Build 2.00.00(019)) ................................................................................. 3 1.6 Migration from previous version .............................................................................................. 4 1.7 Important notice ............................................................................................................................ 5 2. SOLVED AND KNOWN RESTRICTIONS ........................................................................ 6 2.1 Solved restrictions in Halo v2.13.00(012) .............................................................................. 6 2.2 Known restrictions in Halo v2.13.00(012) .............................................................................. 7
- 3 - 1. Release overview 1.1 Envivio Halo, v2.13 (Build 2.13.00(012)) This version is a major release. This version offers: - Support for Flash RTMP (push only. Origin server functionality is not available for Flash). - Live metadata insertion: new feature that allows insertion of metadata in the output stream for applications such as Emergency Alert System (EAS), Nielsen. - Mass configuration tool: GUI has been improved to enable duplication of services, start or stop all services/outputs at once etc - IGMPv3 redundancy
1.2 Envivio Halo, v2.12 (Build 2.12.10(008)) This version is a support release.
1.3 Envivio Halo, v2.12 (Build 2.12.00(005)) This version is a major release. This version offers: - Support for linear ad insertion for HLS and HSS based on SCTE-35 trigger - Live to file publishing for catch-up TV assets creation - iOS 5 features support (alternative audio track, I-frame playlist) - New 1RU form factor (with no change in processing density, input/output capacity)
1.4 Envivio Halo, v2.05 (Build 2.05.00(002)) This version is a minor release. It brings the following new features: - Customization for OEM partners - New GOP signaling named ALD (Adaptation Layer DataField) - Support for HP DL 360 G7 1RU chassis
1.5 Envivio Halo, v2.00 (Build 2.00.00(019)) Halo NMP v2.00 is a major version. This version offers: - New hardware platform based on a 2RU HP chassis - Ingest up to 750Mbps of multi-rate TS content - Up to 50 services processed in parallel
- 4 - HLS and Smooth streaming re-formatting Multi-audio support (up to 4) Subtitling support for HLS and HSS User-definable number of GOPs per HLS segment - Output up to 3Gbps of content - Built-in origin server Stream processing - HLS, Smooth streaming and Flash RTMP formatting. One service can be processed in both formats in parallel, with a user-definable GOP size for HLS (for smooth streaming, fragment size is set to 2 seconds) - Up to 4 audio supported - Closed captioning for HLS and Smooth streaming - DVB-Teletext for Smooth streaming - Halo is compatible with streams from Envivio Muse encoders, and third- party encoders using other GOP signaling methods such as IDR, ALD (Adaptation Layer DataField). Content protection - Support of AES encryption as specified by Apple - Microsoft PlayReady DRM support - Key exchange interfaces for all formats, compatible with Verimatrix, NagraVision, SecureMedia, Conax (ask Envivio for more details). - Key rotation in HLS, with synchronization of the keys used when deployed in 1+1 Operations - 1+1 active synchronization: Processing is synchronized between two Halos deployed in 1+1. This ensures both Halos produces identical chunk, with the same encryption.
1.6 Migration from previous version Migration from 1.00 - No migration is available as version 2.00 is running over a brand new HW platform - Configurations files are not compatible - Licensing is not compatible Migration from 1.50 - No hardware change: version 1.50 and version 2.00 runs on the same HW platforms - Software update: not compatible. In addition, it requires flashing a new OS - Configuration files are not compatible - Licensing is not compatible
- 5 - Migration from 2.xx - 1RU or 2RU compatible HW - Migration via SW update (UPD upload) - Licensing is compatible - A PLP (Production Loading Procedure) document is provided for each release. It needs to be followed carefully for successful upgrades/updates.
1.7 Important notice Licensing When applying a license, network interfaces should ALL be enabled. Indeed, the license manager first checks the connectivity, and make sure all the network interfaces are present (10 for Advanced platform, 12 for Standard platform).
Configuring input and output throughput Halo v2.00 is designed with a quad-gigabit Ethernet card. 2x Ethernet connectors are used simultaneously (the 2 remaining are used for redundancy purposes). The maximum ingest qualified is 750 Mbps total (375Mbps per Ethernet connector). The same rule applies for the output: - Halo running on Standard platform: the output load must be balanced between the 2 physical connectors. - Halo running on Advanced platform: only one 10-Gbe connector is used at a time. No specific configuration is required for this platform.
Frame rates Configuration of the service input source: Frame rates are derived from the input sources. If not present, default values are automatically filled (25 and 30fps, corresponding to DVB and ATSC system respectively). These default values may not reflect the reality (for instance, a QVGA stream at half frame rate), and consequently, will need to be edited manually.
1+1 stream synchronization In order to synchronize two Halos, the outputs must be started, of the same type (HLS, HSS) with the same output name.
- 6 - 2. Solved and known restrictions 2.1 Solved restrictions in Halo v2.13.00(012) Related bug Type Component Severity Description / Impact Identified in version Comment / Workaround 29212 Licensing Network card Major With dual 10GE network card, driver can sometimes be unloaded, leading to a license missing message 2.10 28288 Processing Alarm Major With high loaded configurations (>50 services), GUI is slowing down 2.10 29118 Output Live to file Major Jobs scheduled with overlap can be stuck and not finished. 2.12 28380 Input Capture Major Capture is blocked when service name contains non alpha-numerical characters 2.10 29108 Live to file Scheduling Major Scheduled jobs configuration is lost after Halo restart
29790 Compliance GUI Major IE9 prevents from loading upd update/upgrade files 2.12.00 Downgrade to IE8 for upgrade procedures. 29117 HLS encryption Internal encryption Major When using internal HLS encryption, some keys may not be published with high loaded configuration 2.10 29669 configuration GUI Major Alternative audio groups cannot be modified following a modification of one of its playlist 2.12.01 29767 Alarm Key provisioning interface Major Missing alarm upon connection failure to keys server 2.12.10 29884 Network DHCP Major Switching to DHCP after resetting the whole configuration creates stability issue 2.12.10
- 7 - Related bug Type Component Severity Description / Impact Identified in version Comment / Workaround 29819 Smooth input Major Smooth streaming fragments are not aligned when using non-full frame rates input streams 2.12.10 29857 Compliance SCTE-35 Major SCTE-35 markers are modified when using MPEG2-TS multicast output 2.12.10 29765 performance Origin server Major With smooth streaming only, Halo achieves 1700 simultaneous connections instead of 2000 2.12.00 29693 GUI updater Minor GUI is not accessible after an upgrade. 2.12.01 Browser cache has to be cleared 30008 HLS Audio Major With GOP duration greater than 6000ms, audio video synchronization issue occurs
2.2 Known restrictions in Halo v2.13.00(012) This table lists the major known issues of v2.13.00 (012). Related bug Type Component Severity Description / Impact Identified in version Comment / Workaround 28726 SNMP SNMP layer Major SNMP layer may fail to send traps to Network Management System
28861 Input packetization Major With 3 rd party encoders, AU can be very small, leading to video skip on iPad 2.10 28939 Update GUI Major Updater page is still accessible when enabling access control 2.10 29090 Video playback Smooth streaming Major Smooth streaming player cache needs to be empty after an input signal loss on Halo 2.10 29263 Configuration Live to file API Major Service ID, output ID returned by the 2.12.00
- 8 - Related bug Type Component Severity Description / Impact Identified in version Comment / Workaround live to file scheduling API are modified when re-uploading the configuration 29588 MPEG-TS output format Output Major When formatting in MPEG2-TS (and not HLS nor HSS), fragments not aligned alarms are raised randomly. 2.12.00 30021 Configuration System Major Loading a system configuration fails after the configuration in static mode of an unplugged Ethernet connector 2.13.00 30174 GUI Configuration Major Download of 100 services with IE8 can fail 2.13 Use of Firefox is recommended should such an event happens 30183 Alarm Live Metadata Insertion Major No alarm is raised when sending a request with a late UTC time. 2.13.00 30184 Alarm IGMPv3 Major Countinuity Counter errors when using configuring multicast with IGMPv3 2.13.00 30194 Compliance Origin server Major Interoperability issues with Windows 8 mobile and Halo (only the first chunk is played back) 2.12.01 30204 Alarm RTMP Major Alarm input signal lost is raised when starting an RTMP output with multiple streams, and without %i parameter. 2.13.00 30205 compliance IGMPv3 Major Multicast sources are received twice by Halo, instead of 1 when using IGMP and source filtering 2.13.00 30226 Alarm Stream synchronization Major Stream synchronization alarm is not raised when a first stream synchronization happened, and a new (desynchronized) service is started 2.13.00 30236 Smooth streaming Publishing Major Publishing points are stuck in starting mode upon IIS restart 2.13
- 9 - Related bug Type Component Severity Description / Impact Identified in version Comment / Workaround 30258 Alarm Alarm Layer Major HLS publishing alarms are sometimes cleared and raised again 2.13.00 30264 Alarm Alarm Layer Major Sometimes, alarms are not cleared on Halo (mostly the case for I/O alarms) 2.12.10