Ultra Encode is a product family, not one interchangeable encoder. Confirm the label on the unit—HDMI, SDI, HDMI Plus, SDI Plus, or AIO—before selecting its input, encode profile, audio mapping, recording task, or streaming destination.
For this handoff, the Magewell unit contributes one SRT feed and Callaba SRT Server receives it. Monitoring, recording, and routes are separate Callaba jobs after that feed is accepted.
Model, hardware revision, installed firmware, chosen input, and visible SRT menu.
Magewell as SRT Caller; Callaba listener address, UDP port, access rule, and agreed transport controls.
Confirm the expected peer and transport state; then test the next job independently.
These stages isolate responsibility. A connected SRT session supports the contribution handoff; it does not prove a separate decoder, player, recorder, route, or external destination.
Read the model boundary before configuring it
| Unit group | Commissioning relevance | Keep separate |
|---|---|---|
| HDMI / SDI (Rev B) | One HDMI or SDI input and loop-through. Magewell lists SRT Caller/Listener, H.264/H.265, two encoded AAC channels, and one output audio stream. | Do not borrow Plus/AIO 4K, eight-audio-stream, local-recording, RIST, or ZIXI claims. |
| HDMI Plus / SDI Plus | Magewell lists SRT Caller/Listener, eight encoded/output audio streams, and recording to internal, USB, or network storage. HDMI Plus and SDI Plus retain different physical-source interfaces. | Confirm the installed unit's current input specification; Magewell's SDI Plus material has conflicting 4K wording, so this page makes no generic 4K SDI-input promise. |
| AIO | It can encode one HDMI or SDI input, or mix both as picture-in-picture or side-by-side. Magewell lists SRT Caller/Listener and recording while streaming. | AIO recording is to an SD card, external USB storage, or networked storage (NFS, CIFS, or SMB). Validate its task and selected storage before the event. |
Magewell documents SRT Caller and Listener for these groups, but the reviewed sources do not establish the first firmware that introduced SRT. Treat the installed firmware and the destination controls visible on that exact unit as the operative source for the event.
Set one Caller-to-Listener path
- Prepare the Callaba receiving boundary. Create the SRT listener and record its public address, UDP port, access rule, Stream ID policy, encryption policy, and agreed latency/receive-buffer settings.
- Configure one Magewell destination. In the exact unit's live-destination controls, choose SRT Caller, enter the listener address and port, select the intended encoded stream, and set a Stream ID only when the Callaba rule expects one.
- Match the controls exposed by that unit. Transport controls vary by exact Ultra Encode model and installed firmware. Compare the visible SRT mode, latency, encryption/passphrase, Stream ID availability, and any MTU or recovery settings with the Callaba listener requirements; do not transfer numeric values from another family manual.
- Run the first acceptance test. Start one destination and confirm the intended peer, bitrate, packet loss, RTT, connection duration, peer IP, and event state. A connected socket is not evidence that a later receiver is healthy.
Assign the next job after ingest
Callaba begins at the accepted SRT handoff. Choose the module that owns the next task rather than treating it as a setting on the encoder.
Observe
Multiview is a browser board for reviewed inputs, not a production switcher, VMS, or universal decoder.
Record
Live Video Recording records a reviewed live input continuously or in timed segments. It is distinct from source-side Plus/AIO recording.
Route
SRT routes and multi-streaming are separate output decisions; verify their real receiver.
Use the symptom to choose the next check
- No session
- Check Caller/Listener roles, address, UDP path, port, Stream ID rule, and encryption/passphrase before changing video settings.
- Session, wrong media
- Check the selected HDMI/SDI input, active Magewell destination, encode profile, audio mapping, and the accepted input's media behavior.
- Unstable transport
- Compare bitrate, packet loss, and RTT with the event baseline; adjust one agreed variable at a time with the network owner.
- Downstream failure
- Test the selected board, recording job, route, player, or external receiver independently. Stable ingest does not validate it.
Next steps
Keep the commissioning record with the event: exact model, firmware, input, one destination, listener policy, expected peer, and acceptance observation. Only then add the module the operation needs.
