search for: manual_alloc

Hi, I am currently encoding 32 Khz/Qual-10/UWB encode mode, with MANUAL_ALLOC enabled ( similar to the c5x/c6x configuration). In file sb_celp.c, I noticed the scratch memory grow during recursive (UWB -> WB) calls to 'sb_encode'. 1. 'stack' was not tracked (with 'tmp_stack' as done at other palaces) after/before - auto-correlation/Levinson-...

...y in binary format just to test it decoded back to the I2S channel from the saved file), but I've some difficulties understanding where to start from. Where can I find an example of usage of the libspeex in an embedded platform? Currently I've built the library with a couple of defines: - MANUAL_ALLOC (and the others relevant defines to use static memory) - FIXED_POINT But it still doesn't work (encoded/decoded audio is garbage). So, sorry for the silly questions, but can someone gently point me towards the ligth switch ? :-D Thanks Pietro

Hi, I am using speex 1.2beta2 on a C5416, 16 bit, narrowband. The project I am implementing speex into is very limited in Data space. In the speex decode_init and encode_init there are allocs that, combined, take up 0x0F94 of data memory. I do not know why the various allocs are sized the way they are but that number is too big to fit into our project. I was wondering if those numbers (for

Good afternoon! Thank you for your product Speex. We want to use it in microcontroller AT91SAM7S256 (48 MHz). We applied the following: #define FIXED_POINT #define DISABLE_WIDEBAND #define DISABLE_HIGHPASS #define MANUAL_ALLOC #define OS_SUPPORT_CUSTOM at speex_encoder_init(&speex_nb_mode); speex_decoder_init(&speex_nb_mode); tmp=2; speex_encoder_ctl(st, SPEEX_SET_QUALITY, &tmp); Encoding time for one frame (20 ms) is 46 ms, and decoding time is 4 ms. Is it possible to reduce encoding time? Thank...

The majority of a Speex encoder app does fit in a 6713. The 6713 has 8K of L1 and another 256K of memory 64K of which can be configured as L2 cache. (16,32,48, or 64K). One level of TI's website seems to incorrectly indicate only 64K of L2. I turned off MANUAL_ALLOC and have it allocating internal memory using calloc(). I did change the L2 cache to 2 way (32K) and adjusted the heap size to 12K to get it to fit. I put a wavefile and the .cinit, .const up in the SDRAM. name origin length used attr fill ------...

...w where that clicking noise is coming from. Any advice/comments/suggestions? Here's what's included in my config.h file for Speex (compiled with -DCONFIG_TI_C6X): #define FIXED_POINT #define FRAME_SIZE 160 #define DISABLE_WIDEBAND #define MAX_CHARS_PER_FRAME (42/BYTES_PER_CHAR) #define MANUAL_ALLOC #define USER_MISC Speex narrow band parameters I'm using: Quality: 2 /* 5950 bps */ Enhancement: 0 Vbr: disabled Complexity: 1 The DaVinci processor is relatively new and I can't seem to find anyone who has successfully used Speex on the DSP side. Your help is apprecia...

...nd other times it will not work at >all. > >I think I've found the source of the problem. The speex_alloc() >function, called by speex_echo_state_init(), calls calloc() and returns >a zeroed array. On the other hand, the TI implementation (as it is if >you don't change the MANUAL_ALLOC define) replaces speex_alloc() with a >different version that doesn't use the heap but only allocates memory >from a large application-supplied memory block. Nothing zeroes this >memory, and there is no hint in the comments (ti\user_misc.h, lines >36-46) to let me know that the bloc...

I started my project using the CodeComposerStudio speex_C64_test.pjt in speex 1.1.11.1. To build using floating point, I created a new project with the same files and modified ti\config.h to #undef FIXED_POINT. Is there a better way to configure a floating point processor? I have a few TI specific optimizations that could go into the next release. What's the procedure for submitting code?

> I followed your advice on running the trivial case. The float version > started cancelling sounds out within a second. The fixed point > version also worked, but took a little longer before the effect was > noticeable. Since I now realized the fixed point version might need a > little more tweaking than the float version, I started modifying some > things and ended up with the

...om. Any advice/comments/suggestions? > > Here's what's included in my config.h file for Speex (compiled with -DCONFIG_TI_C6X): > > #define FIXED_POINT > #define FRAME_SIZE 160 > #define DISABLE_WIDEBAND > #define MAX_CHARS_PER_FRAME (42/BYTES_PER_CHAR) > #define MANUAL_ALLOC > #define USER_MISC > > Speex narrow band parameters I'm using: > Quality: 2 /* 5950 bps */ > Enhancement: 0 > Vbr: disabled > Complexity: 1 > > The DaVinci processor is relatively new and I can't seem to find anyone who has successfully used...

...mes it will work well, and other times it will not work at all. I think I've found the source of the problem. The speex_alloc() function, called by speex_echo_state_init(), calls calloc() and returns a zeroed array. On the other hand, the TI implementation (as it is if you don't change the MANUAL_ALLOC define) replaces speex_alloc() with a different version that doesn't use the heap but only allocates memory from a large application-supplied memory block. Nothing zeroes this memory, and there is no hint in the comments (ti\user_misc.h, lines 36-46) to let me know that the block must be zeroed...

...ther times it will not >work at all. > >I think I've found the source of the problem. The speex_alloc() >function, called by speex_echo_state_init(), calls calloc() and returns >a zeroed array. On the other hand, the TI implementation (as it is if >you don't change the MANUAL_ALLOC define) replaces speex_alloc() with a >different version that doesn't use the heap but only allocates memory >from a large application-supplied memory block. Nothing zeroes this >memory, and there is no hint in the comments (ti\user_misc.h, lines >36-46) to let me know that the b...

Jerry, I think that just removing the FIXED_POINT define should be sufficient, though you mind want to turn off MANUAL_ALLOC, because I am not sure if the memory usage is identical for the fixed point build, and the constants in config.h are set for the fixed point build. Are you testing on the simulator, or on an eval board? It does not look like the 6713 has enough memory to hold Speex (64K vs. 1024K for the 6416...

...om. Any advice/comments/suggestions? > > Here's what's included in my config.h file for Speex (compiled with -DCONFIG_TI_C6X): > > #define FIXED_POINT > #define FRAME_SIZE 160 > #define DISABLE_WIDEBAND > #define MAX_CHARS_PER_FRAME (42/BYTES_PER_CHAR) > #define MANUAL_ALLOC > #define USER_MISC > > Speex narrow band parameters I'm using: > Quality: 2 /* 5950 bps */ > Enhancement: 0 > Vbr: disabled > Complexity: 1 > > The DaVinci processor is relatively new and I can't seem to find anyone who has successfully used...