search for: nb_dec_stack

...compiled the lib and it seems to take less then 64K so the only issue is memory usage. I have been testing the speex decode on windows looking at the stack usage and how much is malloc. There appear to be three defines that control much of the memory usage: MAX_CHARS_PER_FRAME , SB_DEC_STACK and NB_DEC_STACK. I have tested lowering these values and then running the speexdec program and looking for errors. By trial and error it appears that I can lower MAX_CHARS_PER_FRAME = 750, SB_DEC_STACK = 750*sizeof(spx_sig_t) and NB_DEC_STACK = 250*sizeof(spx_sig_t) and not get any memory errors but have no...

> > I have tested lowering these values and then running the speexdec > > program and looking for errors. By trial and error it appears that I > > can lower MAX_CHARS_PER_FRAME = 750, SB_DEC_STACK = > > 750*sizeof(spx_sig_t) and NB_DEC_STACK = 250*sizeof(spx_sig_t) > > and not get any memory errors but have no idea if these are safe > > values or not. I could not tell how much stack spaced was used but > > would guess 4 kb would be enough. After making these changes it > > appears to Alloc less the 16kb. >...

...ram. I have done some work with libspeex.dsp by removing references to all modes but narrow band 8000 hz (submode 3). I used the defines: FIXED_POINT, DISABLE_FLOATING_POINT_API, DISABLE_VBR. I also removed the structures for the other submodes and the functions that they called. I reduced the NB_DEC_STACK and NB_ENC_STACK to the smallest values and minimized the heap based on all calls to calloc. I haven't optimized the call stack yet. I reduced the ram usage to around 6k. The problem is when I added the preprocess functionality, the ram usage went to around 20k. I need to know what can be r...

...d it seems to take less then 64K so the only > issue is memory usage. I have been testing the speex decode on > windows looking at the stack usage and how much is malloc. There > appear to be three defines that control much of the memory usage: > MAX_CHARS_PER_FRAME , SB_DEC_STACK and NB_DEC_STACK. MAX_CHARS_PER_FRAME is different from the others. It's a sort of shortcut to remove the need to resize the bit-packer buffer. If you know what you're going to decode, supply your own buffer or can live with realloc() calls, then you can ignore/reduce that one. > I have tested loweri...

...ibspeex.dsp by removing references to all modes but >> narrow band 8000 hz (submode 3). I used the defines: FIXED_POINT, >> DISABLE_FLOATING_POINT_API, DISABLE_VBR. I also removed the >> structures for the other submodes and the functions that they called. >> I reduced the NB_DEC_STACK and NB_ENC_STACK to the smallest values >> and minimized the heap based on all calls to calloc. I haven't >> optimized the call stack yet. I reduced the ram usage to around 6k. >> The problem is when I added the preprocess functionality, the ram >> usage went to around...

...spx_mem_t enc_mem_sw[ENC_MEM_SW_SIZE]; spx_mem_t enc_mem_sw_whole[ENC_SW_WHOLE_SIZE]; spx_mem_t enc_mem_exc[ENC_MEM_EXC_SIZE]; spx_mem_t enc_memexc2[ENC_MEM_EXC2_SIZE]; spx_word32_t enc_pi_gain[ENC_PI_GAIN_SIZE]; int enc_pitch[ENC_PITCH_SIZE]; DecState dec_state; char dec_stack[NB_DEC_STACK]; spx_word16_t dec_excbuf[DEC_EXCBUF_SIZE]; spx_coef_t dec_interp_qlpc[DEC_INTERP_QLPC_SIZE]; spx_lsp_t dec_old_qlsp[DEC_OLD_QLSP_SIZE]; spx_mem_t dec_mem_sp[DEC_MEM_SP_SIZE]; spx_word32_t dec_pi_gain[DEC_PI_GAIN_SIZE]; #endif I noticed that when inside the high pass function that len...

Hi, I am trying to implement Speex in freeRtos on LPC2138 (ARM7 core), to record about 10sec of voice. I like to compress the data by using Speex, because of the limitation of RAM (32KB). I have read that the speex encoder and decoder need less than 6KB RAM. "The fixed-point narrowband encoder+decoder memory use has been cut by more than half, making it possible to fit both in less than 6 kB

...some work with libspeex.dsp by removing references to all modes but > narrow band 8000 hz (submode 3). I used the defines: FIXED_POINT, > DISABLE_FLOATING_POINT_API, DISABLE_VBR. I also removed the > structures for the other submodes and the functions that they called. > I reduced the NB_DEC_STACK and NB_ENC_STACK to the smallest values > and minimized the heap based on all calls to calloc. I haven't > optimized the call stack yet. I reduced the ram usage to around 6k. > The problem is when I added the preprocess functionality, the ram > usage went to around 20k. I need to...

...* [all] Error 2 ====================================================================== # find ./ -name "*.c" -exec grep -nHi 'VALGRIND_MAKE_READABLE' {} \; ./libspeex/nb_celp.c:209: VALGRIND_MAKE_READABLE(st, NB_ENC_STACK); ./libspeex/nb_celp.c:988: VALGRIND_MAKE_READABLE(st, NB_DEC_STACK); ./libspeex/sb_celp.c:270: VALGRIND_MAKE_READABLE(st, (st->stack-(char*)st)); ./libspeex/sb_celp.c:809: VALGRIND_MAKE_READABLE(st, (st->stack-(char*)st)); # find ./ -name "*.h" -exec grep -nHi 'VALGRIND_MAKE_READABLE' {} \; # # pwd /tmp/speex-1.2rc1 # uname -a...

>> There is a bit of work remaining to get the memory usage down for a >> multichannel application. There have been some good posts over the >> last couple of months about reducing memory usage. > > I think 1.1.8 incorporates all memory reductions proposed. Let me know > otherwise. For the persistent storage, the only change that I have made is to MAX_CHARS_PER_FRAME,