search for: win32speak

> (PS, if you do use threads, 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") I've never tested this, but I designed the jitter buffer to work from two threads even without using a mutex. This would work as long as there is one thread doing the "put" and...

>> (PS, if you do use threads, 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") > > I've never tested this, but I designed the jitter buffer to work from > two threads even without using a mutex. This would work as long as there > is one thread doing th...

Thank you for a very good explanation which shed light on some of the questions that I had after reading the source code. Reading your text however, I wonder if I'm perhaps missing an important point on the proper use of the jitter buffer: ... > Now, clearly, if early_ratio is high and late_ratio is very > low, the buffer is buffering more than it needs to; it will > skip a frame

...et arrived in the last 20 ms, you should still call speex_jitter_get, and no matter if 100 packets arrived in the last 20 ms, you should still only call speex_jitter_get once. (PS, if you do use threads, 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...

...acket arrived in the last 20 ms, you should still call speex_jitter_get, and no matter if 100 packets arrived in the last 20 ms, you should still only call speex_jitter_get once. (PS, if you do use threads, 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_b...