-
Notifications
You must be signed in to change notification settings - Fork 686
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
Feature Request - VAD processing for Japanese transcription #54
Comments
Honestly I agree, Whisper seems to hallucinate a lot with Japanese and spirals into a never ending death loop where a phrase is repeated every line from time to time. VAD is pretty much necessary for it. Would also love to see it be implemented in some shape or form! |
I would second this. Especially if it include all different type of VADs
It would be nice to have since I use whisper for Japanese language as well. |
Hi! I find that Whisper still have a problem of repeating lines when transcribe long file in Japanese. Since this issue still open, I assumed nobody is working on it. Here in my repo, I made a simple script that calling Silero-VAD to filter out silence parts and generate chunks of voice-containing audio files. So we can passing those chunks into Whisper to extract subtitles and avoid the hallucination. There is also a script to re-create a complete subtitle from them. The scripts were very naively written and may need more polishing. So feel free to download and modify by yourself. |
Hey there Konstantin
currently i use a branch of whisper that uses a VAD, which produces great results with Japanese language,
Im really impressed with your program here and the ability to use it on an AMD device as im limited to running in colab with the previous model i use, is there any possibility that there could be an integration of a VAD to help break down the text and stop the ghosting error i get when trying to transcribe Japanese content using your application
Thank you so much for your efforts :) appreciate it
The text was updated successfully, but these errors were encountered: