YoloLiv YoloBox SRT and RTMPS workflows with Callaba
More live video workflow notes and product updates.
YoloBox transport decision
Choose direct SRT or RTMP(S) from the installed YoloBox—not from the family name
YoloBox Extreme, Ultra and Pro can all send a switched program into a Callaba workflow, but they do not expose one interchangeable output menu. Extreme’s current specification lists SRT among both network inputs and streaming outputs. Ultra has its own direct-SRT workflow. Public Pro material confirms SRT input support, which is not proof of native SRT program output.
The safe production plan is model first, transport second: use the output the unit actually documents, receive it in Callaba, and create onward SRT only after the program has been accepted.
Follow the branch that matches the output menu
Branch A: direct SRT
Use this branch only when the current model specification, installed firmware and visible output controls support the required SRT direction. Record Caller or Listener, host, UDP port, latency, Stream ID and encryption.
Branch B: RTMP or RTMPS handoff
Send the Pro program over its verified RTMP(S) output. First prove that contribution in Callaba; then create a separate SRT route for the next system. The conversion boundary remains visible and testable.
Use the model selector before copying any fields
YoloBox Extreme
Use Extreme when the high-input portable switcher and its current SRT output match the event. Confirm output codec, raster, frame rate and role on the installed firmware; RTMP(S) remains a deliberate fallback.
Extreme setup guideYoloBox Ultra
Use Ultra for a compact production where the current SRT workflow is visible on the unit. If the destination is absent, update through a planned process or use the confirmed RTMP(S) route instead of improvising another model’s fields.
Ultra setup guideYoloBox Pro
Treat Pro as an RTMP or RTMPS program source unless official model-specific documentation and the installed firmware explicitly prove native SRT output. SRT input support alone does not cross that evidence threshold.
Pro setup guideSeparate switching, contribution and downstream routing
Camera inputs, switching, local graphics, program audio, local recording and the first encode.
One documented SRT or RTMP(S) output, its URL or role, security values and real venue network.
Receiver-side telemetry, decoded preview, Multiview, recording, playback and onward routes.
This boundary prevents an attractive local program preview from being mistaken for remote delivery. Check the YoloBox program locally, then check the independent Callaba result. If one is good and the other is not, the investigation stays focused.
Treat Network Bonding as its own paid connectivity layer
YoloLiv Network Bonding can combine available connections for a field workflow, subject to the selected model, plan and region. It is not SRT encryption and it is not the same thing as application-level failover between two production feeds. Document where bonding terminates and which protocol reaches Callaba.
Test Ethernet, Wi-Fi, cellular or the bonded combination that will actually be used. Source switching and local recording also consume device resources, so rehearse the full production workload rather than an idle color bar.
Run this portable-production acceptance test
- Identify the exact YoloBox model, firmware and enabled services; capture the available output menu without credentials.
- Choose one primary transport and one explicit fallback. Do not silently switch from SRT to RTMPS in documentation or during troubleshooting.
- Create the matching Callaba endpoint and align host, port or URL, role, security and media profile.
- Switch every intended source while monitoring sustained bitrate, decoded motion, program audio and reconnect behavior on the real venue network.
- Record locally and in Callaba, play back both intended evidence layers, and test one downstream route before adding multistream destinations.
Place the Callaba receiver where the team can operate it
Use AWS when a portable contributor needs a reachable public endpoint near the production region. Use self-hosted Callaba when the receive point belongs inside a facility or private network. The same rule applies in both cases: accept one program first, then add recording, Multiview, playback or SRT distribution.
Official YoloLiv references
Check YoloLiv’s current YoloBox Extreme specification, YoloBox Ultra specification, YoloBox Pro specification, and Network Bonding description. Recheck the installed firmware before an event because input and output support can change independently across models.
