Menu
▾
▴
Re: [Kaldi-developers] Kaldi on Windows
|
From: Daniel P. <dp...@gm...> - 2015-03-02 21:34:08
|
I remember why it's not possible to get the scripts to work when compiled in Windows. The scripts depend on Kaldi opening commands from within C++ programs, and the commands need to be interpreted in bash. If you have compiled the binaries in windows this won't work because they don't "know about" cygwin. Now in principle you could try to convert the scripts to DOS commands to make it work. But this would be a huge amount of work; and DOS is too primitive a language. Basically I gave up on doing this when I discovered that there is no documented way to escape double-quote characters in DOS. (It seems empirically that you can sometimes use 3 quotes, and sometimes 4, but the distinction is very mysterious). And some people told me that PowerShell is the recommended way to do scripting now, but Kaldi is based on piping raw data, not objects, and PowerShell treats raw data as a string of objects which happen to be characters, which probably imposes a considerable overhead. Anyway, the standard utilities we need for speech recognition evaluations, such as sph2pipe, sclite and so on, won't work on Windows. Dan On Mon, Mar 2, 2015 at 4:16 PM, Daniel Povey <dp...@gm...> wrote: > librispeech scripts are available in librispeech/s5/. > I am warning you, you will regret trying to do it on Windows. But I would > still appreciate help with the build setup. > > Dan > > > On Mon, Mar 2, 2015 at 4:05 PM, Kirill Katsnelson < > kir...@sm...> wrote: > >> Compiling under cygwin is probably not reasonable for such a >> computation-intensive toolkit. No CUDA, probably no MKL, not even >> instruction set optimization, as far as I understand. >> >> >> >> I’ll see what I can pull out of it when it compiles and tests ok. I know >> of the line ending issues, and hope to be able to handle them. Pipes I am >> not sure, never ran into these before. That would be a more complex problem. >> >> >> >> I do not have access to the WSJ corpus. Are there any pointers to the use >> of LibriSpeech instead? I remember reading your paper where you compared >> the results on DNN in wsj/s5 with LibriSpeech. I’ll have to reread it, but >> as well may ask you while we are communicating :) -- are Kaldi scripts >> available for it? >> >> >> >> -kkm >> >> >> >> *From:* Daniel Povey [mailto:dp...@gm...] >> *Sent:* 2015-03-02 1253 >> >> *To:* Kirill Katsnelson >> *Cc:* kal...@li... >> *Subject:* Re: [Kaldi-developers] Kaldi on Windows >> >> >> >> Hi, >> >> If you are going to use cygwin, then it is best to just compile it in >> cygwin. If you compile using Visual Studio, the binaries won't work >> correctly- I forget whether it relates to how newlines are handled, how >> pipes work, or some other reason. In any case, Visual Studio is quite >> buggy- some problems were reported recently on one of these lists. >> >> Dan >> >> >> >> >> >> On Mon, Mar 2, 2015 at 3:49 PM, Kirill Katsnelson < >> kir...@sm...> wrote: >> >> Thank you Dan! I hope cygwin will take care of the script part, unless >> there are exotic used like unix domain sockets, procfs etc. >> >> >> >> -kkm >> >> >> >> *From:* Daniel Povey [mailto:dp...@gm...] >> *Sent:* 2015-03-02 1127 >> *To:* Kirill Katsnelson >> *Cc:* kal...@li... >> *Subject:* Re: [Kaldi-developers] Kaldi on Windows >> >> >> >> I confirmed on both lists. Replying to kaldi-developers and just bcc'ing >> kaldi-users. >> >> It would be great if you could improve the Windows build for us. >> >> However, Kaldi scripts are dependent on things like bash, and it won't >> work on Windows. So ultimately it will not make sense for you to train on >> Windows- the cost of your time will be more than the cost of a new >> machine. That being said, I would appreciate better Windows build scripts >> (main use case is deployment of recognition on Windows). >> >> Dan >> >> >> >> >> >> On Mon, Mar 2, 2015 at 2:05 PM, Kirill Katsnelson < >> kir...@sm...> wrote: >> >> Hi, >> >> I am trying to compile and use Kaldi on Windows. The perl script that >> comes in the distribution does not produce very useful results, since >> VS2013 has a trouble opening (opening, not compiling!) the resulting >> monster solution of 600+ projects. It does not support CUDA also. >> >> I approached the problem from the square one and am writing msbuild >> scripts with the support for CUDA, MKL and Intel C++ compiler. >> >> Is there any interest in supporting Kaldi build on Windows in the >> mainline distribution? For me, a practical consideration in this decision >> was the cost of building an extra machine with CUDA hardware and Intel >> software just for Kaldi, while my Windows machine already has all this. >> >> Is kal...@li... a closed list? I send a >> subscription request to the both lists, but got a confirmation from the >> -users@ list only. >> >> -kkm >> >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming The Go Parallel Website, >> sponsored >> by Intel and developed in partnership with Slashdot Media, is your hub >> for all >> things parallel software development, from weekly thought leadership >> blogs to >> news, videos, case studies, tutorials and more. Take a look and join the >> conversation now. http://goparallel.sourceforge.net/ >> _______________________________________________ >> Kaldi-developers mailing list >> Kal...@li... >> https://lists.sourceforge.net/lists/listinfo/kaldi-developers >> >> >> >> >> > > |
