similar to: Backup Echo Suppression

Millions of ordinary people have systems that do not meet your stringent specifications. It does not matter what OS you or I use. It's the customers for whom this work is done. -----Original Message----- From: Jean-Marc Valin [mailto:Jean-Marc.Valin@USherbrooke.ca] Sent: Monday, July 02, 2007 6:35 PM To: Coffey, Michael Cc: speex-dev@xiph.org Subject: RE: [Speex-dev] Backup Echo Suppression

Believe me; I've "played with" priorities and buffering. Did you just say you have no idea how the Speex residual echo suppressor works? If that is the case, can you tell me where I could get some information about it? -----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: Friday, June 29, 2007 7:38 PM To: Coffey, Michael Cc:

Selon "Coffey, Michael" <mcoffey@avistar.com>: > Believe me; I've "played with" priorities and buffering. Then either you haven't played well enough or you're using a braindead OS. > Did you just say you have no idea how the Speex residual echo suppressor > works? If that is the case, can you tell me where I could get some > information about it?

I realize that the preprocessor echo suppression is not designed specifically to counter the effects of data loss. On the other hand, as much as I might like to, I do not have the option to "fix that problem for real." The sad truth is that some end users have systems that may drop samples, or do other unfathomable things, no matter what I do. I can not rewrite their drivers, firmware,

What is the current status of the residual echo suppressor in the preprocessor? I ask this because I have occasional problems with the AEC, in which it fails to cancel echo. I think the problems have to do with samples being dropped by the audio IO system, which is effectively impossible to detect and counteract reliably. A colleague recommended using an echo suppression technique (which he

Coffey, Michael a ?crit : > I realize that the preprocessor echo suppression is not designed > specifically to counter the effects of data loss. On the other hand, as > much as I might like to, I do not have the option to "fix that problem > for real." The sad truth is that some end users have systems that may > drop samples, or do other unfathomable things, no matter what

The residual echo suppression is supposed to be working decently well now. However, it's not designed to counter the effects of samples being dropped off the soundcard. You'll just need to fix that problem for real. Jean-Marc Coffey, Michael a ?crit : > What is the current status of the residual echo suppressor in the > preprocessor? > > I ask this because I have occasional

On Jul 2, 2007, at 7:34 PM, Jean-Marc Valin wrote: > Selon "Coffey, Michael" <mcoffey@avistar.com>: >> Believe me; I've "played with" priorities and buffering. > > Then either you haven't played well enough or you're using a > braindead OS. This is sort of what I was talking about with nibbling. Imagine you have a microphone sampling

It appears that both the echo canceller and the noise reducer (NR) introduce rather severe clicking artifacts when presented with audio that has slightly overloaded the A/D converters. I am talking about speech that sounds just slightly distorted, due to clipping, when simply played back. If I pass that speech through the echo canceller or the noise reducer, it acquires really loud clicks and/or

Hello, We've integrated the speex echo canceller into PulseAudio, and coupled with the AGC/denoiser, it works reasonably well and has been a breeze to plug in, so thank you! One thing we're seeing, though, is that the canceller seems to take some time (a few seconds) to "learn", so initially the echo is clearly audible and it slowly fades out. This sometimes occurs in the middle

Hi, We are looking at consolidating our lines with PRI. This will allow the elimination of many fax lines. Some of them will be replaced with this type of config ... PRI * IAX * Channel-Bank FAX We will have daggressor suppressor enabled. Is anyone doing this and should I expect smooth operation? John This e-mail was scanned and found clean by Monroe-Woodbury CSD Antivirus.

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

On 10-06-04 08:31 AM, Henry Gomersall wrote: > I hope people don't resent me making a point on this, as I don't > actually know how the noise suppression in speex works, but I have some > knowledge in the area of noise suppression. > > In general, if you have information about the nature of the noise you > are trying to suppress, you can do much better than just assuming

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

> As you can tell, the AAGC integration with speex was really a classic > hack. Instead of re-creating the hack, what's probably best here is to > integrate AAGC back into speex, and have a proper API. Agreed here. If you can come up with a clean patch to add that feature, it's something I'd like to see in Speex. > For those of you just tuning in, what I call

> In those cases, when you get let's say 1000 packets of 20ms from the mic > you may have only 990 packets of 20ms from RTP incoming stream. > > Thus, before sending outgoing mic/RTP stream, you would wait for 1000 > incoming packets: where last packet in fact arrive 10*20ms = 200ms > after it was supposed to. I have from my experience already seen 4s > of clock deviation

Hi, I implemented a small patch that allows the internal convergence state of the echo canceller to be saved in a file for later use, especially after a process restart or machine reboot. This enables immediate echo cancellation the second time the AEC is run. Of course this works only if the acoustic environment of the device doesn't change and if the soundcard latency is constant. To use

First time here, so I hope this isn''t a FAQ (although I did check *the* faq). I''m using mongrel_cluster with --prefix, and it is very slick. Thanks for that. But I had one problem. At one point in my little app, I have something like this: image_tag(url_for(:action => ''picture'', :id => 1), :size => "160x200") In this scenario,

Hello, I resolved my echo issue using grandstream/estara etc etc sip phones and wcfxo interfaces from digium. I swapped out my via kt400 based msi kt4vl motherboard for an asus p4pe? i845? based motherboard and the echo has completly gone away along with aggressive suppressor option in the makefile. I hope this helps others. Brian J. Schrock Anistone Technologies, LLC 6926 Avery Rd. Dublin, OH

Jean-Marc Valin wrote: > The noise suppressor will only attempt to remove stationary noise, > such as thermal noise, fans, ... The AGC can indeed do strange > things in these cases, but it's been improved in svn (compared to > 1.2beta1). OK, then the problem is that I misunderstood the feature. I assumed that dynamic squelch was part of it, but it's really something more