similar to: 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

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

> 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

> 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.

> 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

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

> 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) 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 delay of the echo. For acoustic echo, that value is generally higher than for line echo. You'll need to experiment, but a value around 500 (for 8 kHz) might be a good start. > 2) I'm assuming I want to call speex_echo_cancel() on each

I am using the denoiser and AGC, but the problem persists if I turn them off (stop calling speex_preprocess() altogether). Also, I have reproduced it on both a noisy system and a quiet system that hardly needs the denoiser. I know what you mean though, I have heard similar sounds when pushing the denoiser too hard. For example, doing 100x AGC, or trying to use an extension cord with my

I think your setup is wrong all the way. First, an uncompressed narrowband (8 kHz) file should take up 272 kB, not 1.43 MB. You're probably dealing with a 44.1 kHz file (you should downsample it first). Once encoded at quality 1, the result should take 8.5 kB, not 21 kB. As for the 92 kB, I have no idea where it may come from. Jean-Marc Le mar 03/02/2004 à 16:16, Rodrigo Parra M a

hi there, I am new to mailing list so excuse me if I don't obey to the 'netiquette'. i am writing voice chat and speex is in the root of it. i write it in Java and use JNI to link with 'C'-based Speex 1.2beta. [I know of JSpeex but there are not implemented some features] recently i decided to use DTX feature of speex as well. the code follows. The problem is that no matter

As I understand it, there are two separate ways to get VAD information from Speex: 1) Using the encoder. 2) Using speex_preprocess(). I present the following observations from an application developer's perspective. They may be wrong, in which case I would appreciate corrections. - The two VAD systems are implemented differently. - speex_preprocess()'s VAD provides more accurate

> 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

It's not really documented, but when you compile with --enable-sse, you need to add -march=pentium3 to the compile switches. That's actually a gcc requirement. Jean-Marc Le mer 21/01/2004 à 04:22, war a écrit : > gcc-3.2.2 + slack 9 + p4 2.6ghz (has sse/2) > > ./configure --prefix=/app/speex-1.1.4 --enable-shared --enable-sse > --with-ogg-dir=/app/libogg-1.1 >

These are my results with the Speex AGC and denoiser: Over the past couple of months, I've spent probably 10-20 hours of conversation with Speex (wideband) doing AGC + denoiser on both ends of the call. I think it does an excellent job of removing most noise while keeping speech intact. Yes, it's possible to make some constant noise (like humming) and have that get removed, but

> 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

Well, you seem to be using FRAME_SIZE but only defining frame_size. Otherwise, the code looks OK, but it's always hard to tell. I suggest you start from speexenc/speexdec or from the example I wrote in the manual at: http://www.speex.org/manual/node12.html Jean-Marc Le ven 19/12/2003 à 05:22, Fabio a écrit : > Hi > i'm developing a sort of VoIP application > for my

Hi All I am using speex in one of my WinCE project. I have been trying to use speex to perform denoise on the captured audio packet and echo cancellation. Following behavior I have observed while using various options. I would really appreciate if you could help me with the issues I am facing. 1. Denoise: I have written the following to code to perform denoise. //To initialize speex

> > > > This time, I've saved the decoder's output. I'm hoping that if you > > listen to it, you might have some idea of the problem. It sounds like > > the low half of the frequency spectrum is somewhat ok, but the high half > > is totally messed up, getting 'frozen' on these weird sounds. (I'm > using > > wideband 16kHz only. VBR

I'm attempting to use speex preprocess for automatic gain control in an application I'm working on and could use some help. I'm using Opus as my codec. In order to keep the number of packets down, I'm using 60msec frames. I'm sampling at 48KHz as is recommended for Opus. So, the frame length is 2880 samples and the sampling rate is 48000. The source of the data is a