We are experimenting with srt-live-server on strm7. This is running on port 2000.

We use stream ID's to identify each stream similar to a URL path. This is done in the format of {pub / sub}/{location}/{production}. The first part indicates if you are publishing (pusher) or subscribing (puller) of a stream. The 2nd and 3rd are purely for organisational purposes.


It is formatted like so: srt://{location}/{production}

An example: srt://


ffmpeg -i {your input} -c copy -f mpegts "srt://{location}/{production}"


Select a custom output. Then put the entire SRT URL in the server field, SRT doesn't use the key field.


The stream ID now starts with sub to indicate we are subscribing / pulling a stream.

It is formatted like so: srt://{location}/{production name}.

An example: srt://


Use the URL as the input, it should automatically detect it.


Use a media source and set the input to the URL.


You will need VLC version 4 to properly view streams. Best way is to download the nightly version of VLC off their website, since the stable release is too old.

Roses 2021

We have split our SRT server into three different sections.

  • ystv
  • la1tv
  • mixer

So both ystv and la1tv are for OB's to stream too. This is then pulled by the remote mixer and then the remote mixer will stream to mixer.

YSTV has got a script which given a {location}/{production} and a LA1TV play path (ob1). Will forward the SRT to LA1TV's RTMP ingest.

In practice

So if you where at an LA1TV OB you would stream something like this: srt://

Then the remote vision mixer would be streaming to: srt://