search for: early_ratio_xx

...s > 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 the sum of all the negative bins. Right. And only the packets that are "just in time" don't get counted in any ratio. > The difference between _long and _short is just how fast they change. > > If a packet has time...

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

...-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. The difference between _long and _short is just how fast they change. If a packet has timestamp outside the bins, it's not used for calculation. Now, clearly, if early_ratio is high and late_ratio is very...

>> FYI: The below is just my interpretation of the code, 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? It would be my pleasure :) >> early_ratio_XX is the sum of all the positive bins. >> late_ratio_XX is the sum of all the negative bins. > > Right. And only the packets that are "just in time" don't get counted in > any ratio. Well.. they're counted in the ontime_ratio_long and _short, right? One thing that m...

...gt; 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. > > The difference between _long and _short is just how fast they change. > > If a packet has timestamp outside the bins, it's not used for > calculation. > > Now, clearly, if e...