Streaming STT with no transcription and zero audio duration

[rodrigo-d-azevedo]

This is an esporadic issue...
Comparing my app´s logs and Deepgram Console log, there are some differences when there´s no text recognition after some seconds of audio streaming. My app´s connects, send some KeepAlive and then disconnect without any text recognized. The human voice in the audio is very clear.

How investigate this issue further? To detect if it was network delay or anything else?

Sequence of request IDS:
fa55a748-cec4-460a-859d-1e57d7376e83 (connected at 03:02:12UTC, disconnected at 03:02:36, but with 0 audio duration in DG log)
d45884b1-e681-4669-b0ec-63c57fdb7fff (connected at 03:02:39, disconnected at 03:02:48, same issue)
4a336ed3-d5e6-45ba-8c09-a702a3f59d4c (Successfull recognition)

2024-10-07T00:02:12: Deepgram connected!
2024-10-07T00:02:15: KeepAlive sent.
2024-10-07T00:02:18: KeepAlive sent.
2024-10-07T00:02:21: KeepAlive sent.
2024-10-07T00:02:24: KeepAlive sent.
2024-10-07T00:02:27: KeepAlive sent.
2024-10-07T00:02:30: KeepAlive sent.
2024-10-07T00:02:33: KeepAlive sent.
2024-10-07T00:02:36: KeepAlive sent.
2024-10-07T00:02:36: 1728270156839 message.data {
2024-10-07T00:02:36:   "event": "stop"
2024-10-07T00:02:36: }
2024-10-07T00:02:36: 1728270156839 STOP
2024-10-07T00:02:36: Disconnected from DeepGram!
2024-10-07T00:02:36: 1728270156839 Client disconnected
2024-10-07T00:02:36: {
2024-10-07T00:02:36:   type: 'Metadata',
2024-10-07T00:02:36:   transaction_key: 'deprecated',
2024-10-07T00:02:36:   request_id: 'fa55a748-cec4-460a-859d-1e57d7376e83',
2024-10-07T00:02:36:   sha256: 'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855',
2024-10-07T00:02:36:   created: '2024-10-07T03:02:12.555Z',
2024-10-07T00:02:36:   duration: 0,
2024-10-07T00:02:36:   channels: 0
2024-10-07T00:02:36: }
2024-10-07T00:02:36: Deepgram connection closed.

Thanks in advance!

[deepgram-community[bot]]

checking your requests on our debug tools, we received no audio for the first two requests.

If you stopped sending keepalives when sending data, but we received none. That would indeed explain the connection and metadata message. You should stop sending keepalives to send data, and resume keepalives between data streams.

luke