similar to: Readding Zlast info to the preprocessor

Hi Jean-Marc > Can you explain what you mean here by "speech switching" By speech switching I mean the adaption of "gain2" when near-end or far-end is talking. What is important is that the timing is good and that the gain is low/high while far/near-end is talking. By timing I mean that the "gain2" should remain low until all far-end talk is final and that the

Johan Nilsson a ?crit : >> There's also a parameter to control the maximum amount of >> suppression allowed: SPEEX_PREPROCESS_SET_NOISE_SUPPRESS : noise >> suppression SPEEX_PREPROCESS_SET_ECHO_SUPPRESS : echo suppression >> when there is no local talk >> SPEEX_PREPROCESS_SET_ECHO_SUPPRESS_ACTIVE: echo suppression in >> double-talk > > Yes, I am

>What happens if you make SPEEX_PREPROCESS_SET_ECHO_SUPPRESS_ACTIVE less >aggressive. Does it end up with too much echo or it just doesn't realise >that it's in double-talk conditions? My impression is that it does not make much difference on the timing to set this parameter less aggressive. Depending on the how loud the near end is talking it may detect double talk but most

Hi All We are working on an ARM-based speaker phone application where the speaker and microphone is placed roughly 8 cm from each other (similar to this one: http://www.voipsupply.com/images/CHAT50SPLASH.jpg). We are using Speex AEC and preprocessor to handle the acoustic echo. The AEC typically contribute with ERLE of 15-20 dB which should be as expected from the algorithm. Additionally we need

Current SVN compilation fails on Win32 (Intel C++ compiler 9.0): ..\..\libspeex\mdf.c(317): error: declaration may not appear after executable statement in block float adapt_rate; Just moved it up to the variable declaration block to solve it locally, but as it's not valid C, I thought I'd mention it ;) PS: With the same compiler, AGC fails horribly (Zlast goes to several

> /* FIXME: This VAD is a kludge */ > .. and it shows (or hears?) unfortunately. I've run a few tests with it > with my users, and they complain that it misdetects too often... In both > directions. Non-speech is detected as speech more often than before, and > more important it also doesn't detect speech as good as before. > I'd really like to see this

Echo cancellation works like a charm, but it seems to confuse the preprocessor a bit. If listening to background music (properly fed through the echo cancellator), the music is removed but the result is still detected as speech even if almost silence remains in the signal. Also, the AGC keeps adjusting to the minute remains in the signal, meaning that sooner or later it will amplify the

On Tue, 2018-06-05 at 10:23 -0700, Joe Perches wrote: > Perhaps these are simpler as > > #define __inline__ inline > #define __inline inline Currently, there are these uses of inline variants in the kernel $ git grep -w inline | wc -l 68410 $ git grep -w __inline__ | wc -l 503 $ git grep -w __inline | wc -l 57 So it seems it's also reasonable to sed all uses of __inline to

I think you'll have to modify Speex to get the functionality you're looking for. I've made a few simple modifications to the AGC to prevent it from 1) exceeding a specified level of amplification and 2) enable and disable adaptation, so I can freeze it at a certain level while speech is not detected. It's mostly just a matter of doing this at the end of speex_compute_agc():

The definition of granule position for an OggDirac elementary stream isn't the same as theora. Index: tools/oggz_tools.c =================================================================== --- tools/oggz_tools.c (revision 3759) +++ tools/oggz_tools.c (working copy) @@ -454,7 +454,15 @@ iframe = granulepos >> granuleshift; pframe = granulepos - (iframe << granuleshift);

A widely used platform doesn't bother to have C99 integer types, so this allows building with it. Reported by sirlemonhead on IRC. Index: src/tools/oggz_tools.c =================================================================== --- src/tools/oggz_tools.c (revision 3827) +++ src/tools/oggz_tools.c (working copy) @@ -450,7 +450,7 @@ dg->pt = (iframe + pframe) >> 9;

Hi, I've been looking a bit at the VAD/AGC situation. I noticed a leftover variable declaration. The AGC used to use nb_loudness_adapt to count the number of frames so far, but it now uses nb_adapt which is shared by all the functions. However, it still allocates and updates nb_loudness_adapt. This patch saves 4 bytes of memory and a partial cycle of CPU power ;) -------------- next part

Hello, I would like to write a program that compute the principal components of a set of data and then 1. Run the dependent variable against the principal components (lagged value) 2. Do prediction , following Stock and Watson (1999) "Forecasting Inflation". All data are time series. Now I can run the program using single factor (first principal component), but I

Johan Nilsson a ?crit : >> What happens if you make SPEEX_PREPROCESS_SET_ECHO_SUPPRESS_ACTIVE less >> aggressive. Does it end up with too much echo or it just doesn't realise >> that it's in double-talk conditions? > > My impression is that it does not make much difference on the timing to > set this parameter less aggressive. Depending on the how loud the

Hi, Here are the next two patches for the data export. speex_get_psd should be applied after speex_get_agc_gain (sent in previous mail). It allows applications to get the power spectrum for the signal and the noise estimate. speex_get_prob should be applied last. It allows fetching the speech probability of the current frame (the value that the _PROB_START and _PROB_CONTINUE parameters are

agc_gain seemed to fit with the idea of what I wanted to do, it was easy to understand its units and behavior, and freezing it produced the desired results. Also I wanted to cap it, so that's done at the same place, and that definitely works. All I want to do is be able to freeze AGC adaptation and put an upper bound on the AGC (for example, 2x amplification). Both of these things seem

On 2008-11-13, Conrad Parker <conrad at metadecks.org> wrote: > I'm wondering if the Dirac granulepos parsing in liboggz and display > in the oggz tools is currently correct, as I'd like to do a release of > these soon. I believe it is -- although if correct support in the rest of the liboggz tools is required, a little more work may need to happen. > Here's some

>> I think the residual echo estimation is fairly reliable but I do not know >> how to use this to improve Pframe and in that way solve our main problem >> with the gain during near end talk. > > How can you tell that the residual echo estimation is reliable? in any > case, I suspect that the whole Pframe idea might have to be revised > (i.e. computing it completely

It was already in the process of being changed, hence the first seven lines of the function. That lapply is no longer needed and has been removed (but was not yet committed). We do normally ask that problems with R-devel ('Under development (unstable)') not be sent to R-bugs: as is quite often the case this is something that is under active development. On Mon, 26 Jun 2006, Peter

Johan Nilsson a ?crit : > We are using Speex AEC and preprocessor to handle the acoustic echo. The > AEC typically contribute with ERLE of 15-20 dB which should be as > expected from the algorithm. Additionally we need about 30 dB echo > suppression which we hope to get from the preprocessor. So far it seems like you're doing things right. > However it has shown to be very