Displaying 5 results from an estimated 5 matches for "jb_get".
Did you mean:
ib_get
2007 Dec 27
1
SIP Channel jitter buffer issue
....conf parameters jenable=yes, jbforce=yes,
jbmaxsize=200 and jbimpl=fixed. However on setting these parameters I am
unable to hear on the trunk side. From the jitter logs as given below, I can
see audio frames being dropped:
JB_PUT {now=1130}: Dropped frame with ts=21125 and len=20
JB_GET {now=1130}: now < next=2121
JB_GET {now=1142}: now < next=2121
JB_GET {now=1163}: now < next=2121
JB_PUT {now=1181}: Dropped frame with ts=21132 and len=20
JB_GET {now=1181}: now < next=2121
JB_GET {now=1183}: now < next=2121
JB_P...
2006 May 03
2
New jitter.c, bug in speex_jitter_get?
> Yes. Jean-Marc has made the API more similar.
>
> Jean-Marc: Have you looked at the API we have for the
> asterisk/iaxclient jitterbuffer?
Just did.
> It's pretty close to what you have now -- the major difference is that
> your jb still assumes it can "own" the data passed in -- it copies it,
> and it destroys it at will. With the API I put together,
2006 May 03
0
New jitter.c, bug in speex_jitter_get?
...re about that one. The problem is what to do when you
> need to discard. You seem to say you return it and ask the user to
> destroy it (how?), but this seemed a bit error prone to me.
We just return a frame with the return value JB_DROP, which tells the
caller to drop this frame, and call jb_get again.
When the caller is done with the jitterbuffer, it calls jb_getall()
repeatedly, until it's empty, and then it can discard all the frames.
> And it's not
> like copying data is that expensive compared to decoding it.
Perhaps it's not expensive, but it's unnecessary...
2006 May 03
2
New jitter.c, bug in speex_jitter_get?
> We just return a frame with the return value JB_DROP, which tells the
> caller to drop this frame, and call jb_get again.
>
> When the caller is done with the jitterbuffer, it calls jb_getall()
> repeatedly, until it's empty, and then it can discard all the frames.
Hmm, looks a bit error-prone to me. Especially considering I still have
to explain that "no, you can't pass ulaw instead o...
2006 May 03
0
New jitter.c, bug in speex_jitter_get?
On May 3, 2006, at 9:12 PM, Jean-Marc Valin wrote:
>> We just return a frame with the return value JB_DROP, which tells the
>> caller to drop this frame, and call jb_get again.
>>
>> When the caller is done with the jitterbuffer, it calls jb_getall()
>> repeatedly, until it's empty, and then it can discard all the frames.
>
> Hmm, looks a bit error-prone to me. Especially considering I still
> have
> to explain that "no, you...