search for: crashbug

...urrent packet, and replaces it with the new one (let's call it newest). get now starts decoding, but the index it found now points to the newest packet, which it will decode and remove from the buffer. Granted, it's not terribly likely to happen, and the jitter-buffer as a whole has no crashbugs regarding two-thread access, but it will sound a bit odd if this should ever happen :) >> 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...

> (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