sebiulabs realtime Documentation

Getting Started

1. Log in to the dashboard with credentials provided by your admin.
2. Go to the Send tab and copy your stream key (starts with sk_).
3. Configure your encoder (OBS, FFmpeg, etc.) using the settings below.
4. Hit Start Streaming — your stream appears on the dashboard within seconds.

Ingest Protocols

In all URLs above, replace {name} with your chosen stream name (e.g. my-stream) and {key} with your stream key from the dashboard.

OBS Studio Setup

OBS Studio (version 30 and later) supports all three streaming protocols. Follow the step-by-step instructions for your preferred protocol below.

WHIP OBS → WebRTC (Recommended — Lowest Latency)

1. Open OBS → Settings → Stream
2. Set Service to WHIP
3. In the Server field, paste the full URL including your stream name and key:

https://cdn.clouds3.uk/live/my-stream?direction=whip&key=sk_your_key

4. Leave the Bearer Token field empty
5. Go to Settings → Output and set Output Mode to Advanced
6. On the Streaming tab, set:

7. Click OK, then click Start Streaming

RTMP OBS → Classic

1. Open OBS → Settings → Stream
2. Set Service to Custom...
3. Fill in these two fields exactly:

Replace my-stream with your chosen stream name and sk_your_key with your actual key from the Send tab.

4. Go to Settings → Output → Advanced → Streaming and configure the encoder settings (see table below)
5. Click OK, then click Start Streaming

SRT OBS → Low-Latency

SRT provides reliable, low-delay delivery with built-in error correction. Use it when streaming over unstable or remote connections.

1. Open OBS → Settings → Stream
2. Set Service to Custom...
3. In the Server field, paste the full SRT URL:

srt://cdn.clouds3.uk:9999?streamid=default/live/my-stream?key=sk_your_key

4. Leave the Stream Key field empty (the stream ID is embedded in the URL)
5. Go to Settings → Output → Advanced → Streaming and configure encoder settings (see table below)
6. Click OK, then click Start Streaming

Recommended OBS Output Settings

Go to Settings → Output, set Output Mode to Advanced, then configure the Streaming tab:

vMix Setup

vMix supports both SRT and RTMP output. Configure one of the following in vMix's output settings.

SRT vMix → SRT Output (Recommended)

1. In vMix, click the gear icon below the stream button, or go to Settings → Outputs
2. Click Output Settings on one of the output channels
3. Set Output Type to SRT (Caller)
4. Fill in the following fields:

5. Under Video, set the codec and quality:

6. Click OK, then click the Stream button to go live

RTMP vMix → RTMP Output

1. In vMix, click the gear icon below the stream button
2. Set Destination to Custom RTMP Server
3. Fill in the following fields:

4. Set video quality: H.264, CBR at 4000 kbps, Keyframe every 1s, Profile: Baseline
5. Click OK, then click the Stream button to go live

Restreamer Setup

Restreamer (by datarhei) is an open-source tool for relaying video sources to streaming platforms. Use it to push an existing source (IP camera, HDMI capture, file) to sebiulabs realtime.

Step-by-Step Configuration

1. Open the Restreamer UI in your browser (usually http://your-server:8080)
2. Set up your video source (RTSP camera, screen capture, etc.) on the Video Setup page
3. On the Streaming / Publication page, click Add new process or edit the existing output
4. Set Output Type to one of the following:

5. Set the video/audio encoding parameters:

6. Click Save and Start the process

Restreamer with FFmpeg Process (Advanced)

If using Restreamer's FFmpeg process directly, use this command template:

{ffmpeg.binary} -i {input} \
  -c:v libx264 -preset veryfast -tune zerolatency \
  -b:v 3000k -g 30 -keyint_min 30 \
  -c:a aac -b:a 128k \
  -f flv "rtmp://cdn.clouds3.uk:1935/live/my-stream?key=sk_your_key"

FFmpeg Command-Line Examples

FFmpeg can be used to ingest from files, cameras, screen captures, or any other source. Below are copy-pasteable commands for each protocol.

RTMP FFmpeg → RTMP

Stream a file or live source via RTMP:

# Stream a video file to RTMP
ffmpeg -re -i input.mp4 \
  -c:v libx264 -preset veryfast -tune zerolatency \
  -b:v 3000k -maxrate 3000k -bufsize 6000k \
  -g 30 -keyint_min 30 \
  -c:a aac -b:a 128k -ar 48000 \
  -f flv "rtmp://cdn.clouds3.uk:1935/live/my-stream?key=sk_your_key"

# Stream a webcam (Linux) to RTMP
ffmpeg -f v4l2 -i /dev/video0 -f pulse -i default \
  -c:v libx264 -preset veryfast -tune zerolatency \
  -b:v 2500k -g 30 -keyint_min 30 \
  -c:a aac -b:a 128k -ar 48000 \
  -f flv "rtmp://cdn.clouds3.uk:1935/live/my-stream?key=sk_your_key"

SRT FFmpeg → SRT

Stream via SRT for lower latency with error correction:

# Stream a file via SRT
ffmpeg -re -i input.mp4 \
  -c:v libx264 -preset veryfast -tune zerolatency \
  -b:v 3000k -g 30 -keyint_min 30 \
  -c:a aac -b:a 128k -ar 48000 \
  -f mpegts "srt://cdn.clouds3.uk:9999?streamid=default/live/my-stream?key=sk_your_key&latency=120000&mode=caller"

# Stream with H.265/HEVC via SRT (better quality, lower bitrate)
ffmpeg -re -i input.mp4 \
  -c:v libx265 -preset veryfast -tune zerolatency \
  -b:v 2000k -g 30 -keyint_min 30 \
  -c:a aac -b:a 128k -ar 48000 \
  -f mpegts "srt://cdn.clouds3.uk:9999?streamid=default/live/my-stream?key=sk_your_key&latency=120000&mode=caller"

WHIP FFmpeg → WHIP (WebRTC)

FFmpeg 7.0+ supports WHIP output for sub-second latency:

# Stream via WHIP (requires FFmpeg 7.0+ built with libdatachannel or libwebrtc)
ffmpeg -re -i input.mp4 \
  -c:v libx264 -preset veryfast -tune zerolatency \
  -b:v 2500k -g 30 -keyint_min 30 \
  -c:a libopus -b:a 128k -ar 48000 \
  -f whip "https://cdn.clouds3.uk/live/my-stream?direction=whip&key=sk_your_key"

FFmpeg Quick Reference

Playback & Sharing

https://dashboard.clouds3.uk/watch.html#my-stream

WebRTC Playback URL

For direct WebSocket signalling (custom players):

wss://cdn.clouds3.uk/live/my-stream

Edge Playback

You can replace cdn.clouds3.uk with a specific edge server hostname if needed. In most cases, the geo-router at play.clouds3.uk handles this automatically and sends each viewer to the best server.

Embedding on Your Website

You can place a live stream on any website by adding an iframe. The embedded player automatically connects viewers to the nearest server for the best performance.

Basic Embed (iframe)

<iframe
  src="https://dashboard.clouds3.uk/embed.html?s=my-stream"
  width="640" height="360"
  frameborder="0" allowfullscreen
  allow="autoplay"></iframe>

Responsive Embed

<div style="position:relative;padding-bottom:56.25%;height:0;overflow:hidden;">
  <iframe
    src="https://dashboard.clouds3.uk/embed.html?s=my-stream"
    style="position:absolute;top:0;left:0;width:100%;height:100%;"
    frameborder="0" allowfullscreen
    allow="autoplay"></iframe>
</div>

Options

The embedded player connects via WebRTC through the geo-router for sub-second delay. You can override the edge server with the node parameter if needed.

Stream Keys

Every user gets a unique stream key (e.g. sk_a1b2c3d4e5f6). Your stream key proves you are authorized to publish a stream. Think of it like a password for your stream.

• Find your key in the Send tab of the dashboard
• Append it to your stream URL as ?key=sk_...
• Click Regenerate to get a new key (the old one stops working immediately)
• Keep your stream key private -- anyone who has it can stream to your account

Dashboard

The dashboard at dashboard.clouds3.uk provides:

• Nodes -- live status of all servers, including CPU usage, memory, and viewer counts
• Streams -- all active streams with codec, bitrate, viewer count, and watch links
• Ingest -- your stream key and all the URLs you need to start streaming
• Users (admin only) -- manage streamer accounts and stream keys
• Autoscale (admin only) -- view auto-scaling status and adjust thresholds