Closed lkraav closed 7 years ago
Thanks, I didn't know about the python bindings in OpenFst 1.5+. Will investigate.
Thanks. In the meanwhile, thanks to Gentoo being able to keep "still-in-use" libraries around, I managed to install openfst-1.6.1, build kaldi-5.1.65 with it, then downgrade to openfst-1.3.4 and build pyfst against this.
make build/output/recording-myaudio.txt
now successfully continues at the pyfst step.
I wonder if there's any weirdness that can occur with this mix. I have a 100 minute audio file I'm transcribing, and ivector-extract
+ fgmm-global-gselect-to-post
processes have been maxing out all 8 cores of the i7 CPU for a couple of hours now at the sid/extract_ivectors.sh: extracting iVectors
step. Is this normal to take a long time even on a modern machine?
No, this is weird. This step shouldn't take much time.
Do you need the speaker ID step at all? Speaker ID tries to add speaker names (Estonian public figures) to the speech segments. You can turn it off using
DO_SPEAKER_ID=no
in Makefile.options
I migrated compounder.py to use OpenFst's native extension. Please test.
No, this is weird. This step shouldn't take much time.
You were correct. I deleted build/
, and restarted the transcription process from scratch (also used DO_SPEAKER_ID=no
). Transcription now finished successfully within reasonable time.
EDIT it would be cool if the build script output some timestamps in the beginning of each line.
I will soon test openfst native extension version and report back.
I will soon test openfst native extension version and report back.
Btw everything seems to work with just openfst
, we can say goodbye to pyfst
.
Recent kaldi requires recent openfst-1.6.x, but pyfst has trouble building with it.
openfst has built-in python bindings since 1.5. Is it within reach to drop pyfst and migrate over?