Skip to main content

Release Notes 2.5.1

Haivision Hub Release 2.5.1 Update

Component Versions

  • HUB: 2.5.1
  • HUB API: 2.5.1

This latest release to Haivision Hub focuses on Hublet performance and provisioning and includes some enhancements to the SignIn screen and left navigation sidebar. 


What's New

  • New design for SignIn screen and left Navigation bar.

  • Removed the following regions from the HUB: koreacentral, northcentralus, southindia, and eastus2. Routes running on those regions are stopped and will not be able to start again without changing the region.

  • Partially provisioned routes that end up failing to start are no longer included in billing.

  • Akamai Hublet now uses Unix time stamps for the video segments naming.

  • Bug and vulnerabilities fixes, stabilization, and improvements.

Known Limitations

  • Agile outputs are disabled for appliance-to-appliance direct routes.

  • Makito X ENC with FW 2.6.0-2 will make the route fail if the fps set in the Preset are higher than the fps of the source input.

  • The bitrate reported in the HUB UI may not be accurate if the encoder bitrate changes for a running route.

  • RTMP Hublet supports streams with a single audio track only.

  • Makito video preset has no validations for max bitrate.

  • When performing bulk operations on routes, some of the status update messages may be missed. 

  • Opening the same Makito route on multiple browser tabs simultaneously, results in intermittent telemetry being displayed.

  • FEC-specific telemetry is not currently supported.

  • RTMP Hublets in consumer-mode report as connected irrespective of the input signal.

  • RTP output Hublet status does not consider the status of the external connections.

  • Subscription selector for Admins – number of routes is not being updated.

  • Akamai Hublet does not support 4:2:2 8-bit and 10-bit source.

  • Akamai Hublet does not support video from Makito X encoder with Intrafresh enabled.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.