search for: jitter_buffer_insert

...cked by the JitterBuffer itself. Why is this necessary? Correspondingly, how is the internal JitterBuffer state affected by calling jitter_buffer_get (and _tick) before jitter_buffer_put has a chance to deliver the first packet of a stream? Should this be avoided? jitter_buffer_get can return JITTER_BUFFER_INSERTION and JITTER_BUFFER_MISSING. In both situations speex_jitter_buffer.c makes the codec interpolate a frame. How are these conditions different, and is there a better recommended strategy for handling one versus the other? Am I correct that calling jitter_buffer_update_delay might eventuall...

...ays assumed there wouldn't be any overflows. What parameter range are you using that causes them? I can always switch to 32-bit, but I prefer 16-bit for memory size reasons (I'll switch if there's no other option). > But now I have another question. If jitter_buffer_get returns > JITTER_BUFFER_INSERTION or JITTER_BUFFER_MISSING, packet->span can be > larger than desired_span or the normal packets' span. Must the > application take this into account? If so, speex_jitter_buffer does > not handle this correctly at the moment. Well, you can choose the size of the insertions or conc...

...etimes exceed +-32k in my opinion. Therefore I thought using spx_int32_t was the simplest solution. But of course you can alternatively check for overflows in shift_timings as it's already done in update_timings. > > But now I have another question. If jitter_buffer_get returns > > JITTER_BUFFER_INSERTION or JITTER_BUFFER_MISSING, packet->span can be > > larger than desired_span or the normal packets' span. Must the > > application take this into account? If so, speex_jitter_buffer does > > not handle this correctly at the moment. > Well, you can choose the size of the...

..._buffer_put has a > chance to deliver the first packet of a stream? Should this be avoided? At this point, this should probably be avoided (I've heard of problems when doing that), but eventually this is a case the jitter buffer should be able to handle. > jitter_buffer_get can return JITTER_BUFFER_INSERTION and > JITTER_BUFFER_MISSING. In both situations speex_jitter_buffer.c makes > the codec interpolate a frame. How are these conditions different, and > is there a better recommended strategy for handling one versus the > other? At this point, the only way to do an insertion w...

...o play, I invoke jitter_buffer_get(), right? The questions that I have are: - what does the method jitter_buffer_get() return when it has no frame? JITTER_BUFFER_MISSING? In this case, should I say "no data" to the audio output stream? - what does it mean when jitter_buffer_get() returns JITTER_BUFFER_INSERTION? The comment "/** A "fake" packet is meant to be inserted here to increase buffering */" is not particularly clear to me. - how do I determine the initial size of the jitter buffer? - how does the jitter buffer resize itself during its operation? - can this jitter buffer be u...