similar to: TMS320VC5502

Hi all, I'm trying to build the celt package on the Texas TMS320VC5510 DSK. I think there are some #define for it in the code, but I'm doing something wrong. Is there any documentation about it? So far I'm building with the TI_C5X_ASM;CONFIG_TI_C55X #define. Any help? Thank you. Giovanni

Hi, I am an applications engineer for Texas Instruments in the UK. I am trying to port the CELT codec to the C5505, this has HW accelerated FFT engine (http://focus.ti.com/docs/prod/folders/print/tms320vc5505.html). I am having problems with the stack allocation. Do you have any reference code that compiles for the C55x under CCS (code composer studio)? *******************************

hi, this patch should fix the symbian build. /alfred -------------- next part -------------- A non-text attachment was scrubbed... Name: speex-symbian2.patch Type: text/x-patch Size: 2669 bytes Desc: not available Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20061115/5ac4915e/speex-symbian2.bin

Hi,I have been trying some different sample rate and bitrate combinations to get a feel for how CELT behaves,too, like Andrew Lentvorski. But I want to use VBR option.I want to ask a question about VBR in CELT codec.Can we use VBR option in CELT ??? "byte_per_packet" variable in code means constant bit rate, does not it ?In this code : bytes_per_packet is constant.len =

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

Hi With 32-bit Xubuntu-14.04. When I compile FFmpeg from git using speex-1.2rc1 it builds OK. When I compile FFmpeg from git using speex-git it fails to build. (speex-HEAD-78cce67) It's not a big deal, I don't mind using speex-1.2rc1. But am I doing something wrong or is there something wrong with speex-git? (I've put the details in a txt attachment to keep this email post

Hi Jim, > Build 11169 in SVN works correctly. Good. I'll try not to forget the EXTEND32 from now on. > I have attached a zip file (renamed > .txt) with a patch to bits.c to make the byteswapping for TI DSPs > consistent. Seems like unzip can't read it. Either it's in an unknown format or the file got corrupted. Could simply send as multiple (uncompressed)

hi Jean-Marc, I just updated from svn and it looks like there are some errors in the speex.mmp file. the filters.c is duplicated, and the fft/kiss.c files are still missing.. /alfred Jean-Marc Valin wrote: > Applied in svn. Thanks. > > Jean-Marc > > Alfred E. Heggestad a ?crit : >> hi, >> >> this patch should fix the symbian build. >> >> >>

> You found it. The SHL32 (not SHR32) line fixes the problem. It must be > doing a 16-bit shift, then extending the result (which is reasonable). As > it happens, that it the same macro which gave us trouble last May > (25th/26th), when the C55 build was more subtlely broken. Yes, that's what I finally remembered. I think I've fixed all occurrences (by adding EXTEND32)

Stuart, Jean-Marc, >> 1) We need our own "fixed_xx.h" header file. I don't know why, and >> haven't >> had time to investigate, but there is a definite improvement when I use >> the >> attached fixed_c55x.h file which has turned all the maths into inline >> functions. > > Did you try with fixed_generic.h or just with fixed_debug.h?

I am having trouble compiling Opus for my TI55xx project. When I define CONFIG_TI_C55X, I get several compile errors regarding int vs long and int vs opus_int32. (i.e. int *value = va_arg(ap, opus_int32*); in opus_decoder_ctl). Also, shouldn't the following be included at the top of opus_types.h? #ifdef HAVE_CONFIG_H #include "config.h" #endif Thanks.

Hi, I'm trying to make OPUS run on TI55, at the moment on the evm 5515 board. I'm compiling with FIXED_POINT, DISABLE_FLOAT_API, TI_C5X_ASM, CONFIG_TI_C55X. I'm actually interested only in the CELT part, so I'm also using OPUS_APPLICATION_RESTRICTED_LOWDELAY. It compiles but I'm still having few problems. I was wondering if anyone succeeded in making it run on this device, or

Hello to everyone! During building speex library for Symbian OS I encountered some problems. All thess problems can be solved by modifying the speex sources. I don't have access to SVN repository of speex, so I will just describe the changes to be done: 1) mmp file in symbian derictory misses windows.c sources. You need to add this string into speex.mmp: SOURCES windows.c 2) Symbian OS

Hi Jean-Marc, Hi Jim, I have also seen some problems with the 1.1.8 release on the C55x. So far I have boiled down the issues to the following: 1) We need our own "fixed_xx.h" header file. I don't know why, and haven't had time to investigate, but there is a definite improvement when I use the attached fixed_c55x.h file which has turned all the maths into inline functions.

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

Hello ! I am developing a kind of phone using TI's OMAP 5912 and speex. The soft works great on ARM, and it is time to move speex and voice processing stuff to DSP. Could some one point me how to do it ? Should I install CCS ? Or it possible to compile speex using just ti_dsptools ? Does anybody ran speex and dsp gateway ? It would be great, if some one share makefile, cmd etc. for

Hi Stuart, > 1) We need our own "fixed_xx.h" header file. I don't know why, and haven't > had time to investigate, but there is a definite improvement when I use the > attached fixed_c55x.h file which has turned all the maths into inline > functions. Did you try with fixed_generic.h or just with fixed_debug.h? fixed_debug.h uses int and short directly, so I know

hi, am trying to understand speex's algo. have a few questions. 1) autocorrelation: in the function, _spx_autocorr (for floating point version), there is a line ac[0] += 10; correct me if i am wrong, i suppose the addition of 10 is used to condition the autocorrelation matrix. wonder how the value of 10 is arrived at? 2) levinson durbin (LD) algo in the function _spx_lpc, i referred

Hi Jean-Marc I'm looking at the 1.0.5 source, and I'm not seeing an _spx_lpc(). There's an _spx_autocorr(), which is in lpc.c and is called near the start of the encoder function in nb_celp.c. The encoder seems to call the autocorr() function, then calls wld() to do something called Levinson-Durbin. Am I right in thinking that after the call to wld(), the st->lpc[] array

- Replaced blanket #define of 8 & 64 bit types with typedefs for each platform to match 16 & 32 bit types. - Updated existing typedefs for each platform to fix odd values and improve consistency. --- include/opus_types.h | 125 ++++++++++++++++++++++++++++++++++++++++----------- 1 file changed, 100 insertions(+), 25 deletions(-) diff --git a/include/opus_types.h