search for: mark_schilling

Hi Jozsef, this approach sounds interesting. Do have you have some source code available ? Thanks Mark -----Original Message----- From: speex-dev-bounces at xiph.org [mailto:speex-dev-bounces at xiph.org] On Behalf Of Jozsef Vass Sent: Friday, September 25, 2009 11:43 PM To: mark_schilling at gmx.de Cc: speex-dev at xiph.org Subject: Re: [Speex-dev] High CPU usage I have run into the same issue. Before sending a frame to encoder, I calculate the energy. If it is less than a small threshold, I simply replace this frame with "silence frame," which is 320 random samples of va...

...essage: 1 Date: Wed, 13 Jun 2012 10:01:52 +0000 (UTC) From: Tanmay Ambre <ambre.tanmay at gmail.com> Subject: Re: [Speex-dev] High CPU usage To: speex-dev at xiph.org Message-ID: <loom.20120613T115653-705 at post.gmane.org> Content-Type: text/plain; charset=us-ascii Mark Schilling <mark_schilling <at> gmx.de> writes: > > Hi Jozsef, > > this approach sounds interesting. > Do have you have some source code available ? > > Thanks > > Mark > > -----Original Message----- > From: speex-dev-bounces <at> xiph.org [mailto:speex-dev-bounces &lt...

I have run into the same issue. Before sending a frame to encoder, I calculate the energy. If it is less than a small threshold, I simply replace this frame with "silence frame," which is 320 random samples of values smaller than 3 (16 kHz). BTW, I have only experience this problem with certain USB headsets that provide you all 0 samples when muted. Jozsef

...ted. Using FIXED_POINT solved it. But what are the drawbacks of FIXED_POINT in comparison to FLOATING_POINT? Mark -----Urspr?ngliche Nachricht----- Von: speex-dev-bounces at xiph.org [mailto:speex-dev-bounces at xiph.org] Im Auftrag von Jozsef Vass Gesendet: Freitag, 25. September 2009 23:43 An: mark_schilling at gmx.de Cc: speex-dev at xiph.org Betreff: Re: [Speex-dev] High CPU usage I have run into the same issue. Before sending a frame to encoder, I calculate the energy. If it is less than a small threshold, I simply replace this frame with "silence frame," which is 320 random samples of va...

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

Hi Tanmay, >Does compiling speex API with DISABLE_FLOAT_API and DISABLE_VBR solve the >problem? I remember that this fixed the problem. But at that time I also needed VBR so this was not an option. As far as I know, it is related to some calculations that involve float denormals that cause the high CPU usage. Today I'm still using the following code before speex_encoder_init and

Hi Marian, I took a brief look at RFC 5574 and as far as I understand, you can simply do it like this: SpeexBits b; speex_encode(state, some320bytePCM1, &b); speex_encode(state, some320bytePCM2, &b); After that, get the encoded data with speex_bits_write and put it in your packet. Mark -----Original Message----- From: speex-dev-bounces at xiph.org [mailto:speex-dev-bounces at

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

Hi Jeff, Hi Jean-Marc, I first modified the FPU control word to raise an exception whenever a denormal is used. Then I used the debugger to locate the exceptions and added VERY_SMALLs where they seem to fit well. Although I got CPU usage as low as 10%, I seriously lack knowledge of how things work inside speex. So just changing some code is not the best idea for me. My second attempt was to