24.10 Media Server

In the new release, we continue to develop API v3 by expanding the capabilities for monitoring and server integration with client systems. We also simplify working with configurations: now you can retrieve a stream’s settings from the transcoder and use them for preparing files or transcoding streams.

Let’s go over the details.

Retrieve stream configurations from the transcoder

Now, Media Server allows you to obtain the stream configuration from the transcoder and apply it for transcoding other streams or video preparation. All you need to do is copy the track settings from the ‘stream_save’ method. This is particularly convenient for those embedding ads into their streams. There’s no need to search for seamless embedding settings anymore—just grab the required configuration from the transcoder and use it without altering the stream itself.

Check the status of pushers and incoming MPEG-TS streams via API v3

It’s now easy to determine whether the push UDP with the Standby option enabled is currently active by referring to API v3. The ‘stream_get’ method now includes the field stream.pushes[].stats.status, which shows one of three statuses: error, waiting, and OK.

Additionally, error counters for the MPEG-TS stream are now available. ‘Stream.stats.input’ indicates how many packets with errors were received, how many 404 errors occurred, and so on.

Add your own appliances for recording Flussonic Media Server archives

Flussonic’s hardware devices now support the mounting and unmounting of additional DVR disks for recording archives, as well as their formatting.

Download encoder firmware at high speed

Recently, we noticed slow firmware download speeds and errors that interfered with updates. We changed the storage: download speeds have increased several times over.

View data by labels received from auth_backend

Now in Retroview, you can view data snapshots based on labels.

Use more modern DRM protocols

With ezDRM, we’ve transitioned to more up-to-date interaction protocols CPIX v2.1.

Achieve stable video quality even with significant bitrate fluctuations

Previously, if the video source experienced sharp bitrate fluctuations, users would encounter bitrate trimming at the CBR output—software bitrate limitations. This could result in video artifacts.

In the new Media Server version, we disable trimming if we detect a problematic source but no explicit request for CBR is present in the configuration.

Use Video4Linux (v4l) on a separate node

v4l sources (SDI, DVB) have now been moved to a separate segment, which sends data to the server via a signaling protocol and shared memory. This simplifies code debugging and the use of libraries.

Read more about all the improvements and bug fixes in the changelog. We are always happy to answer your questions: support@flussonic.com.