Setting Up a Magewell Ultra Encode
Send your service from a Magewell Ultra Encode to the platform over RTMPS, an encrypted connection, with the exact settings.
Setting Up a Magewell Ultra Encode
These steps use the Ultra Encode's web interface (open the encoder's address in a web browser), as described in Magewell's current Ultra Encode manual. The Ultra Encode streams to the platform over RTMPS — RTMP inside an encrypted connection, so your stream key never crosses the internet in clear text.
4K. The Ultra Encode AIO, HDMI Plus and SDI Plus encode 4K. The Ultra Encode HDMI and SDI encode up to 1080p — they accept a 4K input but stream it at 1080p.
Have the Connect your encoder card open in The Hub → Streaming — it appears when you start or schedule a stream.
Set the main stream's encoding
On the Encode tab, under the main stream settings:
| Setting | 1080p | 4K |
|---|---|---|
| Code type | H.264 | H.264 |
| Resolution | 1920×1080 | 3840×2160 |
| Frame rate | 30 | 30 |
| Bitrate | 6,000 Kbps | 16,000 Kbps |
| Keyframe interval | 60 frames | 60 frames |
| Audio | AAC, 160 Kbps | same |
The Keyframe interval is counted in frames: 60 — Magewell's default — is one keyframe every 2 seconds at 30 frames per second. Leave Code type on H.264; the platform does not take H.265.
Send over RTMPS
On the Live tab, click Add and select RTMP/RTMPS:
| Magewell field | Value |
|---|---|
| Name | Anything, such as Church stream |
| Stream | Main stream |
| URL | Paste the Server from the Hub, rtmps://ingest.streaming.1stflock.com:443/live |
| Stream key | Paste the Stream Key from the Hub |
| Authentication | Off |
Save it and start the stream. The Stream Key changes with every stream: each week, edit this entry and paste the new one.
Or send over SRT (encrypted)
If your Ultra Encode offers it, SRT is the better choice: it copes better with a shaky internet connection and recovers faster if one of our servers fails. It is encrypted with a passphrase of the stream's own, shown on the Connect your encoder card beside the Stream ID; without it the connection is refused. SRT needs outgoing UDP to port 8890; if your network blocks it, use RTMPS above.
On the Live tab, click Add and select SRT Caller:
| Magewell field | Value |
|---|---|
| Name | Anything, such as Church stream |
| Stream | Main stream |
| Address | ingest.streaming.1stflock.com |
| Port | 8890 |
| Latency | Leave the default (120 ms) |
| Stream ID | Paste the Stream ID from the Hub, whole |
| Encryption | AES-256 |
| Passphrase | Paste the Passphrase from the Hub |
Save it and start the stream.
The Stream ID and the passphrase change with every stream. Each week, paste the new Stream ID and Passphrase from the Hub; everything else stays.
If something goes wrong
- It will not connect over SRT. Check Address is the bare host (no
srt://), Port is8890, Encryption isAES-256with this stream's Passphrase, and the Stream ID is exactly as shown, starting withpublish:live/. If your building's firewall blocks outgoing UDP, ask whoever looks after the network to allow outgoing UDP to port8890, or use RTMPS. - It will not connect. Check the URL starts with
rtmps://— notrtmp://— includes:443, and ends in/live, and that the Stream key is this stream's and complete: it contains a?and a=. - Viewers see stalls at the start. Check the main stream's Keyframe interval is
60.
The settings every encoder needs, and what to expect if a server fails, are in Choosing and Setting Up an Encoder. Support is available 24/7.