Version 2.0.7.x
Last updated
Last updated
In the channel overview we now provide the option to enable monitoring to a channel. This will start a backend process that is constantly fetching the source and output channel and checks if ads get inserted.
For Enterprise and Professional we now provide the option to use a custom CDN by moving the encoded and packaged advertisements to a CDN. This can happen via FTP, Azure Blob Storage, AWS S3 and other storages. The setup will be done by the Serverside.ai support team.
For HLS Live channels a preroll can be configured to show advertisements before the stream is being displayed
To prevent the parallel encoding and packaging of advertisements that are requested at exactly the same time (within 3-10 milliseconds) a Redis based mutex now blocks the second request.
After a packaging job has run the duration of the output media is now saved.
https://staging.serverside.ai/app/assets/<assetId>/medias/<mediaId>
Changed the ads to be always encoded as timeline instead of template.
The Google Ad Manager implementation now forwards all custom parameters from the client to the ad-server.
Streams produced by the unified streaming packager have a different schema to signal ad-marker than usual which is now supported.
Example stream: https://live.unified-streaming.com/scte35/scte35.isml/.m3u8
The management platform was overwhelmed by to many concurrent ad-request. As a mitigation responses are cached in the worker component for one minute.