search for: speexjitter

Hi! I am still trying to clean the voice after procesing it with speex echo cancellation filter. I get some artifacts, the echo is removed, but you can here some metallic voices in background. Jean, in your test client you are using UDP connection and SpeexJitter to make sure UDP packets are in order. What if I use TCP/IP, do I still have to use SpeexJitter when using speex_echo_cancel ? regards hs

...stions about the speex_jitter_buffer when used with DTX here goes: I want to use the speex_jitter_buffer with muliple streams (multi client) and with DTX so that clients will only transmit data when they are actually saying anything, but Im unsure of how the ticking is handled. I have 1 x SpeexJitter struct per client stream Im using portaudio and Im planning on using the callback to iterate through all the buffers getting decoded frames. There is no upper limit (in theory) to how many client streams/buffers there can be and as far as I can see the speex_jitter_get(..) performs quite a b...

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

...the speex codec to speed things up, in case it's a speed of processing issue? I am seeing a fair number of problem records coming out of the speex jitter buffer, but they might just mean that data isn't being fed in fast enough into the buffer. I'm checking: speex_jitter_get(&speexJitter, (short *)newData, NULL); if (speexJitter.valid_bits == 0) //bad record { fprintf(stderr, "Interpolating since nothing happened!!!!\n"); fflush(stderr); } Does this say I'm processing too slowly into the buffer, or that the data put in is somehow corrupt? The application is Windows...

...er. First of all, I'm a bit confused about the code to use. Googling the subject I've find that there are, or there were, two jitter buffers, a generic one and a speex-specific one, 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 t...

Oh, I forgot to mention one thing. I currently append a few bits of custom information to each speex packet which I fetch out with things like speex_bits_unpack_unsigned(&sjJitter.current_packet, 1); It would be very usefull if the jitter buffer didn't actually decode the packet, but instead returned a pointer to it (or NULL if you should play silence and -1 if you should repeat the