One entry point
Share or embed one grouped viewer URL instead of distributing a separate link for every language.
Multilingual live streaming
One SRT contribution. Up to eight language tracks. One viewer link.
Callaba receives a multitrack SRT programme. The operator listens to and names each audio track, creates and verifies one Web Player per language, then combines those players in one viewer-facing LANGUAGE_LIST group.
SRT contribution liveSRT · MPEG-TS
The real product path
Keep one programme together until the viewer chooses a language
A single public URL does not mean one hidden black box. The source, selected tracks, player variants, and group remain separate objects that an operator can verify.
- 01
Receive the SRT programme
Send one MPEG-TS contribution with the produced audio tracks to a Callaba SRT Server.
- 02
Identify every track
Open stream statistics, listen to each audio track, and give it a language or commentary name.
- 03
Build the language variants
Create one Web Player per audience language and use SELECT_AUDIO_TRACK to map the intended source track.
- 04
Publish one language selector
Add the verified players to a LANGUAGE_LIST group, choose the default, and test every switch in a clean browser.
What the viewer gets
A language choice that does not look like an operations diagram
The audience opens one branded page. The selected language is obvious, the other approved variants remain available, and shared access rules apply to the group instead of being explained in an email.
Named language choices
Use audience-facing labels and select which language opens first.
Shared event controls
Apply group-level branding, event information, password access, viewer credentials, or supported pay-per-view settings.
callaba://live/eventLive
Technical specification
Multilingual live streaming contract
These are the capabilities an operator can verify in the current Callaba workflow. The evidence column names the control or API object that proves each claim.
| Capability | Current contract | How to verify it |
|---|---|---|
| Contribution | One SRT/MPEG-TS programme with up to 8 produced audio tracks. | Use an encoder or Generate Test Video (with 8 audio tracks), then confirm the stream on the SRT Server. |
| Track inspection | Listen to discovered audio tracks and assign operator-readable names. | Open SRT Server statistics and use the audio-track preview and naming controls. |
| Track selection | Select one source audio track, with optional channel handling, for each output process. | Set Modify Audio Tracks to SELECT_AUDIO_TRACK; the runtime maps the chosen audio index. |
| Browser playback | Create a live Web Player for every approved language or commentary variant. | Create and test each player independently before adding it to a group. |
| Unified viewer | LANGUAGE_LIST Web Player Group with named choices and one default selection. | Create the group, add ordered players, select the default, and open the public group URL. |
| Access and presentation | Shared authorization, supported pay-per-view settings, logo, cover, event date, timezone, and support contact. | Configure the group-level viewer settings and retest with a signed-out browser session. |
| Automation | REST APIs for Web Players and Web Player Groups after the UI workflow is proven. | Use /api/vod/* and /api/vod-group/*; start from the reviewed create examples. |
Where this fits
One pattern, several real audience jobs
International conferences
Keep the main programme and interpreter mixes aligned while viewers choose their language from one page.
Sports commentary
Publish home, away, neutral, or regional commentary variants from one multitrack contribution.
Corporate town halls
Give regional teams a controlled viewer surface with a default language and shared access policy.
Accessible live events
Offer a produced audio-description or alternative-audio variant beside the main programme.
The modules behind the solution
Use the product surface first; automate only after every language works
SRT Server owns ingest and track inspection. Web Players turn approved tracks into browser variants, and a Web Player Group brings those variants together for the audience.
01
Callaba SRT Server
Receive the multitrack programme, inspect signal state, preview audio, and name the tracks.
→02Web Players and groups
Package each selected language for browser playback and combine the verified variants in one viewer page.
→03Restreaming
Send a selected commentary or language track to a platform or partner destination when the job is distribution, not browser choice.
→04Video Calls
Bring remote speakers or interpreters into the production when needed; interpretation quality and the finished language mix remain a production responsibility.
→Operator runbook
Read the Web Player Groups guide Build and test the viewer from the same controls operators use
The Web Player Groups guide covers the language-list object, shared viewer policy, default selection, and the checks to run before sharing the public URL.
Questions before going live
Multilingual live streaming FAQ
Can one SRT stream contain all language tracks?
Yes. The reviewed Callaba workflow accepts one MPEG-TS programme over SRT with multiple produced audio tracks. The documented test source contains eight tracks.
Do viewers receive eight separate links?
No. Operators create and verify the required player variants, then publish them through one LANGUAGE_LIST group URL with clear audience-facing labels.
Does Callaba translate the event automatically?
No. Callaba does not create translations, interpretation, dubbing, or audio description. Those tracks must be produced upstream; Callaba carries and presents them.
Can one language also be sent to YouTube or another destination?
Yes. A Restreaming job can select the required source audio track and send that version to an approved platform or custom destination.
Can the grouped viewer be private or paid?
The current Web Player Group object supports shared authorization and supported pay-per-view settings alongside branding and event metadata. Test the exact access path before the event.
Verify all eight tracks before the event
Start with one multitrack SRT source and one clean browser
Name every track, verify every player independently, then test the grouped viewer as a signed-out audience member. That sequence catches the failures a polished landing page cannot.