Displaying 3 results from an estimated 3 matches for "arrivel".
Did you mean:
arrives
2005 Sep 18
0
How does the jitter buffer "catch up"?
..., protect speex_jitter_put/get with a mutex
(CRITICAL_SECTION I believe they're called in Win32Speak) -- calling put
and get at the exact same time from different threads leads to "features")
This allows the jitter buffer to actually buffer, and try to keep the
delay between frame arrivel and frame play to a minimum.
As for detecting outages, a hack I use is to check jitter->valid_bits. If
it's set, we decoded "something", if it's not, we're interpolating
something which may not sound that good so feed the soundcard 20ms of
silence instead.
Incidentally...
2005 Sep 22
0
How does the jitter buffer "catch up"?
...ads, protect speex_jitter_put/get with a mutex
(CRITICAL_SECTION I believe they're called in Win32Speak) -- calling put
and get at the exact same time from different threads leads to "features")
This allows the jitter buffer to actually buffer, and try to keep the
delay between frame arrivel and frame play to a minimum.
As for detecting outages, a hack I use is to check jitter->valid_bits. If
it's set, we decoded "something", if it's not, we're interpolating
something which may not sound that good so feed the soundcard 20ms of
silence instead.
Incidentally, o...
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_X...