similar to: strange encode/decode results on C54x

wow, the attitude wasn't necessary. What I was asking wasn't in the documentation, how am I supposed to know I wasn't supposed to initialize the encoder/decoder every time (I was trying to save space for the allocs), I've never dealt with codecs before and it isn't in the documentation. I was not insinuating that your code was wrong, I was hoping you could tell me that I set

I thought I should be getting 20 words because in the windows app the command line repeats "nbBytes = 20" through the entire decode phase. I wonder how the frames got misaligned...right now I get 10 words of data followed by 10 words of 0's which I look at through a memory window in code composer. now I am pretty sure there is a terminator word that gets in there so that would make

Jean-Marc was correct in that the 16bit value was the culprit for my encoding woes. after I changed that to a 32 bit value I believe it encodes correctly, but I really don't have much of any way to know this absolutely. I am using the 1.2beta2. I would use the enctest program, I have looked it over and based a lot of what I am doing on that code but the project I am developing this on is

Mike, Generally "Invalid mode encounterd" == "frames are misaligned" You should be getting 20 bytes from the encoder each time, and passing 20 bytes to the decoder each time. Is it correct that you have modeled your main loop after testenc-TI-c5x.c? If you look at encoded silence with a binary editor, you should be able to see the 20-byte repetition pattern. You can also

Michael Jacobson a ?crit : > wow, the attitude wasn't necessary. Sorry about that, but I also like when people read the doc carefully. > What I was asking wasn't in the > documentation, how am I supposed to know I wasn't supposed to initialize > the encoder/decoder every time (I was trying to save space for the > allocs), I've never dealt with codecs before and

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

This is going to take some explaining and I apologize in advance if any of this is found in the manual or sample code but I couldn't find it. I just graduated last may and this is my first experience with vocoders and dissecting a professional's code. I work for a company that is currently using a G729A vocoder from a 3rd party software company and is looking into speex so they no

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

Hi, So I got a crash on the following code: k1=SUBMODE(lpc_enh_k1); k2=SUBMODE(lpc_enh_k2); which in the newer codebase is: bw_lpc(SUBMODE(lpc_enh_k1), st->interp_qlpc, awk1, st->lpcSize); bw_lpc(SUBMODE(lpc_enh_k2), st->interp_qlpc, awk2, st->lpcSize); I am not sure if the newer code will have the same issue but the following check is

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

John, > 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

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

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

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

Jean-Marc, >> > It's odd that it "almost" works with the fixed_generic.h. The easiest >> > thing would be to gradually replace routines and see which one causes >> > problem. It's most likely (though I'm not 100% sure) that somewhere in >> > the code, I have a 16-bit value that gets sent to a function/macro that >> > expects 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)

> Use speex_mode_query with SPEEX_SUBMODE_BITS_PER_FRAME > You need to pass the submode number with the pointer and the number of > bits per frame is returned using the same pointer. Note that with > speex_mode_query, the first argument is the mode (e.g. &speex_nb_mode), > not the encoder/decoder state. Thank you Jean-Marc, This works well. Now a followup question. Is there

I need to shrink speex so it will fit on an embedded processor along with some other code. The chip has only 20k of ram. I have done some work with libspeex.dsp by removing references to all modes but narrow band 8000 hz (submode 3). I used the defines: FIXED_POINT, DISABLE_FLOATING_POINT_API, DISABLE_VBR. I also removed the structures for the other submodes and the functions that they called.

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.