adorable-petabyte-73906
12/31/2025, 2:37 PMtall-airline-16756
12/31/2025, 2:37 PMtall-airline-16756
12/31/2025, 2:37 PMrime/arcana or cartesia/…)?
• Are you using LiveKit’s inference TTS (inference.TTS()), a provider plugin (e.g., rime.TTS(), elevenlabs.TTS()), or a realtime model that handles audio?
• After the change, is a TTS provider configured and initialized for that agent? (If TTS wasn’t set, text chat can work while voice won’t.)
• Do you see any errors or warnings in server or client logs when attempting to play audio?
Answering these will let me give step‑by‑step fixes (or a specific config snippet) to restore voice.
Sources: Rime TTS | LiveKit docs | Agents and handoffs | LiveKit docs | Cartesia TTS | LiveKit docs | Streamline Troubleshooting with Agent Observability | OpenAI Realtime API plugin guide | LiveKit docsadorable-petabyte-73906
12/31/2025, 2:37 PMtall-airline-16756
12/31/2025, 2:38 PMllm= and tts=). Wrap it in triple backticks if possible.
• Any error messages in server or client logs when the agent attempts to speak?
If you prefer, here’s a sample of how to explicitly set Azure TTS alongside an Azure LLM:
session = AgentSession(
llm=openai.LLM.with_azure(...), # your Azure LLM config
tts=openai.TTS.with_azure(voice="ash"), # explicit Azure TTS config
# ... stt, vad, etc.
)
Send the snippet and any errors and I’ll provide the exact code or config fix.
Sources: Realtime model plugins | LiveKit Docs | Azure OpenAI TTS plugin guide | LiveKit docs | Azure Speech TTS plugin guide | LiveKit docsadorable-petabyte-73906
12/31/2025, 2:38 PMtall-airline-16756
12/31/2025, 2:39 PMAgentSession (or agent init) lines for stt=, llm=, and tts= (wrap in triple backticks).
• Any error messages or warnings from server or client logs when you trigger voice.
• Whether you’re using a realtime LLM or a request/response LLM (Azure realtime vs Azure standard).
• Which TTS provider (Azure TTS, OpenAI TTS, etc.) and voice name you expect to use.
Quick checks you can run now:
• Confirm tts= is explicitly set in the session after switching to Azure LLM — switching LLM does not auto-enable TTS.
• Look for TTS initialization or synthesis errors in logs (auth, quota, or codec errors).
• If using a realtime model, verify it allows external TTS in your pipeline (some realtime setups handle audio differently).
Send the code and any logs and I’ll give the exact config or fix.adorable-petabyte-73906
12/31/2025, 2:39 PMtall-airline-16756
12/31/2025, 2:40 PMAgentSession (or agent init) lines for stt=, llm=, and tts= (wrap in triple backticks).
• Whether your Azure LLM is configured in realtime mode or standard request/response.
• Do you see the STT transcript appear anywhere (client console, server logs, or agent logs)? If yes, paste one example transcript.
• Any VAD or silence/utterance settings you use (e.g., vad, stop_on_silence, timeouts).
• The sequence you use to trigger the pipeline (push-to-talk vs continuous), and whether the LLM returns text when you call it directly in text mode using the same inputs.
Quick checks you can run now while you gather that:
• Confirm STT transcripts are reaching the process that forwards to the LLM (look for the transcript string right before the LLM call).
• If possible, call the LLM directly with a sample transcript (same text STT produced) to confirm LLM responds in voice mode.
• Check for any conditional logic that only forwards transcripts to LLM for chat mode (e.g., a flag that distinguishes text chat vs voice pipeline).
Send the small code snippets and one transcript sample and I’ll give the exact lines to fix (or a minimal repro to run).