LiveU Solo, Solo Pro, and Studio SRT handoffs to Callaba
More live video workflow notes and product updates.
Bonded contribution service decision hub
LiveU SRT is a service-assisted contribution path, not simply a socket exposed directly by the field unit. Official Solo guidance routes SRT through the LRT cloud, supports caller mode and requires the relevant subscription, firmware and zone. LiveU Studio has a separate publishing-point workflow that can send a produced program to a reachable SRT server.
Written by Iurii Pakholkov, founder of Callaba. Materially reviewed on July 17, 2026 against the official sources listed below.
Choose the correct LiveU Solo, Solo Pro, and Studio SRT handoffs to Callaba
| Path | Operational role | When to choose it |
|---|---|---|
| LiveU Solo | Bonded field contribution converted to SRT caller output through the LRT cloud. | Choose for an existing Solo on supported firmware with the required LRT subscription and zone. |
| LiveU Solo Pro | Bonded field contribution with the documented SRT caller path and optional HEVC selection. | Choose when Solo Pro input, connectivity and end-to-end HEVC compatibility match the event. |
| LiveU Studio output | A produced Studio program publishes to a reachable Callaba SRT endpoint. | Choose when Studio owns switching and audio buses and Callaba owns receiving and later outputs. |
Keep the source, handoff and Callaba roles explicit
Source-side responsibility
The Solo unit owns camera input and field encoding while LiveU services own bonding, debonding and the configured zone. Studio owns production switching and selected output buses in its workflow.
Transport handoff
The handoff records account entitlement, unit and firmware, zone, destination type, hostname, port, Stream ID, passphrase, latency, codec and who can operate the cloud service.
Callaba responsibility
Callaba owns the reachable SRT listener, receiver telemetry, Multiview, recording, routing, playback and downstream automation after the LiveU-managed path emits the feed.
Validate the LiveU service boundary, not only the field encoder
- 1. Record the unit model, firmware, LRT subscription and selected zone. A Solo menu alone does not prove that the account can create the required SRT destination.
- 2. Choose raw field contribution through Solo or produced output through Studio. Name that ownership boundary so operators know where switching, audio mixing and recovery occur.
- 3. Create a reachable Callaba listener, then enter hostname, port, Stream ID, passphrase and latency in the LiveU destination. Follow Studio guidance and omit protocol prefixes from its hostname field.
- 4. Use H.264 for broad compatibility or Solo Pro HEVC only after the complete route is verified. Test the same cellular, Ethernet, Wi-Fi or bonded connectivity planned for the event.
- 5. Confirm the feed in LiveU and Callaba, interrupt one uplink, inspect recovery, make a recording and exercise the final route. Document which support team owns each side of an incident.
After preflight, use the SRT Gateway hub for architecture choices, the SRT Server guide for receiver concepts, Multiview for browser operations, and the SRT API documentation for automation. These shared resources do not replace the model-specific guide linked in the decision table.
Official references reviewed
Capabilities and menu fields can change with hardware revisions, firmware and account entitlements. Recheck the exact model before a production event.
- LiveU Solo SRT support note — Official caller-only, firmware, LRT subscription, zone and passphrase boundary.
- LiveU Studio SRT output — Official publishing-point fields, audio routing, validation and troubleshooting.
- LiveU Solo Pro to Studio over SRT — Official destination setup, latency guidance and Solo Pro codec distinction.
Frequently asked questions
Does LiveU Solo send SRT without an LRT subscription?
Official LiveU guidance says the Solo SRT feature uses the LRT cloud and requires an LRT subscription. Confirm entitlement and zone before treating SRT as an available production output.
Which SRT mode does LiveU Solo use?
The documented Solo destination is SRT caller. Create a reachable Callaba listener and align hostname, port, Stream ID, passphrase and latency rather than reversing the relationship.
Can every Solo use HEVC over SRT?
LiveU documents the codec choice between H.264 and HEVC for Solo Pro. Do not extend that statement to every original Solo; verify the unit, zone and downstream decoders.
When should LiveU Studio send the feed instead of Solo?
Use Studio output when switching, graphics or audio-bus selection in Studio defines the program that Callaba should receive. Use Solo when the field unit contribution itself is the intended boundary.
What does Callaba add after LiveU bonding?
Callaba adds independent receiver telemetry, browser Multiview, recording, protocol routes, playback and automation. It does not replace the LiveU subscription, zone, bonding service or field-unit controls.
Move from device choice to a tested receiving path
Open the exact-model guide, validate one contribution feed in Callaba, then add recording, monitoring and downstream routes only after the ingest contract is stable.
