search for: arrivel_margin

Displaying 4 results from an estimated 4 matches for "arrivel_margin".

Did you mean: 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"?
...rrival_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_margin is increased, so if this packet was 40ms after the current timestamp, the 40ms bin would be increased. If this packet arrived 60ms too late (and hence is useless), the -60ms bin would increase. early_ratio_XX is the sum of all the positive bins. late_ratio_XX is the sum of all the negative bins...
2005 Sep 18
2
How does the jitter buffer "catch up"?
...ply 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_margin is increased, so if this packet was 40ms after > the current timestamp, the 40ms bin would be increased. If > this packet arrived 60ms too late (and hence is useless), the > -60ms bin would increase. > > early_ratio_XX is the sum of all the positive bins. > late_ratio_XX is th...
2005 Sep 18
2
How does the jitter buffer "catch up"?
...ail, 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: > -60ms -40ms -20ms 0ms +20ms +40ms +60ms > when a packet arrives, the margin matching it's arrivel_margin is > increased, so if this packet was 40ms after the current timestamp, the > 40ms bin would be increased. If this packet arrived 60ms too late (and > hence is useless), the -60ms bin would increase. Right. > early_ratio_XX is the sum of all the positive bins. > late_ratio_XX is...