search for: desired_span

...auses 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 concealment, so I'm not sure what's the problem. The app definitely needs to u...

Hi, I see you're changing the jitter buffer around quite a bit. Could you let us know when it's ready for general testing? (At the moment it doesn't handle missing packets at all) Best wishes, Thorvald

...ible) so I can fix it? Also, I'd be very interesting in getting test "data" for the jitter buffer. By that I mean, just a log of how you are calling it. More specifically: - Every time you call _put(), print the timestamp and span of the packet - Every time you call _get(), print the desired_span argument (it's a new argument) - Every time you call _tick(), with no argument. For example, the file could look like: PUT 1000 100 GET 100 TICK PUT 1100 100 GET 100 TICK ... That would help me make sure that the jitter buffer works for your case. I actually encourage everyone using the jitt...

...ion. 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 insertions or concealment, so I'm > not sure what's the problem. The app de...

...lso, I'd be very interesting in getting test > "data" for the jitter buffer. By that I mean, just a log of how you are > calling it. More specifically: > > - Every time you call _put(), print the timestamp and span of the packet > - Every time you call _get(), print the desired_span argument (it's a > new argument) > - Every time you call _tick(), with no argument. > > For example, the file could look like: > > PUT 1000 100 > GET 100 > TICK > PUT 1100 100 > GET 100 > TICK > ... > > That would help me make sure that the jitter buffe...

...itterBufferPacket *packet) +EXPORT void jitter_buffer_put(JitterBuffer *jitter, const JitterBufferPacket *packet) { int i,j; int late; @@ -459,7 +459,7 @@ } /** Get one packet from the jitter buffer */ -int jitter_buffer_get(JitterBuffer *jitter, JitterBufferPacket *packet, spx_int32_t desired_span, spx_int32_t *start_offset) +EXPORT int jitter_buffer_get(JitterBuffer *jitter, JitterBufferPacket *packet, spx_int32_t desired_span, spx_int32_t *start_offset) { int i; unsigned int j; @@ -674,7 +674,7 @@ } -int jitter_buffer_get_another(JitterBuffer *jitter, JitterBufferPacket *pack...

...itterBufferPacket *packet) +EXPORT void jitter_buffer_put(JitterBuffer *jitter, const JitterBufferPacket *packet) { int i,j; int late; @@ -459,7 +459,7 @@ } /** Get one packet from the jitter buffer */ -int jitter_buffer_get(JitterBuffer *jitter, JitterBufferPacket *packet, spx_int32_t desired_span, spx_int32_t *start_offset) +EXPORT int jitter_buffer_get(JitterBuffer *jitter, JitterBufferPacket *packet, spx_int32_t desired_span, spx_int32_t *start_offset) { int i; unsigned int j; @@ -674,7 +674,7 @@ } -int jitter_buffer_get_another(JitterBuffer *jitter, JitterBufferPacket *pack...