similar to: Data space crunching-how small can I get?

Can someone enlighten me on what the status is of aspect ratio in theora is ? The ti structure has aspect_num and _den values, which I assume give the intended display aspect ratio (e.g. 4/3). The sample files on the bittorrent seem to say both values are 0 for all files. I'd think it should at least be made impossible to have a 0 as the denominator. The library doesn't check the

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-Durbin scope (~line

Hi, Attached is my patch to add theora encoding to ffmpeg's libavcodec (by using libtheora). I am requesting help to fix the bug I mention below and am seeking general comments before I submit the patch properly. Files encoded using this encoder have a problem playing in VLC. The files will not play unless "Drop late frames" has been unticked in the advanced video settings.

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: ln 1719 for me if (st->highpass_enabled) highpass(out,

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?

Hi, I'm evaluating the libspeex library for usage in an embedded platform based on an ARM7 TDMI micro (the ubiquitous Atmel AT91SAM7S). In details, I'm trying to use libspeex to encode the audio stream coming into the micro from an I2S channel and saving the encoded audio to an SD card (currently in binary format just to test it decoded back to the I2S channel from the saved file), but

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,

> 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

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

Hi, I've been trying to get Speex to compile and run on the DSP of TI's new DaVinci System-On-Chip processor, which has both an ARM (ARM926) and a DSP (C64+, based on the C6400). I used the latest code (1.2beta) and followed the example in the speex- 1.2beta1/ti/speex_C64_test trunk to build the Speex library for the DSP. Basically I have a loopback application on the ARM that samples

Itay, >I am trying these things, but the main problem that has been bothering >me recently is that the fixed-point algorithm works "sometimes". Meaning >that sometimes 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

Hi Jean-Marc, I have tested Speex in fixed-point mode on my PC without clicking noise. As I mentioned below, I tested Speex in fixed-point mode running natively on the ARM side of the DaVinci without click noise. I only get the clicking noise when running Speex on the DSP side. For the TI C64+ DSP on the DaVinci processor, the TI-specific switches doesn't do much other than defining the

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

Jean-Marc was correct in that the 16bit value was the culprit for my encoding woes. after I changed that to a 32 bit value I believe it encodes correctly, but I really don't have much of any way to know this absolutely. I am using the 1.2beta2. I would use the enctest program, I have looked it over and based a lot of what I am doing on that code but the project I am developing this on is

Mike, Generally "Invalid mode encounterd" == "frames are misaligned" You should be getting 20 bytes from the encoder each time, and passing 20 bytes to the decoder each time. Is it correct that you have modeled your main loop after testenc-TI-c5x.c? If you look at encoded silence with a binary editor, you should be able to see the 20-byte repetition pattern. You can also

I thought I should be getting 20 words because in the windows app the command line repeats "nbBytes = 20" through the entire decode phase. I wonder how the frames got misaligned...right now I get 10 words of data followed by 10 words of 0's which I look at through a memory window in code composer. now I am pretty sure there is a terminator word that gets in there so that would make

Jean-Marc, I am trying these things, but the main problem that has been bothering me recently is that the fixed-point algorithm works "sometimes". Meaning that sometimes 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

Jim, You're right, the memset really is there, how could I miss that? :) I also spoke too soon, as my change doesn't solve anything. At each run, something random causes the algorithm to either work or not work at all. There is a correspondence between whether the echo cancel works and whether the st->PHI and st->W arrays contain data or zeroes. (the arrays contain zeroes when alg

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 go off chip, you lost a

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