https://livekit.io logo
Join Slack
Powered by
i have strange issue , i use deepgram stt , somet...
# ask-ai
m
i have strange issue , i use deepgram stt , sometimes i got this ╭────────────────┬──────────────────────────────────────╮ narpos-survey-new | │ Metric │ Value │ narpos-survey-new | ├────────────────┼──────────────────────────────────────┤ narpos-survey-new | │ Type │ stt_metrics │ narpos-survey-new | │ Label │ livekit.plugins.deepgram.stt.STT │ narpos-survey-new | │ Request ID │ c6a16a08-0671-4ef8-a2d8-d16ab9d0d750 │ narpos-survey-new | │ Timestamp │ 2025-07-25 135324 │ narpos-survey-new | │ Duration │ 0.0000s │ narpos-survey-new | │ Streamed │ ✓ │ narpos-survey-new | │ Audio Duration │ 5.0000s │ narpos-survey-new | ╰────────────────┴──────────────────────────────────────╯ narpos-survey-new | narpos-survey-new | narpos-survey-new | narpos-survey-new | narpos-survey-new | STT Metrics Report narpos-survey-new | ╭────────────────┬──────────────────────────────────────╮ narpos-survey-new | │ Metric │ Value │ narpos-survey-new | ├────────────────┼──────────────────────────────────────┤ narpos-survey-new | │ Type │ stt_metrics │ narpos-survey-new | │ Label │ livekit.plugins.deepgram.stt.STT │ narpos-survey-new | │ Request ID │ c6a16a08-0671-4ef8-a2d8-d16ab9d0d750 │ narpos-survey-new | │ Timestamp │ 2025-07-25 135329 │ narpos-survey-new | │ Duration │ 0.0000s │ narpos-survey-new | │ Streamed │ ✓ │ narpos-survey-new | │ Audio Duration │ 5.0500s │ narpos-survey-new | ╰────────────────┴──────────────────────────────────────╯ narpos-survey-new | narpos-survey-new | narpos-survey-new | narpos-survey-new | narpos-survey-new | STT Metrics Report narpos-survey-new | ╭────────────────┬──────────────────────────────────────╮ narpos-survey-new | │ Metric │ Value │ narpos-survey-new | ├────────────────┼──────────────────────────────────────┤ narpos-survey-new | │ Type │ stt_metrics │ narpos-survey-new | │ Label │ livekit.plugins.deepgram.stt.STT │ narpos-survey-new | │ Request ID │ c6a16a08-0671-4ef8-a2d8-d16ab9d0d750 │ narpos-survey-new | │ Timestamp │ 2025-07-25 135335 │ narpos-survey-new | │ Duration │ 0.0000s │ narpos-survey-new | │ Streamed │ ✓ │ narpos-survey-new | │ Audio Duration │ 5.0500s │ narpos-survey-new | ╰────────────────┴─── Main Problem: Duration 0.0000s Seeing Duration: 0.0000s in your STT metrics indicates that Deepgram STT is operating in streaming mode, but the transcription process is not complete. stt.py:302-311 Cause of the Problem I see repeated metrics in your logs with the same Request ID (c6a16a08-0671-4ef8-a2d8-d16ab9d0d750). This means: Audio Duration increases (5.0000s → 5.0500s) - audio is being received Duration remains at 0.0000s - transcription is not completed Streamed: ✓ - streaming is active This pattern indicates that STT is receiving audio but is not producing a transcription result. why this is happening ? i dont have this in cartesia , only ın google stt and deepgram stt , out of 3 calls 1 is like this, no transcribe , so lmm not work because of this .
t
Thanks for reaching out, Ayse. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
The issue you're observing, where the 
Duration
metric shows 
0.0000s
in Deepgram STT metrics, is expected behavior for streaming STT. Here's why: • The 
Duration
metric represents the time it took to create a transcript. For streaming STT, this is always set to 
0.0
because the transcription process is continuous and real-time, rather than being tied to a single request. • The 
Audio Duration
metric, which increases (e.g., 5.0000s → 5.0500s), indicates the actual duration of audio being processed. This is the more meaningful metric for streaming scenarios. • The 
Streamed
flag being active confirms that the STT is operating in streaming mode. However, the repeated metrics with the same Request ID and no transcription result suggest that while audio is being received, the transcription process is not completing. This could be due to: • Network interruptions or latency affecting the streaming connection. • Configuration issues with the Deepgram STT plugin. • Potential bugs or limitations in the integration between LiveKit and Deepgram STT. Since this issue does not occur with Cartesia but happens intermittently with Google STT and Deepgram STT, it may be specific to how these services handle streaming audio or their integration with LiveKit. To investigate further, you may need to: 1. Check the network stability and ensure low latency for the streaming connection. 2. Review the configuration settings for the Deepgram STT plugin to ensure they match the recommended setup. 3. Examine the logs for any errors or warnings during the affected calls. If the issue persists, it may require a deeper investigation into the integration or the STT service itself. Sources: Logs, metrics, and telemetry | LiveKit Docs | livekit-agents/livekit/agents/metrics/usage_collector.py
2 Views
Open in Slack
PreviousNext
Powered by