Displaying 6 results from an estimated 6 matches for "winbuf".
Did you mean:
inbuf
2006 Nov 15
2
Quick survey for Speex 1.2
...; 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 want
everything in one chunk, just...
2007 Aug 07
1
Attempting to shrink speex: Are these functions necessary?
I'm glad to hear that my data size 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 a...
2006 Nov 15
0
Quick survey for Speex 1.2
...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 defined above is used to allocat...
2006 Nov 15
0
Quick survey for Speex 1.2
...emory 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. I...
2007 Aug 07
0
Attempting to shrink speex: Are these functions necessary?
...r that my data size 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
What I meant is that you can reduce the stack part (assuming you're not
already using VAR_ARRAYS or USE_ALLOCA). The other...
2006 Nov 13
13
Quick survey for Speex 1.2
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