similar to: Artifacts in One Channel of Stereo C55x Implementation

Hello, I am interested in using the CELT codec for an embedded project around the DSP C55x family from TI. Is this someone has already done? Which is necessary to do that, which compiler, is there a specific configuration ? Is it necessary to have an Operating system to run the CELT codec ? Is it possible to instantiate several times the CELT codec ? Thank you in

Hello everyone, I just wanted to see if anyone else is using PLC on the C55x and having success? I am seeing some issues and was curious if I was doing anything wrong/stupid or maybe I have found a bug? I am using: - the CELT library from OPUS 0.9.5 ( I checked the git repo and no check ins have comments about PLC, I assume it hasn't been updated) - FRAME_SIZE: 240 - PACKET_SIZE:

Hi Jim, Thank for the patch. I'll apply it when I have a few minutes. If I haven't done so after a few weeks, please send it again. I'm in the process of relocating to Australia, so everything's a bit of a mess around here. Also, please post the c5X-specific files to the list (.cmd, .pjt, ...) so they'll be archived. Last thing, I see you defined spx_word64_t as long long for

Jean-Marc, Last week I tried the SVN code (build 11700) on the TI C55x DSP, and found that operation was broken again. I traced this to build 11522, committed on 5 June. The problem is in lsp.c, function lsp_to_lpc(). The line (lsp.c line 461 in build 11700): xin = 1<<(QIMP-1); /* 0.5 in QIMP format */ evaluates to zero. The following change corrects the problem: xin =

The attached file contains build files for TI's Code Composer Studio (CCS) for the C54x, C55x, and C6x DSPs. I had intended to post this a couple of months ago, but it took a long time to get around to doing the little bit of cleanup required. This is a file I/O loopback application suitable for running with the CCS simulators, for evaluating memory and MIPs requirements for these

Hello everyone, I have been having trouble utilizing the PLC function (I think). In older versions (0.7.1) a pointer to NULL did the trick, but with code from the tip of the GIT repository, this method causes the codec to crash on the C55x fixed point platform. I have not determined where the crash occurs. I have also attempted to pass in an array of zero's and this creates an echoey, reverby

Jean-Marc, I have attached a small patch with modifications to arch.h, bits.c, and misc.c. This contains the few mods remaining to support the various fixed point TI DSPs after the work that you did at the end of May (thank you for this). arch.h: Add switch for compilers not supporting "long long" (C55x does, C54x and older C64x does not) bits.c: Allow external definition for max

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 Randy, Thanks for reply. I have one question though. While compiling the speex (downloaded from http://downloads.xiph.org/releases/speex/speex-1.2rc1.tar.gz), I gave ./configure -enable-ti-c55x option and then built the library through make and make install using cygwin. In this case, I get this error "error: member "bits.o" of archive

Hi, I can see that there has been some effort to compile the SPEEX codec to operate on the TI c54x and c55x DSPs and I am wondering if anyone would be able to update the mailing list with their current MIPs and Memory resource requirements for their c54x and/or c55x compilation? The only estimate I was able to find in the mailing list archive was 42MIPs but I'm not sure if this is an

hey guys, I am using the tip of Git and attempting to compile for a C55x DSP. I am running into a couple compile errors and have found the source of the issue. The errors: "celt.c", line 957: error: declaration may not appear after executable statement in block as well as "celt.c", line 2303: error: declaration may not appear after executable statement in block Both of

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 =

On Thu, 2005-01-13 at 12:42 -0500, Jean-Marc Valin wrote: > Le jeudi 13 janvier 2005 ? 10:59 -0500, Jared Whitby a ?crit : > > Interestingly enough.. I started playing around with preprocessing > > options in 1.1.6 and happened upon the denoise filter > > (SPEEX_PREPROCESS_SET_DENOISE). When i run the test tone using that > > option it is completely filtered out and I

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

Jim, Thank you very much for your suggestions. I managed to get the C55x code working on the simulator. I would like to port Speex both on a C5502 EVM and a C5509A EVM. As such, if you can provide me with the details of your port on the C5509A, it would be greatly appreciated. Furthermore, I am looking for some technical documentation on the CELP algorithms. I would like to better

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?

Jean-Marc Valin wrote: > I don't know all the details, but here's a (partial) list of archs on > which I've heard of Speex running. I'm sure there are others (especially > the float version should really run on any chip with an FPU). > > float: > x86/x86-64 (SSE assembly optimizations provided) > PowerPC > SPARC I've had floating decoding running on a

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, My name is Jean Quirion and I am a DSP engineer. Currently I am working on a project where it is desired to implement a VoIP solution over a GSM GPRS link. I would like to use Speex as the vocoder for this application. This application would require the Speex encoder/decoder and possibly the pre-processor to run on a low power fixed-point DSP such as a TI C55x. Thus, I am interested in

Hello, In doing a series of non-linear estimations of a function which is a sum of a varying number of sinusoids, I would like to "autogenerate" the arguments needed by nls() depending on that number. For example, when there are two sinusoids: > nls( y ~ mu + A1 * cos(2*pi*f1*x - P1) + A2 * cos(2*pi*f2*x - P2), data = some.xy.data, start = list( mu=some.value0,