similar to: Re: Speex 1.1 is out

Sounds great!! I will definitely give these new features a try and let you know how it goes. Every one of them (except for the narrowband mode) will be really useful to me. I have a few questions after looking through the source code: Echo cancellation: 1) What should I use for a filter length for speex_echo_state_init()? 2) I'm assuming I want to call speex_echo_cancel() on each

> 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? If by "used with other codecs", you mean that you can use the result as input to any codec you like, the answer is yes. > Somebody could send me some documentation or sample, or explain the next > functions: > >

Just to let you know I released 1.1: This is an unstable release. It brings many new features, some of which are still experimental. The new features are: * a denoiser that removes most of the background noise and can be used before encoding (available as --denoise in speexenc) * adaptive gain control (AGC), which adjusts the volume to a constant level (available as

> Then I pulled the microphone out. Our system still records noise. To > isolate the problem, I wrote a small app just to open the device and > record raw samples, calls speex_denoise() and outputs both sample > sets. > The noise is still there, with level fluctuating with gain level, > unless > "All mute" is chosen. > In the case when NO microphone is

Hi, Thanks, that gave me some ideas. I have tried calling speex_echo_cancel and speex_preprocess separately and jointly, with a number of different filter lengths, and using the cancelled and non-cancelled data as input to the pre-filter, with and without the residual echo, etc. but there doesn't appear to be valid data in the echo or the cancelled frame any way I try it. Back to the

Le dim 31/08/2003 à 20:12, Daniel Vogel a écrit : > > This works really well for white noise reduction. However > > what I've noticed was the amplitudes of normal speech samples > > also get reduced. > > Noticed this as well recently. This is probably due to the AGC (Adaptive Gain Control) that's integrated with the denoiser. I'll try adding an option to

> So I have had a chance to delve deeper into the new pre-processing > code- I was also able to get VAD, AGC, Denoising, etc working inside of the > current release candidate (1.0.3). For some reason, the 1.1.2 > release didn't properly encode/decode in our system (on windows) > and I haven't had time to determine why. In any case, all of the features > jointly work

> 1) AGC: This seems to work pretty well in all cases. I had previously > hacked-in the "compander" filter from sox for a similar effect. What > I've noticed is that speex_preprocess's AGC has no "knobs", and it > seems to use an attack/decay that is a lot faster than what I had > chosen from the sox compander, but it works pretty well nonetheless.

This is only remotely related: just out of curiosity, does speex_preprocess work very well for you ? It only works to certain extend for me, and does not seem to completely remove noise from sound card. Even if you unplug the microphone, it still could not get rid of the noise. Any idea how it could be totally eliminated ? <p>Thanks <p><p>-----Original Message----- From: Tom

Tom, You can look in my archives for my posts on this topic, but what I've found is that the echo canceller works to some extent, but if you're also using the other preprocessing (which you'd definitely need to do _after_ ec, otherwise ec probably won't work at all), the AGC function ends up reversing the effect of ec. That is, while ec reduces the echo, it doesn't

Hi, There seems to be some confusion as to how speex_denoise (now called speex_preprocess) works. Unlike what some here assume, the noise estimation is not done offline or while prompting the user. The system automatically adapts the noise estimate when it detects that the user is not talking. This also means that it is able to adapt to changing noise environments - as long as the noise is not

> I'm being PHBed into a VOIP project, and Speex sprang to mind. > Bandwidth is > going to be a fairly serious issue for us. With regards to a Speex > enc/decoder, I was wondering: Rick Kane and David Siebert have already > asked > about this, but seem to have gotten very different responses - the > former a > call to arms, and the latter a "well, if you do it,

I don't think the echo canceller works yet. The best I could get it to do is trash my audio. If it does work, some sample code demonstrating its use would be really appreciated... Here is what Jean-Marc has said about it in the past: > What should I use for a filter length for speex_echo_state_init()? "Well, it depends on your problem. The filter length represents the maximum

> I just downloaded http://www.speex.org/download/speex-1.1.4.tar.gz and > tried to build it but the file denoise.c seems to be missing from the > archive. > Can you fix this or is it better to get everything from cvs? You're using Windows, right? The project file is simply out of date. The denoise.c file has been renamed to preprocess.c > Another question, when will a stable

OK, so the problem doesn't seem to be the VAD specifically. Can you tell me how much audio you had in the test? It may be that nothing's wrong and the code just isn't so fast that you can do 100 channels. Or maybe it just needs a bit of optimization... Jean-Marc Le mer 31/03/2004 à 10:03, Steve Kann a écrit : > Jean-Marc Valin wrote: > > >If you set the denoiser

Actually, there are probably some batch programs that could do the job. It's definitely not a job for speexenc, which I'd like to keep simple. Jean-Marc Le ven 09/01/2004 à 17:37, Asger Kunuk Alstrup a écrit : > Hi, > > Speex is great! > > We are using it to compress hundreds of megabytes of speech for use in our > application that trains people in

> First i want to say that libspeex produce defently too much > errors. I think it was written by a mathematician, right ;-)). No, it was written by an electrical engineering Ph.D. student (i.e. me). Note that if you are that concerned with warnings (and code quality I hope), perhaps the best thing to do is start using *stable* versions. If you use a stable version (1.0.2, but I'll

> 1. Compile Error with regular mode (FIXED_POINT undefined) at lsp.c line 104 > static inline spx_word16_t spx_cos(spx_word16_t x) . VS6 does not like > the inline keyword here. Removing it allows compiling. > > same with cb_search_sse.h line 34. It seems like your compiler simply doesn't like "inline". I suggest doing a -Dinline= which is what autoconf

Le lun 10/11/2003 à 11:19, Massimo a écrit : > On Sun, 2003-11-09 at 21:00, Jean-Marc Valin wrote: > On recent x86 processors, floating point is faster than fixed-point. > > Jean-Marc > > This left me something shocked. Please, can you tell me what kind of > processors are showing this behaviour? Are you referring to speex > codec

Hi everyone, I've just released version 1.1.4. This includes some code cleanup and improvements to the fixed-point port and SSE optimizations. All the SSE code has been converted to intrinsics and some new functions have been implemented with SSE. Overall, the speed has been increased by up to ~30% with SSE. Jean-Marc -- Jean-Marc Valin, M.Sc.A., ing. jr. LABORIUS