similar to: Fw: Voice Activation Level (speex 1.1.11.1)

Lis, I suggest you try tweaking Speex's VAD probabilities as Steve suggested. But consider a simple threshold-based approach as a backup option. Personally, I struggled with Speex's VAD algorithms (both encoder and preprocessor) for a long time, tweaked the probabilities, wrote special case code to work around the mistakes, and was still never satisfied with the results. In times

Hi...Tom, How to use the code you written? Can you show me some example? Thanks, -----Original Message----- From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] On = Behalf Of Tom Grandgent Sent: Friday, March 03, 2006 12:57 AM To: Steve Kann; Lis Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] Voice Activation Level (speex 1.1.11.1) Lis, I suggest you try tweaking Speex's

I implemented the calcPower(). It works perfectly. The example is given you in just about 6 hours. Cant paste the whole source here and need to meet someone now. Thanks all (particulary tom). I try to figure out whitch problem exists with the #define SPEEX_PREPROCESS_SET_PROB_START 14 theese days ----- Original Message ----- From: "¼Õ½Â¿ø" <ssw0725@ncsoft.net> To: "Tom

There is a problem in speex_preprocess_ctl. Both speech_prob_start and speech_prob_continue are set to 327.67 for all input values except 0 which results in 0. This is in floating point mode. I think the included patch fixes the problem. Mikael -------------- next part -------------- Index: libspeex/preprocess.c =================================================================== ---

Did you check it against the trunk in SVN? If it's not applied, and you can hook Jean-Marc up with an email address like yours, I'm sure he will get right on it. :) Tom Mihai Balea <mihai@hates.ms> wrote: > > Hi all, > > Did anything happen to this patch? > It seems to me that it fixes a valid issue, but I'm not an expert. > Anyways, I didn't see

I checked it against the latest code in the git repository and it wasn't there. Mihai PS: if JM wants a @hates.ms address, I could prolly hook him up. Especially if he throws in some VAD code that's not "a hack" :) On Nov 5, 2007, at 2:08 PM, Tom Grandgent wrote: > Did you check it against the trunk in SVN? > > If it's not applied, and you can hook Jean-Marc up

Jean-Marc Valin wrote: >>Reverberation suppression? >> >> > >Basically, it means that if you are in a room with lots of echo (long >decay), I can reduce it a bit. > > > >>I guess this would help reduce local source echoes? I've never >>_noticed_ that to be a problem in my use, but I would imagine that >>using a notebook's

Sorry. I forgotten the words volume or loudness. But it is know as microphone stroke too, i think. If something can tell me something about that procedure it would complete my pleasure. To bring back memories, i only wanted to know wheather i can change a variable that holds the sound intensity (loudness) needet to start "encoding >> sending" if the speex codec is in voice

What you want is simply a loudness threshold-based detector. It's not very complicated to do, but there's nothing in Speex that currently does that (not that I think it's really useful in practice). Jean-Marc Le jeudi 02 mars 2006 ? 04:26 +0100, Lis a ?crit : > Sorry. > > I forgotten the words volume or loudness. > But it is know as microphone stroke too, i think. >

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

I havent had found anything in the documentation about voice activation levels. Does i can change a variable to change the accuracy for activations? If not does the speex lib already implement a function for read out the sound level of a frame? Thanks for the advance. Lis (Louis Hoefler) -------------- next part -------------- An HTML attachment was scrubbed... URL:

Alex, It's purely empirical, but I've found that values in the range of 0.001 to 0.002 tend to offer a nice tradeoff between rejecting unwanted sounds and picking up all legitimate speech. I use a default of 0.0015 in my program and it seems to work well. For bounds of the GUI slider, I use 0.00005 and 0.01. Sorry, but I don't know how these values translate to dB or any other

Manisha, I'm still here. :-) Here's the function: // Returns the average power level in the given signal float getPower(signed short int *signal, int numSamples) { int i; float amp; float powerSum = 0.0f; for (i = 0; i < numSamples; i++) { amp = (float) abs(signal[i]); powerSum += amp * amp; } return powerSum / (32768.0f * 32768.0f *

Dear sirs, Speex fails to link with my application on symbian, sdk versions 2nd edition fp2 and fp3 with this errors: ..\..\..\SYMBIAN\8.0A\S60_2ND_FP2\EPOC32\RELEASE\ARMI\UREL\SPEEX.LIB(../../../SYMBIAN/8.0A/S60_2ND_FP2/EPOC32/BUILD/SRC/SPEEX/SYMBIAN/SPEEX/ARMI/UREL/SPEEX.o)(.text+0x158):Speex.c: undefined reference to `floor'

Hi all and Jean-Marc, Firstly thanks a lot to you for helps, at last I accomplished to use speex-1.2beta1 in my speech application. I try to understand speex source code and improve speech quality. The problem in my application (like many people in the list says) is noise. So I've added VAD in preprocessor as following: int param_enabled = 1; int param_disabled = 0; int sampling_rate

Hi all and Jean-Marc, Firstly thanks a lot to you for helps, at last I accomplished to use speex-1.2beta1 in my speech application. I try to understand speex source code and improve speech quality. The problem in my application (like many people in the list says) is noise. So I've added VAD in preprocessor as following. VAD in preprocessor is very good, there is not noise outside speech. I

Jean-Marc, > I've got no problem cross-compiling with gcc for Blackfin. See the > README.blackfin file. Thank you for your help, Jean-Marc. I get no further with that than I did before, I'm afraid. I get: [willmore@l2 speex-1.1.11.1]$ export CC=pic30-elf-gcc [willmore@l2 speex-1.1.11.1]$ ./configure --enable-fixed-point --host=pic30-elf configure: WARNING: If you wanted to set

Hi, If I use --enable-fixed-point-debug I can't use --enable-fixed-point and vice versa? Because when I try to copile with these two option an error occur as follows: gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I.. -I/home/liselene/projects/speex/speex-1.1.11.1/bin-fixed/include -g -O2 -MT modes.lo -MD -MP -MF .deps/modes.Tpo -c modes.c -fPIC -DPIC -o .libs/modes.o

Hello, all! I'm trying to see if I can get stock Speex to compile for dsPIC using the current release of the gcc compiler targeted for it. I'm stuck at the very beginning of trying to get past the configure stage. Can anyone who cross-compiles give me an example of how they do that? Cheers, David

Thank you to all, i've discovered the problem, i was using 1.0.5 version, now i'm using 1.1.11.1 and tick is disappeared.... speex_decode now return -1 if end of stream is reached, in previous version it was returning 1...maybe can help someone...thank you again Carlo -------------- next part -------------- An HTML attachment was scrubbed... URL: