Displaying 3 results from an estimated 3 matches for "vad_continu".
Did you mean:
vad_continue
2004 Aug 06
4
Memory leak in denoiser + a few questions
...f speex to use it.
Also, I do have a couple of patches to the preprocessor to send along
actually; basically this makes the start and continue probabilities
parameters that can be set by callers. We're currently using very low
probabilities; Much lower than your defaults, VAD_START=0.05
VAD_CONTINUE=0.02. We also have 20 frame (2/5 sec) "tail" that is
outside the preprocessor, which continues treating some frames as speech
after the detector has dropped out.
<p>Here's a patch:
<p>==================================================
<p>Diff for file preproce...
2004 Aug 06
0
Memory leak in denoiser + a few questions
...gt; Also, I do have a couple of patches to the preprocessor to send along
> actually; basically this makes the start and continue probabilities
> parameters that can be set by callers. We're currently using very low
> probabilities; Much lower than your defaults, VAD_START=0.05
> VAD_CONTINUE=0.02. We also have 20 frame (2/5 sec) "tail" that is
> outside the preprocessor, which continues treating some frames as
> speech after the detector has dropped out.
That's the same patch you sent a while ago, right? Sorry, I haven't had
much time for Speex lately....
2004 Aug 06
2
Memory leak in denoiser + a few questions
On Mar 28, 2004, at 8:23 PM, Jean-Marc Valin wrote:
>> The st->zeta pointer isn't freed in the
>> speex_preprocess_state_destroy()
>> function of the preprocess.c file (alloced in line 167). It's in
>> Speex 1.1.4
>> by the way.
>
> Oops... Thanks for letting me know. I'll change that for the next
> release (in the mean time, the fix is