similar to: frame_size parameter

Hi Jean, Thank you for your reply. Ok... I'm gonna use 'samples per channel' everywhere I see 'samples'... but what about the 'speex_echo_playback' function ? it does the following loop: ... for (i=0;i<st->frame_size;i++) st->play_buf[st->play_buf_pos+i] = play[i]; ... So... if frame size is 'samples per channel' it will copy only half the

In stereo mode, you need to use the init_mc() call and consider the number of samples *per channel*. Also, more than 20 ms frames are a bad idea. Jean-Marc danflu at uninet.com.br a ?crit : > Hi, > > I'm using the echo cancellation api and I would like to > clarify the 'frame_size' parameter used in > speex_echo_state_init(frame_size,filter_length). > > >

Hello guys, I want to make echo tail parameter in my app changeable during run-time. So my question is:f Should I use speex_echo_state_reset function for this? Just call speex_echo_state_init function with new values after that? Or perform a full de-initialization and initialize echo cancellation with new tail value? I'm also using preprocessor - does the same apply to it?

Hi, I would like to have some more information about the parameter of speex_echo_state_init. I have a clear idea of the importance of the filter_length in the echo cancellation, what it is more obscure for me is the role of frame_size and how its value affect the algorithm. Let use, for example, frame_size = 400, would I obtain the same result of using frame_size = 200 but with half method call?

Hello, I would like to test the echo cancel algorithm available in unstable version 1.1.4. This echo canceller can be used with other codecs like G711? Somebody could send me some documentation or sample, or explain the next functions: SpeexEchoState *speex_echo_state_init(int frame_size, int filter_length); void speex_echo_state_destroy(SpeexEchoState *st); void

Hello, I've just caught a strange crash in speex_echo_state_init routine. It happened only on one WinXP machine, while on others using XP, Vista and 7 everything is fine. Crash occures in mdf.c line 434: st->spec_average = DIV32_16(SHL32(EXTEND32(st->frame_size), 15), st->sampling_rate); Got any ideas or should I provide more information of the OS? Thanks a lot!

Hi, I've been reading the speex echo cancellation documentation and it says : ".... It is important that, at any time, any echo that is present in the input has already been sent to the echo canceller as echo_frame. ... "; All I'm doing in the echo cancellation process is initializing it once with a call to : SpeexEchoState* speex_echo_state_init(int frame_size, int

Hi Jim, I've just been made aware of these problems (look for the thread "speex echo cancellation limitations"). It's on my short-term TODO list. > If fftwrap.c, I ifdefed out the spx_fft_float and spx_ifft_float routines, > because there were not used and required smallft.c (which is not so small at > all) to be added to the build. Right, need to cleanup that

My data is speech sampled as pcm mono 32khz. I want to use vad for regulating the agc gain mechanism. So... if voice is not detected I just reduce the agc value in order to not amplify the 'silence' otherwise we just increase the agc value if it is below the minimum. Thanks, Daniel ----- Original Message ----- De: Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> Para: danflu at

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

"frame_size = PCM audio in signed 16-bit format (native endian). There must be exactly frame_size samples per channel." Sorry for such a simple request, but could you please clarify the definition of frame_size when using stereo audio channels? When you say "frame_size samples" does this mean that, if my frame_size is defined as 128, there are 64 left samples and 64 right

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

Jean-Marc Valin wrote: > I suggest you have a look at the new API I introduced in svn (see > testecho.c). It's easier to use, harder to screw up, and it means I can > improve it in the future without breaking things. > > Jean-Marc Thanks for your response. Yes, I followed The World Institute for Mental Health recommendation. :) But I think the problem might still present

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

Hi Anton Thanks for the info... What if I use this function do I still need to sync the playback and capture? Assuming that the captured voice (*rec) already contains the echo which I need to cancel out... -------------------------------- void speex_echo_capture (SpeexEchoState *st, const spx_int16_t *rec, spx_int16_t *out) Parameters: st Echo canceller state rec signal

Hi Ted, Thanks a lot for this analysis. > In FLOAT_DIVU() it hangs at the following: > while (a.m >= b.m) > { > e++; > a.m >>= 1; > } > for the case where a and b are both zero (yes, division by zero). > This happens from mdf.c: True, that needs to be fixed even after I fix the rest. > leak_estimate =

Aha. By "frames" I assume you mean 10ms or 20ms or whatever I have passed as frame_size to speex_echo_state_init. Correct? (I suppose I could go to a smaller frame size if desiring finer precision.) I gather that prop[] contains proportional adaptation rates. I guess I'll have to read up on the MDF algorithm to get a better sense of what that means. Thanks -----Original

? hi all, i am using the Acoustic Echo Cancellation from "Speex 1.1.12 version" in my VOIP application. Is it that the frame length to be chosen should always be 20ms or can i have flexibility in chosing the frame lenght? on what parameters does the frame length choise depends? thank you all, Shri. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Please, I'm looking at speex rc1 echo_cancellation API docs and I found there is now a funcion for doing decorrelation: void speex_decorrelate( SpeexDecorrState * st, const spx_int16_t * in, spx_int16_t * out, int strength) How does it fit to the speex_echo_cancellation function ? When removing echo from multiple channels I need to decorrelate the input mic first and