-
Notifications
You must be signed in to change notification settings - Fork 15
Transcription missing end of the file #19
Comments
Hello.. I used the example_audio.zip and I get only "hello" too. I am trying to transcribe a file with this library too. The file I am using is following. I am not getting any returns for my file thou. Would you mind to take a look at it and suggest if I am missing anything? Followings are the settings I used.
By the way, I found a more elegant way to end the streaming of the file. I will comment in the library. |
I found a small hack that seems to solve the issue, it is similar to what you did in the issue you linked. I just concatenated 1s silence at the end of file. I used something like:
I believe the issue could come from the real time transcribe API. If the audio suddenly ends just after a word, the last sentence being transcribed is never returned. |
Hi @agonza1 , what is the sample rate that you are using? Is it the sample rate from the file? Mind to explain why you choose sample rate for throttle but the example used 2 x sample rate.. I am still getting empty results or bit and pieces of wrong transcribe.. |
In my case I had a sample rate of 16khz so I didn't need to put the 2 in front. I believe 16khz is the max supported so that's why you need to throttle. If you are not getting any transcriptions from your files I would verify the file is audio only and with the right codecs, etc. You could use something like:
to check it out |
First, I would like to thank you for setting this module. It works great!
I was just having some issues with voice transcriptions at the end of the file. So I am streaming from a local file, very similar to what you did here .
After using:
And
I can get a transcript but it is always missing the end part of the transcription, (e.g: I say: "hello world", transcription returns: "hello" and ends). I just uploaded an example wav audio here: example_audio.zip. This file gets transcribed fine when using batch transcriptions instead of aws-transcribe.
The text was updated successfully, but these errors were encountered: