Displaying 3 results from an estimated 3 matches for "speex_decode_bit".
Did you mean:
speex_decode_bits
2004 Dec 21
2
Jitter buffer
...oesn't necessarily know if the speex
codec is loaded..
And later, it might also be useful to have an API which takes a bunch of
SpeexBits, and gives the caller a way to split up the SpeexBits into
separate 20ms frames. [The first API could be a subset of this].
The main API would be:
int speex_decode_bits(SpeexBits *inBits, SpeexBits*outBits).
inBits is SpeexBits containing the bits we're interested in.
outBits may be NULL. If not NULL, and inBits contains valid frames,
they are written, one frame per call, to outBits.
it would return the same values as speex_decode(_int).
SpeexBits inBi...
2004 Dec 21
0
Jitter buffer
...ke
that idea.
Jean-Marc
> And later, it might also be useful to have an API which takes a bunch
> of SpeexBits, and gives the caller a way to split up the SpeexBits
> into separate 20ms frames. [The first API could be a subset of this].
>
> The main API would be:
>
> int speex_decode_bits(SpeexBits *inBits, SpeexBits*outBits).
>
> inBits is SpeexBits containing the bits we're interested in.
> outBits may be NULL. If not NULL, and inBits contains valid frames,
> they are written, one frame per call, to outBits.
>
> it would return the same values as speex_...
2004 Nov 17
3
Jitter buffer
Jean-Marc Valin wrote:
>>Heh. I guess after playing with different jitter buffers long enough,
>>I've realized that there's always situations that you haven't properly
>>accounted for when designing one.
>>
>>
>
>For example? :-)
>
>
I have a bunch of examples listed on the wiki page where I had written
initial specifications: