search for: speex_jitter_

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

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

Hi All We are working on an ARM-based speaker phone application where the speaker and microphone is placed roughly 8 cm from each other (similar to this one: http://www.voipsupply.com/images/CHAT50SPLASH.jpg). We are using Speex AEC and preprocessor to handle the acoustic echo. The AEC typically contribute with ERLE of 15-20 dB which should be as expected from the algorithm. Additionally we need

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:...

Hi, A while ago I mentioned I was considering splitting libspeex into two parts. I'm attaching a patch that does exactly that, but I haven't applied it to svn because I first want to have some feedback. That patch leaves the codec in libspeex and moves the other stuff (jitter buffer, AEC, preprocessor, ...) to libspeexvoip (I'm open to suggestions on better names). Some of the things