-
-
Notifications
You must be signed in to change notification settings - Fork 203
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
Timestamps always maximum length when using Silero VAD #287
Comments
Hi, This seems to be default behavior of the whisper, not just VAD. Regardless of whether each segment tries to start from the end of the previous segment (if possible), it should still captrue the correct timestamp. If the longer segment is the problem, try setting |
Just reproduced hallucinations on a sample. This happens under all the +) And I observed the same hallucinations with |
pyannote have their own VAD as I understand - maybe one could use it?
From https://github.com/shashikg/WhisperS2T
|
a fix was merged for faster whisper - maybe that solves the problem? SYSTRAN/faster-whisper#921 |
Thanks, but it might not be about improving this, it's probably about fixing the batch transcription bug. I'm considering implementing whisperX's and my own implementation for the VAD and using the better one after comparing them. I don't have time for this right now, hope I can do it as soon as possible. Or any PR for this would be welcome. |
Faster-whisper programmers say it is not a VAD issue maybe here: |
Transcription appears to be accurate, however the ending timestamps for each line are always set at the beginning timestamp of the next line, resulting in subtitles constantly displayed long after speech ends, e.g.:
The text was updated successfully, but these errors were encountered: