RIST: Reliable Internet Stream Transport

1. What is RIST?

RIST stands for Reliable Internet Stream Transport. The specification family published by the Video Services Forum (VSF) describes an interoperable transport for live video over IP connections where packets can get lost, arrive late, or arrive out of order.

RIST replaces neither the camera nor the encoder. It carries the already encoded contribution, often as an MPEG transport stream, from the sender to a receiver, decoder, or production system. Typical uses are outside broadcasts, feeds between sites, and professional point-to-point links over the public internet.

2. How RIST recovers lost packets

Sender and receiver work together through feedback. If the receiver detects a gap, it can request the missing packets again. The sender keeps data around for a short time and resends the requested packets. That improves picture stability, but it needs enough buffer time and bandwidth headroom.

A bigger buffer raises the chance of a successful retransmission, but end-to-end latency grows with it. To pick a sensible setting, you have to look at RTT, packet loss, stream bitrate, and how much delay your workflow can tolerate, all together.

3. Simple Profile and Main Profile

Higher profiles build on the features of the earlier ones. What matters is not which profile can do more on paper, but which profile sender and receiver both support. Before real use, you have to match the profile, encryption, and URL syntax on both sides.

4. Sending RIST from OBS

OBS Studio can send a finished stream over RIST to a compatible receiver. The address rist://SERVER:PORT is only a pattern, not a clickable server and not a ready-made configuration.

1. In OBS, go to Settings → Stream and select the service Custom.
2. Enter the real RIST address of the receiver and follow its profile and port requirements.
3. Leave the stream key empty. According to the OBS guide, this field is not used for RIST output.
4. Configure the buffer and expected total bandwidth to match on both sides.
5. Before going live, test packet loss, reconnection, audio, and the actual delay.

Parameters like bandwidth, buffer, and session-timeout affect recovery. Base the values on measurements, and do not copy them unchecked from someone else's example.

5. Receiving RIST in OBS

When receiving, the OBS source you pick is what matters. The official OBS RIST guide distinguishes between:

• VLC Video Source: according to OBS, it can receive RIST Simple Profile. VLC must be installed on the production computer for this.
• Media Source: according to OBS, it can receive RIST Main Profile. Turn off "Local File", set the matching RIST address as the input, and use mpegts as the input format.

If OBS itself receives on a local address, the OBS guide shows a URL following the pattern rist://@LOCAL_IP:PORT. Your own IP, the port, and any required options must match the other end. The pattern address cannot be used as is.

Practical example: through a RIST relay to OBS

Signal path: camera/encoder or a sending OBS → RIST connection → RIST relay on a server → second RIST connection → receiving OBS. That way the contribution first lands at a fixed endpoint and is then picked up in OBS at a different location. The libRIST software offers a tool called rist2rist for this kind of forwarding.

1. The sender transmits to the RIST input of the relay.
2. The relay must make the received stream available on a separate RIST output that OBS can reach. The input and output connections need matching profiles, ports, and, if used, encryption.
3. On the production computer in OBS, create a source for receiving and enter the real relay address. For a remote endpoint, the OBS guide shows an address following the pattern rist://RELAY_IP:PORT: VLC Video Source for Simple Profile, or Media Source with the input format mpegts for Main Profile.

Important: "Picking up" here means that OBS opens a connection to the RIST output set up for that purpose. An arbitrary server or an SRTLA relay does not automatically provide such a RIST output. The extra hop needs resources and can add more delay, so test both legs separately.

6. RIST, SRT, SRTLA, or RTMP?

For a typical smartphone or backpack IRL setup, SRTLA and SRT are usually easier to get into. RTMP/RTMPS often stays important for the output to the platform. RIST gets interesting when existing broadcast devices, receivers, or service providers already support the standard and you want to build a vendor-neutral feed.

7. Practical check before you go live

• Do both endpoints support the same RIST profile?
• Are the UDP port and firewall rule opened only as far as necessary?
• Is the bandwidth headroom big enough for the stream plus retransmissions?
• Does the buffer fit the measured RTT and packet loss?
• With Main Profile, is the encryption you want set up identically on both sides?
• Did you run a longer test with an artificially worse connection?

A successful connection alone is not enough. What counts is a clean picture, synchronized audio, controllable latency, and a clean recovery after a short interruption.

8. Official information and related guides

Always check technical details against the implementation you actually use. Further reading: the VSF RIST activity group and the official RIST guide for OBS Studio.

9. Common questions