alphacep / alphacep/vosk-api

Python binding: strange effect when reusing KaldiRecognizer (Reset not working properly?)

Aperta
#1,372 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Jupyter Notebook
Stelle
15.1k
Fork
1.8k
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

Hi,

I noticed a strange effect when I checked a set of transcriptions created by running through a number of WAV files in different folders. Sometimes I get slightly different results for the same WAV files with the exact same settings, depending on the order of processing the files 🤨.

Since I was reusing the `KaldiRecognizer` in a loop (`for wav in wav_files ...`) I thought the only logical explanation could be that there is "something" left internally that remains inside the recognizer and influences the next transcription and indeed, when I add `rec = KaldiRecognizer(model, 16000)` in **every** iteration the effect is gone and everything is always identical 🤔.
I tried to add `rec.Reset()` instead, but that didn't work, only creating a new instance every time helps.

Is this expected behavior? Shouldn't a `rec.FinalResult()` or a `rec.Reset()` always reset the recognizer properly?

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.