Source handoff
List each venue or studio feed, who controls it, and the format the field system can supply. Keep camera control, intercom and production switching outside the scope unless those integrations have been reviewed.
REMOTE PRODUCTION CONTROL
Give distributed contribution a visible route to the production handoff
A remote workflow starts with a compatible contribution handoff from a field encoder, studio, NDI network, or browser participant. Callaba gives operators defined checkpoints for transport state and Multiview, then hands the approved programme to the production system, recording workflow, partner, or audience destination. It does not replace the upstream switcher, intercom, graphics, or the downstream delivery system.
CONTRIBUTION TO OUTPUT
Name the signal path and the operator checkpoint at each handoff
Separate contribution, production control, and distribution so a downstream destination never becomes the first place a failure is discovered.
- SOURCE
Accept the agreed contribution
Receive the SRT, RTMP, RTSP, NDI, or compatible browser source that the field team and production destination have verified.
- CHECK
Use an operator checkpoint
Inspect source state and live transport telemetry, then confirm the picture in Multiview before the production team takes the handoff.
- PATH
Prepare the production path
Bridge the reviewed NDI workflow or configure primary and backup SRT routes; validate recovery behavior with the actual source, buffers, network, and destination.
- HANDOFF
Pass the approved programme onward
Hand the approved programme to the external production system, recording workflow, browser playback, platform, partner, or CDN that owns the next job.
SCOPING THE SHOW
Start with the handoffs your remote team has to own
A remote-production plan becomes concrete when everyone can name three things: where the programme feed originates, what the remote operator must be able to see, and where the approved output goes. Bring those answers to the review, and map the smallest workflow that can be tested with the actual contribution and destination.
Operator decision
Define what the remote operator watches, which visible condition calls for action, and who may approve a route change. A useful plan names the decision as clearly as the signal path.
Programme destination
Name production, recording and audience handoffs separately. That prevents a healthy preview from being mistaken for an accepted end-to-end programme path.
Operating boundaryThe review produces a test plan for the deployed encoders, buffers, network and destinations; it is not a latency or availability guarantee.
FAILOVER ACCEPTANCE
Prove the recovery path before the programme depends on it
Turn source redundancy into an operating procedure. Run one controlled acceptance sequence with the real field encoder, Callaba deployment, production destination, buffers, and network.
- 01Inputs
Inventory the path
List every primary and backup contribution URL, the Callaba server, and the downstream production destination.
- 02Bitrate + RTT
Establish a live baseline
Run the primary source long enough to observe its normal bitrate, RTT, buffers, and loss counters in the operator experience.
- 03Detect
Interrupt the primary
Stop or isolate the primary source during a controlled window and record when the disconnect becomes visible.
- 04Recover
Confirm recovery
Verify that configured reconnect and routing-host fallback reaches the prepared backup, then record destination recovery time.
REMOTE OPERATIONS
One control layer for contribution and production teams
The same deployment can support a small remote show or a repeatable contribution workflow. Prove the operator runbook in the UI before automating the reviewed configuration through the API.
Transport visibility
See whether contribution is arriving, inspect current SRT telemetry, and use recent RTMP runtime context where available.
NDI network control in the UI
Manage NDI discovery, network addresses, machine identity, configuration, and adapters without relying on terminal-only operations.
Prepared recovery
Keep primary and backup routes visible, then validate reconnect and fallback behavior before production.
WHERE THE WORKFLOW FITS
Use the same operating model across real production scenarios
Distributed event production
Receive field contribution and give a central team a monitored path to programme output.
Cloud production bridge
Connect the reviewed NDI workflow with public-network contribution, then hand the programme to the production and delivery systems that own those jobs.
Remote studios and guests
Combine encoder, software, and browser sources in a controlled production environment.
PRODUCT LAYER
Choose the Callaba products behind the workflow
Start with the modules the operators need. Add the remaining capabilities as the production path, audience, and retention plan become clear.
SRT Server
Public-network contribution with transport monitoring and access controls.
Cloud NDI
Discovery, configuration, adapters, and network control from the Callaba UI.
Callaba Multiview
A shared operations view for live sources and outputs.
Live Video Failover
Configured primary and backup routes with reconnect and fallback after a disconnect.
IMPLEMENTATION GUIDE
Read the remote production guideConnect SRT, NDI, Multiview, and recovery in a REMI workflow
Map field contribution, the operator checkpoint, production handoff, recording, and delivery ownership before automating a repeatable step.
OPTIONAL AUTOMATION LAYER
Read the API workflowManage a proven remote contribution path through the API
Provision and manage the reviewed SRT server configuration, then connect the accepted source path to downstream production modules. Use the authenticated operator UI for live transport telemetry and the documented REST API for configuration and current active state.
WORKFLOW QUESTIONS
Remote production FAQ
Can Callaba support a REMI or distributed production workflow?
Yes. A reviewed workflow can accept compatible SRT, RTMP, RTSP, NDI, and browser-oriented contribution, give operators a transport and Multiview checkpoint, and hand the approved programme to the next production, recording, or delivery job. The exact path depends on the field encoder, network, and destination.
Can operators see SRT transport health?
Yes. The authenticated Callaba operator UI exposes live receive and send rate, bandwidth, RTT, buffer, packet, and loss counters. For automation, use the documented REST configuration and current active-state methods; persistent SRT transport history is not part of the public API contract.
Can NDI networking be configured without using a terminal?
Yes. Callaba provides NDI discovery, machine and network settings, configuration import or editing, and adapter controls through the UI.
Can remote production run self-hosted?
Yes. Teams can deploy Callaba on Linux infrastructure in the required network or use a cloud deployment.
Does failover guarantee a hitless transition?
No universal hitless guarantee is claimed. Recovery behavior should be validated with the real source, destination, latency, buffer, and network conditions.