search for: nb_enc_stack

...e 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 removed or reduced...

Happy new year all! I have had a few issues with this sort of stuff- you could adjust NB_ENC_STACK or SB_ENC_STACK (which ever you may be fiddling with) and see if the problem goes away- could be the allocation for the vorbis psy tables takes up more space than the current stack size allows (not sure how allocated? Could be your settings for supporting alloca/etc. are set different than jm, d...

...moving 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...

...e ENC_MEM_EXC_SIZE 20 #define ENC_MEM_EXC2_SIZE 20 #define ENC_PI_GAIN_SIZE 8 #define ENC_PITCH_SIZE 4 #define DEC_EXCBUF_SIZE 500 #define DEC_INTERP_QLPC_SIZE 10 #define DEC_OLD_QLSP_SIZE 10 #define DEC_MEM_SP_SIZE 20 #define DEC_PI_GAIN_SIZE 8 EncState enc_state; char enc_stack[NB_ENC_STACK]; spx_word16_t enc_winbuf[ENC_WINBUF_SIZE]; spx_word16_t enc_excbuf[ENC_EXCBUF_SIZE]; spx_word16_t enc_swbuf[ENC_SWBUF_SIZE]; spx_word16_t enc_lagwindow[ENC_LAGWINDOW_SIZE]; spx_lsp_t enc_old_lsp[ENC_OLD_LSP_SIZE]; spx_lsp_t enc_old_qlsp[ENC_OLD_QLSP_SIZE]; spx_mem_t enc_mem_sp[ENC_M...

...lock you've previously allocated. > In my current implementation, all the memory allocations are collected > together to form one big structure like below, > > typedef struct { > > EncState enc_state; > > char stack[NB_ENC_STACK]; > > spx_word16_t winBuf[80]; > > spx_word16_t excBuf[612]; > > spx_word16_t swBuf[612]; > > spx_word16_t lagWindow[22]; Yuk. That's so.... G.729 and ITU codecs :-) As much as you'd like something like that, it would be a pain to maintain it. If you...

...tor, but I just fixed an off-by-one overflow on the heap. Maybe that was the error and your debugger is just reporting a wrong offset. Could you try what's in the current svn (you were using svn already, right)? Jean-Marc > I have had a few issues with this sort of stuff- you could adjust NB_ENC_STACK > or SB_ENC_STACK (which ever you may be fiddling with) and see if the problem > goes away- could be the allocation for the vorbis psy tables takes up more > space than > the current stack size allows (not sure how allocated? Could be your > settings for > supporting alloca/etc...

...the inital stage since all the memories are allocated at the initial stage. In my current implementation, all the memory allocations are collected together to form one big structure like below, typedef struct { EncState enc_state; char stack[NB_ENC_STACK]; spx_word16_t winBuf[80]; spx_word16_t excBuf[612]; spx_word16_t swBuf[612]; spx_word16_t lagWindow[22]; ............................................ int pitch[16]; VBRState vbr; } speex_encoder_memory; The structure define...

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

...bspeex.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...

...e] Error 1 make[1]: Leaving directory `/tmp/speex-1.2rc1' make: *** [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 'VALG...

...; > > In my current implementation, all the memory allocations are collected > > together to form one big structure like below, > > > > typedef struct { > > > > EncState enc_state; > > > > char stack[NB_ENC_STACK]; > > > > spx_word16_t winBuf[80]; > > > > spx_word16_t excBuf[612]; > > > > spx_word16_t swBuf[612]; > > > > spx_word16_t lagWindow[22]; > > Yuk. That's so.... G.729 and ITU codecs :-) As much as you'd like > something li...

> When enabling and compiling this with mingw on Win32, my debugger > complains about heap overruns when calling speex_encoder_destroy(). This > could be a mingw issue though, as I also found a stackalignment bug which > prevents me from _USING_SSE (apparantly -mpreferred-stack-size is just > "prefered" and therefore ignored... *Sigh*). Just so I understand, the

Hi everyone, As you may have guess, Speex 1.2 is slowly approaching, though there's still a lot left to do so I can't say how long it'll take. I thought this was the right time to ask if there's anything missing or that can be improved to make 1.2 better. At this point, it can't be anything major, but there are still some changes that are possible, e.g: - Improving some

>> 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,