fbpx

Using IP Video Streaming Sources

dt logo 1.5inchDrastic software supports a number of IP video standards in videoQC, Net-X-Code and other products.  To access these streams, a URL style string is used to describe them.  For some sources, like RTSP, this string is fairly standard.  For others, like NDI, a URL style has been developed to allow those streams to be specified.  Currently, udp://, rtp://, srt://, rtsp://, ndi://, s2022:// and s2110:// are supported.  This document describes the URLs' format in more detail.  We have also added some applications specific notes for connecting our software to other applications.

 

Basic IP Video URLs

An IP video URL will always start with the type of stream you are expecting.  Some of the types include udp://, rtp://, rtsp://, ndi://, s2022:// and s2110://.  This will be followed by an IP address or resolvable name for the address of the stream.  For some streams there will be a port value, and then a description of the stream on that device.

UDP and RTP

UDP and RTP streams can be elementary video or audio streams, or more commonly a transport stream with PMT/PAT and a number of streams within it. For UDP and RTP, you can specify a TCP (direct) address, but normally it will be a muticast group address, and also a port is normally specified.  Here are a few examples:

  • udp://239.254.40.40:5004
  • rtp://239.100.20.20:50004
  • rtp://239.100.30:31:1234

SRT

SRT streams contains a transport stream with PMT/PAT and a number of streams within it. For SRT you can specify a TCP (direct) address, but normally it will be a muticast group address, and also a port is normally specified.  A password for encrypted service can also be set.  Here are a few examples:

  • srt://239.254.40.40:5004?mode=listener
  • srt://172.12.25.20:5006?mode=caller
  • str://239.100.30:31:1234?mode=caller&password=thisisapassword&user=thisisauser

RTSP

RTSP streams require not only the device address, but also the description of the source of the stream you are accessing on that device.  RTSP are also often user/password protected, so you may have to send a user/password in the form "<user>:<pass>@" just before the device identifier. Here are a few examples, and their sources:

  • rtsp://192.168.100.10/axis-media/media.amp  (an Axis camera)
  • rtsp://192.168.199.11/user:pass@/video1+audio1  (a Marshall camera, with password)
  • rtsp://192.168.160.20:/onvif/media.amp  (an OnVIF source)
  • rtps://192.168.150:11/video1?videocodec=h264  (a Marshall camera, video only, force h.264)

NDI

NDI is NewTek's video over IP protocol.  It requires a device name and a source name to access NDI sources.  NDI sources may also be searched on the local network. To enable the search, run DDRConfig and select the Advanced tab.  Go to /VVW/Config and change EnableNDISearch = 1.  If it does not exist, then create a new Numeric value for it.

ddrconfig enablendisearch

To specify an NDI stream, use the device name, followed by a space, and then the source name within brackets.

  • ndi://USER-PC (Desktop [2])
  • ndi://TestCameraSource (ISO_1)
  • ndi://PC2 (Google Chrome [1])

S2022 and S2110

The SMPTE 2022-6 and SMPTE 2110 protocols can be accessed via SDP or manual setup.  To access an SDP source:

  • s2202://192.168.101.200/channel1.sdp
  • s2110://mainsources.drastic.ca/crosspoint10.sdp

For some Drastic software, the source can be set up manually.  For S2022, this is a single set of Source IP, Source Port, Destination IP, Destination Port and Interface address.  One or any combination of these can be used the describe the source of the SMPTE 2022-6 stream, which contains all the video, audio and HANC/VANC channels.  For SMTPE 2110, up to three sets of the same information are required to describe the video, audio and anc streams, which are all separate.  A PTP grandmaster may also be specified.  Here is the configuration dialog from 4KScope:

S2022 SMPTE 2110 IP Config

 Application Specific Notes

VLC (version 3.0.8 and greater)

VLC support a number of streaming formats from the menu Media | Open Network Stream.  Here you can read our UDP://, RTP:// and SRT://.  If you are using multicast IP addresses (eg. 239.#.#.#), VLC prefers that you add an at sign (@) before the ip, like:

rtp://@239.240.30.30:5004

You can also use the @ sign to recieve on any address using just the port:

udp://@:5004

For SRT, VLC only suppports the being a 'caller', so our software needs to be setup as a listener.  A typical setup would be

SMPTE2NET:  srt://172.16.12.25:5000?mode=listener

VLC:  srt://172.16.12.25:5000

Assuming the IP 172.16.12.25 was the IP of the machine SMPTE2NET is running on.

OBS - Open Broadcast System

OBS supports UDP, RTP and SRT using it FFMPEG media reader.  It will support both listener and caller modes in the latest versions (26.0.2 or greater).  The reconnect is not 100% reliable, so if connection is lost, then you may have to open the source again to have it setup.  To add a UDP, RTP or SRT source, click the + button in the Source pane and select MediaSource.  In the Properties, un click Local File, add the standard srt string, for listener or caller

srt://172.16.12.25:5000?mode=listener

Set the input format to "mpegts" without the quotes, and setup the bufferring and reconnect to taste.

Marshall and other Cameras

Most cameras we have tested operate as callers, so our software will have to be setup as a listener on the local IP the SRT stream is coming in on.  Alternately, you can us the all addresses mode by using the 0.0.0.0 IP

srt://0.0.0.0:5000?mode=listener