1. In some cases in event streaming, there is a need to pack different audio content (different languages, music) into a single track. The Flussonic transcoder is now able to split each audio track with several channels into separate mono tracks (the name of the option is ‘split_channel’). The use of third-party utilities is not required.

  2. CUDA driver is now supported by Flussonic Coder. This feature will allow us to achieve great benefits in future releases. Cuda is used to resize the video (e.g., compress Full HD to 720p). Therefore, we will unload the main video cores and increase the density of the chassis. This will make Coder even more productive – more channels can be processed on one Jetson.

  3. Now, when publishing via WebRTC, the user can select the available resolutions supported by the camera quickly in the capture settings.

    When communicating with low latency via WebRTC, in some scenarios, the user is required to publish the highest or lowest possible video quality. In online education, for example, it could be useful to see faces and expressions very well. In this case, it is necessary to transmit consistently in high quality.

    (Please note: if adaptive mode is enabled on the server, the quality of the published video may decrease according to the adaptivity settings on the server. Also, when adaptive mode is enabled, it may happen that the browser will choose average quality by default to save bandwidth).

  4. In previous releases, we added an adaptability option for WebRTC Flussonic so the video quality adjusted to the Internet speed of each user. What quality is needed to start playback in order to provide the viewer with the best user experience?

    If you choose high quality or even medium – there may not be enough bandwidth. First, buffering will occur, then then the picture quality will get worse. If you start showing with a low bitrate, then the quality of service will decrease for those viewers who have good Internet access.

    Since this version, the start track for WebRTC adaptive bitrate playback can be selected personalized for each playback session. Therefore, UGC and other services, based on the statistics they collect, can set an individual default quality to each viewer (for example, depending on the country, device, previous sessions of a particular user).

  5. In version 22.02, we taught Flussonic, when playing over WebRTC, to send lost UDP packets in response to a message from the browser. Therefore, we managed to combine minimal latency and the best video quality.

    In some cases, the behavior of the WebRTC adaptive bitrate algorithm led to the fact that the server still continued to retransmit the lost packets, instead of switching to a different quality.

    In this release, we changed the algorithm, and WebRTC ABR now works even better: the server counts the number of NACK packets sent by the browser. Based on this, switching to a track with a higher or lower bitrate takes place. (NACK – negatively acknowledged packets – messages from the browser about not receiving certain media packets).

  6. Added a slider to DVR player timeline. Now a simple drag of the mouse is enough to navigate through the timeline of the DVR player. (Previously it was necessary to click on the buttons).

  7. The Flussonic transcoder is now able to encode 10-bit HEVC streams from SDI and other sources.

  8. There is a technical name of the stream in Flussonic – ‘stream name’, it is used in the configuration and references. In contrast, the stream title is an additional description, and it is the title that is shown to end users in the interfaces (e.g., the name of the TV channel in the program guide).

    In this release, the stream title is also displayed on a restreamer. In addition, we fixed the issue when the titles were not displayed for disabled streams.