Haivision Pro460 SRT setup: multi-camera remote production with Callaba Gateway
More live video workflow notes and product updates.
Pro460 multi-camera bonded production plan
Terminate the bonded field operation before creating four Callaba SRT handoffs
The Haivision Pro460 is designed to deliver either four synchronized HD camera feeds or a single 4K/UHD source from the field. Its six integrated 5G modems and SST transport belong to the Pro460-to-StreamHub contribution layer. For a Callaba workflow, StreamHub receives that bonded operation and creates SRT IP outputs; Callaba then monitors, records, and routes those individual program feeds. Keeping that boundary visible is essential when four cameras must remain identifiable and production-ready.
The recommended multi-camera architecture
Connect and genlock the four intended HD sources as required by the production. Configure Pro460 multi-encoding and send the field contribution over SST to a licensed StreamHub using the network links selected for the event. In StreamHub, prove all four inputs. Create one named SRT output for each selected input and send each output as Caller to its own Callaba Listener and UDP port.
The Pro460 also offers an SRT Receiver destination type with Caller or Listener mode and an explicit Ethernet-port selection. That can be useful for a direct fixed-network test or a simpler single-feed design. It is not a substitute for SST when the requirement is six-modem cellular bonding, video return, intercom, or the complete StreamHub-controlled remote-production path.
The moving blocks show logical handoff direction. They do not visualize packet bonding, promise frame accuracy after every downstream operation, or report latency. Reduced-motion settings stop the animation.
Know which system owns each production feature
Haivision documents six integrated 5G modems, alternative 4G LTE, Ethernet and Wi-Fi 6 links, four frame-synchronized HD inputs, genlock, or one 4K/UHD source. It also documents video return, two-way intercom, IFB, and a Data Bridge for camera control and tally-related IP communication. Those features make the Pro460 a remote-production transmitter, not merely a four-channel generic SRT encoder.
| Production concern | Owning boundary | Evidence required |
|---|---|---|
| Camera lock and genlock | Sources and Pro460 input configuration. | All expected standards detected, genlock state qualified, and camera labels matched to physical inputs. |
| Cellular/IP aggregation | Pro460 SST transmitter and StreamHub receiver. | Expected network links participating, aggregate capacity under motion, and a controlled single-link removal. |
| SRT conversion/handoff | StreamHub IP Output to a Callaba SRT Server. | One output per assigned StreamHub input, matching roles, ports, latency, identity, and security settings. |
| Operator monitoring | Callaba Multiview after SRT ingest. | Four correctly labeled tiles with moving video and selected audio; no tile cross-assignment. |
| Recording and routing | The specifically configured Callaba modules after ingest. | A playable sample and destination proof for every feed that the production must preserve or deliver. |
| Return, intercom, and Data Bridge | Haivision Pro460/StreamHub remote-production system. | Separate talk/listen, return-display, camera-control, and tally tests; forward SRT health is not their pass condition. |
Phase 1: commission the Pro460 camera package
Choose quad-HD or 4K
Use multi-encoding mode for the four-HD-source production described here. Use single encoding for a one-source or 4K plan. Do not describe four HD plus 4K as simultaneous just because both modes appear in the product specification.
Name cameras by production role
Record source connector, camera label, live profile, codec, resolution, frame rate, bitrate, audio layout, and record profile. A copied profile must be reviewed for its input selection before it is started.
Prove synchronization where it matters
Check genlock and source timing with the production’s accepted instruments. A browser Multiview is valuable visual monitoring, but it is not a substitute for frame-accurate timing validation at the switching boundary.
Use H.265/HEVC or H.264/AVC according to the complete receiver and production chain. Haivision’s current Pro460 live-profile documentation lists codec, bitrate, audio, and transport-stream controls and notes additional conditions in multi-encoding mode. Record the installed firmware and use its own menu ranges; do not transplant a Pro360 profile or an older Pro460 limit into the show file.
Phase 2: establish the SST contribution and StreamHub input map
Create or select the intended StreamHub destination profile on the Pro460, with the StreamHub address, input assignment, credentials, and any approved encryption settings. Select the four live profiles for multi-encoding and start the transmission. Verify every camera appears on the correct StreamHub input before adding Callaba.
Observe all field links under ordinary load, then remove one connection at a time. Confirm which links are actually bonded, whether surviving aggregate capacity covers all active encodes, and whether picture continuity meets the event requirement. Bonding cannot create bandwidth that the remaining links do not have. Six installed modems also do not guarantee six useful, independent carriers at a particular venue.
If video return, intercom, or remote camera control is in scope, commission them now as separate tests. Haivision’s Data Bridge operates as an IP tunnel through the transmitter/receiver ecosystem and has documented mode constraints. Do not wait until the SRT output is complete to discover that camera control, tally, or talkback uses an untested network or destination.
Phase 3: create four StreamHub-to-Callaba SRT outputs
- Create and start four Callaba SRT Servers in Listener mode using the Callaba SRT receiving guide. Assign a unique name and reachable UDP port to each camera.
- Open those UDP ports in cloud security, host firewall, and intervening network policy. Keep the source-to-port table in the production runbook.
- In StreamHub, create the first SRT IP Output profile. Select Caller, enter the corresponding Callaba address and port, and match the approved latency and encryption contract.
- Assign camera input one to that output. Start it and confirm the correct image and audio appear in the expected Callaba session.
- Repeat for cameras two through four, changing output name, StreamHub input, UDP port, and any identity used for access or routing.
- Add four Callaba Multiview tiles in the same ordering used by the director. Make and play a short recording from each received input.
- Attach each feed only to its approved onward route. Validate the destination from the receiving end; a configured route is not delivery proof.
Acceptance test the production, not just the transport
- Identity: place a slate in front of one camera at a time and verify the matching Pro460 channel, StreamHub input, Callaba listener, Multiview tile, recorder, and route.
- Motion: run representative detail and movement across all cameras while watching aggregate contribution capacity and each SRT handoff.
- Audio: identify required channels with safe test material, then confirm mapping after StreamHub and in every selected Callaba output.
- Timing: measure synchronization at the production boundary that will switch or replay the cameras; record the method and tolerance.
- Link failure: interrupt each field connection independently, without changing the StreamHub-to-Callaba network, and capture the visible outcome.
- Handoff failure: interrupt one SRT output and confirm only its intended Callaba branch changes while the other camera sessions remain usable.
- Restart: stop and restore a live profile, the StreamHub output, and the Callaba listener in controlled tests so operators know which layer recovers automatically.
- Files: retrieve a recording for each source and inspect beginning, a high-motion section, audio, and the ending after a clean stop.
Troubleshoot the hop that lost evidence
One camera is absent everywhere
Check its physical input, detected standard, live-profile source, and multi-encoding assignment. If StreamHub never receives it, changing a Callaba port cannot help.
All cameras fail together
Inspect common power, aggregate network capacity, the Pro460 live state, and StreamHub reception. Correlate link participation and bitrate before reducing four profiles indiscriminately.
StreamHub is healthy; one Callaba feed is missing
Verify that camera’s StreamHub SRT output is enabled and references the right input. Compare its Caller destination, UDP port, firewall, and security contract with the matching listener only.
Two Callaba tiles are swapped
Trace the slate through StreamHub output assignments and listener names. Correct the map at the first crossed association; renaming the Multiview tiles alone leaves recordings and routes wrong.
Cuts or replay are misaligned
Return to camera/genlock state, encode mode, network delivery, decoder buffering, and the production switcher. Compare timestamps and objective measurements rather than estimating alignment from four browser tiles.
Video is good but intercom fails
Keep the forward contribution running while examining the Haivision return/intercom configuration. SRT delivery to Callaba is a separate success condition and should not be disrupted during diagnosis.
Continue from contribution into Callaba operations
Use the Callaba SRT Server product page to plan receiver monitoring and downstream branches. The Haivision workflow hub provides the family-level architecture context. After the four manual handoffs pass, the Callaba SRT Server API can automate reviewed server lifecycle work while the camera-to-port map remains explicit.
Official Haivision references
- Haivision Pro460 product page — six 5G modems, four synchronized HD or 4K/UHD contribution, genlock, return, intercom, and Data Bridge positioning.
- Current Pro460 documentation overview — current official quick start, user guide, and supported operation.
- Pro460 destination profiles — StreamHub and direct SRT Receiver configuration fields.
- Pro460 live profiles — single/multi encode settings, supported codec and transport controls, and documented mode notes.
- StreamHub SRT IP Output guide — official output creation and input-assignment sequence.
Rehearse the four-camera map on the deployment you will operate
Build the Callaba receiving side, prove each StreamHub output independently, and let the same Multiview labels follow through recordings and routes before the bonded field system is called ready.