search for: c55

> The C55 and C64 builds diverge in exactly the same place as before (byte > 0x1000). The output from C55 build 11387 (svn head) diverges from C55 build > 11343 slightly later (byte 0x1116). Similarly, the output from C64 build > 11387 (svn head) diverges from C64 build 11343 slightly later (by...

..._fft is a separate packaged I merged into Speex, but which I haven't yet fully converted to use the Speex functions/macros. > My builds for the two platforms used exactly the same source files, though > there were a few ifdefs in the test_echo routine to deal with file I/O for > the C55 with its 16-bit char size. When I get a chance, I will add some > instrumentation and see if I can find where things diverge. Just looking at > the canceled audio files with a waveform editor, they were not obviously > different, so it is not a burning issue for me. Try updating svn...

...ion. - Jim ----- Original Message ----- From: "Jim Crichton" <jim.crichton@comcast.net> To: "Jean-Marc Valin" <Jean-Marc.Valin@USherbrooke.ca> Cc: <speex-dev@xiph.org> Sent: Wednesday, May 10, 2006 11:47 AM Subject: Re: [Speex-dev] Speex echo canceller on TI C55 DSP >>> My builds for the two platforms used exactly the same source files, >>> though >>> there were a few ifdefs in the test_echo routine to deal with file I/O >>> for >>> the C55 with its 16-bit char size. When I get a chance, I will add some &gt...

>> My builds for the two platforms used exactly the same source files, >> though >> there were a few ifdefs in the test_echo routine to deal with file I/O >> for >> the C55 with its 16-bit char size. When I get a chance, I will add some >> instrumentation and see if I can find where things diverge. Just looking >> at >> the canceled audio files with a waveform editor, they were not obviously >> different, so it is not a burning issue for me....

...ld 10143 introduced another bug, that was the reason for the 1.1.11.1 release. > There is just four lines in modes.c which declare the constant, and one line > changed in nb_celp.c and sb_celp.c which use the constant. Looking at > nb_mode, QCONT16(.0002,15) evaluates to 0x3FF9 on the C55 and 0x4006 on the > C6x. When I patch the value 0x4006 into the C55 build, the output matches > the C6x. The problem is that 2^15 evaluates to -32768 on the C55 and 32768 > on the C6x. Right on! > Applying our friend EXTEND32 causes the constant to evaluate correctly. In > f...

...e because kiss_fft had used up almost all of the heap, and fwrite would not work, so my program would not write out the canceled samples. It was all rather silly, really, but a consistent allocation mechanism would avoid some of the confusion. >> Finally, there is a lingering issue. The C55 and C64 builds cancel the >> echo >> similarly, but they do not produce the same results. The files match for >> the first 0x1000 bytes (2048 samples, or 16 frames). We recently sorted >> out >> something like this in the encoder, but I am not sure if the expected...

https://bugs.freedesktop.org/show_bug.cgi?id=90967 Bug ID: 90967 Summary: System freeze using nouveau Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

Jean-Marc, I recently started looking at running the echo canceller on a TI C55 DSP along with the 8kbps narrowband Speex encoder/decoder. This is one of those "braindead compilers" that you refer to from time to time, and cannot handle the float struct assignments in the return statements in pseudofloat.h. Most of these were eliminated in build 11311 (patch by...

...e: 0 0 1 1 0 2 D D 5 0 8 11 19 3D 51 74 3A 8 11 8 4 Do you have any suggestions? - Jim ----- Original Message ----- From: "Jim Crichton" <jim.crichton@comcast.net> To: <speex-dev@xiph.org> Sent: Monday, May 08, 2006 12:11 PM Subject: [Speex-dev] Speex echo canceller on TI C55 DSP > Jean-Marc, > > I recently started looking at running the echo canceller on a TI C55 DSP > along with the 8kbps narrowband Speex encoder/decoder. This is one of > those "braindead compilers" that you refer to from time to time, and > cannot handle the float st...

Dear All, When I used speex on C55, the program always printed out something like "Persist Allocated..." and couldnot run into the core program. What's wrong ? Thanks. Hua -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/speex-dev/attachments/2017012...

...example, including instructions on these last changes. Also, I > would like to modify the memory allocation to follow the same structure as > the encoder/decoder, including the ability to override the malloc function. What do you mean here? > Finally, there is a lingering issue. The C55 and C64 builds cancel the echo > similarly, but they do not produce the same results. The files match for > the first 0x1000 bytes (2048 samples, or 16 frames). We recently sorted out > something like this in the encoder, but I am not sure if the expected > results are the same he...

Hello, &nbsp; I have an OMAP5910 OSK board with C55 dsp and ARM9 processor. I just want to use speex as a simple application on the platform in order to check dsp's working well or not. &nbsp; First, I found speex's source codes include "ti/speex_C55_test" directory so I thought speex could run on my platform well. Se...

...bug, that was the reason for >the 1.1.11.1 release. > >> There is just four lines in modes.c which declare the constant, and one >> line >> changed in nb_celp.c and sb_celp.c which use the constant. Looking at >> nb_mode, QCONT16(.0002,15) evaluates to 0x3FF9 on the C55 and 0x4006 on >> the >> C6x. When I patch the value 0x4006 into the C55 build, the output >> matches >> the C6x. The problem is that 2^15 evaluates to -32768 on the C55 and >> 32768 >> on the C6x. > >Right on! > >> Applying our friend EXTEND32...

...the TI directory for the echo canceler example, including instructions on these last changes. Also, I would like to modify the memory allocation to follow the same structure as the encoder/decoder, including the ability to override the malloc function. Finally, there is a lingering issue. The C55 and C64 builds cancel the echo similarly, but they do not produce the same results. The files match for the first 0x1000 bytes (2048 samples, or 16 frames). We recently sorted out something like this in the encoder, but I am not sure if the expected results are the same here. Do you expect b...

...>> because there were not used and required smallft.c (which is not so small >> at >> all) to be added to the build. > > Right, need to cleanup that part... > >> With these changes, the link was successful, using testecho.c with some >> modifications for the C55 environment. The code and data memory >> requirements were a lot more than I had hoped (>20kbytes of dynamic data >> memory for block size=128, tail length = 1024), and I will probably not >> be >> able to fit it in the production build without some trimming. > >...

...d smallft.c (which is not so > >> small > >> at > >> all) to be added to the build. > > > > Right, need to cleanup that part... > > > >> With these changes, the link was successful, using testecho.c with some > >> modifications for the C55 environment. The code and data memory > >> requirements were a lot more than I had hoped (>20kbytes of dynamic > >> data > >> memory for block size=128, tail length = 1024), and I will probably not > >> be > >> able to fit it in the production build...

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 estimate for th...

...>> small > > >> at > > >> all) to be added to the build. > > > > > > Right, need to cleanup that part... > > > > > >> With these changes, the link was successful, using testecho.c with some > > >> modifications for the C55 environment. The code and data memory > > >> requirements were a lot more than I had hoped (>20kbytes of dynamic > > >> data > > >> memory for block size=128, tail length = 1024), and I will probably not > > >> be > > >> able to fit i...

...t_float and spx_ifft_float routines, > because there were not used and required smallft.c (which is not so small at > all) to be added to the build. Right, need to cleanup that part... > With these changes, the link was successful, using testecho.c with some > modifications for the C55 environment. The code and data memory > requirements were a lot more than I had hoped (>20kbytes of dynamic data > memory for block size=128, tail length = 1024), and I will probably not be > able to fit it in the production build without some trimming. Yes, there may be a bit of m...

...patch is larger because some line ends got changed in a couple of the files > when the first patch was applied. I am sorry for the clutter, but its my > first time with the patch tool. > > I have one lingering concern. The C6x encoder does not produce the same > results as the C55x and C54x. The waveform reproduction is less accurate as > measured by a sample by sample comparison. In the test programs, the SNR is > 11.10 in the C55x and C54x, and 10.79 in the C6x build. I figured that the > encoders might not produce bit-exact results because of differences in...