Displaying 2 results from an estimated 2 matches for "speex_jitter_blabla".
2007 Jul 10
1
In-band user data
...rameter is included to allow coming up iterations of the
> jitter-buffer to improve the perceived quality by changing the packet,
> without changing the API.
>
Ah, so the data in the jitter buffer should still be a pure speex
packet? I thought one of the reasons for moving away from
speex_jitter_blabla was to make the jitter buffer more generic? I'm
currently using 1 byte before the packet for metadata which accompanies
each and every packet. I could move that to in-band user data as well,
but that would mean it's 2 bytes instead of 1 :(
2007 Jul 07
3
In-band user data
Hi,
I'm moving my "metadata" which accompanies some of the speech packets
into the speex bits. However, as usual, I'm a bit confused.
The manual (PDF from current SVN), section 5.10 (bottom of page 21)
states that:
"Finally, applications may define custom in-band messages using mode 13.
The size of the message in bytes is encoded with
5 bits, so that the decoder can