AJA SRT Gateway Workflows with Callaba
More live video workflow notes and product updates.
AJA workflow selector
Choose compact contribution or multi-channel processing before you configure Callaba
HELO Plus and BRIDGE LIVE solve different source-side jobs. HELO Plus is the compact choice around a single-program streaming and recording operation. BRIDGE LIVE belongs in a denser encode, decode and transcoding design where channel count, codecs, I/O and automation must be planned together.
The Callaba role begins at the network handoff: receive the configured output, prove transport and decoded media, then attach Multiview, recording or routing. This hub selects the AJA path; the linked device guides own the actual fields.
Pick the lane that matches the production job
HELO Plus
Use for a compact single-program operation where the local source and local recording need their own proof alongside the network output.
- Verify input and audio before transport.
- Prove local recording separately from SRT.
- Match the installed software to the current manual.
BRIDGE LIVE
Use when several simultaneous processing jobs, codec combinations and network outputs form one capacity envelope. A single successful channel does not validate the planned system.
- List the complete channel and codec mix.
- Confirm physical I/O and every output role.
- Test automation only after the manual path passes.
Do not silently turn an RTMPS workflow into SRT
The AJA HELO RTMPS material is a separate protocol path. If that is the verified output of the installed product and workflow, keep its page and Callaba endpoint labelled RTMPS. Shared goals such as live delivery do not justify copying SRT modes, UDP ports or recovery assumptions into it.
Open the HELO RTMPS workflow. For HELO Plus or BRIDGE LIVE SRT, continue with their dedicated guides above.
Validate BRIDGE LIVE at the intended load
Before rehearsal, write down the simultaneous channel count, direction, codec, raster, audio mapping and downstream destination for every job. Then run that complete mix rather than extrapolating from one channel. The following visual is a capacity reminder, not a claim about a fixed channel limit:
encode
decode
transcode
route
Watch the AJA system and every matching Callaba input at the same time. Stable receiver bitrate with wrong audio or a missing channel is still a failed acceptance test.
Use one sign-off sequence for either AJA lane
- Record exact hardware, installed software and the selected protocol.
- Confirm source lock, raster, frame rate and the full audio map on the AJA side.
- Create one matching Callaba endpoint from actual network reachability.
- Compare SRT mode, address, UDP port, Stream ID, latency and encryption where used.
- Prove sustained transport, decoded motion and audio in Callaba.
- Make and play a short recording rather than trusting a green state alone.
- Interrupt the source and network output separately; document recovery.
- For BRIDGE LIVE, repeat at the complete planned load.
Review updates and security before the event
Redact credentials and site addresses from exported configurations. Assign an operator for the AJA source-side system and another for the Callaba handoff so route authority is clear during an incident.
Use current AJA references
Confirm capabilities with the official BRIDGE LIVE page, HELO Plus page, and the manual and release notes for the installed version. Review AJA security advisories and confirm whether a notice applies to the precise product and software in service.
