This feature requires OBS Studio 25.0 or newer.
For a video demo, see here:
SRT is mostly used in the broadcast and corporate world at the moment. See the NAB 2018 SRT panel with ESPN, NFL, Microsoft speakers talking about their use of SRT:
The NAB 2019 NAB SRT panel can be watched here: https://www.haivision.com/resources/webinars/broadcast-panel. (Hey Haivision, friendly suggestion: it'd be nice to have this vid posted on YouTube instead of having to enter personal info! :P )
Unlike RTMP, SRT is an open source protocol, and the source code can be found on GitHub. While RTMP development has been abandoned since 2012, SRT development is still very much active.
As a protocol, it is content agnostic, although the industry uses it along with an MPEGTS container, which is the de facto standard in broadcast industry. (In terms of comparison, RTMP protocol relies on the FLV container.) The MPEGTS container is usually used along with UDP protocol, which makes it fast, but very unreliable and prone to packet loss. It can also be used with TCP, which is more reliable but has larger latency. SRT adds up to these two protocols to transport MPEGTS, with the best of two worlds: the reliability of TCP, and the lower latency of UDP. It also supports encryption and bonding.
Other competing new protocols are WebRTC, Zixi (closed source) and RIST; the latter two are quite similar to SRT and all go beyond RTMP.
Short answer: NO (or not yet?)
Long answer: None of the main streaming services support the SRT protocol for ingest. Most still use RTMP (Twitch, YouTube, Facebook...). (Mixer though relies on WebRTC through its proprietary FTL protocol which OBS already supports). If you're using exclusively these services, no need to read further.
At this stage of the adoption of SRT protocol, you'll have to be technically inclined if you want to use SRT. If you are able to set up your own streaming server, maybe redirecting your streams to the main services like Twitch or YouTube and are interested in achieving low-latency with improved network resilience, read on.
The other category of users who could potentially be interested belong obviously to the professional broadcast industry. This wiki entry can be considered as fairly advanced in that it requires access to a server and being able to set it up.
The configuration of OBS itself ranges from easy to medium in terms of difficulty. The server setup is more challenging since it requires system/network admin knowledge.
Live software encoders :
The following servers support SRT ingest:
Additionally, though it is technically not a server, FFmpeg can be used in listener mode to ingest an SRT stream. It won't be able to serve the stream as a real genuine server would do. But it could be used to transmux to RTMP and route to nginx-rtmp for instance, which can then handle the ingest to Twitch/YouTube/Facebook/etc.
ffmpeg -i srt//IP:port?mode=listener -c copy -f flv rtmp://IP:1935/app/streamName
The following players can be used to watch an SRT stream :
Download VLC 3.0 here or VLC 4.0 here (warning: this is the development version of VLC).
If you just want to test without disturbing your current VLC install, we advise you to download a portable install (zip).
Media > Open Network Stream:
enter the SRT IP which has the form
It is required that ffplay be compiled with libsrt support. To the extent of our knowledge, there does not seem to be any such binary widely available, although there are no license constraints.
Just launch the command-line:
There are two ways of setting up OBS Studio to connect to a server. The first is simpler but gives less options at the moment. The second is a bit more difficult to setup but gives more fine tuning capabilities (and at the moment of this writing is more stable).
Note that while the discussion focuses on SRT protocol, UDP or TCP can also be used instead.
Credit: Aaron Boxer, Collabora (SRT Alliance) author of the new SRT output
Settings > Stream
srt://IP:port(OBS Studio will also accept any protocol relying on MPEGTS container and supported by FFmpeg, therefore UDP, TCP, RTP, etc.)
OBS Studio will accept options in the syntax:
srt://IP:port?option1=value1&option2=value2. The full list of options is those supported by FFmpeg: http://ffmpeg.org/ffmpeg-protocols.html#srt.
The most important option is latency in milliseconds (ms). It has a default value of 120 ms and should be at least 2.5 * (the round-trip time between encoder and ingest server, in ms).
Another sometimes required option is the mode, which can be
caller opens client connection.
listener starts server to listen for incoming connections.
rendezvous use Rendez-Vous connection mode which is a bi-directional link where the first to initiate handshake is considered caller. The default value is caller and usually need not be set for OBS Studio since it'll be in caller mode normally.
A case where it's useful to set the mode to
listener is when sending a stream to VLC. OBS Studio then acts as a server to VLC, which is the client. On a LAN for instance, set OBS Studio to
srt://127.0.0.1:port?mode=listener to establish a connexion to VLC which you point to
This option is a bit more complicated. It relies on the
Advanced: Custom FFmpeg Recording output.
Settings > Output
Output modedropdown, select
Custom Output (FFmpeg)
FFmpeg Output Typedropdown, select
Output to URL
File Path or URLbox, type the SRT URL:
srt://IP:port(options like latency are entered with the syntax
Container Formatdropdown, select
Muxer Settingscan be left blank, or you can use the (MPEGTS FFmpeg muxer options)[http://ffmpeg.org/ffmpeg-formats.html#mpegts-1] with the following syntax
option=valuepairs must be separated by a space).
show all codecsto display all codecs available to FFmpeg.
Note that several audio tracks can be selected. They can be identified on the ingest server side by what is called a PID. On default value, the video track has
pid 0x100 (=256), and the other audio tracks have
pid 0x101 etc. If you need to change the pid of your tracks, use the muxer option MPEGTS_start_pid in 7.
Pros/Cons in comparison with Option 1: