Matrox Maevex to Callaba: SRT, RTSP, and recorder workflows

May 14, 2026

Written by Iurii Pakholkov

Founder of Callaba. Building cloud video tools for SRT, RTMP, WebRTC, NDI, live routing, monitoring, recording, and production workflows.

Release: Callaba 8.4

Magewell Ultra Encode is a family of HDMI, SDI and AIO hardware encoders for live IP video workflows. The practical Callaba path is simple: send SRT from Ultra Encode to Callaba Gateway, then use the received feed for monitoring, recording, playback and routing.

This guide is written for the search intent behind Magewell Ultra Encode SRT, Magewell Ultra Encode HDMI SRT, Magewell Ultra Encode SDI SRT, Magewell Ultra Encode multiview, Magewell Ultra Encode recorder and Magewell Ultra Encode playback.

Quick answer: how do I connect Magewell Ultra Encode to Callaba Gateway?

Create an SRT server in Callaba Gateway in Listener mode, open the selected UDP port, then set the Magewell Ultra Encode output to SRT Caller. Enter the Callaba public IP or DNS name, destination port, latency, stream ID if used, and the same passphrase if encryption is enabled. After Callaba receives the feed, you can use it for browser multiview, cloud recording, playback, routing, restreaming or delivery.

The recommended setup keeps Callaba Gateway as the public SRT listener and Ultra Encode as the caller from the venue or site network.

What this setup does

This workflow sends a live video feed from a Magewell Ultra Encode device to Callaba Gateway over SRT. Callaba receives the stream in the cloud, then the feed can be monitored, recorded, previewed, routed, restreamed, used in a web player, or placed into a browser-based multiview board.

Magewell Ultra Encode captures HDMI, SDI, or AIO source content and sends the stream over SRT.
Callaba Gateway listens on a public UDP port and accepts the incoming SRT stream.
Operators use Callaba to check preview, bitrate, codec, packet loss, recording, multiview, playback, and route behavior.

Ultra Encode sends the encoded stream. Callaba turns that source into a monitored and routable cloud workflow.

Which Ultra Encode model do you have?

The SRT setup is similar across the Ultra Encode family, but the source connector and production role are different. Ultra Encode HDMI is usually used when the source is HDMI. Ultra Encode SDI is stronger for broadcast-style SDI sources. Ultra Encode AIO is the cleaner option when you want HDMI and SDI in the same appliance.

Choose the Magewell model based on the source connector first. The Callaba SRT ingest logic stays the same.

Magewell model	Best Callaba angle	Note
Ultra Encode HDMI	HDMI source to SRT ingest, multiview, recorder and playback.	Good for cameras, laptop outputs, switchers and presentation feeds.
Ultra Encode SDI	SDI source to SRT ingest, browser monitoring and cloud routing.	Good for broadcast cameras, production routers and venue SDI outputs.
Ultra Encode AIO	HDMI or SDI source to Callaba with broader output options.	Good when the source type may change between events.

Recommended SRT mode: Callaba Listener, Ultra Encode Caller

For most cloud ingest workflows, the cleanest connection model is:

Callaba Gateway: Listener
Magewell Ultra Encode: Caller

This keeps the public listening port on the Callaba side. The site network only needs to allow the Ultra Encode unit to send outbound UDP traffic to the Callaba IP and port.

A template SRT URL looks like this:

srt://YOUR_CALLABA_IP:10100?mode=caller&latency=200&streamid=magewell-ultra-encode-main

A filled example for field testing can look like this:

srt://demo.callaba.io:10100?mode=caller&latency=200&streamid=magewell-ultra-encode-main

Use the second example as a template. Replace host, port, stream ID and passphrase with your own Callaba values.

Before you start

Prepare the SRT connection before touching the live production profile. This avoids changing many values at once and then not knowing which one caused the problem.

Before you start: confirm the exact Ultra Encode model and firmware support the SRT mode and output settings you plan to use. Magewell supports both SRT Caller and SRT Listener on Ultra Encode models, but field names can differ between UI versions.

Callaba public address Use the public IP address or DNS name of the Callaba instance that will receive the SRT stream.

UDP port Choose one UDP port for this Ultra Encode input and make sure it is open in the cloud firewall or security group.

Latency Start with 120–500 ms for normal internet contribution. Increase it if the network is unstable.

Stream ID Use a clear name such as magewell-ultra-encode-main if your workflow uses stream ID routing.

Passphrase If you enable encryption, use the same passphrase on both sides. Keep it within the valid SRT length range.

Media profile Confirm what Callaba will receive: H.264/H.265, resolution, frame rate, bitrate and audio format.

Step 1: create the SRT listener in Callaba

In Callaba, create a new incoming SRT server for the Magewell feed. The exact module name can differ by UI version, but the operational idea is the same: Callaba opens a UDP port and waits for the Ultra Encode unit to connect.

Open your Callaba environment.
Create a new SRT input or SRT server.
Set the role to Listener if the UI exposes this option.
Choose a UDP port, for example 10100.
Set latency, for example 200 ms as a starting point.
Add a stream ID if your routing model uses it.
Add the same passphrase that you plan to use on Magewell, if encryption is needed.
Open the UDP port in your cloud firewall or security group.

Step 2: configure the Magewell Ultra Encode SRT output

Open the Ultra Encode web UI and choose the output session that should send the source to Callaba. Firmware versions can change exact labels, so look for streaming protocol, SRT, output, destination, or session settings.

Select the HDMI or SDI input you want to send.
Set the streaming protocol to SRT.
Set the connection mode to Caller.
Enter the Callaba public IP address or DNS name as the destination address.
Enter the same destination UDP port that Callaba is listening on.
Set latency to the same starting value, or close to it.
Enter stream ID if Callaba expects one.
Enable encryption only if you have already prepared the same passphrase in Callaba.
Start the output and watch for connection state in Callaba.

Ultra Encode devices can be used for multi-destination workflows. For the first Callaba test, start with one clean SRT output. After the first feed is stable, add multiview, recording, playback, restreaming or a second destination.

Settings table

This table is the fastest way to avoid mismatches. The words in the Magewell interface can differ, but the values must describe the same SRT connection.

Match SRT transport settings first. Then verify codec, bitrate, audio and workflow outputs.

Setting	Callaba Gateway	Magewell Ultra Encode	Why it matters
Mode	Listener	Caller	One side must wait, the other side must connect.
Address	Public IP or DNS	Callaba destination address	Magewell must call the reachable Callaba address.
Port	Open UDP port	Same destination port	A wrong port looks like no connection at all.
Latency	120–500 ms starting point	Same or close value	Too low can break stability on noisy networks.
Stream ID	`magewell-ultra-encode-main`	Same value if used	Useful when several Magewell streams share routing logic.
Passphrase	Same encrypted stream passphrase	Same encrypted stream passphrase	If encryption is enabled, both sides must match exactly.

Magewell Ultra Encode multiview workflow with Callaba

Magewell does not need to be your browser multiview system. It can be the reliable source encoder. After Callaba receives the SRT stream from Ultra Encode, that feed can be placed on a browser-based multiview board with other sources, backup paths, remote feeds or player outputs.

This is useful when operators need to monitor several encoder feeds without bringing every stream back into a local hardware multiviewer.

Interactive check: open the Callaba multiview demo to see how a received source can look after cloud ingest. Your real Magewell feed would appear as a live input in your own deployment.

Magewell Ultra Encode recorder workflow: device-side recording vs cloud recording

Some Ultra Encode workflows can include device-side or source-side recording, especially with newer or broader models such as AIO. Callaba adds a different layer: cloud-side recording after SRT ingest. These two approaches do not replace each other. They protect different parts of the workflow.

Recording layer	What it protects	When to use it
Magewell/source-side recording	The source side, before internet transport.	Use it when the site needs a local copy or source-side fallback.
Callaba cloud recording	The received workflow side, after SRT reaches the cloud.	Use it when you need proof of what actually arrived at the gateway.

For critical workflows, the best setup can be parallel recording: keep a local or source-side recording near the encoder and record the received SRT stream in Callaba. That way you have one copy before transport and another copy after ingest.

Magewell Ultra Encode playback workflow with Callaba

Playback can mean several things in an Ultra Encode workflow. It can mean browser preview in Callaba, a player page for viewers, or downstream routing to another production or display system.

For browser playback, Callaba receives the SRT stream and makes it available for preview, web player, monitoring or downstream delivery. For production playback, the same received source can be routed to restreaming, recording, multiview or another output workflow.

If you want to understand the player side, use the HLS streaming server guide as the next step after SRT ingest.

What to monitor in Callaba after Magewell starts streaming

Once the Ultra Encode output is active, Callaba should become the operational source of truth for the incoming feed. Do not only check whether the stream is connected. Check whether it is useful for production.

Connection state: the Magewell caller should appear as connected to the Callaba listener.
Bitrate: confirm that the live bitrate matches the expected encoder profile.
Codec: confirm H.264/H.265 and profile compatibility with the next part of the workflow.
Resolution and frame rate: confirm the received values match the source format.
Audio: check that audio exists and is routed as expected.
Packet loss / stability: watch for packet loss, reconnects, or jitter symptoms.
Preview: use browser preview or multiview to confirm the picture is actually live.
Recording and playback: test recorder and player paths after the source is stable.

Operational rule: the stream is not ready when the socket connects. It is ready when connection state, preview, bitrate, audio, recording, playback and downstream routing all look correct.

Troubleshooting

Most Ultra Encode to Callaba SRT issues fall into a small number of buckets. Check them in this order.

Start with transport settings. Only move to media, recorder, playback and routing after SRT is stable.

1. No connection in Callaba

Confirm Callaba is in Listener mode.
Confirm Ultra Encode is in Caller mode.
Check the destination IP or DNS name in the Magewell profile.
Check that the UDP port is open in the cloud firewall.
Check that the site network allows outbound UDP to that port.

2. Connected, but no picture

Confirm the HDMI or SDI input has a valid signal.
Confirm the output session is active.
Start with a simple H.264 profile before testing more complex settings.
Check resolution, frame rate, bitrate and audio mapping.
Restart only the stream output first, not the whole device, so you can isolate the issue.

3. Stream drops or stutters

Increase SRT latency.
Lower bitrate and test again.
Check uplink speed from the site network.
Watch packet loss and reconnect behavior in Callaba.
Avoid unstable Wi-Fi or congested internal paths for the encoder network.

4. Playback or multiview does not show the source

Confirm that the SRT input is connected and visible in Callaba.
Check that the correct input is assigned to the multiview tile or player route.
Check browser permissions, codec support and player URL.
Use a single clean route before adding several destinations.

Official references used for this guide

Use these if you need exact Magewell model details, protocol lists, session limits or SRT behavior before configuring a production device.

FAQ

Can Magewell Ultra Encode send SRT to Callaba Gateway?

Yes. Ultra Encode HDMI, SDI and AIO support SRT. In a simple cloud ingest setup, Callaba Gateway listens for the incoming SRT stream and the Magewell encoder connects as the caller.

Should Ultra Encode be Caller or Listener?

For most public cloud workflows, set Callaba as the SRT Listener and set Ultra Encode as the SRT Caller. This keeps the open UDP port on the cloud side and usually makes firewall rules easier at the site.

Can I use Magewell Ultra Encode with browser multiview?

Yes. Ultra Encode sends the SRT stream to Callaba. After Callaba receives it, the feed can be placed on a browser-based multiview board with other sources.

Can Callaba record a Magewell Ultra Encode stream?

Yes. After Callaba receives the SRT stream, you can record the received feed in the cloud. This is different from source-side recording and is useful when you need proof of what reached the gateway.

Can Callaba provide playback for a Magewell Ultra Encode stream?

Yes. After SRT ingest, Callaba can provide browser preview, web player delivery or downstream routing to another workflow, depending on your deployment.

Which Ultra Encode model should I use?

Use Ultra Encode HDMI for HDMI sources, Ultra Encode SDI for SDI sources, and Ultra Encode AIO when you want HDMI and SDI in one unit or need broader output options.

Final practical rule

Make the first Magewell → Callaba SRT connection boring. One output, one UDP port, one listener, one caller, no unnecessary routing. When that is stable, add encryption, stream ID, multiview, recording, playback and destinations.

Last updated: May 14, 2026

Try Callaba Gateway with your Magewell Ultra Encode

Create an SRT listener in Callaba, send an Ultra Encode stream to the gateway, and monitor the feed before routing it to recording, restreaming, multiview, playback, or player delivery.

See SRT server setup Open multiview demo