search for: user_misc

...> less messy than misc.h/misc.c were. The TI C64x build produces bit-exact results with build 12825 (April 2007, a bit before 1.2beta2). The C54x and C55x builds did not work because the manual allocation scheme was broken when misc.c was removed. The old override mechanism was: 1. Define USER_MISC in config.h 2. In, misc.c, include user_misc.h if USER_MISC is defined 3. Put the allocation override code in user_misc.h. The result is that the override code is included in one source file (misc.c), so there are no duplicate definitions. How would you like to see this implemented under the...

...about 0.5kB in the test builds. This could be reduced by moving the guts of the routines to a separate C file, and reducing the inline functions to just call those routines. I have not had time to test that approach, but the present patch is sufficient to get the build working again. Also, ti/user_misc.h should be replaced by the similar ti/os_support_custom.h file, which is also attached. I remember your having some trouble reading my patches (from Tortoise SVN) before, so let me know if I need to format this differently for you to use it. Sorry if this was holding you up. - Jim ----- Or...

...ion (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 externally. I >believe this should be clarified in these comments, or perhaps instead >add a memset in speex_alloc() in ti\user_misc.h to zero the memory. >Now that I'm zeroing this block in my initialization, everything...

> 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

...(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 externally. I >believe this should be clarified in these comments, or perhaps instead >add a memset in speex_alloc() in ti\user_misc.h to zero the memory. >Now that I'm zeroing this block in my initialization, everythi...

Please correct me if I am wrong, Jean-Marc, but I do not think that any patches are getting applied to 1.0.5 anyway. Also, if you expect a patch to be applied, you will need to provide the changes as a patch, not as a modified copy of the source tree. The 1.2 branch includes a mechanism for private memory allocation from a static buffer. You provide a usermisc.h file that replaces the

...e 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 externally. I believe this should be clarified in these comments, or perhaps instead add a memset in speex_alloc() in ti\user_misc.h to zero the memory. Now that I'm zeroing this block in my initialization, everything seems to be wor...

...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 appreciated. Thanks. Re...

I have sent the visual studio project files that compile the speex client to jean-marc directly (as an attachment), sometime this week, I will also upload the binary builds of static library files to my site www.phonestack.com. I am porting our LTP (lightweight telephony protocol) to some embedded systems. I require to run speex in an environment that doesn't support memory allocations. How

...NG method is not efficient in reducing the code footprint because the >> majority of the overhead happens in the points of invocation of the speex_warning rather than >> in the function itself. > >How about: >#define OVERRIDE_SPEEX_WARNING >#define speex_warning(x) {} >in user_misc.h? That should do the trick. May be. But once again, why not do it in official release? >> With all my suggestion applied there is an opportunity that minimized speex would fit in on-chip >> code memory of BF532 (48KB). However the original goal of fitting in BF531 (32KB of on chip co...

...uggestions? > > 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....

...est.cmd (C5509A linker command file) speex_c55_test\speex_c55_test.pjt (Code Composer Studio Project File ) src\boot.asm (to force wait states to 0 for the simulator, otherwise cycle count is much too high) src\testenc-54x.c (derived from testenc.c, manual alloc, byte packing/unpacking added) src\user_misc.h (contains the manual memory alloc routines, with debug code ) Could you? Thanks, Mateus Lima * * -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/speex-dev/attachments/20050901/8ec29f80/attachment.htm

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

...that I would suggest here. I was not able to use the default speex_alloc for this build, because the TI calloc routine would not work with a heap larger than 16383 chars, with the small memory model that I am using. I was already using a different alloc mechanism in the encoder/decoder build (user_misc.h in the ti directory), and I used that method successfully here. However, since kiss_fft_alloc was not using speex_alloc, I ended up with two memory allocation methods. Then I scratched my head for a while because kiss_fft had used up almost all of the heap, and fwrite would not work, so my...

...test.cmd (C5509A linker command file) speex_c55_test\speex_c55_test.pjt (Code Composer Studio Project File ) src\boot.asm (to force wait states to 0 for the simulator, otherwise cycle count is much too high) src\testenc-54x.c (derived from testenc.c, manual alloc, byte packing/unpacking added) src\user_misc.h (contains the manual memory alloc routines, with debug code )

This must have been an enormous pain to track down. The manual alloc routine in the TI directory (user_misc.h) clears the allocated memory, but maybe you have changed this. >> it will just start filling data in, which it shouldn't. I see that >> innov_save is set at the beginning of a for loop at: >> for (sub=0;sub<st->nbSubframes;sub++) >> { > ... >>...

...uggestions? > > 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....

hi, I am using speex1.2beta2 on a TI 54x on narrow band I have been trying to get speex to work for a while now, and it's been a real teeter-totter ride. For a long time I noticed that I will get a project to work and then without changing any code and programming it to an eprom/flash the project will not work. It turns out it was a value called innov_save. I found this bugger by zero

Hi, Just a couple tips to reduce complexity. First, I think you'd get a good speedup by enabling the PRECISION16 switch (if it's not done already). This (very) slightly reduces quality, but means you convert a lot of "emulated" 16x32 multiplications into 16x16. There are also several routines that would benefit from platform-specific optimizations. There are already

-----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: Thursday, June 14, 2007 11:17 PM To: Michael Shatz Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] Blackfin inline assembler and VisualDSP++ toolchain Michael Shatz a ?crit : >>> Actually, you're the first I know using the VisualDSP++ toolchain >>> :-) >> >> I guess