search for: disable_vbr

...uffer algorithm and resampler improvements/fixes. This is also the first release where libspeex can be built without any floating point support. To do this, the float compatibility API must be disabled (--disable-float-api or DISABLE_FLOAT_API) and the VBR feature must be disabled (--disable-vbr or DISABLE_VBR). You can download it from http://www.speex.org as usual. Have fun, Jean-Marc

I need to shrink speex so it will fit on an embedded processor along with some other code. The chip has only 20k of ram. I have done some work with libspeex.dsp by removing references to all modes but narrow band 8000 hz (submode 3). I used the defines: FIXED_POINT, DISABLE_FLOATING_POINT_API, DISABLE_VBR. I also removed the structures for the other submodes and the functions that they called. I reduced the NB_DEC_STACK and NB_ENC_STACK to the smallest values and minimized the heap based on all calls to calloc. I haven't optimized the call stack yet. I reduced the ram usage to around 6k. Th...

...resampler improvements/fixes. This is also the first release where > libspeex can be built without any floating point support. To do this, > the float compatibility API must be disabled (--disable-float-api or > DISABLE_FLOAT_API) and the VBR feature must be disabled (--disable-vbr > or DISABLE_VBR). You can download it from http://www.speex.org as usual. > > Have fun, > > Jean-Marc > _______________________________________________ > Speex-dev mailing list > Speex-dev@xiph.org > http://lists.xiph.org/mailman/listinfo/speex-dev > > ___________________________...

...g > http://lists.xiph.org/mailman/listinfo/speex-dev > Hi, I am having a similar problem. Definitely when some head phones are muted I get high CPU usage. Also it seems on some older machines using Pentium 4 the CPU usage is very high. Does compiling speex API with DISABLE_FLOAT_API and DISABLE_VBR solve the problem? Thanks Tanmay ------------------------------ Message: 2 Date: Wed, 13 Jun 2012 20:41:07 +0200 From: "Mark Schilling" <mark_schilling at gmx.de> Subject: Re: [Speex-dev] High CPU usage To: speex-dev at xiph.org Message-ID: <20120613184107.245260 at gmx.n...

...working Visual Studio 6.0-2017 solutions * Generates working Unix Makefile * Supported options (<option> - <default value>): * `ENABLE_FLOATING_POINT` - on * `ENABLE_FIXED_POINT` - off * `ENABLE_FIXED_POINT_DEBUG` - off * `USE_GPL_FFTW3` - off * `DISABLE_FLOAT_API` - off * `DISABLE_VBR` - off * `ENABLE_VORBIS_PSY` - off * `ENABLE_SSE` - on if supported * `ENABLE_ARM4_ASM` - off * `ENABLE_ARM5E_ASM` - off * `ENABLE_BLACKFIN_ASM` - off * `ENABLE_TI_C55X` - off * `USE_SPEEXDSP` - on if library found * `DISABLE_BINARIES` - off * `ENABLE_PACKAGE_CONFIG` - on, [CMake...

...r algorithm and resampler improvements/fixes. This is also the first release where libspeex can be built without any floating point support. >To do this, the float compatibility API must be disabled (--disable-float-api or DISABLE_FLOAT_API) and the VBR feature must be disabled (--disable-vbr or DISABLE_VBR). Does 14525 still need this limit? Has this problem fixed by the newest revision 16402? Thanks Barry

Greetings to All! Now I am trying to run speex on TI DSP... I need only coder+decoder+AEC. Bitrate 8000bps. Building with floating point support. What can i do, to reduce RAM consumption? I mean very serious RAM optimisations. Deleting not used structure fields, etc... May be I can do something with alloc... Help me to determine that it is possible to throw out. What is best result(in RAM

...fit on an embedded processor along >> with some other code. The chip has only 20k of ram. I have done >> some work with libspeex.dsp by removing references to all modes but >> narrow band 8000 hz (submode 3). I used the defines: FIXED_POINT, >> DISABLE_FLOATING_POINT_API, DISABLE_VBR. I also removed the >> structures for the other submodes and the functions that they called. >> I reduced the NB_DEC_STACK and NB_ENC_STACK to the smallest values >> and minimized the heap based on all calls to calloc. I haven't >> optimized the call stack yet. I redu...

...u can probably reduce that to >2-3 kB if you only use a single narrowband mode. Nullifying the pointers means that I don't treat the code as a black box. Which means that if I upgrade to the next version of the library I'd have to reapply the patches. >> For starter, I would like DISABLE_VBR analogous to DISABLE_WIDEBAND. >> After that, it's probably possible to put vocoder under conditional compilation >> the stuff that is used only in vocoder modes. It seems that modes 3 to 7 are too >> similar to each other to save significant amount of code by eliminating som...

...c. It would be nice to have a README.code-reduction >file that collected some of the advice that hits the list from time to time. Yes, the final application very likely to use a single data rate. And yes, readme.code-reduction is an excellent idea. >>>> For starter, I would like DISABLE_VBR analogous to DISABLE_WIDEBAND. >>>> After that, it's probably possible to put vocoder under conditional >>>> compilation >>>> the stuff that is used only in vocoder modes. It seems that modes 3 to 7 >>>> are too >>>> similar to each...

...entation would be so simpler and more reliable. On the code size things are less rosy. The wideband indeed goes away with DISABLE_WIDEBAND but that's about all. Due to extensive use of function pointers very little unused stuff beyond wideband goes away when unused. For starter, I would like DISABLE_VBR analogous to DISABLE_WIDEBAND. After that, it's probably possible to put vocoder under conditional compilation the stuff that is used only in vocoder modes. It seems that modes 3 to 7 are too similar to each other to save significant amount of code by eliminating some of them, but I have a fe...

...+88,7 @@ return 0; } -int speex_std_high_mode_request_handler(SpeexBits *bits, void *state, void *data) +EXPORT int speex_std_high_mode_request_handler(SpeexBits *bits, void *state, void *data) { spx_int32_t m; m = speex_bits_unpack_unsigned(bits, 4); @@ -97,7 +97,7 @@ } #ifndef DISABLE_VBR -int speex_std_vbr_request_handler(SpeexBits *bits, void *state, void *data) +EXPORT int speex_std_vbr_request_handler(SpeexBits *bits, void *state, void *data) { spx_int32_t vbr; vbr = speex_bits_unpack_unsigned(bits, 1); @@ -106,7 +106,7 @@ } #endif /* #ifndef DISABLE_VBR */ -int spe...

...ements/fixes. This is also the first release where >> libspeex can be built without any floating point support. To do this, >> the float compatibility API must be disabled (--disable-float-api or >> DISABLE_FLOAT_API) and the VBR feature must be disabled (--disable-vbr >> or DISABLE_VBR). You can download it from http://www.speex.org as usual. >> >> Have fun, >> >> Jean-Marc >> _______________________________________________ >> Speex-dev mailing list >> Speex-dev@xiph.org >> http://lists.xiph.org/mailman/listinfo/speex-dev >>...

...peex so it will fit on an embedded processor along > with some other code. The chip has only 20k of ram. I have done > some work with libspeex.dsp by removing references to all modes but > narrow band 8000 hz (submode 3). I used the defines: FIXED_POINT, > DISABLE_FLOATING_POINT_API, DISABLE_VBR. I also removed the > structures for the other submodes and the functions that they called. > I reduced the NB_DEC_STACK and NB_ENC_STACK to the smallest values > and minimized the heap based on all calls to calloc. I haven't > optimized the call stack yet. I reduced the ram usag...

How much memory reduction are you after? There's lots of stuff you can delete, starting with defining DISABLE_VBR, DISABLE_WIDEBAND and DISABLE_FLOAT_API. From there, you can delete all the *table.c files except for exc_10_32_table.c, gain_table_lbr.c and lsp_tables_nb.c. In libspeexdsp, you can pretty much delete everything (preprocessor, jitter buffer, resampler, ...) but mdf.c Jean-Marc ??????? ???????...

Hi Tobias, I don't know if you've noticed, but ST actually released an optimised port of Speex for their chip (see mailing list archive). About disabling wideband, that can be done by defining DISABLE_WIDEBAND. You probably also want to define DISABLE_VBR and DISABLE_FLOAT_API. As you noted, you can also disable more than half the codebooks. That being said, I think adding a bunch of macros to the main codebase to do that automatically, would just make things more confusing. Jean-Marc Tobias Erichsen a ?crit : > Hi everyone, > > I'm...

...CPU usage of Speex the most is whether it is compiled for floating point or fixed-point. [...] On the x86 architecture, floating-point is generally faster, but not always. " And: "Until the VBR feature is ported to fixed-point, you will also need to configure with ?disable-vbr or define DISABLE_VBR." So at least variable bit rate is not supported with FIXED_POINT. Mark -----Original Message----- From: speex-dev-bounces at xiph.org [mailto:speex-dev-bounces at xiph.org] On Behalf Of Mark Palkow Sent: Wednesday, September 30, 2009 11:52 AM To: speex-dev at xiph.org Subject: Re: [Speex-...

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

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

...+88,7 @@ return 0; } -int speex_std_high_mode_request_handler(SpeexBits *bits, void *state, void *data) +EXPORT int speex_std_high_mode_request_handler(SpeexBits *bits, void *state, void *data) { spx_int32_t m; m = speex_bits_unpack_unsigned(bits, 4); @@ -97,7 +97,7 @@ } #ifndef DISABLE_VBR -int speex_std_vbr_request_handler(SpeexBits *bits, void *state, void *data) +EXPORT int speex_std_vbr_request_handler(SpeexBits *bits, void *state, void *data) { spx_int32_t vbr; vbr = speex_bits_unpack_unsigned(bits, 1); @@ -106,7 +106,7 @@ } #endif /* #ifndef DISABLE_VBR */ -int spe...