Earlier quoted context omitted.
It looks like the database will be open sourced later this year: https://voice.mozilla.org/faq I'm wondering if the format will be easily translatable to the kinds of models that software like CMUSphinx and Julius use https://cmusphinx.github.io/ http://julius.osdn.jp/en_index.php
It's weird to me that they publish the project about having an open dataset of voice data, with only a promise the open it up later.
Project Common Voice
41–50 of 61 posts
Re: Project Common Voice
#42The terminology is a bit confusing. They are saying that they want to build voice recognition but it seems like they actually might want to build a speech recognition engine. Speech recognition is about recognizing the speech, the spoken words. Voice recognition is about recognizing the speakers voice, i.e. identifying the speaker. Also, maybe they also want to build a text-to-speech (TTS) system but I'm not sure. No…
To answer you question: Common Voice is about building a collection of labelled voice data (ie. sentence clips w/ transcripts) that can be used to, for instance, train speech-to-text algorithms. Part of the goals of this project though is to figure out how this data can best help people build voice technology. So it's pretty open ended at this point.
Mozilla does have an open source speech-to-text engine [1] we are developing, and we hope one day to use the Common Voice data to train this engine. DeepSpeech and Common Voice are related, but separate projects, if that makes sense.
As for LibriSpeech, the DeepSpeech team at Mozilla does use this data for training. However, the language is pretty antiquated, and we only get about 1K hours of data, whereas you need about 10K hours to get to a decent accuracy (WER of 10% and below). Common Voice is about adding to public corpora like LibraSpeech, not replacing them.
Re: Project Common Voice
#43Earlier quoted context omitted.
It's weird to me that they publish the project about having an open dataset of voice data, with only a promise the open it up later.
It's Mozilla, they likely just don't have the infrastructure/code in place yet. They definitely get my trust for believing they actually will. They have been very good in the past about keeping things open. They make mistakes sometimes, but their goals are all about being open.
Re: Project Common Voice
#44The terminology is a bit confusing. They are saying that they want to build voice recognition but it seems like they actually might want to build a speech recognition engine. Speech recognition is about recognizing the speech, the spoken words. Voice recognition is about recognizing the speakers voice, i.e. identifying the speaker. Also, maybe they also want to build a text-to-speech (TTS) system but I'm not sure. No…
> Speech recognition is about recognizing the speech, the spoken words. Voice recognition is about recognizing the speakers voice, i.e. identifying the speaker. Perhaps they want to do both eventually (?) That could explain the name.
Re: Project Common Voice
#45Is the data going to be freely available as well? It's a little unclear whether they intend to make it separately available or not.
Re: Project Common Voice
#46And... 503'd. I didn't catch what the intended use case was before it died, but I'm guessing computer generated voice? Most of the computer generated stuff I've seen uses trained actors. Which neatly avoids the problem of trying to reconcile a myriad of accents and dialects, which was immediately apparent from the first two samples I tried. edit: back up, seems to be about voice recognition, which this could help wit…
Re: Project Common Voice
#47Is the data going to be freely available as well? It's a little unclear whether they intend to make it separately available or not.
It looks like the database will be open sourced later this year: https://voice.mozilla.org/faq I'm wondering if the format will be easily translatable to the kinds of models that software like CMUSphinx and Julius use https://cmusphinx.github.io/ http://julius.osdn.jp/en_index.php
If you poke around github and the Kaldi lists a bit more you can see that they are experimenting with and probably planning to use Kaldi.
I wonder what they plan to do for provisioning. It is one thing to collect data and train models, but quite another to make the service available over the web in an unlimited capacity. And we are not yet to the point where you can reasonably expect to run a high quality open-vocabulary STT system in your browser. The search network is typically in the GBs range.
Re: Project Common Voice
#48Cool project, really aligned with the mission of Mozilla, and with a pleasant UX. And if you're a non-english speaker like me validating sentences is a nice way of improving your comprehension.
Yep! Though us non-native speakers should really be recording, too. So we're not left behind in voice recognition.
If you are a non-native speaker, we need your voice!
Re: Project Common Voice
#49Re: Project Common Voice
#50Earlier quoted context omitted.
Yep! Though us non-native speakers should really be recording, too. So we're not left behind in voice recognition.
Exactly! Part of the goals of Common Voice is to make voice recognition work better for non-north american men (which is where the vast majority of the training data comes from). If you are a non-native speaker, we need your voice!