SRT vs RTMPS
Xive takes your stream over RTMPS or SRT. Both end up as the same channel, the same live video and the same replays. The difference is how well they cope with a bad connection.
The short answer. On a wired, stable connection, use RTMPS: it works with every encoder and every multistream service. If you stream over Wi-Fi, a mobile hotspot or a connection that drops packets, try SRT. Use one or the other, never both at the same time.
Side by side
| RTMPS | SRT | |
|---|---|---|
| Xive server | rtmps://ingest.xivecdn.com:443/live/ | srt://live.cloudflare.com:778 plus a stream id and passphrase |
| What you paste | Server and stream key | One SRT URL that already contains the stream id and passphrase |
| Runs over | TCP, port 443 (like a web page) | UDP, port 778 |
| Encrypted | Yes (TLS) | Yes (passphrase) |
| Packet loss | A lossy link slows the whole stream down, so it buffers or drops frames | Lost packets are resent within a short window, so brief loss doesn’t reach viewers |
| Encoder support | Every encoder and multistream service | OBS, vMix, hardware encoders and most modern tools (caller mode) |
| Viewers, replays, clips | Identical. It is the same channel and the same recording either way. | |
Xive does not offer plain (unencrypted) RTMP, WHIP, or going live from the browser. On a phone, use the Xive app’s Go Live instead.
When SRT is worth it
- Wi-Fi. Even good Wi-Fi drops packets when the microwave or a neighbour’s network gets busy.
- Mobile hotspots and 4G/5G routers, including streaming from a car or an event.
- Long distances to the nearest server, where small losses add up.
- Viewers report freezes but your OBS stats show your upload is fine most of the time.
SRT can’t create bandwidth you don’t have. If your upload is simply too slow for your bitrate, lower the bitrate first (see the setup guide).
When to stay on RTMPS
- You are on a wired connection and the stream is already smooth.
- Your encoder, or a multistream service in front of Xive, only speaks RTMP/RTMPS.
- Your network blocks outgoing UDP (some offices, schools and hotel networks do). RTMPS uses port 443, which is almost never blocked.
Setting up SRT in OBS
- 1
Open Creator Studio → Settings → Stream (thexive.com/live-dashboard/settings/stream), press Show next to the SRT server URL and copy it.
- 2
In OBS: Settings → Stream, Service Custom. Paste the SRT URL as the Server and leave Stream Key empty.
- 3
Keep the same encoder settings as RTMPS: H.264 (not the AMD encoder), CBR, 2-second keyframes, AAC audio.
- 4
Start Streaming. Going back to RTMPS is just pasting the RTMPS server and key again.
Service: Custom
Server: srt://live.cloudflare.com:778?streamid=…&passphrase=…
Stream Key: (leave empty)
Encoders that ask for the SRT values in separate boxes (server, port, stream id, passphrase) can use the Other encoders section on the same Creator Studio page. Set the encoder to caller mode; Xive does not accept listener or rendezvous mode.
The SRT URL is as secret as your stream key. It contains your passphrase, so never show it on stream. Regenerating your key in Creator Studio changes the SRT passphrase too, so paste the new URL into OBS afterwards.
SRT and rebroadcasting
How you send your stream to Xive doesn’t affect rebroadcasting: Xive forwards the same stream to every destination you’ve turned on. Destinations themselves can be rtmp://, rtmps:// or srt:// servers. See Rebroadcast to other platforms.
Troubleshooting
SRT won’t connect at all
Most often the network blocks outgoing UDP: switch back to RTMPS. Otherwise, re-copy the SRT URL from Creator Studio (it changes when you regenerate your key) and check the encoder is in caller mode.
It connects but the channel never goes live
Same causes as RTMPS: a keyframe interval left on 0/auto, or audio that isn’t AAC. Fix them in Settings → Output, then stop and start streaming.
Still freezing on SRT
Your upload can’t keep up even with retransmission. Lower the bitrate to about 70% of your measured upload speed, or move to a wired connection.