-
Notifications
You must be signed in to change notification settings - Fork 4
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
Update to Coqui Speech-to-Text #1
Comments
Hi Josh, I tried to have a go with the QuickStart guide in https://stt.readthedocs.io/en/latest/ on an up-to-date Ubuntu box but it fails. Any pointers? srp ==
|
Hmm, nevermind. I tried this again and it seems happy now. Likely some form of PEBKAC. |
@iamsrp -- the |
Josh, I made the changes to use Coqui and it seems to work fine on Ubuntu. However, it fails to
Are you planning a Pi version at some point? That's pretty much core to Dexter alas... Thanks, srp |
Hi @iamsrp -- definitely good for raspberry pi :) I just realized this isn't in our docs, at STT.readthedocs.io Thanks for pointing it out! |
Thanks for pointing to that Josh; I hadn't seen you had those prebuilt wheels. However, I am possibly being dim but it looks like the listed releases are for Python3.7 for ARM? I only see https://github.com/coqui-ai/STT/releases/download/v1.2.0/stt-1.2.0-cp37-cp37m-linux_armv7l.whl in there but:
meaning:
Is this just me missing something obvious? Cheers, srp |
Unfortunately it looks like 3.9 is where the world is at these days. It's the default version for Raspberry Pi OS, and Ubuntu, now. FWIW I also tried to srp |
We'll be releasing some ARM p3.9 wheels soon:) |
Thanks. That would make me wheely happy. Ho, as they say, ho. :) srp |
Hi Josh, I saw there was a new alpha release but couldn't see the Python 3.9 version for arm in it. Do you know when it's scheduled to flow through to the release pages? Thanks srp |
The 3.9 builds didn't make it to the release, I ran into some bugs with the Raspbian Bullseye libsox package and with a change in the cross build process between 3.7 and 3.9. So I need to take a look again when I have some time. |
Got it, thanks. I'll circle back around at a later date. Thanks again for taking the time to work on it. srp |
Hi, Just checking in to see if you had time to take another look at this. I saw there was a new release but didn't see the 3.9 Arm assets in it yet. Thanks, srp |
Hi Josh, I had a little go with trying to do the cross-compiling myself this weekend but hit a few roadblocks. (It looks like some of the underlying code in Bazel etc. might have changed of late.) Just wondering if you guys had any more luck with this. Thanks, and have a good weekend. srp |
We're in the process of updating to TensorFlow 2.9, which might help with this. So far we haven't had luck adding the ARM builds.
…-- reuben
On 3. Jul 2022, at 21:58, iamsrp ***@***.***> wrote:
Hi Josh,
I had a little go with trying to do the cross-compiling myself this weekend but hit a few roadblocks. (It looks like some of the underlying code in Bazel etc. might have changed of late.)
Just wondering if you guys had any more luck with this.
Thanks, and have a good weekend.
srp
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
Thanks for the update Reuben. Good luck with the TF update; they can sometimes be "interesting"..! And I appreciate the efforts. srp |
I just circled back around to this and saw that there was a new release and, with it, the Python 3.9 ARM support! I just tested it and it's all working nicely. Thanks for getting it sorted. Since we're now on Coqui I am going to close this out but let me know if you think there's anything more pending. srp |
Hi there @iamsrp 👋
Very cool project you have here -- Thanks for sharing it with the open-source community!
You might not know, but Coqui STT is the new, actively maintained fork of DeepSpeech. It would be a fairly easy upgrade, and the new Coqui v1.0 model is much more accurate than the old DeepSpeech models 😄
For more context: mozilla/DeepSpeech#3693
The text was updated successfully, but these errors were encountered: