Skip to content
Callaba

SRT player guide: receive, inspect and watch an SRT stream

On this page

Start with a native receiver, then prove the media

For an SRT contribution feed, start with a native receiver such as ffplay, OBS or a tested VLC build. A browser media element does not natively open an srt:// URL; browser playback starts after the contribution has been received and made into a browser-compatible output.

A successful SRT session and a playable picture are separate results. Mode, host, UDP port, latency, Stream ID and passphrase open the session. The container, tracks, timestamps and codecs decide whether the receiver decodes it. If the job is to create, protect or operate the receiving endpoint, go to Callaba SRT Server. This guide starts at the receiver.

Run the quickest useful receiver test

ffplay is the shortest path to a direct check when the installed FFmpeg build includes SRT. OBS Media Source gives an operator a graphical preview after its SRT input details are set. VLC can be useful for a local view if the exact installed build supports the required SRT mode; confirm that build and test the agreed endpoint. None of these choices makes an unknown payload decodable.

1. Try ffplay against the agreed endpoint

For a receiver calling a known listener, replace the placeholders with an endpoint you are allowed to use:

Command
ffplay "srt://LISTENER_HOST:PORT?mode=caller"

For a receiver waiting for a caller:

Command
ffplay "srt://0.0.0.0:PORT?mode=listener"

Then use the same host, port, mode, Stream ID, passphrase and latency policy in OBS or another native receiver. FFmpeg documents the SRT URL options; OBS documents its SRT input workflow. Do not paste a passphrase into tickets, chat or shell history you do not control.

2. Match Caller and Listener before changing player settings

The common arrangement is simple: a Listener waits on a UDP port and a Caller connects to its reachable address. Write both roles down, verify the host and port from the sender network, then start the player. Two listeners wait; a Caller aimed at an unreachable address will not be fixed by a codec setting. Rendezvous is a separate configuration that both endpoints must support.

When encryption is enabled, use the same passphrase and compatible key settings at both ends. If a service uses a Stream ID to select a stream, preserve its syntax and escaping. Treat both as connection data: keep secrets out of screenshots and reports, and compare a denied session with the available endpoint logs.

3. Probe a connected stream that will not play

SRT carries packets, not a promise about the video codec, audio codec or container. MPEG-TS is common for contribution, but it still needs valid programme information, timestamps and streams the chosen player can decode. Probe the same endpoint before changing latency again:

Command
ffprobe -v error -show_format -show_streams "srt://LISTENER_HOST:PORT?mode=caller"

Look for the container, video and audio codecs, profiles, tracks and timestamps. Compare those facts with the player’s documented support.

Live SRT player demo

Test an SRT player connection

Create a temporary connection for one hour. Send an SRT stream to the publisher address in Caller mode, leaving Stream ID empty. After the publisher connects, watch it in Multiview below or connect a native player to the receiver address in Caller mode.

Ready to create

Set latency for recovery, not appearance

SRT latency gives late packets and retransmissions time to arrive. It is not the whole glass-to-glass delay; encoding, decoder buffers, packaging and viewer buffers add their own delay. Start with the measured route, then compare clean and impaired conditions while watching loss, retransmissions, drops and decoded continuity.

In FFmpeg-style SRT URLs, latency=200000 means 200 ms because the value is in microseconds. It is only an example. Record the effective value at both endpoints and tune for the actual contribution path.

If bitrate is present but the screen is black

What you seeCheck next
No connectionRoles, reachable host, UDP port, firewall and access data.
Connected, no picture or audioRun the probe; check programme information, codecs, tracks and timestamps.
Picture breaks under lossCompare route measurements and recovery latency before changing the player.

That separation prevents a payload problem from becoming an endless sequence of connection changes.

Choose the viewing handoff deliberately

Use native SRT for a direct contribution check. For a shared operator view, receive the feed and use Multiview to verify picture, audio meters, stream information and connection events. For browser delivery, publish and test a browser-compatible output with the Web Player. A route that looks healthy at ingress is not a substitute for checking the final viewing surface.

When the receiver test becomes an operating path, the SRT monitoring preset is a starting configuration for four incoming SRT sources and four Multiview slots. For a production path that also needs recording, processing and an AV Mixer workflow, review the SRT production preset before configuring the exact source and output.

Keep a short receiver check

  1. Record the endpoint roles, host, port, latency, Stream ID policy and encryption state.
  2. Confirm the real sender network can reach the receiver.
  3. Check transport during a clean interval and the impaired condition that matters for the event.
  4. Confirm a decoded picture and programme audio on the intended player.
  5. Restart one side in a planned test and check the final operator or viewer surface again.

For protocol detail, see the SRT live-transmit documentation and the Callaba SRT protocol guide.

SRT player FAQ

Can a browser play an SRT URL directly?

Not through the standard HTML media element. Receive SRT first and publish a browser-compatible output.

Why can an SRT connection show bitrate without video?

The session may work while the player cannot decode the container, tracks, timestamps or codec profile.

Should the player use Caller or Listener mode?

Use the role that complements the agreed peer and its network reachability.

Does more SRT latency always fix packet loss?

No. It gives retransmissions more time, but it cannot open blocked UDP, repair sustained capacity loss or decode an unsupported payload.

Next steps