similar to: Frame size for speex_echo_state_init

Displaying 20 results from an estimated 8000 matches similar to: "Frame size for speex_echo_state_init"

2006 May 08
5
Speex echo canceller on TI C55 DSP
Hi Jim, I've just been made aware of these problems (look for the thread "speex echo cancellation limitations"). It's on my short-term TODO list. > If fftwrap.c, I ifdefed out the spx_fft_float and spx_ifft_float routines, > because there were not used and required smallft.c (which is not so small at > all) to be added to the build. Right, need to cleanup that
2006 May 09
2
Speex echo canceller on TI C55 DSP
Just tried your files and I'm not running into any infinite loops and the cancellation works fine. Unless the C6x has the same problem, I suspect a 16-bit problem. I'll check and see if I find something. About the r=0 problem, I can't find where it ends up in a denominator, so I suspect is not (directly) the problem. Jean-Marc Le lundi 08 mai 2006 ? 20:05 -0400, Jim Crichton a ?crit
2006 May 09
2
Speex echo canceller on TI C55 DSP
> I built and ran the same test on the TI C64 simulator, and the echo was > canceled nicely (about 10:1 reduction in the peak amplitude during the > second of two brief speech bursts). So, my problem must again be related to > the 16-bit processing on the C5X DSPs. Good. At least we've narrowed it down a bit. > Also, the line where it is hanging is: >
2007 Jul 02
1
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
2007 Jul 02
1
Backup Echo Suppression
Jean-Marc, I think I can speak for most everyone here when I say we appreciate *very much* your code beyond the codec that helps people who use Speex in real applications. How far you want to take that code is up to you, of course. (And contributors, to a degree.) I don't think any reasonable person is expecting your code to solve everything. But when people are running up against
2014 Dec 18
1
[ARM][FFT][NEON] Integrate Ne10 into Opus?
Hi Ralph, I have pushed patches to enable radix 3 and radix 5. Github: https://github.com/projectNe10/Ne10/releases/tag/v1.2.0 Best Regards, Phil Wang > Date: Thu, 11 Dec 2014 10:46:50 -0800 > From: Ralph Giles <giles at thaumas.net> > Subject: Re: [opus] [ARM][FFT][NEON] Integrate Ne10 into Opus? > To: opus at xiph.org > Message-ID: <5489E69A.5000305 at thaumas.net>
2007 Jul 02
3
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:
2014 Dec 11
2
[ARM][FFT][NEON] Integrate Ne10 into Opus?
Hi everyone, I am working on Ne10 project. Ne10 provides NEON optimized FFT routines that are much faster (compared to those without NEON), on most ARMv7-A and all ARMv8-A devices. How about integrate it into Opus? I am not familiar with configure script, but I find "Optinal Packages" in it. If we provides --with-ne10-fft option, the one extra thing that users need to do is to
2015 Oct 16
1
[RFC V3 7/8] armv7, armv8: Optimize fixed point fft using NE10 library
Hi Timothy, Sorry for late reply. I have upstreamed the patch to fix the regression here: https://github.com/projectNe10/Ne10/commit/ee5d856cd9cb8c4a15ace567df4239f4e788d043 I have tested it with Vish's branch: http://git.linaro.org/people/viswanath.puttagunta/opus.git/shortlog/refs/heads/rfcv3_fft_fixed) Both unit test dft and unit test mdct passed on ARM v7/v8, floating point/fixed
2006 May 02
3
Re: speex echo cancellation limitations
Hi Ted, Thanks a lot for this analysis. > In FLOAT_DIVU() it hangs at the following: > while (a.m >= b.m) > { > e++; > a.m >>= 1; > } > for the case where a and b are both zero (yes, division by zero). > This happens from mdf.c: True, that needs to be fixed even after I fix the rest. > leak_estimate =
2006 Jun 07
7
AEC frame size
? hi all, i am using the Acoustic Echo Cancellation from "Speex 1.1.12 version" in my VOIP application. Is it that the frame length to be chosen should always be 20ms or can i have flexibility in chosing the frame lenght? on what parameters does the frame length choise depends? thank you all, Shri. -------------- next part -------------- An HTML attachment was scrubbed... URL:
2007 May 22
3
Clicking Problems with slightly clipped audio
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
2006 May 08
0
Speex echo canceller on TI C55 DSP
> I've just been made aware of these problems (look for the thread "speex > echo cancellation limitations"). It's on my short-term TODO list. I saw the other thread, my problems happened in different (but similar) routines. >> If fftwrap.c, I ifdefed out the spx_fft_float and spx_ifft_float >> routines, >> because there were not used and required
2006 May 10
2
Speex echo canceller on TI C55 DSP
> Build 11387 produces the same result as my modified build 11343. Because of > compiler limitations in the TI tools, I did have to make modifications to > pseudofloat.h (separating return of float values) and nb_celp.c (adding > braces around a variable declaration in the middle of code). I have > attached a patch. You might prefer to do the nb_celp.c change in a >
2006 May 09
0
Speex echo canceller on TI C55 DSP
>Just tried your files and I'm not running into any infinite loops and >the cancellation works fine. Unless the C6x has the same problem, I >suspect a 16-bit problem. I'll check and see if I find something. About >the r=0 problem, I can't find where it ends up in a denominator, so I >suspect is not (directly) the problem. I built and ran the same test on the TI C64
2006 May 10
0
Speex echo canceller on TI C55 DSP
Jean-Marc, Well I finally tracked down the problem. Then I checked my mail and found that you had fixed it several hours earlier. :( Build 11387 produces the same result as my modified build 11343. Because of compiler limitations in the TI tools, I did have to make modifications to pseudofloat.h (separating return of float values) and nb_celp.c (adding braces around a variable declaration
2006 Oct 24
1
fixed point AEC
Thanks Jean, I missed that detail. I have a few more compile errors if you could help me with it => In function speex_echo_state_init in mdf.c I am getting error: "undefined reference to exp". I don't see a fixed point implementation of "exp". Can you point me to the correct files. I am using the following files from speex 1.2 beta1 => mdf.c,
2007 Jun 07
1
Time Delay Estimation
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
2009 May 27
1
How to write a loop?
Dear R helpers,   Following is a R script I am using to run the Fast Fourier Transform. The csv files has 10 columns with titles m1, m2, m3 .....m10.     When I use the following commands, I am getting the required results. The probelm is if there are 100 columns, it is not wise to define 100 commands as fk <- ONS$mk and so on. Thus, I need some guidance to write the loop for the STEP A and
2011 Sep 25
0
[LLVMdev] POSIX thread library support
Hi chenwj, According to the link, I found that during the compiling process, the option "-emit-llvm" must be added to generate immediate object *.o. [hanfeng at os-wstation02 fft]llvm-gcc -c fft.c -emit-llvm Then using llvm-ld will generate two files - a shell excutable and a llvm bytecode data both of which would run perfect. [hanfeng at os-wstation02 fft]llvm-ld -o FFT fft.o [hanfeng