-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
over 5min simple_file #26
Comments
Hi @kazuhitogo, Could you clarify what you mean by "maintaining a session"? If the signatures are becoming invalid after 5 minutes I believe you're hitting the issue noted in the quickstart section:
The Transcribe Streaming API is meant for realtime audio and processes at that rate. If you're streaming prerecorded audio that's longer than 5 minutes, it will need to be rate limited to being sent closer to real time. Otherwise, the payloads are signed in the client and then can't be processed by the service until after they expire. |
There's some code in one of the unit tests that shows how to rate-limit. I got it going as shown below (it pulls the whole WAV into memory which is only good for relatively short files). The only trouble is, the transcript results seem to get "stuck" every 15 seconds or so; they stop coming, and then resume after a bit, but they are missing a string of words in the meantime.
|
Thanks for the response. I am sorry for the delay in confirming. Am I correct in assuming that this is not possible? Thank you. |
I can't figure out how to maintain a session for more than 5 minutes using http2. doc describes how to specify expire-time for websocket, but not for http2. Is there any way to connect a session for more than 5 minutes with this SDK?
The text was updated successfully, but these errors were encountered: