similar to: Clicking noise using Speex built for TI C64+ DSP of DaVinci Processor

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

Sorry everyone, but I figured it out; it's working now. The problem was in my monoToStereo and stereoToMono functions (the Linux OSS driver on the ARM side only supports stereo so I had to convert it to mono before feeding it to Speex); also I had an alignment issue with my buffers I was using on the DSP side. Thanks Jim/Jean-Marc for your help! Regards, Andy ----- Original Message ----

Hi, My company just recently bought a TI DaVinci development board and I'm trying to port Speex to run on it. The TI DaVinci chip has an ARM926 processor and a TMS320C64+ DSP in it. I was able to get Speex somewhat working on a TMS320VC5510 about a year ago but I was wondering is there anything special I need to do to get Speex working on the TMS320C64+ DSP in the DaVinci chip. I

Hi, I'm currently working on the TI DaVinci processor, which has an ARM926 processor and a TMS320C64+ DSP in it. I have been using Speex 6kbps (narrowband, quality=2, complexity=1, perceptual_enh=0) on the DSP C64+ side without any issues; the voice sounds very good for such a low bandwidth requirement. However, recently, I tried out the 4kbps mode (changing quality to 1) on the DSP and it

Hi, My company just recently bought a TI DaVinci development board and I'm trying to port Speex to run on it. The TI DaVinci chip has an ARM926 processor and a TMS320C64+ DSP in it. I was able to get Speex somewhat working on a TMS320VC5510 about a year ago but I was wondering is there anything special I need to do to get Speex working on the TMS320C64+ DSP in the DaVinci chip. I

Jerry, Thanks for the response; basically, I need to get just the narrow band working now (maybe use advanced features such as jitter buffer, echo cancellation, VAD, etc in the future); the DSP will do the encode and decode simultaneously as data are available. My main objective is just do a voice application that runs on the ARM side of the DaVinci with the codec running on the DSP side; the

Thanks Jean-Marc. Is there a Speex trunk for the C64xx I can use? Or do I have to figure what options to turn on (in configure) when building the library? Thanks. Regards, Andy Ngo ----- Original Message ---- From: Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> To: ndno72-speex@yahoo.com Cc: jtrantow@ieee.org; speex-dev@xiph.org Sent: Tuesday, December 5, 2006 2:52:02 PM Subject:

Tried your fixed_generic.h change but that didn't help. Andy ----- Original Message ---- From: Andy Ngo <ndno72-speex@yahoo.com> To: Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> Cc: speex-dev@xiph.org Sent: Wednesday, December 12, 2007 4:13:35 PM Subject: Re: [Speex-dev] 4kbps sounds robotic on TMS320C64 Jean-Marc, Yes, fixed-point is enabled (#define FIXED_POINT in

Do you need to encode and/or decode? I did some work optimizing the DM642 speex 1.1.11.1 encoder earlier this year. I was able to reduce the narrow band MIPS from approx 30 to 16 using some of the #pragmas and optimizing the functions (Following the BlackFin example.) The project I was working on has been put on hold so I haven't looked at the more recent changes. If you are tight on

Hi, I am attempting to port the speex library to TI Davinci DM35x Family. My questions are: 1. What is the best ./configure option for it? Is it ARM5e / ARM4 ? when I tried these two the during the compiled a warning "I suppose you can have a [ARM4/ARM5E/Blackfin] that has float instructions?" 2. is there any available demos for the echo cancellation because I can get it

Andy Ngo wrote: > Thanks Jean-Marc. Is there a Speex trunk for the C64xx I can use? Or > do I have to figure what options > to turn on (in configure) when building the library? Thanks. Support is in the main version. Just look at the TI/ directory for extra TI-related stuff. Jean-Marc > Regards, > Andy Ngo > > ----- Original Message ---- > From: Jean-Marc Valin

(Resending since the archive seems to have eaten the text.) I'm working on getting Speex running on a TI Davinci (6441), on both the ARM and the DSP. My immediate goal is to understand the processing requirements on different architectures so that I can properly specific an engineering project. I have it up and running on the ARM, and I just wanted to see if anyone could sanity-check

Jean-Marc, Yes, fixed-point is enabled (#define FIXED_POINT in config.h). I haven't tried anything lower than 4kbps; like I mentioned, 6kbps sounds fine so it's very strange. The only code I changed to get 4kbps was setting quality to 1 so that is the only difference in my test code between using 4kbps and 6kbps. It seems to be in the encoder. On the ARM side, I encoded a 8Khz 16-bit

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

> 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

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

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

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

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?

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