Release 5.5.0


Since it's April, spring is technically here, yet a cold snap has currently strained our cabin fever to a breaking point. Apparently, Mother Nature likes to play April Fool's jokes too. Just a few more New England snowstorms and we should be able to feel our toes again.

Despite the date, we are very serious about our new release 5.5.0 for Server, HTML5, and the Mobile SDK! We are very excited that this latest release adds more security to our mobile apps with mobile encryption through SRTP. We've also added support for decoupled shared objects. That means you can now build text chats, shared whiteboards, games & many more real-time data-oriented applications without the need for an audio/video stream accompanying it.

We really need to stop releasing actual updates on April Fool's Day...

See below for the full release notes:


Red5 Pro Server

Release 5.5.0 - April 1st, 2019

  • New - Websockets decoupled from streams (allows shared objects to be used independently of a live stream)
  • New - Stream encryption via SRTP for mobile SDK clients (NOTE: Requires Red5 Pro Mobile SDK version 5.5.0 or higher)
  • New - Unpublish stream server API call unpublishLiveStream Clustering - streaming on demand is active by default
    * NOTE: if you want to play back HLS over cluster/autoscaling, then you will need to change streaming on demand to false in {red5pro}/conf/cluster.xml
  • Fixed - Invalid response trying to get stream stats for a subscope
  • Fixed - Errors if two separate clients attempted to subscribe to a stream at the exact same time
  • Fixed - Conference example leaves one connection on hold or closes connections
  • Fixed - Chrome WebRTC broadcaster bitrate doesn't go above 600 kbps (fixed in HTML5 SDK)
  • Fixed - AWS Cloud Storage Plugin may list out wrong folder if you have multiple root folders
  • Fixed - Firefox WebRTC to Safari HLS stalls after around 2 minutes (note: fix requires enabling preprocessor in the webapp, which will also increase CPU usage)
  • Fixed - Autoscaling - Error reading a configuration policy that contains the 0 character
  • Autoscaling - Improved error messaging when trying to add origin node to a VPC that doesn't exist


Release 5.5.0 Server Performance Metrics

Tests were run against an AWS c5.large instance (2 CPUs with 4GB memory, 2GB allocated to java_heap). We used our RTMP Bee, RTSP Bee, and RTC Bee clients to do load testing.

Publishing a 240p (426x240, 256kbps) stream via RTMP, we were able to achieve the following while still maintaining the quality of stream:

  • 500 WebRTC subscribers
  • 2,000 RTSP (mobile) subscribers
  • 1,100 RTMP subscribers

Publishing a 720p (1280x720) 1,500kbps stream via RTMP, we were able to achieve the following while still maintaining the quality of stream:

  • 220 RTC subscribers
  • 450 RTSP subscribers
  • 300 RTMP subscribers

The same server type (2 CPUs with 4GB memory, 2GB allocated to java_heap) can support approximately 50 RTMP publishers in 480p (tested using the RTMP Bee Publisher test).


SDK

Release 5.5.0 - April 1st, 2019


HTML5 SDK

  • Fixed - Mobile Safari issues with beforeunload
  • Fixed - Chrome WebRTC broadcaster doesn't go over 600kbps
  • Support for Chrome auto-playback restrictions
  • Decoupled SharedObjects (see example here
  • Updated conference example


iOS SDK

  • Added SRTP Secure encrypted streaming option (NOTE: Requires Red5 Pro Server version 5.5.0 or higher)
    • See new publish and subscribe examples in streaming-ios example app
  • API status codes added to API docs
  • Added Metal-based view to replace deprecated GLKView
  • Fixed: Muting subscriber audio doesn't work (subscribe mute audio test added)
  • Fixed: Swift memory leak when grabbing image frames


Android SDK

  • Added SRTP Secure encrypted streaming option (NOTE: Requires Red5 Pro Server version 5.5.0 or higher)
    • See new publish and subscribe examples in streaming-android example app
  • More stability fixes
  • Fixed: Muting subscriber audio doesn't work

To get the latest release, please login to your account and download the new build.
To upgrade your server, follow this link.
To upgrade your stream manager, follow this link.
For test applications, visit our Github page.

  • Share: