search for: mem_sp

...1 = xin1 - 2.f*x_freq[i2] * *n1 + *n2; xout2 = xin2 - 2.f*x_freq[i2+1] * *n3 + *n4; ... in the floating point version this code can produce xout1 or xout2 that go to INF. That is the main issue- I have also seen the IIR filter go wonky occasionally, which is what is corrupting st->mem_sp. Usually this is just because there are some odd values in st->interp_qlpc. However it seems like it can also just happen sometimes as output of the _mm_mul_ps multiply goes to INF (this can also happen in the non-sse code). I am working on figuring out why this is happening. With the new cha...

...e can be shrunk considerably, however I do not know the minimum values that I would set the static arrays to be. I hate to be a bother but could you tell me the minimum values for these arrays/structures in the state structure? Thanks! encode: stack winBuf excBuf swBuf lagWindow old_lsp old_qlsp mem_sp mem_sw mem_sw_whole mem_exc mem_exc2 pi_gain pitch decode: stack excBuf interp_qlpc old_qlsp mem_sp pi_gain >>> Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> 08/06/07 7:04 PM >>> Last thing. All the codebooks are stored as tables of char, so you're probably wastin...

...DecState *st; st=(DecState*)state; speex_free (st->inBuf); speex_free (st->excBuf); speex_free (st->innov); speex_free (st->interp_qlpc); speex_free (st->qlsp); speex_free (st->old_qlsp); speex_free (st->interp_qlsp); speex_free (st->mem_sp); speex_free (st->comb_mem); speex_free (st->pi_gain); speex_free (st); } This would apply to the encoder destroy functions also. -Fritz On2 Technologies, Inc. http://www.on2.com

...> xout2 that go to INF. Well, the question is where does the problem come from. To give INF on the output, there would need to be a problem with the input. Checked that? > That is the main issue- I have also seen the IIR filter go wonky > occasionally, which is what is corrupting st->mem_sp. Well, they would if the filter is bad (read unstable). > Usually > this is just because there are some odd values in st->interp_qlpc. > However it seems like it can also just happen sometimes as > output of the _mm_mul_ps multiply goes to INF (this can also > happen in the no...

A little more info on this: I backtracked deeper into this and it looks like excBuf is corrupted, which is corrupted by low_innov_alias being invalid. However it is not entirely clear where that gets initialized (in sb_celp it is set to out+st->frame_size) Tom

...st->interp_lsp = speex_alloc((st->lpcSize)*sizeof(spx_lsp_t)); st->interp_qlsp = speex_alloc((st->lpcSize)*sizeof(spx_lsp_t)); st->first = 1; for (i=0;i<st->lpcSize;i++) { st->lsp[i]=LSP_SCALING*(M_PI*((float)(i+1)))/(st->lpcSize+1); } st->mem_sp = speex_alloc((st->lpcSize)*sizeof(spx_mem_t)); st->mem_sw = speex_alloc((st->lpcSize)*sizeof(spx_mem_t)); st->mem_sw_whole = speex_alloc((st->lpcSize)*sizeof(spx_mem_t)); st->mem_exc = speex_alloc((st->lpcSize)*sizeof(spx_mem_t)); st->pi_gain = speex_alloc((st-...

...> however I do not know the minimum values that I would set the static > arrays to be. I hate to be a bother but could you tell me the > minimum values for these arrays/structures in the state structure? > Thanks! > > encode: stack winBuf excBuf swBuf lagWindow old_lsp old_qlsp mem_sp > mem_sw mem_sw_whole mem_exc mem_exc2 pi_gain pitch > > decode: stack excBuf interp_qlpc old_qlsp mem_sp pi_gain What I meant is that you can reduce the stack part (assuming you're not already using VAR_ARRAYS or USE_ALLOCA). The other variables above still require the same size th...