Changelog
Back to THEOlive
Back to All
added

New stream config, extended features for scheduler and more!

over 1 year ago by Tim Leenaers

The latest release of the THEOlive REST API and console comes with a set of new and improved features. We'll discuss them shortly in this changelog article, more information can be found in the related guides and API references.

Goodbye ingestConfig, hello streamConfig!

Up until now, you had to pass the ingestConfig object when creating or updating a channel. With this object, you could set the abr, fps, resolution (poorly named aspectRatio in the early days) and a preset (3 options which resulted in a specific ABR ladder).

From now on, you can pass the streamConfig object instead: it expects you to pass a max bitrate value (bitrate, in Mbps), a max resolution (resolution, can be "1080p", "720p", "576p", "360p") and the fps used. Based on these values, an ABR ladder will be picked that fits your needs. The pricing per minute transcoded and viewed will also be set based on the chosen profile.

More information can be found in the dedicated Stream Configuration guide. Also refer to the updated API references for more information about the integration.

Note: passing the ingestConfig object instead will still work, some backwards compatibility is provided. However, we encourage you to migrate to the new streamConfig approach when you can.

Extended list of scheduler features

We've extended the possibilities of our scheduler:

  • The end time has been made optional.
  • You can terminate a scheduler manually through the console, or via the API.
  • You can optionally set:
    • clientId: an ID for your reference (for example the ID of a table record in your database)
    • metadata: a list of key-value pairs
  • 15 minutes after the scheduler has been terminated, a report will be generated and downloadable. You can request the link via the Get scheduler report API.

Read more about it in out Scheduler guide.

Failover on alias level

Setting a failover channel has been possible for already some time now. A small disadvantage was that you could only set it on the main channel level. We have now changed this approach to be able to set a failover on alias level.

More information can be found in the guides and API references.

Geo-blocking: adding mode to whitelist or blacklist

We added the option to pass a mode when enabling geo-blocking. Up until now, you only had the option to pass a list of countries where the stream could be viewed (= whitelisting). Since today, you can also use the "blacklisting" mode: the countries you'll pass will have no access to the stream, while all the others have.

Head over to the Geo-blocking guide for more detailed information!

Updated OpenAPI specs