-
Notifications
You must be signed in to change notification settings - Fork 227
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
Is this repo usable for a production use case!! #158
Comments
@MahmoudAshraf97 , will appreciate your take on this! Thanks for sharing your work! |
Hello and thanks for the input، please open a PR with any changes you see that are useful and we can discuss them together |
@MahmoudAshraf97 , Thanks for your understanding! This is what I want to do:
Let me know what you think. It will take some time to make all these changes. Before I spend any time, I wanted to align with you. Thanks! |
@MahmoudAshraf97 , do you have any feedback? |
@MahmoudAshraf97 , thought? |
I'm not speaking for @MahmoudAshraf97 here, but if you take a look at his response from Jan 24, it's pretty clear. This is an open source project that he's doing for whatever his reasons are. @utility-aagrawal, you are treating it like a commercial product that you are paying for. If you want these changes, you are free to implement them and submit the PR's to get them merged into the project. If you are not a developer, you could pay someone to do the work and submit the patches. |
I have this running in a production environment - it’s stable, consistent, and does a great job |
Hi All,
I am wondering if anyone has used this repo for a production use case. Currently, I am using openai whisper for transcription but want to include speaker diarization now. I have tried pyannote in the past but results from this repo look much better. My concern is that the source code hasn't been written keeping a production use case in mind - not too flexible, too many log messages, etc. I can rewrite this code but what if there were updates in the future. Will appreciate the community's input on this. Thanks!
The text was updated successfully, but these errors were encountered: