Closed motapinto closed 3 months ago
Hi @motapinto
Thanks for providing all this info. Will need a second to sift through it. I can answer some of your initial comments though in the meantime.
I leave transcription script that handles transcription running for some time and eventually that error appears. Can share entire code privately.
If you can log into Discord and share, that would be very helpful.
I tested this and keep alive message is sent even without starting microphone, so not sure why in "Error message type 2" I get 1011 websocket error.
If you have KeepAlive=True
, the Live Client will send keepalive messages continuously. The purpose of the message is when audio data from your source is not streaming through the client, the keepalive message will prevent DG from closing the socket. The 1011 close socket could happen though for other unforeseen reasons, however.
Is it necessary to send keep alive even with those options or can this be another problem?
If you aren't sending data and want to hold the DG connection open, then you need to enable the keepalive. The other option is that if you don't have the option set, you might want to control the "I'm not sending any data". In other words, you might prefer the disconnect, and if your application still needs the transcription because the process isn't done, you re-create the client for a reconnect. The advantage here is that this client has a fresh state.
Will take a look through the logs and drop more info here.
For my notekeeping, this thread in Discord is the same problem: https://discord.com/channels/1108042150941294664/1214170879647289416
Via discord, we ended up finding the problem for anyone else that is interested. the problem is:
in the meantime, these are just examples to demonstrate functionality and don't affect the core of the client code
What is the current behavior?
Deepgram seems to stop working after running live transcription script for some time, usually accompanied by an "Fatal error on SSL transport" error. This is delaying a wider release for live products.
Steps to reproduce
I leave transcription script that handles transcription running for some time and eventually that error appears. Can share entire code privately. The client is already initialized with
config = DeepgramClientOptions(verbose=logging.WARN, options={"keepalive": "true"})
. I tested this and keep alive message is sent even without starting microphone, so not sure why in "Error message type 2" I get 1011 websocket error. Is it necessary to send keep alive even with those options or can this be another problem?Please tell us about your environment
Other information
Error message type 1
Error message type 2
Error message type 3