Addition of a changelog widget in the webapp dashboard

We recognized that it was not always easy to stay up-to-date with our latest features and bug fixes without checking the changelog of our Knowledge Center.

We have created a widget directly displayed on the web app dashboard to let you see new changelog entries.

Byte-range requests

We had an issue with HTTP requests that included one or more range HTTP headers (byte-range) on our manipulated manifests (that we were answering with an HTTP 206). This impacted insertions and ad replacements for the application Dynamic Ad Insertion.

We are happy to report that we fixed the problem, and you can now continue to use byte-range requests.

As a reminder, our platform returns HTTP response status code 206: Partial Content to indicate that an HTTP request has been completed and that the message body contains the requested data ranges.

Support transcode of .ts ads

Some ads we receive to be inserted in our DAI app are in .ts format (Content-Type: video/mp2t).

We now support the on-the-fly transcoding of .ts files to be inserted in HLS and DASH feeds.

Change of behavior with slate/gap-filler for Live DAI app

Previous behavior: in the context of live ad replacement, if a slate (gap-filler) was configured within the service, and a VAST (Video Ad Serving Template) response was empty, the entire ad pod was replaced by the slate..

New behavior: instead of replacing the entire ad pod with a slate in the event of an empty VAST, we maintain the original ad pod as intended.

Support manifest URLs with no file extension

Some packagers generate manifest URLs that don't end with .mpd or .m3u8.

We now support this type of URLs.

Support of HEAD on streaming requests

When activating Server Side Ad Tracking, some players cannot detect ad segments' MIME types. Therefore, these players perform HEAD requests to broadpeak.io for more information on the ad segments.

We now support HEAD requests on the platform to support this kind of use case.

Management of PDT not synchronized with current time

Some of our customers have Live sources with a PDT (Program-date-time) that is not synchronized with the current time.

We have lifted the requirement to have the origin Manifest (PDT) synchronized with the wall clock. From now on, Manifest PDT can run behind or in front of the wall clock.

Addition of new IPs to whitelist

We continue to extend our infrastructure, which means we ask potentially for our customers to whitelist additional IPs in case of any geo-fencing or whitelisting at the Origin level.

Please check our Platform Access page for the list.

Service tagging

You can now tag services with custom values (a-z, 0-9, - and _) in order to categorize your services (by environment, customer, project..). The configuration happened via API in creation/update of services:

Note: tags replaces former environmentTags property (that has been deprecated).

Or you can use our web app to define tags on services (at the "Input" step):

You can now filter your consumption by tags:

Addition of new IPs to whitelist

We continue to extend our infrastructure, which means we ask potentially for our customers to whitelist additional IPs in case of any geo-fencing or whitelisting at the Origin level.

Please check our Platform Access page for the list.