search for: lsp_scale

Hello list I'm joining the effort to port speex to a fixed-point version, but as I'm a physicist used to deal only with floating point numbers (lots of them), I have no practice in working with fixed-point versions of such numbers. For instance, in the first source I'm trying to work with, nb_celp.c, it is hard to see that the following two lines of code yield the same

I emailed Jean-Marc the arch.h about one week ago, not quite sure whether he actually received that email. Anyway, here I have an improved version of arch.h that I believe that it would be better, to use __int64 only if compiling on eMbedded Visual C++ compiler, so for any other compiler, keep it the same (use long long) ---------------------------------- Chan Kei Yuen (Kenji)

Hi, I am using speex 1.2beta2 on a 24bit DSP that has a severe program and data space limitations. I am only interested in the speex decoder for 11kbps narrowband implementation. I am using the following parameters and structures 160, /*frameSize*/ 40, /*subframeSize*/ 10, /*lpcSize*/ 17, /*pitchStart*/ 144, /*pitchEnd*/ /* 11 kbps medium bit-rate

Hi Jean-Marc, Based on the wonderful Speex project, I've created SpeexOutLoud, essentially a Speex codec port for Windows Mobile 2003 devices. I've included a sample project intended to show the usage of SpeexOutLoud codec in a Pocket PC application based on .NET Compact Framework. I'd request you to please go through the attached build, and include it as a contribution to the

I've never tried Speex on a 24-bit DSP, but I would suggest actually leaving the code (nearly) as-is. The scaling factors actually should not change because I'm using integer multiplications, not fractional multiplications. So what should happen is that the top 8 bits or 24-bit values and the top 16-bit of 48-bit values will be unused (filled with sign bits). There may be a few cases where

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.