Haivision Makito X4 Rugged SRT setup: field contribution with Callaba Gateway
More live video workflow notes and product updates.
Makito X4 Rugged multi-input mission workflow
Give every sensor a named path from connector to Callaba destination
A four-input rugged encoder rewards disciplined mapping. The Haivision Makito X4 Rugged can ingest multiple digital or analog sources, encode HEVC or H.264, associate KLV or CoT metadata, and originate SRT. The safest Callaba design does not call the appliance “camera one” and hide everything behind it. It records which physical source drives which encoder, transport stream, SRT identity, Callaba listener, Multiview tile, recording, and onward route.
Lead with one-to-one source ownership
For an initial quad-HD mission build, create a distinct logical chain for each required input. A practical pattern is Makito SRT Caller to Callaba Listener, with a unique UDP port and source name per feed. Prove input A all the way through monitoring and recording before cloning a profile for B, C, or D. That sequence prevents a crossed cable, reused Stream ID, or copied encoder association from looking like network loss.
The product also supports a 4K/UHD operating case. Treat quad-HD and 4K as different input plans, not simultaneous promises. Confirm the installed hardware, connector drawing, firmware, licenses, selected input personality, and supported signal formats against Haivision’s current documentation before cabling the platform.
Names are examples, not prescribed mission labels. The animated bridges show configuration association, not measured timing or an automatic matrix. Reduced-motion preference disables the pulses.
Understand what is specific to the Rugged X4
Haivision documents four physical BNC video inputs in the compact appliance: input one can accept up to 12G-SDI or composite video, while inputs two through four can accept up to 3G-SDI or composite video. The unit has eight encoding cores and supports multi-HD or a single 4K/UHD input workflow, HEVC and H.264, KLV and CoT metadata, analog audio, and two Ethernet ports. These are flexible alternatives on four connectors, not eight separate video inputs.
| Layer | Record for every feed | Failure caught early |
|---|---|---|
| Physical input | Connector, digital or composite source, expected format, source owner, and whether the platform is using multi-HD or 4K operation. | A valid picture on the wrong BNC, unsupported format, or an assumed connector combination. |
| Encode | Video encoder name, input association, HEVC/H.264 choice, resolution, frame rate, rate policy, and audio encoder. | A copied profile still pointing to another sensor or a downstream decoder rejecting the codec. |
| Metadata | SDI, network, or Rugged serial source; KLV/CoT format; filtering; decimation; and intended video association. | Correct imagery with stale, crossed, or missing geospatial context. |
| SRT output | Caller/Listener role, interface, address, UDP port, Stream ID, latency, security contract, and redundancy state. | Two feeds competing for one identity, a blocked port, or traffic leaving on the wrong link. |
| Callaba continuation | Listener name, Multiview tile, recorder, route, downstream owner, and an acceptance sample. | A healthy ingest feeding the wrong monitor, archive, or distribution destination. |
Build the first channel from the Callaba listener backward
Create one listener using the Callaba SRT Server procedure. Assign a documented UDP port and start the service. Open the same port in every receiving firewall or cloud rule. If Stream ID or encryption will be enforced, define the approved value and secret-management process before anyone enters settings on the encoder.
On the Makito X4 Rugged, confirm the source on its intended input, then create the video and audio encoders for that source. Configure the metadata input only if the channel needs it. In Outputs, add a TS over SRT stream, attach the correct content sources, select Caller, and enter the Callaba address and port. Match latency, Stream ID, encryption, and passphrase. Start the output and keep the remaining channels stopped until Callaba shows stable transport and usable media.
Assign the received feed to a clearly labeled Multiview tile, create a short recording, and play it. If metadata is mission-critical, route or capture a sample for an analyzer or exploitation system that understands the required KLV carriage. Only then duplicate the pattern for the next input, changing every identifier and source association that must remain unique.
Scale to four feeds without multiplying ambiguity
Use a deterministic naming scheme
Include platform, sensor role, and path in names that operators can read under pressure. A listener called “input-3” becomes dangerous after cabling changes; a label tied to the mission map remains reviewable.
Budget the aggregate, not one encode
Add the actual video, audio, metadata, and recovery overhead for all active outputs. Test on the constrained operational link. Four individually reasonable profiles can still exceed shared capacity.
Separate clock proof from picture proof
Set and verify the time source across the workflow so logs can be correlated. Haivision’s multi-channel synchronization feature has specific encoder-and-decoder requirements; a Callaba Multiview layout is an operator view, not a claim of frame-accurate output synchronization.
Preserve a one-channel baseline
Keep an approved minimal profile available. When the full mission set fails, it lets the team determine whether the issue is common infrastructure or the resource load and mapping introduced by additional feeds.
Engineer dual-network operation as a real failure-domain test
The Rugged X4 has dual network interfaces, and Haivision describes load balancing, network redundancy, and hitless-failover uses. The exact behavior depends on the configured output and compatible receiving design. A normal pair of independent SRT outputs is not automatically the same as SRT path redundancy, and two interface addresses are not proof that traffic uses independent networks.
Begin with the primary direct SRT path. If the approved receiver combination supports Haivision’s SRT redundancy configuration, add the second path and observe statistics for both. Otherwise, build separately named primary and alternate feeds that the Callaba operator can distinguish and switch or route by the documented procedure. Pull each physical link in turn. Record whether the session stays established, whether decoded video remains continuous, and what happens to recording and onward routes.
Operational acceptance is a four-row test, not one green light
- Source isolation: cover or change one sensor at a time and verify only its expected Makito preview, Callaba tile, and recording change.
- Audio identity: place a distinct test tone or spoken identifier on each required audio path and confirm the correct channel after ingest.
- Metadata identity: validate required KLV/CoT fields with a suitable decoder; do not treat a visible overlay as proof of the underlying elementary stream.
- Capacity: run all intended encodes with representative motion while recording aggregate sender and receiver rates.
- Restart: reboot or restart outputs in the approved sequence and confirm names, port assignments, and downstream bindings return correctly.
- Path loss: remove each network interface without touching the other and document continuity or the required operator response.
- Archive: play a segment from every Callaba recording, checking beginning, middle, end, audio, and source identity.
- Route: prove each destination receives only the authorized feed and that stopping one route does not disturb another.
Troubleshoot by comparing rows in the source map
One tile repeats another sensor
Inspect the Makito output’s video-encoder association before changing ports. Then compare Stream IDs and Callaba listener-to-tile bindings. Reused labels often hide a copied content selection.
All feeds degrade at once
Look for a shared uplink, switch, power source, aggregate bitrate ceiling, or receiver resource limit. Simultaneous impairment across four healthy inputs points to common infrastructure more often than four sensor faults.
Only composite video is absent
Confirm the physical input supports the intended analog configuration and that the current input plan permits it. Check the installed connector documentation instead of applying the SDI signal assumptions.
SRT connects but a feed is black
Confirm input lock and encoder state, then verify the correct encoder is attached to that output. A successful SRT handshake proves peer negotiation, not a valid sensor image.
Clocks or cuts look misaligned
Check source timing, NTP, genlock-related workflow requirements, encode settings, network variation, and downstream buffering. Multiview is useful observation, but use the production synchronization measurement expected by the consuming system.
Recording contains the wrong mission feed
Preserve the incoming sessions while checking the Callaba source-to-recorder mapping. Rename ambiguous objects, capture a new short sample, and verify it before deleting or changing any operational evidence.
Connect transport to the rest of the Callaba operation
Review the Callaba SRT Server capabilities for connection monitoring and downstream options, and use the Haivision SRT integration hub to keep this Rugged procedure distinct from other Makito models. After the four source mappings are proven manually, the SRT Server API reference can support repeatable provisioning. Automation should create the reviewed map; it should not invent port or sensor ownership.
Official Haivision references
- Makito X4 Rugged product page — rugged form, multi-input options, encoding cores, codecs, metadata, and network interfaces.
- Makito X4 Rugged specifications — current four-input connector capabilities, network interfaces, audio, and operating formats.
- Makito X4 stream settings — SRT connection, security, path, latency, content-association, and output controls.
- Makito X4 metadata capture — input association, KLV/CoT network sources, and Rugged serial controls.
- Makito multi-channel synchronization guidance — scope and requirements for frame-aware encoder/decoder workflows.
Put the source map where operators can prove it
Choose a Callaba deployment, commission each sensor independently, and use the live operator surface to confirm that transport, video, audio, metadata evidence, recording, and routing agree.