Find an Event and Add an LL-TTS Language Source

Add a TTS node, select an authorized event and language, and verify live translated audio.

Written By 4ALL.LIVE

Last updated 1 day ago

Add a Signal TTS input for an authorized event and target language, then verify that live translated audio reaches the graph.

Best for: operators routing one server-generated LL-TTS language from a live 4ALL event into a Signal pipeline.

Add the TTS source

  1. With the pipeline stopped, add a TTS input.
  2. Refresh events.
  3. Select the authorized event owned by the currently selected organization and team.
  4. Select a server-advertised target language.
  5. Connect the TTS node to a meter, processing chain, or output.
  6. Start the pipeline.
  7. Wait for the node to show Streaming, then confirm translated audio on the local meter and output.

One TTS node selects one event and one advertised language. The received stream is mono 24 kHz PCM. Use a distinct node and output path for each language that must be routed independently.

Event and language selection

Events are scoped to the authorized organization and team. An event can be absent because it is offline, unavailable, owned by another workspace, or not currently advertised to Signal. If a saved event is no longer available, Signal reports that condition rather than silently selecting a different event.

If a previously selected language is no longer advertised, the language selection falls back to the advertised default, then English if it is offered, then the first valid advertised language. Always verify the resulting language before opening the route to listeners.

Important: Signal receives LL-TTS generated by 4ALL servers. It does not generate speech locally, and its TTS node is not a floor-audio pass-through.

Verify live audio

  • The selected event and language match the production plan.
  • The Live Setup producer browser is actively publishing while recording is active and not paused or merely testing.
  • The node reaches Streaming.
  • The local meter moves with translated speech and the dedicated output carries the correct language.
  • The route survives a controlled stop and restart while off air.

Troubleshoot

  • No events: confirm authorization, organization and team selection, network access, and event availability.
  • Saved event no longer available: stop, refresh, and select the authorized live event rather than assuming the old assignment.
  • Wrong language: inspect the advertised list and any fallback selection, then choose and listen to the intended language.
  • Waiting for audio: confirm the designated producer holds the lease, recording is active, TTS or LL-TTS is enabled, and credentials, entitlement, wallet, caps, and network are valid.
  • Retryable error: allow the node's retry and backoff while preparing the approved fallback; do not repeatedly rebuild the graph on air.

Capacity and licensing boundary

Multiple identical event and language nodes in one Signal process can share one receive session. Do not claim that every language requires its own Signal license. A 4ALL team member must validate workstation, device-license, and physical I/O capacity.