whisper.cpp
whisper.cpp copied to clipboard
ggerganov
Add release with binaries
That's quite a big bunch of binaries if you want to cater for every possible hw/OS/etc combination... AVX2 enabled binaries will simply crash if the hardware doesn't support AVX2, just as an example. Automated builds can help there ofc, but the user would still have to know which exact binary to use. Currently it's all figured out during the compilation process and making that a runtime thing could be more trouble than its worth. Hmm, then again this might be a good combo with whispercppGUI... I mean, maybe whispercppGUI could ship with multiple "main" binaries and then choose the right one for the host hw.
Alternatively, build scripts / instructions could be provided for a wide variety of platforms. This would probably increase the user base considerably and the results would always be suitable.
I agree with @misutoneko - it would be too much effort to maintain. Maybe in the future - right now things are still changing quickly.
@geimist I like the idea of scripts/instructions. Right now, the steps for different platforms are too scattered - there are some in the README.md, in some issues, in the discussions and in the Github Actions file. There is also the CMake build which is not documented at all. Probably it would be better to put all of them in a single README / Wiki.
I don't speak on behalf of GGerganov and im sorry if this sounds harsh,
but if you can't figure out how to compile the code from this github repo within about 15 minutes then its probably not the right project for you right now.
The OpenAI Python implementation has MANY more followers/contributors and likely has something closer to an end-user implementation that your looking for.
On Tue, 13 Dec 2022 at 05:00, Georgi Gerganov @.***> wrote:
I agree with @misutoneko https://github.com/misutoneko - it would be too much effort to maintain. Maybe in the future - right now things are still changing quickly.
@geimist https://github.com/geimist I like the idea of scripts/instructions. Right now, the steps for different platforms are too scattered - there are some in the README.md, in some issues, in the discussions and in the Github Actions file. There is also the CMake build which is not documented at all. Probably it would be better to put all of them in a single README / Wiki.
— Reply to this email directly, view it on GitHub https://github.com/ggerganov/whisper.cpp/issues/232#issuecomment-1347098321, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALQR6Z6A6OM3S2YF5N4CPLWM5Y4TANCNFSM6AAAAAASYFSQJ4 . You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- Sincerely
Jay
Related, not asking for binaries, but can we please have release tags on the repo, so that it is easier to package it for various package managers?
Added first release for v1.0.4 + Windows binaries
https://github.com/ggerganov/whisper.cpp/releases/tag/1.0.4