-
Notifications
You must be signed in to change notification settings - Fork 55
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
WebUI for new voices #63
Comments
Not the owner but : wouldn't be way simpler to use gradio for example? You could get a nice ui working in minutes, and a complex ui in hours |
I'm not normally a big fan of gradio, but I agree, I think it's far better suited for a simple UI than adding npm dependencies. |
Also might be relevant. The faster whisper server repo has a gradui UI : https://github.com/fedirz/faster-whisper-server |
That changes my project's course a little bit, but I'm all in for a new challenge! I'll see what I can initially contribute with Gradio, and perhaps we can expand from there :) |
Referencing PR #65 on this issue. |
Have not forgotten! |
I've done some very basic work on a voice recording/playback/inference WebUI that could be an interesting addition to
openedai-speech
. I would like to know if you'd consider an interactive WebUI for this project or if such development would simply interface withopenedai-speech
to maintain its focus.My goals are currently:
Since the In Browser recording part would require some npm libraries, a frontend section in this project would have to be created, therefore I completely understand if in your opinion this should be kept separate.
Anyway, I think we should debate and find the most suitable place for something like this!
The text was updated successfully, but these errors were encountered: