search for: jitter_buffer_

Hi. After changing my code to construct a JitterBufferPacket and passing that to speex_jitter_put, my program works with the new jitter buffer using the wrapper functions (speex_jitter_* instead of the new jitter_buffer_*). However, a lot of warning: did you forget to call jitter_buffer_tick() by any chance? is displayed. Looking at speex_jitter_get, the logic seems to be as follows: if there is another frame in the previously fetched packet, decode it and call jitter_buffer_tick else get a new packet and decod...

Le mardi 02 mai 2006 ? 18:15 +0200, Thorvald Natvig a ?crit : > Hi. > > After changing my code to construct a JitterBufferPacket and passing that > to speex_jitter_put, my program works with the new jitter buffer using the > wrapper functions (speex_jitter_* instead of the new jitter_buffer_*). Oops, I forgot to make sure I keep the API stable for the old buffer. Any thoughts on the change (revert or continue as is)? > However, a lot of > warning: did you forget to call jitter_buffer_tick() by any chance? > is displayed. > > Looking at speex_jitter_get, the logic seem...

...is this still true or they've been joined? Downloading the 1.2rc1 source code there's no trace of the SpeexJitter structure and wrapper functions included in the speex_jitter_buffer.h / speex_jitter_buffer.c, are these files obsolete? Do I have to directly use the functions that start with jitter_buffer_? The second question is related to the timestamp and the packet span. I'd use with nb decoder 160 for the span but, what about the timestamps? Somewhere I've read that the timespan increments are meant to be in milliseconds, so I should increase the timestamp value of each packet increseing...

>> After changing my code to construct a JitterBufferPacket and passing that >> to speex_jitter_put, my program works with the new jitter buffer using the >> wrapper functions (speex_jitter_* instead of the new jitter_buffer_*). > > Oops, I forgot to make sure I keep the API stable for the old buffer. > Any thoughts on the change (revert or continue as is)? Well, I presume the idea of keeping speex_jitter_* around is to enable old programs to compile "out of the box" with newer versions of speex wit...