SRT
Using Secure Reliable Transport (SRT) to publish to Dolby.io Real-time Streaming
Secure Reliable Transport (SRT) is an open-source protocol that uses an intelligent packet retransmit mechanism on top of a UDP data flow, along with AES-128 and 256-bit encryption. Dolby.io Real-time Streaming natively supports publishing from an SRT source.
This document will guide you on how to broadcast an SRT Stream to Dolby.io Real-time Streaming with SRT-capable software or hardware.
Getting Started
If you haven't already, begin by following the Getting Started tutorial to create a Dolby.io application and start your first broadcast. You will need to create a publish token to generate the necessary SRT details.
How-to Find your SRT Publish Path
Select the publish token that you want to use for your SRT streaming application.
Click on the Publishing tab for information on how to connect as a publisher to your Dolby.io account.
In order for you to publish to Dolby.io Real-time Streaming with SRT you will need two things from the form, the SRT publish path and SRT stream ID (which includes your unique Stream Name and Publishing Token).
This information will authenticate you as a publisher on Dolby.io Real-time Streaming and allow you to successfully broadcast from an SRT source using your account.
Using the SRT Publish Path and Stream ID
How the SRT publish path and SRT stream ID values are used is dependent on your software or hardware device. For example, some devices/encoders accept the values as separate parameters and some require them combined as a single URL. If your encoder has a separate streamId field, you will want to provide the SRT publish path and the SRT stream ID fields from the dashboard. If your encoder only has a single field for SRT, use the SRT publish URL.
The following are examples of how these values can be used:
- Combined as a single SRT publish URL: srt-publish-path?streamid=encoded-srt-stream-id. In the screen above the example is
srt://srt-auto.millicast.com:10000?streamid=myStreamName%3Ft%3Drc-0eIP8R7TbyqrBzKCehNh.... - As two separate fields, the SRT publish path and SRT stream ID. In the screen above, the examples are
srt://srt-auto.millicast.com:10000andmyStreamName?t=rc-0eIP8R7TbyqrBzKCehNh....
SRT Encryption
We offer passphrase encryption to protect your stream from unauthorized access. You can enable the encryption in the dashboard by toggling the passphrase encryption setting on. This step generates your SRT passphrase to protect your stream.
SRT Limitations
The following are some limitations when using SRT with Real-time Streaming:
- The SDK currently supports the H.264 and H.265 video codecs and the AAC audio codec
- Multiple programs or sub-streams are not supported
If you have needs like these, please contact us.
Learn More
Learn more by exploring the developer blog and code samples.
Updated 29 days ago