Displaying 7 results from an estimated 7 matches for "early_ratio_short".
2005 Sep 18
2
How does the jitter buffer "catch up"?
...ing, you'd need to increase
> SPEEX_JITTER_MAX_BUFFER_SIZE to the longest delay you're expecting, and
> then inside the block on line 231 (which says)
> if (late_ratio_short + ontime_ratio_short < .005 && late_ratio_long +
> ontime_ratio_long < .01 && early_ratio_short > .8)
> .. add something that multiplies all the magins with 0.75 or so at the
> end. This will force the jitter buffer to only skip 1 frame at a time and
> wait a bit before it skips the next one.
Don't think it's necessary since there's already some code that shifts
the...
2005 Sep 18
0
How does the jitter buffer "catch up"?
...gt;
> 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 might be worth mentioning: the sum of all the margins will
never be higher than 1.0, so a test for early_ratio_short > 0.7 means
(roughly) that 70% or more of the packets in the last short-term time
period were early.
>> Depending on your chosen transmission method, during network hiccups
>> you'll either have lost packets or they'll come in a burst when the
>> network conditions r...
2007 Mar 08
4
Introduction and patch
Hi,
I'm one of the people working on the Rockbox project
(http://www.rockbox.org) which is an open source alternative firmware
for a range Digital Audio Players. Recently we integrated support for
the Speex codec using libspeex and seems to work well. If you could add
Rockbox to your list of software that supports Speex, that'd be great.
So that's the introduction done. Now for
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
2007 Mar 08
0
Introduction and patch
...cket->len;j++)
> + for (j=0;((unsigned)j)<packet->len;j++)
> jitter->buf[i][j]=packet->data[j];
> jitter->timestamp[i]=packet->timestamp;
> jitter->span[i]=packet->span;
> @@ -251,7 +251,7 @@
> float ontime_ratio_long;
> float early_ratio_short;
> float early_ratio_long;
> - int chunk_size;
> + int chunk_size = 0;
> int incomplete = 0;
>
> if (jitter->interp_requested)
> @@ -369,7 +369,7 @@
> /* Check for potential overflow */
> packet->len = jitter->len[i];
>...
2005 Sep 18
0
How does the jitter buffer "catch up"?
...t you're describing, you'd need to increase
SPEEX_JITTER_MAX_BUFFER_SIZE to the longest delay you're expecting, and
then inside the block on line 231 (which says)
if (late_ratio_short + ontime_ratio_short < .005 && late_ratio_long +
ontime_ratio_long < .01 && early_ratio_short > .8)
.. add something that multiplies all the magins with 0.75 or so at the
end. This will force the jitter buffer to only skip 1 frame at a time and
wait a bit before it skips the next one.
2005 Sep 18
2
How does the jitter buffer "catch up"?
...u'd need to
> increase SPEEX_JITTER_MAX_BUFFER_SIZE to the longest delay
> you're expecting, and then inside the block on line 231 (which says)
> if (late_ratio_short + ontime_ratio_short < .005 &&
> late_ratio_long + ontime_ratio_long < .01 &&
> early_ratio_short > .8) .. add something that multiplies all
> the magins with 0.75 or so at the end. This will force the
> jitter buffer to only skip 1 frame at a time and wait a bit
> before it skips the next one.
>
> _______________________________________________
> Speex-dev mailing list...