You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
frontend.util.Microphone does not clean its queue of data objects to be output when (re)starting recording.
When using that Microphone DataSource with endpointing, recognition may stop after SpeechEndSignal and leaves data objects in the queue when I then call stopRecording(). In particular, the old DataEndSignal is still there (before a new DataStartSignal appears followed by the new audio once recording resumes). The old DataEndSignal breaks recognition (or maybe already VAD?) even before the new data can be processed further down the pipeline.
The fix is to add
audioList.clear();
somewhere around line 444 (i.e., before creating the new recordingThread or before starting it). I'm happy to provide such a fix.
The text was updated successfully, but these errors were encountered:
timobaumann
changed the title
frontend.uitil.Microphone needs to clean up before (re)starting recording
frontend.util.Microphone needs to clean up before (re)starting recording
Dec 7, 2018
frontend.util.Microphone does not clean its queue of data objects to be output when (re)starting recording.
When using that Microphone DataSource with endpointing, recognition may stop after SpeechEndSignal and leaves data objects in the queue when I then call stopRecording(). In particular, the old DataEndSignal is still there (before a new DataStartSignal appears followed by the new audio once recording resumes). The old DataEndSignal breaks recognition (or maybe already VAD?) even before the new data can be processed further down the pipeline.
The fix is to add
somewhere around line 444 (i.e., before creating the new recordingThread or before starting it). I'm happy to provide such a fix.
On another note: I filed this as https://sourceforge.net/p/cmusphinx/bugs/482/ but I'm unsure which of the bug trackers is currently used, so re-filing.
The text was updated successfully, but these errors were encountered: