PTZOptics SRT Gateway Workflows with Callaba
More live video workflow notes and product updates.
PTZOptics camera selection
Choose the camera by the room and shot, then prove one SRT path end to end
PTZOptics uses SRT across several current camera families, but the cameras are not interchangeable. A Move 4K chosen for tracking a stage, a Link 4K integrated into a mixed AV system, a Move SE used for an HD room, and a Studio Pro placed close to a presenter lead to different format, control and cabling decisions.
Callaba begins after the camera creates its encoded network output. It supplies the matching SRT peer, receiver-side statistics, decoded preview, Multiview, recording and controlled downstream routes.
Use this camera matrix before opening a setup guide
Write the connection settings down before touching the firewall
For a venue-to-cloud test, camera as Caller and Callaba as Listener is usually the simplest starting relationship because the camera initiates outbound UDP. Listener mode is valid only when Callaba can deliberately reach the camera-side address and port. Record the choice rather than changing roles during an incident.
Keep PTZ control and SRT media as two separate checks
A camera may pan and recall presets while its media session is down. The reverse is also possible: Callaba may receive a healthy picture while the operator has lost camera control. Give the control network and the contribution path separate owners, monitoring and failure notes. This distinction is especially important when several cameras share a switch or a constrained venue uplink.
Use stable operational names such as Stage-left Move 4K rather than identifying a source only by port number. A useful name lets the Multiview operator, network engineer and camera operator discuss the same source without exposing public credentials.
Run this acceptance test with the real room and network
- Record the full model, lens variant and firmware. Confirm that the SRT controls described in the selected guide are visible on that unit.
- Prove picture composition, PTZ presets and every required audio input locally before diagnosing transport.
- Create the matching Callaba peer, open only the required UDP path, and align role, port, Stream ID, encryption and latency at both ends.
- Operate the camera through representative movement while watching incoming bitrate, RTT, packet loss, decoded motion and audio in Callaba.
- Stop and restore the camera output. Measure reconnection, make a short recording, play it back, and only then add Multiview destinations, routing or failover.
Choose the Callaba receive point from network ownership
Use an AWS deployment when remote cameras need a public receiving point near the production region. Use self-hosted Callaba when the receive server belongs inside a facility or private network. The operator sequence stays the same in either case: receive one named feed, inspect transport and media, record evidence, then extend the accepted input.
Official PTZOptics references
Check the current Move 4K product and specifications, Gen 3 web UI documentation, and Horizon audio and video settings. Those resources identify the supported interface families; the installed model and firmware remain the production authority.
