similar to: Echo Canceller on Windows Mobile

Hi Jean Marc, We are running the speex echo canceller code on a Windows Mobile smartphone using a TI OMAP 201MHz 850. We are making voip calls and audio is working without echo canceller code. Simply adding the following 2 functions whether the echo cancellation is wired in (ie we use the output frame ) or not performance becomes terrible. Note 2 separate threads are used to handle audio.

Hi, I am new to speex so please redirect me to some links if the question is repetative. Just for testing the echo canceller performance, I have added mdf,fftwrap,misc,kiss_fftr,kiss_fft source files to my project. Now In my multithread application when I receive packets from mice, I calls speex_echo_capture(echo_state, input_frame, output_frame,Youtput_frame) with input_frame as

Hello, i'm adding echo cancellation to my voip application, but when i call speex_echo_capture() or speex_echo_playback() causes an assertion failed, it seens that there is a delete in any where. i've encapsulated echo canceller in a class that storage the state and simply call the functions: void EchoCanceller::Playback(short *echo_frame) { speex_echo_playback(echo_state,

Anton A. Shpakovsky <saa <at> tomsksoft.com> writes: > > As for me - speex_echo_cancellation is a better choise. Try using it in > capture thread instead > of those speex_echo_capture and speex_echo_playback functions. > > And please, describe your problem in details. Cause the fact that you > "didn get echo cancellation" > doesn't mean you are

Well, I'm not a professional in AEC theory, but what I've mentioned is: speex_echo_state_init(20, 320*10) - frame size should correspond to 20ms. At your sampling rate (16000hz) is should be 16K*0.02 = 320. The same I can notice about echo tail. 100ms: 16000*0.3 = 4800, not 3200 as you has. But that's not crucial I think. Just wanna you get the point. "Internally,

I did the test on another PDA which runs XScale 416Mhz CPU, the EAC arithmetic could be done in 1ms, but for the previous PDA (TI OMAP 168Mhz), it take more than 100ms! Though EAC could run in time on the new PDA, it did no help to cancel the echo, here is my test scenario: Init echo_state: echo_state=speex_echo_state_init(160,1120); int tmp=8000;

Can you first try the svn version (or apply https://trac.xiph.org/changeset/11882). As I mentioned in a previous email, there's a bad bug in the 1.2beta1 echo canceller. Jean-Marc Coffey, Michael a ?crit : > Hi Folks, > > I am having trouble using speex_echo_cancel. As a starting point, I am > using the testecho.c source code. I compiled the 1.2beta1 version. I > have not

Hello all. A few questions on using speex's echo cancellation, for clarifying: 1) I assume that the echo_frame in this method: speex_echo_playback(echo_state, echo_frame) is just raw "pcm_s16le" type bits/data? I'm a bit new to all this... 2) I assume from this thread: http://lists.xiph.org/pipermail/speex-dev/2009-March/007151.html that speex_echo_playback and

Hi Folks, I am having trouble using speex_echo_cancel. As a starting point, I am using the testecho.c source code. I compiled the 1.2beta1 version. I have not tried any other versions of speex. The document says that the order of arguments to Speex_echo_cancel is (echo_state, input_frame, echo_frame, output_frame, residue) where "input_frame" is as captured from mic and

Terrific! The patch fixes my problem quite decisively. I will want to use this with a 16K sample rate. Is it expected to work well with just another slight patch, or will we need to modify it more deeply? Also, are there any tunable parameters besides tail length? I am wondering about the aggressiveness of adaptation and I know you are an expert in that area. Thanks so much, Michael

Hi, when I use preprocessor with AEC, VC++ alerts me about heap corruption. I have protected speex_echo_playback, speex_echo_capture and speex_preprocess_run with mutexes, to avoid echo_state being used at the same time, but it still happens. Any help about this ussue? Thank you.

2006/11/2, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca>: > > Today I tried speex echo cancellation on my VoIP application running > > on a windows mobile based PDA (OMAP1510 168MHz). The result is > > disappointing: it takes 150-250 ms to do echo cancellation (by calling > > speex_echo_capture() ) for a 20 ms frame! > > Are you by any chance using an insane

Hi So in your case if you don't want to use speex_echo_cancellation than you should do next way: Save the playback frames (clean echo) within separate playback thread with speex_echo_playback func. Then use speex_echo_capture - it will remove the clean echo frame (saved with speex_echo_playback func) from const spx_int16_t *rec buffer (saved with speex_echo_capture) and you will get

Hi, my VoIP system uses speex with framesize = 160 samples(20 ms) at 8khz, sending and receiving paquets of 1600 samples(200 ms). When I receive a packet, I buffered it (I have also tried with speex_echo_playback) before sending to the speaker. When I capture from microphone, I fist remove DC offset (I saw in OPAL sources) and then I call speex_echo_cancellation for every one of the 10

Welcome everybody. I am new here on the list. Thank you very much for speex encoder and decoder. They are working great. I compile speex coded for str911 Arm processor. But I have a big problem with echo canceller from 1.1.12 speex package. I create echo canceler state: SpeexEchoState * echo_state = speex_echo_state_init(FRAME_SIZE, FRAME_SIZE * 5); FRAME_SIZE is in my project 160 samples.

hi, I tried to encode the voice data read from AudioQueue and then decode it. There was nothing but rhythm left, it sounds like robot's voice, but I cannot recognize any word. The app was compiled by XCode 4.1. Speex 1.0.5 and 1.2.rc1 gave the same result. When compiling speex 1.0.5, I added them to Xcode project, set the Header Search Paths, then compiled successfully. When compiling speex

Hello, We are experiencing a few problems with Speex AEC. We are using it to process audio data on a real time stream over IP with Speex codec (frame size = 320). We initialize the echo state like this : SpeexEchoState * echo_state; echo_state = speex_echo_state_init(320,512); int sr = 16000; speex_echo_ctl(echo_state, SPEEX_ECHO_SET_SAMPLING_RATE,&sr); We are not really sure about

All, The implementation of SPEEX_PREPROCESS_GET_ECHO_STATE in preprocess.c seems to be broken. The value of the echo_state pointer is assigned to the stack variable rather than to the memory location pointed to by the stack variable. Code snippet from preprocess.c: case SPEEX_PREPROCESS_GET_ECHO_STATE: ptr = (void*)st->echo_state; break; It seems as though the code should

There were little changes when I activate "echo cancel" without AGC. And activating "echo cancel" with AGC results poor voice quality. The relationship between input frame and echo frame is written to "very important" in SpeeX 1.1.11.1 manual. And I use "previous decoded data" for echo frame. <<<<---- no problem??? I show you again my code

As for me - speex_echo_cancellation is a better choise. Try using it in capture thread instead of those speex_echo_capture and speex_echo_playback functions. And please, describe your problem in details. Cause the fact that you "didn get echo cancellation" doesn't mean you are doing smth wrong. Regards, Anton A. Shpakovsky -----Original Message----- From: speex-dev-bounces at