-
Notifications
You must be signed in to change notification settings - Fork 547
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
Major Misidentification Issues in Diarization #248
Comments
I'm having the same experience, just recently tried the diarization on a file with two speakers (swedish language), the transcription works great but the diarization results are very poor. |
could you provide the code for the diarization process? |
same issue here, I tried to downgrade the pyannote model but nothing better |
The problem is pyannote itself. Could you try to run it by itself to see if you get a different result? From my experience, I did not get a better result. |
Anyone know any good alternatives for diariziation that plays nice with insanely fast whisper? |
I have the same issue. During segmentation I also get a message This is on macOS and seems to consistently happen across various recordings with 3-4 speakers. The command I used was:
The code in https://github.com/MahmoudAshraf97/whisper-diarization is able to successfully diarize the same file, however it is much slower as it runs on the CPU rather than the GPU on my M1 Mac. |
I recently tried to transcribe and diarize a meeting with six people. The transcription is spot-on, but there are a lot of misidentification issues in the diarization. For instance, this is two different people talking (a man and a woman):
And this is the same person talking:
I'm not clear on whether this is a
pyannote
problem, an issue with my recording (made in a conference room on an iPhone), or a limitation of current diarization models in general. I get the same problem even if I specify the number of speakers in the command line.Is there a way to improve the diarization? I'd welcome any insight the community has. Thanks!
The text was updated successfully, but these errors were encountered: