search for: c5416

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

Hi, I am using 1.2beta2 on a C5416 doing narrowband in the decode function I am having a problem with the execution of my program vectoring off to random interrupts that are not used. I have tracked down the error to the highpass function called in nb_decode -very close to the end of the function-context: it is called here: l...

...you can tweak the sizes in config.h. You just have to declare the variable and add this init before the call to speex_encoder_init, and go back and look at the variable after you run some data through. #ifdef STACKDBG spxGlobalScratchFree = spxGlobalScratchPtr; #endif If you think that the C5416 build is broken, then (as Jean-Marc said) tell us what version you are using. There is a C54x project in the speex source tree that runs directly in the Code Composer simulator. If that fails in the latest code, let me know and I will work on tracking it down. As Jean-Marc indicated, this build...

...n tweak the sizes in config.h. You just have to declare the variable and add this init before the call to speex_encoder_init, and go back and look at the variable after you run some data through. #ifdef STACKDBG spxGlobalScratchFree = spxGlobalScratchPtr; #endif If you think that the C5416 build is broken, then (as Jean-Marc said) tell us what version you are using. There is a C54x project in the speex source tree that runs directly in the Code Composer simulator. If that fails in the latest code, let me know and I will work on tracking it down. As Jean-Marc indicated, this build...

...you can tweak the sizes in config.h. You just have to declare the variable and add this init before the call to speex_encoder_init, and go back and look at the variable after you run some data through. #ifdef STACKDBG spxGlobalScratchFree = spxGlobalScratchPtr; #endif If you think that the C5416 build is broken, then (as Jean-Marc said) tell us what version you are using. There is a C54x project in the speex source tree that runs directly in the Code Composer simulator. If that fails in the latest code, let me know and I will work on tracking it down. As Jean-Marc indicated, this build...

If you look at low cost (~$10 to $20 at quantities) fix-point DSPs (TI C5416 for example), they don't have a lot of on-chip RAM. 5416 has 128k, which is already a lot. Of cause you can use external RAM, but this not only will increase cost and board space, but will also degrade performance a lot. Many of the speed-enhancing tricks only work with on-chip memory. Once you...

Hi all: I am a newbie to vorbis, and I want to develop vorbis decoder onto TI c6701 evm board. And I try the tremor code and libvorbis and the code from http://www.xiph.org/archives/tremor/200210/0001.html . But all of them stll work good in MSVC but terrible in c6701. I dont know wher the problem is??Problem of code or problem of memory allocation?? it decodes almost noise,.... When I

...irst experience with vocoders and dissecting a professional's code. I work for a company that is currently using a G729A vocoder from a 3rd party software company and is looking into speex so they no longer have to pay royalties. The product we are trying to force speex into is based on a TI C5416 DSP that did narrowband 8-bit, 8kbs. The product was fairly full as it is so some modifications had to be made in order to fit speex into the project just to allow it to link. The modifications are based off assumptions that I made when looking over the code so I may have been absolutely wrong....