similar to: Supported DSPs

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

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 fixed: ARM (v4 and v5E) (assembly optimizations provided) Blackfin (assembly optimizations provided) TI

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

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

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)

> 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)

> >I fixed it in svn. Could you check that? > > Now all platforms match again. Note that the measured SNR for this test > sample is lower than with the broken code (10.87 vs 11.10), but of course > this is no way to judge the real quality. SNR, especially on a single sample, can be very misleading. Yet, could you just check that the DSP results match what you get on a PC?

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, I want to take a .wav and generate a bytestream that I can feed direct to speex_decode(). The speexenc program appears to produce it wrapped up in an ogg stream, and it doesn't have any sort of "raw" mode. I've tried hacking on it to remove the ogg parts, but I must have got it wrong, as my decode dies after decoding 160 bytes (which I believe is one frame) with an

Hi; I have a question about speex on TMS320C54X: I have build and run the related project on Code Composer Studio IDE (ver. 3.1) and the male.snd (93.7KB) was its input file and malebits5x.dat (5.85KB) and maleout5x.snd (93.5KB) are output files. What is malebits5x.dat file? if it is encoded file, why I could'nt decode it? Also if maleout5x.snd is output recoverd file why after

I have sent the visual studio project files that compile the speex client to jean-marc directly (as an attachment), sometime this week, I will also upload the binary builds of static library files to my site www.phonestack.com. I am porting our LTP (lightweight telephony protocol) to some embedded systems. I require to run speex in an environment that doesn't support memory allocations. How

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: maleout12may.wav Type: audio/wav Size: 95884 bytes Desc: not available Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20050524/57112d0c/maleout12may-0001.bin

> The C5x and C6x output diverges in build 10143, which has log message "lpc > floor converted to fixed-point." Also, the measured SNR changed from 11.05 > in builds 9854-10141 to 9.22 and 9.24 in 10143. Actually, build 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

Jean-Marc Valin wrote: > I suspect something related to endianness or word size here. On a related point, has anyone ever compiled FIXED_POINT Speex on a system with 16-bit chars? Will it definitely work, definitely not work, or might it work and no-one has any idea? :-) More specifically, I'm trying to decode Speex data encoded using sampleenc. So, it's definitely been encoded

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

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?

>> Nice call. The culprit is SHRL32. This is not used in many places, and >> in >> most of those, the operand comes from EXTEND32. The only really >> suspicious >> instances is in lsp.c (lsp_interpolate): >> >> spx_word16_t tmp = DIV32_16(SHL32(1 + subframe,14),nb_subframes); >> (subframe is an int) >> ... >> I see that your

Hi everyone, I've recently done some major internal changes in Speex aimed at reducing RAM (by nearly a factor of 2!) and improving quality of the fixed-point. In doing so, I might have accidently broken a few things. I'd like to hear feedback on the current svn code to make sure I fix any regression before the next release. I'm already aware that --enable-vorbis-psy is broken and

Jean-Marc, Attached is a patch (to build 14264) to fix the TI DSP builds with the recent restructuring of libspeex. The change adds a hook in os_support.h to allow the user to override some memory allocation and I/O functions. A similar hook was present in misc.c, but was lost when that file was removed. Also, the size of the private memory allocation area has been reduced, to match

Hi everyone, In the 1.1.x branch, I've kept adding more stuff to libspeex: preprocessor, AEC, etc. I'm now considering moving all those to a separate library (libvoip, libspeech, whatever). Anyone on this list has good reasons I should consider for either splitting or not splitting libspeex? Cheers, Jean-Marc