11 ms·

> As another practitioner, I find it odd that the author mentions frameworks such as OpenNMT but not Kaldi when comparing SST toolkits/frameworks. [unpopular o

by qayxc 7y ago

> As another practitioner, I find it odd that the author mentions frameworks such as OpenNMT but not Kaldi when comparing SST toolkits/frameworks. [unpopular opinion ahead] Maybe that's because Kaldi represents the ultimate culmination of the author's critique: • the provided scripts are useless to anyone without access to the academic datasets they use • Kaldi is very cumbersome and overly complex to use and adapt (most of the toolchain relies on exact copies of entire directory trees) • Kaldi is a research tool by researchers for researchers and not in any way shape or form aimed at practitioners in search of a deployable solution • Kaldi is very poorly documented (from a user perspective) and focuses on recipes for your own experiments, not writing applications and roll out In summary, Kaldi isn't a practical toolkit. It's a framework for R&D on speech-to-text.

nshm 7y ago
> the provided scripts are useless to anyone without access to the academic datasets they use Kaldi team shares all datasets when possible on http://openslr.org http://openslr.org, a major collection of speech datasets. Librispeech and Tedlium were major breakthrough in their times. When everyone in research trained on 80 hours WSJ and Google trained on 2000 hours private dataset, 1000 hours of librispeech was a game changer. > Kaldi is very cumbersome and overly complex to use and adapt (most of the toolchain relies on exact copies of entire directory trees) On the other hand the Kaldi API is very stable. You still can run 4 year old recipes with simple run.sh. Any tensorflow software gets obsolete once in 3 months when TF API changes. Kaldi recipe results are usually reproducible up to the digit and you can even see the tuning history (which features did improve, which didn't). > Kaldi is a research tool by researchers for researchers and not in any way shape or form aimed at practitioners in search of a deployable solution There are hundreds of companies all over the world building practical solutions with Kaldi. The only thing that Kaldi team should do is to ask users to mention it. > Kaldi is very poorly documented (from a user perspective) and focuses on recipes for your own experiments, not writing applications and roll out There are also dozen of projects on Github which enable use of Kaldi with simple pip install or docker pull. kaldi-gstreamer-server, kaldi-active-grammar, vosk and many others.
albertzeyer 7y ago
(Disclaimer: I also work in the field.) I would disagree with most of your points. The provided scripts are available for a huge number of datasets. Many of the datasets are also useful for use in production. And it's very simple to adapt the provided scripts for further data. Kaldi is complex and big, yes. But you don't have to use all of it. And it is that way because doing STT properly simply is complex. At least for the conventional standard hybrid HMM/NN models. You could surely go some of the end-to-end ways but that will lead to other problems in production. And once you need to deal with these problems, it might become even more complicated. (This is a whole topic on its own...) Kaldi is used in research as well as in production. It can be easily deployed. Kaldi is very well documented. Just check the homepage of it. In addition to it, there is a huge community (both academia and industry).

by qayxc 7y ago

nshm 7y ago

> the provided scripts are useless to anyone without access to the academic datasets they use Kaldi team shares all datasets when possible on http://openslr.org http://openslr.org, a major collection of speech datasets. Librispeech and Tedlium were major breakthrough in their times. When everyone in research trained on 80 hours WSJ and Google trained on 2000 hours private dataset, 1000 hours of librispeech was a game changer. > Kaldi is very cumbersome and overly complex to use and adapt (most of the toolchain relies on exact copies of entire directory trees) On the other hand the Kaldi API is very stable. You still can run 4 year old recipes with simple run.sh. Any tensorflow software gets obsolete once in 3 months when TF API changes. Kaldi recipe results are usually reproducible up to the digit and you can even see the tuning history (which features did improve, which didn't). > Kaldi is a research tool by researchers for researchers and not in any way shape or form aimed at practitioners in search of a deployable solution There are hundreds of companies all over the world building practical solutions with Kaldi. The only thing that Kaldi team should do is to ask users to mention it. > Kaldi is very poorly documented (from a user perspective) and focuses on recipes for your own experiments, not writing applications and roll out There are also dozen of projects on Github which enable use of Kaldi with simple pip install or docker pull. kaldi-gstreamer-server, kaldi-active-grammar, vosk and many others.

albertzeyer 7y ago

(Disclaimer: I also work in the field.) I would disagree with most of your points. The provided scripts are available for a huge number of datasets. Many of the datasets are also useful for use in production. And it's very simple to adapt the provided scripts for further data. Kaldi is complex and big, yes. But you don't have to use all of it. And it is that way because doing STT properly simply is complex. At least for the conventional standard hybrid HMM/NN models. You could surely go some of the end-to-end ways but that will lead to other problems in production. And once you need to deal with these problems, it might become even more complicated. (This is a whole topic on its own...) Kaldi is used in research as well as in production. It can be easily deployed. Kaldi is very well documented. Just check the homepage of it. In addition to it, there is a huge community (both academia and industry).