Web socket connects but does not send back results sporadically

[bronaugh]

Hi there,

We've been testing out Deepgram integration for our application - specifically, to transcribe live audio using the Speech to Text Transcription API. So far we've been pretty impressed; however, one issue we've been having is that roughly 1 time in 3, we will connect, stream audio to the web socket, and receive no messages back from Deepgram with results.

Hoping you can provide some insights into why this might be happening. We've tried this across three different machines on both Windows and OSX, and the behaviour remains the same. We're using Electron 33.3.1, Chrome 130.0.6723.170.

Language being used is Javascript.

Example with results (request ID: e3e0e320-a3f7-49a4-af10-e9cd70c41812):

Example without results (request ID: 12500384-30b8-430a-abe0-14169eff060b):

[deepgram-community[bot]]

Thanks for asking your question. Please be sure to reply with as much detail as possible so the community can assist you efficiently.
_{Consider joining our Discord community for more opportunity to engage with your fellow Deepgram users. You can earn points which can be redeemed for cool stuff by being active in our communities!}

[deepgram-community[bot]]

Hey there! It looks like you haven't connected your GitHub account to your Deepgram account. You can do this at https://community.deepgram.com - being verified through this process will allow our team to help you in a much more streamlined fashion.

[deepgram-community[bot]]

It looks like we're missing some important information to help debug your issue. Would you mind providing us with the following details in a reply?

• The programming language you are working in (e.g. JavaScript, Python).
• The deepgram product you are using (e.g Speech to Text, Agent API)
• A request ID that triggered your error or issue.

[bronaugh]

Added these details.

[jkroll-deepgram]

Hi @bronaugh, thank you for sharing this report with request IDs.

For the request 12500384-30b8-430a-abe0-14169eff060b that you didn't get any results back from Deepgram, I see a logged error on our side that we received corrupt or unsupported audio data in that stream, causing us to close the stream.

In your testing, are you sending new audio each time, or are you streaming the same audio back? Would you be able to share audio that you can reproduce this error with?

[bronaugh]

Hi @jkroll-deepgram ,

Thanks for the input there. What we found is a race between our audio capture code and Deepgram's connection open timing, which caused us to not send the first frame of a webm audio stream. Without this first frame, the stream would appear to be corrupted.

We've fixed this issue, so we consider this issue to be resolved.

Again, thank you for your timely and informative reply!