similar to: Speex 1.1 is out

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

> 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

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

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

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

this is not really a development question, but i didn't find another mailing list to ask it. any idea why size of wav file doubles when it is encoded to speex and back to wav: $ ls -ls testi.wav 40 -rw-r--r-- 1 foo foo 40674 May 4 14:38 testi.wav $ speexenc --denoise --agc --quality 10 testi.wav testi.spx Encoding 8000 Hz audio using narrowband mode (mono) $ ls -ls testi.spx 20

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

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

Juha Heinanen writes: > any idea why size of wav file doubles when it is encoded to speex and > back to wav: > > $ ls -ls testi.wav > 40 -rw-r--r-- 1 foo foo 40674 May 4 14:38 testi.wav > > $ speexenc --denoise --agc --quality 10 testi.wav testi.spx > Encoding 8000 Hz audio using narrowband mode (mono) > > $ ls -ls testi.spx > 20 -rw-r--r-- 1 foo foo 16405

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

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

Hi, I have a curious problem with speex. As long as I'm talking, it takes about 2-5% of my CPU. This seems ok. But as soon as I stop talking, CPU utilization rises to about 30-45% and stays there until I start talking again. I compiled speex from source and use it with these settings: - Preprocessor: Denoiser = ON, AGC = ON - Encoder: ABR = 15000, DTX = 1, Mode = narrowband, Rate = 8000 Hz.

Hi, I am working with libspeex api. I would like compare the size of speex file encoded with libspeex and the size of speex file encoded with speexenc. For example, I encode with speexenc (narrowband, quality 1) a wav file of 1.43 MB (17 seconds) output a spx file weight 21KB, for other hand I encode with libspeex the same wav file with same characteristics in arm processor, pocket pc and the

Hi Jean-Marc, I tried to add VERY_SMALL at the input of the encoder, but that did not change much. Here's a list of source code locations where denormals appear for the first time as calculation results. This list is based on a 4 minutes recording of ambient sound that is passed to speexenc 1.2rc1 with the command line --narrowband --denoise --agc --abr 15000

> 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

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

Hi -- I'm looking at adding Speex decoder and encoder support to the Miles Sound System, a commercial library used by game developers on various platforms including PCs, the Mac, and game consoles. As part of my initial evaluation, I've gone ahead and downloaded the 1.0.4 and 1.1.1 Win32 binary distributions and played around encoding and decoding various files with the speexenc.exe and

Hi Jean-Marc, I recompiled with FIXED_POINT and CPU utilization stays below 4%. This is a great improvement. So how can I fix this to work with floating point ? Thanks. Mark -----Urspr?ngliche Nachricht----- Von: Jean-Marc Valin [mailto:jean-marc.valin at usherbrooke.ca] Betreff: Re: [Speex-dev] High CPU usage Hi, Sound like it could be the good old denormalised float problem on the Intel