search for: blooiiing

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

...y to > > get better quality than just putting zeros. > > Actually, I oversimplified a bit. I check if valid_bits has been zero for > the last 4 frames or more, because once you interpolate more than 100ms > from the last known state, you end up with some weird > blipp-blopp-blooiiing sound. Actually it reminds me of the ambient sound > of weird aliens in bad 50s scifi movies. At that point, silence is much > better :) Then it would be a problem with the packet loss concealment. It's actually decreasing the level of the interpolated audio with time. Maybe it's n...

...nterpolating a frame is exactly to > get better quality than just putting zeros. Actually, I oversimplified a bit. I check if valid_bits has been zero for the last 4 frames or more, because once you interpolate more than 100ms from the last known state, you end up with some weird blipp-blopp-blooiiing sound. Actually it reminds me of the ambient sound of weird aliens in bad 50s scifi movies. At that point, silence is much better :)

...et better quality than just putting zeros. >> >> Actually, I oversimplified a bit. I check if valid_bits has been zero for >> the last 4 frames or more, because once you interpolate more than 100ms >> from the last known state, you end up with some weird >> blipp-blopp-blooiiing sound. Actually it reminds me of the ambient sound >> of weird aliens in bad 50s scifi movies. At that point, silence is much >> better :) > > Then it would be a problem with the packet loss concealment. It's > actually decreasing the level of the interpolated audio with ti...