Skip to main content

Release Notes 2.1.0

Haivision Hub Release 2.1.0 Update

Component Versions

  • Hub: 2.1.0

This latest release to Haivison Hub focuses on new features, improvements and fixes. 

What's New

  • Appliance-to-appliance direct routes.
  • Count of paired appliances added to Usage dashboard.
  • Cloud hublets are not clickable for appliance-only subscriptions.
  • Telemetry improvements: graphs available for SRT counters with connection granularity.
  • Enhancements to prevent route provision/de-provision errors.

Known Limitations

  • Agile outputs are disabled for appliance-to-appliance direct routes.
  • Only a single input hublet per route is allowed.
  • Makito X ENC with FW 2.6.0-2 will make route fail if the fps that is set in the Preset is 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 makes telemetry being displayed intermittent.
  • Notifications are sent to every user in the active Hub subscription only.
  • FEC-specific telemetry is not supported.
  • RTMP hublets in consumer mode are reported as connected irrespective of the input signal.
  • RTP output hublet status does not consider the status of the external connections.
  • Instant bitrate displayed in the topology view is not accurate for internal connections.
  • Connection state for internal connections is not correctly updated when there is no input signal.
  • Subscription selector for admins – number of routes is not updated.
  • Akamai hublet does not support 4:2:2 8 and 10bit 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.