similar to: Echo Can Tail Length

David Baker a ?crit : > Hi, > > I've been trying to understand the documentation on the Speex echo > canceller, and unless I'm confused, I think there's a mistake > somewhere. The documentation on http://speex.org/docs/manual/speex-manual/node7.html#SECTION00740000000000000000 > says, " The recommended tail length is approximately the third of > the

Hello all, I am trying out the echo cancellation of Speex (1.2beta2) on Windows XP. I use the Windows Media API (i.e. waveInOpen, waveOutOpen etc) for playback and capture, but I cannot make echo cancellation works in my use case. Here is a description of what I tried: (the sound is in 8kHz and 16 bits per sample, the frame size is 240, tail_length is long enough to cover the far end to near end

Hello everyone, I'm a new comer to this mailing list. I found that the echo_diagnostic.m included in speex-1.2rc1 seems to have grammar mistakes which cause parse error in octave 3.6.2. I wonder if anyone have ever executed this code under octave/matlab. I also made some minor modifications to the file to correct those errors and publish it here. If it can helps the project to be more

*Sigh* Some day I'll learn to set the right sender address when posting to membership-restricted mailing addresses. Was wondering why this hadn't arrived. Reposted message as follows: Hi, Would a patch to change the constants on line 454 - 462 in the preprocessor into variables be of general interest? At the moment, whether or not "is_speech" is 1 is hardcoded to be

Thank you for you quick reply, Jean-Marc. I have just used a human voice to replace the sine wave, but the result is like a broken voice after tens of seconds. Do you have some sample voice in .sw that I can test with? I want to have one set or a few sets of sample voice that work for my understanding and debugging. This is the output from echo_diagnostic.m in my human voice test: Far end to

Hi, I'm trying to use Speex Echo Canceller for mobile device. The AEC works well so far. However, I want to know how to remove reverberation significantly. I noticed it's not implemented yet in Speex AEC. Are you going to implement it in next version? Could you provide some ideas how to handle reverberation on current version? Thanks in advance. Sincerely, Dennis

Hi: I have been trying to test the speex AEC by playing a voice sample (pre-recorded) as a echo and capturing a new voice sample and playing the pre-recorded one, for reference. [Sampling rate 8 KHz, frame size 64] For some reason, I dont see any removal of echo. Does anybody have a idea of * Testing the AEC in some other mechanism or * Getting some sample files for testing AEC Thanks Su ---

> Thank you all for valuable input, > > another question: when do I actually need the echo cancellation > (hardware / on board /on module ) ? > It depends on your environment. If there are still analog devices in addition to VoIP, I'd say always, but Asterisk has a rudimentary echo canceller already on board. The Telcos use echo cancellers themselves, but it cannot hurt to

On Mar 28, 2004, at 8:23 PM, Jean-Marc Valin wrote: >> The st->zeta pointer isn't freed in the >> speex_preprocess_state_destroy() >> function of the preprocess.c file (alloced in line 167). It's in >> Speex 1.1.4 >> by the way. > > Oops... Thanks for letting me know. I'll change that for the next > release (in the mean time, the fix is

Hi Jean-Marc > Can you explain what you mean here by "speech switching" By speech switching I mean the adaption of "gain2" when near-end or far-end is talking. What is important is that the timing is good and that the gain is low/high while far/near-end is talking. By timing I mean that the "gain2" should remain low until all far-end talk is final and that the

http://dovecot.org/releases/dovecot-1.0.rc30.tar.gz http://dovecot.org/releases/dovecot-1.0.rc30.tar.gz.sig So, this is it. Unless you can find a new and important bug within a week, this release is the same as v1.0. I'll only update the version number and NEWS file. Changes since rc29: * PAM: Lowercase the PAM service name when calling with "args = *". Linux PAM did this

http://dovecot.org/releases/dovecot-1.0.rc30.tar.gz http://dovecot.org/releases/dovecot-1.0.rc30.tar.gz.sig So, this is it. Unless you can find a new and important bug within a week, this release is the same as v1.0. I'll only update the version number and NEWS file. Changes since rc29: * PAM: Lowercase the PAM service name when calling with "args = *". Linux PAM did this

> Thanks for the great work. It indeed helps to diagnose of echo > canceller and narrow down the > problem area. Good, so it worked for you? > I am not an expert in the signaling processing but I > wonder if it is possible > to add the linearity check in the echo_diagnostic function? Theoretically, yes. In practice, I'm not sure how accurate it would be. Do you have any

Hi: Can anyone give some insight on: 1) As per the Speex manual, there is a mention of the relationship between input frame and echo frame (Pg 19, Para 2). I was wondering of what would be the ideal delay between these two frames, so that the echo is already fed to the canceller and the echo cancellation filter is not inefficient. 2) Corresponding to the above mentioned delay, what filter

hello all, we are developing and porting vorbis1decoder on a 24 bit platform. in the process we came across somedoubts about node bytes and leaf words. from the specification we got that we are arranging the huffman codeword tree into an array. the nodebytes are the number of bytes that are required to represent a node and leafwords are the no. of bytes required to represent the leaf i.e the

Hi everyone, I think this should be interesting to all of those with echo cancellation problems. I finally check in some code to make these problems easier to debug. You'll need to have svn version for this. First, you need to manually define DUMP_ECHO_CANCEL_DATA in the compilation (sorry configure switch for now). With that, the AEC will automatically save the near-end, far-end and output

Hi Sebastian, It boils down to this: The previous heuristic solver could return infinite cost solutions in some rare cases (despite finite-cost solutions existing). The new solver is still heuristic, but it should always return a finite cost solution if one exists. It does this by avoiding early reduction of infinite spill cost nodes via R1 or R2. To illustrate why the early reductions can be a

Hi Lang, I'm surprised about the fact that you omit R1/R2 reductions in some cases. Can you give a more detailed description of the bug (e.g. a PBQP dump)? Best regards, Sebastian Lang Hames wrote: > Hi Sachin, llvm-dev, > > I've just committed a new PBQP solver which, among other things, > should take care of this bug. > > Please let me know how it works out for you.

All I can say for now is that: 1) My diagnostic tool does funny things that need to be fixed 2) It was probably also getting confused by the clicks at the end of the files 3) There seems to be odd things with your recordings, though I can't say what that would be. Are you changing something during the recording by any chance? Note that if a person close to the mic of speaker moves, that

Unlivable. I fix it. I forgot the speex_preprocess(m_pPreprocess, buf, NULL) need to do enough samples too. Tks a lot! And speex_preprocess_ctl(preprocess, SPEEX_PREPROCESS_SET_DEREVERB, &tmp); f=.4; speex_preprocess_ctl(preprocess, SPEEX_PREPROCESS_SET_DEREVERB_DECAY, &f); f=.3; speex_preprocess_ctl(preprocess,