search for: teligy

...of the previous point, speex_preprocess()'s VAD can get into a bad state, given an input that varies drastically in amplitude/behavior, after which point its accuracy is ruined and the only solution is to destroy/recreate the preprocess state. Tom "Paul Gryting" <paul.gryting@teligy.com> wrote: > > In speexenc.c, speex_preprocess() is not called unless AGC or denoise is > enabled. > If only VAD is enabled, it does not get called. > > speex_preprocess() has vad_enabled specific code to detect voice activity. > speex_preprocess() > { > ... >...

I'm finding it dificult to get the code to fit within c5x dsp, especially due to the large heap necessary for the huge allocations in nb_encoder_init and nb_decoder_init. Are the people that have this running using additonal external ram? Has anyone experimented with reducing the internal encoder/decoder stack sizes for narrow band... is there a practical minimum that is usable? Also,

Jamey, There is a previous posting in the speex archives with a link to the dsp c5x patch. Archive link: http://lists.xiph.org/pipermail/speex-dev/2004-October/002847.html Patch link: http://lists.xiph.org/pipermail/speex-dev/attachments/20041029/facb8c73/spee x-1.1.6-jeh1-0001.bin But that patch is very different (much smaller) then the dsp c5x patch at

I saw a thread in the list archives about a speex port to TI 55x DSP. Wondering how that worked out (is working out)? Also wondering if there is a source archive for it, or if the patch in the email archives is still current, or if there's been updates. Any info appreciated. Thanks Paul