Skip to content
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

Prediction on new audio file #23

Closed
nisarshah opened this issue Nov 29, 2018 · 2 comments
Closed

Prediction on new audio file #23

nisarshah opened this issue Nov 29, 2018 · 2 comments

Comments

@nisarshah
Copy link

Hi,
How to use pytorch-kaldi in production environment after training the Model.
I have models ready, which I have generated by using core Kaldi. The problem I am facing is that it takes lot of time during decoding/prediction phase.

So please let me know how to use this tool during live environment.
Also if you have useful suggestions for Kaldi deployments please share.

Also I am planing to integrate Kaldi model in one of ours applications which is live.
So yours suggestions will be very useful for me.

--
thanks
Nisar

@TParcollet
Copy link
Collaborator

Hi !
For now, the only solution is to first train your pytorch model, and then call run_exp.py with a modified conf file with the number of epoch set to 0 (and also a specific [dataset] section that you can call as a testing dataset. We are aware that this is not optimal for real production case, and we are currently working on a side script that one can call to just decode .wav files from a previously trained pytorch model. Nonetheless, you can dive a bit on the run_exp.sh script to better understand how you can easily build your own script (if you are in a hurry).

I worked a bit with Kaldi in production environment (with automatic transcriptions of uploaded audio files). Nonetheless, and as you mention, the decoding time can be a problem. One of the solution we found is to use speaker diarization, so we can split the decoding in multiple threads with one thread equal to a speaker.

@mravanelli
Copy link
Owner

mravanelli commented Nov 29, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants