No matching documents found
In our latest release, we’re excited to introduce a range of significant improvements. We ensured perfect time synchronization across all connected devices and enhanced media delivery reliability with API NTP settings. For enabling seamless ad insertion and precise ad delivery vis CSAI and SSAI we preserved SCTE markers for SRT streams.
Advertisers and broadcasters can seamlessly insert and deliver targeted ads to viewers, enhancing the overall viewing experience and monetization with the new update when SCTE-35 markers are handled more effectively, whether content is being re-streamed via M4F/M4S or published via SRT.
Additionally, our internally developed SRT implementation improves compatibility, reliability, security, and performance. A periodic NAK packet enhances signal reception, providing a stable streaming experience. Plus, an automatic stream configuration simplifies MPTS stream management by eliminating manual configuration. These updates aim to enhance your media delivery and content management processes.
API NTP settings
For consistent timestamps and scheduling a pusher is synchronized across all connected devices with no time drift thanks to a new feature of configuring NTP.
To ensure seamless ad insertion and delivery of targeted ads to viewers through CSAI and SSAI effective implementation, SCTE markers are preserved within the output manifests for HLS, MPEG-DASH, and MPEG-TS formats, when restreaming via m4f and m4s.
In the current update we enhanced accurate ad insertion throughout the content delivery process when the content is published via SRT through an implementation of SCTE-35 markers pass-through.
With improved compatibility, reliability, security, and performance while providing flexibility, integration options, and scalability for media streaming and broadcasting SRT streams are received and processed with the internally developed SRT implementation.
To provide our customers with a more reliable and stable video and data transmission over the SRT protocol we added a NAK packet to be periodically sent to Flussonic SRT implementation. With this Flussonic Media Server helps to maintain a smooth and uninterrupted signal reception for a more reliable streaming experience for users.
We simplified the management of MPTS streams containing SCTE-35 markers, no need for manual configuring anymore. Within MPTS streams, when there is an SCTE-35 PID present, the stream_identifier_descriptor is automatically added to the PMT for that stream.
In our latest update, we’ve made several notable improvements to Flussonic:
We streamlined the API schema by removing some fields, while some fields were modified for play session authentication.
In terms of the DVR archive, we significantly improved the export feature. Exported MP4 videos now maintain a consistent and accurate frame rate, resulting in smoother and more reliable video playback.
We also addressed various issues that were affecting user experience and work efficiency, ensuring a more reliable and efficient Flussonic experience overall.
We removed some unused fields ad_inject and ad_schedule endpoints from the Flussonic API schema
dvbsubs_ocr fields for MPEG-TS input and the
cluster_key field for a stream from the Flussonic API schema.
cluster_key can be assigned to a server or an input
Modified the field types of play sessions auth in the Flussonic API schema.
vb field from the Flussonic API schema.
Deleted the deprecated
buffer field from event_sink configuration.
dns parameters from the push stats in the API schema.
dns parameters from the push stats in the API schema.
In the current update we improved the overall quality and usability of the DVR archive export feature, making sure that the exported MP4 video maintains a consistent and accurate frame rate, providing smoother and more reliable video playback when viewing the exported content.
We also fixed some issues that affected user experience and work efficiency:
To improve user experience and flexibility when accessing DVR content in web applications using THEOplayer, we removed
availabilityEndTime parameter from DASH static manifest .
Live stream from an NVR camera starts and is played correctly.
The DVR player operates correctly and efficiently, downloading video segments only under a corresponding request, avoiding consuming unnecessary bandwidth or storage.
HTTP 500 error was fixed when DVR requested a particular recording segment to improve reliability and functionality of the DVR system, ensuring that recorded video segments can be retrieved and played back without interruption or server errors.
With the new update Flussonic Media Server effectively manages DVR archive storage adhering to specified settings and cleaning up content as required.
We also fixed that Flussonic Media Server effectively manages DVR archive storage, adhering to specified limits and cleaning up content as required, even in cases where there may be communication or request issues with the Central component. This is important for maintaining storage efficiency and ensuring that archived content is retained within the desired limits.
The issue when server configuration was not updated while uploading configuration with an empty list using PUT request was fixed. With this fix we ensure that our server configuration can handle a broader range of configuration data, including cases where empty lists are involved.
The WebVTT subtitles generated by the OCR are displayed correctly without unnecessary duplications. This is essential for providing accurate and readable subtitles for video content, improving the overall viewing experience for users.
Offline license update:
An update process for an offline license is fixed through the offline_request file regeneration was fixed during the update.
Camera archive recording:
Camera video archive recording occurs timely after the live stream took place.
We added an experimental option for codec selection in browsers working with AMD cards, with that we try to resolve a problem related to how Chrome browser when used on desktops with AMD graphics cards selects and works with codecs. With this option in place we provide a potential solution to these issues for their further testing and feedback.
SCTE ad markers in Flussonic are now properly represented in DASH manifests, without any unintended duplication to avoid incorrect ad insertion.
We improved load balancing based on GeoIP to direct traffic to servers that are geographically closer to a user, reducing latency and improving content delivery.
Config_external does not receive duplicating requests anymore, to avoid inefficiencies and potential issues with the configuration process.
Since 23.09 SCTE-35 markers are correctly encoded and included in generated HLS manifests for an accurate synchronization of events, such as ad insertion, during video playback, ensuring a seamless and synchronized viewer experience.
Media Server reliably captures RTSP stream without any termination when attempting to receive, process, or record it providing uninterrupted playback, good quality and content availability.
No more 500 errors, subtitles are played as intended or if there is a problem at the input they are neatly discarded.
Multimedia content delivered via MPEG-DASH, including audio tracks, is correctly formatted and played back without issues related to extra symbols in the language descriptor.
We fixed a reached_max_restart_intensity error that occurred during streaming to ensure smooth and reliable operation. No more interruptions or freezing of a stream due to this error condition.
There was a problem with improper processing API PUT requests that included null values, causing errors and disruptions in data updates. This issue has now been fixed, ensuring seamless handling of such requests, enhancing the software reliability, and preventing interruptions in data management processes.
In our latest updates, we refined Flussonic Media Server documentation and navigation. This includes restructuring the navigation menu to make important resources more accessible, adding a new article on DVB-compatible streaming, and enhancing documentation clarity with clearer descriptions. We also provided valuable configuration examples, updated information, and important warnings to ensure users have a smoother and more informed experience with Flussonic Media Server.