RTMP setup (OBS, StreamLabs, encoder)
Pointing your streaming software at Suzko.
Get your stream credentials
/tools/cloud-streaming → Stream Inputs → New stream. You get:
- Server URL (e.g.
rtmps://live.suzko.net:443/live) - Stream key — a unique token. Treat it like a password.
OBS Studio
- Settings → Stream
- Service: Custom
- Server: the Server URL from Suzko
- Stream Key: the stream key
- Use authentication: off
- OK. Click Start Streaming.
StreamLabs OBS
Same flow as OBS, in Settings → Stream → Custom Ingest.
Hardware encoders (Teradek, Tricaster, AJA)
Generally:
- Protocol: RTMP or RTMPS
- URL: the Server URL
- Stream name / key: the Stream Key
- Codec: H.264, AAC
SRT (preferred for unreliable networks)
If your network drops packets, SRT is more forgiving than RTMP. We expose an SRT endpoint per stream:
srt://srt.live.suzko.net:6000?streamid=<your-stream-key>
OBS supports SRT natively (Service: Custom, Server: paste the
srt://... URL).
Recommended encoding settings
| Setting | Value |
|---|---|
| Codec | H.264 |
| Audio | AAC, 128–192 kbps |
| Bitrate | 4500–6000 kbps for 1080p60, 2500–4000 for 1080p30 |
| Keyframe interval | 2 seconds |
| Encoder | NVENC (NVIDIA), QuickSync (Intel), or x264 |
| CPU usage | Medium-fast for x264 |
Higher bitrates = better quality but more bandwidth needed at your end + at every destination's ingest.
Going live
- Start your encoder pushing.
- The Suzko stream dashboard shows the stream as Live within a few seconds.
- Click Go live to fan out to your destinations.
When you stop the encoder, the stream auto-ends after a few seconds of no input. VOD recording finalises within a minute.
Health monitoring
The live dashboard shows:
- Inbound bitrate (matches what you're sending)
- Per-destination status (OK, delayed, failing)
- Dropped frames + reconnect events
If a destination errors mid-stream, we keep trying — your other destinations are unaffected.