Displaying 5 results from an estimated 5 matches for "sb_dec_stack".
Did you mean:
nb_dec_stack
2006 Jan 02
2
Speex decode memory usage on an Arm processor (wideband)
...ssing power and I 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 er...
2006 Jan 03
1
Speex decode memory usage on an Arm processor (wideband)
> > 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 chang...
2005 Jun 06
1
Bug from revision 9316: SB_ENC_STACK misdefined
...7 @@
/* Default size for the encoder and decoder stack (can be changed at compile time).
This does not apply when using variable-size arrays or alloca. */
#ifndef SB_ENC_STACK
-#define SB_ENC_STACK (1000*sizeof(spx_sig_t))
+#define SB_ENC_STACK (10000*sizeof(spx_sig_t))
#endif
#ifndef SB_DEC_STACK
2006 Jan 02
0
Speex decode memory usage on an Arm processor (wideband)
...mpiled 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.
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 h...
2005 May 25
3
Speex on TI C6x, Problem with TI C5x Patch
>> 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,