similar to: ietf discussion about draft-ietf-avt-rtp-speex

On Mon, 6 Nov 2006, Jean-Marc Valin wrote: > That's quite a strange problem. Considering that Speex doesn't have any > "init code" (stuff that executes when it's loaded), there's no way this > could be a bug in Speex. True. > I see two likely possibilities (plus lots of > unlikely): > 1) A bug in your code. Linking with Speex pushes your code to a

In a "normal" frame that doesn't have in-band signalling (which nobody seems to use anyway), the frame starts with the narrowband information. If the frame is in wideband, then this will be followed by a bit of wideband information that starts with a bit set to 1 (narrowband starts with a bit set to 0). Have a look at what the Speex decoder does. You may actually want to have similar

If you want to test the AEC, I recommend using the svn version of Speex. Jean-Marc Aymeric Moizard a ?crit : > > I finally solved my problem: > > My **static** speex library is compiled with: > -D_LIB > > While I should compile it with: > -D_USRDLL > > I'm not able to understand completely why: anyway, it > now can be compiled without breaking anything.

On Wed, 6 Dec 2006, lianghu xu wrote: > Hi Jean-Marc, > > I remember you said that the SDP tells the mode information. Right. But a decoder like speex can always be configured from information contained in the incoming stream. That makes your application more interroperable. Aymeric MOIZARD / ANTISIP amsip - http://www.antisip.com osip2 - http://www.osip.org eXosip2 -

I'm getting confused, what's the problem exactly? The AGC doesn't remove the DC or it adds one? Jean-Marc Aymeric Moizard a ?crit : > Hi Jean-Marc & all, > > I'm currently working on a wav file with very low volume. > This wav also contains a DC component. > > Using testdenoise with modification (AGC turned on with > 20000.0 value) I'm able to

Hi, Speex-dev: ? I have some problems about complie speex on pxa-270. I use libspeex.so.1.4.0 at my platform after complie speex and all function is ok, but the cpu loading is 99%. How can i do to reduce the cpu loading? ? note: 1. My Platform are os: linux 2.6.19 , cc: gcc-2.95.3 , cpu: pxa-270, ogg: libogg-1.1.3, speex: speex-1.2beta3 2. I configure speex by the follow command. ./configure

Hi, I'm experiencing weird problems while testing speex (I want to test the echo canceller first) on PDA with WM5 version pocket PC 2005. Here is the strange scenario: 1-> App running without being linked with speex -> no problem 2-> App running while being linked with speex -> crash at always the same place. NO ACCESS TO

Sorry, got the subject wrong in the last mail. My e-mail client is playing games with me...

Dear Sir/Miss: I'm very sorry to bother you,but I've found a bug in the Speex,Version 1.2beta1,and also I've have some questions. I'm deeply impressed by the work you have done in the coding and decoding of speech signal.But when using speex,I encoutered a bug,that is when in 32K mode,the window size is still 200 samples,but not 400 samples,the bug will bring the problem of

Aymeric Moizard a ?crit : > > I'm working on the echo canceller with the SVN, with Windows Mobile 5 > PocketPC. > > Obviously, I can't make it run correctly. What happens/doesn't happen? > My question: If I use the SPEEX_PREPROCESS_SET_ECHO_STATE, I have > changes in the sound: noise seems to be removed. Noise should be removed even without

Hi We are working on a speaker phone system using PJSIP and Speex Speech processing API on an ARM platform. Currently we have spent about a month on getting the AEC to work properly and we have worked through the most common causes of problems (such as clock drift, synchronization problems and non-linearity's in echo path). Now we achieve ERLE of about 17 dB which tells me that the AEC is

> In those cases, when you get let's say 1000 packets of 20ms from the mic > you may have only 990 packets of 20ms from RTP incoming stream. > > Thus, before sending outgoing mic/RTP stream, you would wait for 1000 > incoming packets: where last packet in fact arrive 10*20ms = 200ms > after it was supposed to. I have from my experience already seen 4s > of clock deviation

Isn't this the same problem described starting at the bottom of this page? http://www.embeddedstar.com/articles/2003/7/article20030720-11.html Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > > > As it says in 5.4.1 of the good book "Using a different soundcard to do > > the capture and playback will *not* work, regardless of what you may > > think.

On Sat, Nov 1, 2008 at 2:40 PM, Aymeric Moizard <jack at atosc.org> wrote: > The vcproj file provided for 2005 in 1.2rc1 does not include > _USE_SSE when compiling the project for "Release_SSE". This > define is only used when compiling under "Release_Dynamic_SSE". > > Is this just because the vcproj file is wrong or is it because > this #define must not

> No, the 1.2beta1 preprocessor works rather well. I have a different opinion, but glad you like it anyway :-) > In fact, I very much welcomed the change that the preprocessor in > 1.2beta1 now starts out with the assumption of there being no speech, > and only activating and adapting AGC when where there is new activity > detected above that. As a result, with 1.2beta1, there is

Dear all, I have just implemented a gstreamer plugin for the Speex AEC, but now I would like to extend it to a multichannel echo cancellation I have been searching documentation about that but I could not find it Where it is? If it doesn't exist? Could you add a short example showing how do you think it should work? or It's "just" necessary to: init the multichannel echo

Hi Aymeric, > 2 questions: I count 4 :-) > * Do you "feel" that the current svn is enough stable Yes. I'm planning on releasing it as 1.2beta3 this week. Even in normal time, I try to keep svn in good shape so it is almost always better than the last release. And even when it breaks, Speex bugs tend to be very obvious and easy to reproduce (no segfaults that happen once a

Hi everyone, After years of effort, the Speex RTP payload format is now approved as an RFC: http://www.rfc-editor.org/rfc/rfc5574.txt Many thanks to everyone who participated. Enjoy! Jean-Marc

Hi everyone, After years of effort, the Speex RTP payload format is now approved as an RFC: http://www.rfc-editor.org/rfc/rfc5574.txt Many thanks to everyone who participated. Enjoy! Jean-Marc

Hi, So I see in: split_cb_shape_sign_unquant this call is going wrong: ind[i] = speex_bits_unpack_unsigned(bits, params->shape_bits); ind as a way negative number- basically this should return bet. 0-255 or somesuch right? So seems like I need to reset speex at this point if if (ind[i] > 256) like the note says. So I guess my question is is this range still valid? also what is the