VITEC MGW Ace Encoder to Callaba: SRT contribution workflows
More live video workflow notes and product updates.
Contribution encoder decision hub
MGW Ace is a contribution encoder, not the cloud operations layer. Its job is to turn a baseband source into a protected transport stream. Callaba receives that stream and gives operators a separate place to validate arrival, observe the path, record it and route it onward.
Written by Iurii Pakholkov, founder of Callaba. Materially reviewed on July 17, 2026 against the official sources listed below.
Choose the correct SRT contribution workflows
| Path | Operational role | When to choose it |
|---|---|---|
| Ace as SRT caller | The encoder initiates toward a reachable Callaba listener. | Usually the simplest boundary when the field side can make outbound UDP connections. |
| Ace as SRT listener | Callaba initiates toward an addressable encoder endpoint. | Use only when routing and firewall policy make the encoder safely reachable. |
| Rendezvous or multi-destination | Advanced peer negotiation or multiple destinations. | Validate exact firmware, NAT behavior and output limits before promising it in a show design. |
Keep the source, handoff and Callaba roles explicit
Source-side responsibility
VITEC owns SDI or HDMI acquisition, hardware H.264/HEVC encoding, transport packetization and source-side metadata.
Transport handoff
The handoff contract is codec, resolution, frame rate, audio, SRT mode, port, Stream ID, encryption and a tested loss/latency budget.
Callaba responsibility
Callaba owns receiver reachability, live transport statistics, recording, Multiview, protocol routing, playback and operational automation.
Validate MGW Ace before a contribution event
- 1. Record the exact MGW Ace hardware and firmware version. Release notes matter because SRT library, Stream ID and RTMPS behavior have changed between firmware releases.
- 2. Choose H.264 for the widest downstream compatibility or HEVC when bandwidth efficiency is required and every downstream decoder has been verified.
- 3. Create the opposite connection role in Callaba, then align port, encryption and Stream ID character for character. Open UDP in the actual traffic direction.
- 4. Exercise the workflow under representative packet loss and round-trip time. Hardware encoding latency does not include network recovery, receiver buffering or playback delay.
- 5. Confirm video, every required audio channel, captions or metadata, recording and the intended downstream route. Preserve screenshots without embedded credentials.
After preflight, use the SRT Gateway hub for architecture choices, the SRT Server guide for receiver concepts, Multiview for browser operations, and the SRT API documentation for automation. These shared resources do not replace the model-specific guide linked in the decision table.
Official references reviewed
Capabilities and menu fields can change with hardware revisions, firmware and account entitlements. Recheck the exact model before a production event.
- VITEC MGW Ace Encoder product page — Official role, codec and contribution use cases.
- MGW Ace Encoder datasheet — Official SRT modes, codec ranges, interfaces and encryption details.
- VITEC firmware knowledge base — Model release notes used to confirm firmware-dependent behavior.
Frequently asked questions
Which SRT modes does MGW Ace Encoder support?
The official encoder datasheet lists caller, listener and rendezvous modes. Pick one mode for the primary route and test it through the real firewalls; support on paper does not prove that the selected NAT topology is reachable.
Can MGW Ace send HEVC over SRT to Callaba?
The encoder supports HEVC/H.265 and SRT. Callaba can receive the transport, but the complete route is acceptable only after the chosen profile, bit depth, audio and every downstream consumer have been tested together.
Which firmware adds Stream ID or RTMPS?
Use the VITEC release notes for the installed branch rather than copying a version from a different Ace device. Record the reviewed firmware in the runbook and repeat the preflight after an upgrade.
Which UDP port and firewall direction are required?
They follow the selected caller/listener relationship. The caller initiates to the listener UDP port. Permit only the required path and verify the public address, security group, host firewall and any intermediate NAT.
What does VITEC handle and what does Callaba handle?
VITEC performs source acquisition and hardware encoding. Callaba starts at ingest and adds receiver telemetry, browser monitoring, recording, routing, playback and API-driven operations.
Move from device choice to a tested receiving path
Open the exact-model guide, validate one contribution feed in Callaba, then add recording, monitoring and downstream routes only after the ingest contract is stable.
