Displaying 4 results from an estimated 4 matches for "arrival_margin".
2005 Sep 18
3
How does the jitter buffer "catch up"?
Is is possible to give a short hint about how the jitter buffer would
"catch up" when network condition have been bad and then get better?
I'm using the jitter buffer with success now, but sometimes I have a
long delay that's caused by bad network conditions and then later when
the conditions get better, I would think we would want the audio to
gradually catch up with real-time
2005 Sep 18
0
How does the jitter buffer "catch up"?
...er buffer functionality?
>
> Thank you very much.
>
> Baldvin
>
>
FYI: The below is just my interpretation of the code, I might be wrong.
Each time a new packet arrives, the jitter buffer calculates how far ahead
or behind the "current" timestamp it is; this is called arrival_margin.
The "current" timestamp is simply the last frame successfully decoded.
It maintains a list of bins for margins, this is short and longterm
margin.
Think of the bins like this:
-60ms -40ms -20ms 0ms +20ms +40ms +60ms
when a packet arrives, the margin matching it's arrivel_margi...
2005 Sep 18
2
How does the jitter buffer "catch up"?
...gt; >
> > Baldvin
> >
> >
>
> FYI: The below is just my interpretation of the code, I might
> be wrong.
>
> Each time a new packet arrives, the jitter buffer calculates
> how far ahead or behind the "current" timestamp it is; this
> is called arrival_margin.
> The "current" timestamp is simply the last frame
> successfully decoded.
>
> It maintains a list of bins for margins, this is short and
> longterm margin.
>
> Think of the bins like this:
>
> -60ms -40ms -20ms 0ms +20ms +40ms +60ms
>
> when a pa...
2005 Sep 18
2
How does the jitter buffer "catch up"?
...ode, I might be wrong.
Most of it is right. Actually, would you mind if I use part of your
email for documenting the jitter buffer in the manual?
> Each time a new packet arrives, the jitter buffer calculates how far ahead
> or behind the "current" timestamp it is; this is called arrival_margin.
> The "current" timestamp is simply the last frame successfully decoded.
Minor detail, it's the last played (whether it was successfully decoded
or not).
> It maintains a list of bins for margins, this is short and longterm
> margin.
> Think of the bins like this:
&g...