You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perhaps the error could be due to repeatedly calling await session.stop()? But if i don't call it, then it never calls the 'endOfTranscription' function. So how do I fix it?
Also I just wonder why is the audio format 'file'? I am streaming audio from a react app to a node js proxy server because I don't want to expose my speechmatics credentials to the front end(isn't this the standard practice?)
The text was updated successfully, but these errors were encountered:
Thanks for filing an issue. Apologies for the delayed response.
I haven't tried running your code yet, but this error does indeed sometimes happen when stopping and starting sessions very quickly. This is because we track and limit how many open connections there are per account at a given time, and this process isn't instant.
Short-lived JWTs for our real-time API can be generated by a backend server or serverless function. These tokens are safe to send to the browser, as they can expire as soon as you like.
In the next few days we will be revamping the SDK, and we will have plenty of examples for real-time transcription and more. For now, to solve your problem I would recommend looking into generating JWTs (which would eliminate the need for a proxy server), or adding some delay when restarting sessions in your proxy server.
Describe the bug
Randomly getting this error
Here is my code
My event handlers:
startSession method:
Perhaps the error could be due to repeatedly calling await session.stop()? But if i don't call it, then it never calls the 'endOfTranscription' function. So how do I fix it?
Also I just wonder why is the audio format 'file'? I am streaming audio from a react app to a node js proxy server because I don't want to expose my speechmatics credentials to the front end(isn't this the standard practice?)
The text was updated successfully, but these errors were encountered: