SRT ingest for live events

July 2024

What’s changing

MK.IO now supports Secure Reliable Transport (SRT) ingest for live events.

Who is impacted

Anyone who is using MK.IO for live events transcoding should consider using SRT instead of RTMP for new channels.

Why you would use this / Why it matters

MK.IO uses RTMP by default to ingest streams for live event. Although RTMP is widely supported and used, SRT offers better performance and security and is the best choice for deployments of new transcoding channels in the cloud.

Additional details

By design SRT is well suited to carry video with a high level of security over unreliable networks. Packet loss and jitter management is much better than RTMP.

This makes it the best choice in cloud environment where network condition can vary and security of data is required.

The SRT ingest is available for live encoding ingest, live passthrough ingest remains RTMP only.

Getting started

From now on in MK.IO, when you create a new live event, you can choose between RTMP and SRT transport protocols.

When using SRT in MK.IO will use an AES-128 encryption by default. The negotiation between the caller and the receiver can lead to a different key length.

In case of SRT, a passphrase is required.

Availability & rollout plan

SRT ingest for live event is available in all regions starting July 17th 2024.

There is no additional charge associated to this feature.