-
Notifications
You must be signed in to change notification settings - Fork 24
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
STT 1.4.0 - CommonVoice 12 #168
base: master
Are you sure you want to change the base?
Conversation
I would still like to:
But we can do those in other PRs. |
""" | ||
_logger.info("Creating corpora...") | ||
corpora_data = self._parse_tsv() | ||
+ # FIXME: THIS IS WRONG DONT USE VALIDATED.TSV AS A SOURCE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixme? :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is your patch ahahha :) I have not touched it.
I'm not even sure why it's there to begin with :')
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To reflect them all... |
What happened with this? That would be really nice to get a new model based on Coqui and the latest CV release (it's the way to go isn't?) |
Coqui is defunct, and I guess @wasertech stopped working on his model as well? I agree it would be fine but ... |
Well, I just moved on to other (more maintained) architectures, as I didn't wanted to maintain it alone. I tried Wav2Vec 2.0 for a while and currently, I am using Faster-Whisper for real-time transcription because those architecture are better suited for my use. I have a relatively big language model (~7B parameters) behind my transcription services so I need a large enough model to use for real-time open domain conversations. DeepSpeech/STT are just not cutting it for this use case unfortunately. The code in my branch should still (mostly) work with the latest release of STT (1.4.0), so you (or anyone interested) can still use it to train or fine-tune models, but yeah it's unlikely for me to produce a new STT model given the availability of better suited architectures for my application. |
What about we keep
commonvoice-fr/DeeepSpeech/
as it is and simply addcommonvoice-fr/STT/
instead?I've started from my branch
stt140-cv9
which produced my latest models so I know it works. I updated it to use CV12 but that's basically it.There are still some points I want to address before I train my next models so that's why it's still a draft but let me know if you already want to merge this new directory and let me update it later.
It's now much easier to compare the differences between
DeepSpeech
andSTT
.Checkout deepspeech-stt.diff