No TranscriptReceived Events When Streaming MediaRecorder Chunks (WebM/Opus)

[neon sail]

Thanks for asking your question. Please be sure to reply with as much detail as possible so the community can assist you efficiently.
-# If you haven't done so, ensure your Discord and Github profiles are linked to Deepgram so you can earn points to redeem on cool stuff just by being active!

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?

• A request ID that triggered your error or issue.

[wicked flint]

Don't have a request ID

[lethal summit]

I'm having the exact same problem. I can see that I have successful logs in the deepgram dashbaord just no transcriptions coming in at all

[wicked flint]

Does anyone have a fix for this? I'm really stuck on this, can't seem to get it to work...

[fervent gulch]

Can you confirm with version SDK you are using?

I am assuming you are using our JS SDK as you mentioned Node,js, so correct me if that is wrong.

I suggest first thing is to use the most current v4 version of the JS SDK if you are trying to use v3.

We recently did a Major version bump and you should upgrade as soon as possible as we don't maintain backwards compatibility on major SDK versions.

[wicked flint]

Even with the new version, I get the following error (1006): ❌ Deepgram setup fout: DeepgramVersionError: You are attempting to use an old format for a newer SDK version. Read more here: https://dpgr.am/js-v3

at new Deepgram (/app/node_modules/@deepgram/sdk/dist/main/index.js:35:15)

at WebSocketServer.<anonymous> (file:///app/server.js:35:22)

at WebSocketServer.emit (node:events:518:28)

at WebSocketServer.completeUpgrade (/app/node_modules/ws/lib/websocket-server.js:436:5)

at WebSocketServer.handleUpgrade (/app/node_modules/ws/lib/websocket-server.js:344:10)

at Server.upgrade (/app/node_modules/ws/lib/websocket-server.js:119:16)

at Server.emit (node:events:518:28)

at onParserExecuteCommon (node:_http_server:938:14)

at onParserExecute (node:_http_server:839:3) {

__dgError: true

} @woeful oracle

This is the code, I can't find anything wrong with it...

[wicked flint]

I might have found a workaround, when using socket.io it seems to be able to connect to deepgram. But still experiencing no live transcription when talking...

[fervent gulch]

Do you have any request IDs you can share with us so we can take a deeper look?