Hey Everyone!
Stable release of MistServer 3.13 is out now! As always full changelog is available here.
Downloads are available here.
Major highlights are:
Caching feature released
With 3.13 a new caching feature is introduced. This caching feature can be set up from the general tab within MistServer or by adding the options to the config API call.
To set up caching you will need to provide a path and a size either in bytes or % of the drive to use. The lowest number will win in the case of both being filled in.
Three types of data will be cached:
- DTSH files
- Stream data
- Segmented output files
Files will be stored based on the duration it took to create, how often it is requested and the expiration date of the data. More details on how the cache works can be found here
Any cached files will be using an UUID that is regenerated whenever a DTSH header is (re)created, thus allowing for replication detection and caching accordingly.
DTSC can now be used for VoD content
As part of the caching feature DTSC support for VoD content has been added as well. This means that any stream within MistServer can now be properly pulled using DTSC.
TS-based outputs can remap the stream PIDs
It is now possible to remap the stream PIDs while a TS-based output is requested or pushed out of MistServer. You can find the full documentation here
Statistics are now split in input and output stats
We have updated stream-wide statistics to also include input and output based stats, not just a mixed version. This is more in line with other protocol stats such as WebRTC or SRT statistics.
Not all inputs have been fully updated, however SRT based inputs have been fully updated first. You should now see the following stats for input and output:
- RTT
- Protocol Latency
- Packets received
- Packets lost
- Packets resend
- Packets recovered
Note that packets recovered can only happen if a recovery protocol is activated such as FEC and depending on the side of the connection a full picture might not be available. Only the receiving side can accurately measure packets lost and the sending side relies on the receiving side to report these back.
Sending a USR2 signal to MistInBuffer will print live media ingest status
You can now send a USR2 signal to the MistInBuffer to receive current live media ingest status within the log.
Improved live status detection for certain inputs
Some inputs within MistServer weren't being properly detected as a live ingest, this affected streams using processes or SRT listening inputs in particular. The live status detection for these streams has been adjusted and they will now properly show as a live stream.
Various other bugfixes and improvements
For the other improvements and bugfixes we'd recommend going to the changelog.