similar to: Fatal end of line errors occur when trying to compile libspeex in eVC++ 3.0 or 4.0

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

Hello Carl, Can you send me libspeex compilated in eVC. And can you describe where and how set the FIXED_POINT flag in eVC. Thanks you. Regards. Rodrigo. <p>----- Mensaje original ----- De: "Carl Douglas"<CarlD@itouchmobility.com> Env.: 15/01/04 17:43:43 Para: "speex-dev@xiph.org"<speex-dev@xiph.org> Asunto: RE: [speex-dev]

Hi all, I'd like you to know i'm not able to build Speex library anymore from CVS without modfing the code in mdf.c. This is due to the fact that EVC++ compiler doesn't like memory allocations in this form: spx_word16_t w[N]; where N is not a constant. I know this is not an error for gcc compiler and ANSI standard but it is in VS2005 and EVC++ 4.0 If someone knows how to compile

I have built the Speex library for Pocket PC using the FIXED_POINT flag in eVC 3. It works fine. I think the iPAQ 3600 (ARM SA 1110, I think this is a 200mhz cpu), is a bit slow for encoding in realtime. The Speex encode function takes 30+ ms to encode one 20ms sample frame in a debug build. I didn't try the release build with compiler optimization. The iPAQ 3970 (PXA250, I think this is a

Hi all, As someone knows i'm tring to develop a VoIP application for my ipaq 3850 (200 Mhz) using speex... I guessed, for better perfomance, to build libspeex using GCC under linux or cygwin with --enable-fixed-point and --enable-arm-asm and use the compiled library under Embedded VC++ 3.0. I don't know if it's possible and only today i started to read something about cross-compiling

On Tue, Dec 20, 2005 at 09:22:36PM +1100, Jean-Marc Valin wrote: > I'll try fixing that. It's funny "gcc -ansi -Wall" doesn't even complain > about it despite the fact it's not C89-compliant. "gcc -ansi -pedantic -Wall" does the trick. Does seem like a bug if there are other major compilers that don't implement this though. Does the non-embedded

Hi, I am probably missing something really simple (since I don't know very much about compiling or anything) but I am trying to compile the latest version of Speex (1.1.10) into a .lib file. I have compiled it with GCC under Cygwin with -enable-fixed-point and --enable-static, and have produced a .a file. I want to be able to use it with eMbedded Visual C++ 4.0. I guessed that I would need

I'll try fixing that. It's funny "gcc -ansi -Wall" doesn't even complain about it despite the fact it's not C89-compliant. In the mean time, you can always replace it with: spx_word16_t w[1024]; and you'll be fine (unless you try AEC with a frame size > 512). Sorry about the inconvenience. <cheap shot>Must be the price to pay for using an inferior

Yeah, MSVC doesn't like that notation.. You can use alloca which allocates stuff on the stack instead I believe. -----Original Message----- From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] On Behalf Of Ralph Giles Sent: Tuesday, December 20, 2005 9:52 AM To: Jean-Marc Valin Cc: Speex Mailing List Subject: Re: [Speex-dev] CVS compilation and EVC++ 4.0 On Tue, Dec 20, 2005

How big is difference between encoding speeds of libspeex compiled with arm-asm, and without it? My application is written in EVC++, but there is no inline assembler, so I have to compile speex without arm-asm. But I still trying to find a way to use speex with arm-asm under my EVC++ application. I tried to compile speex with arm-asm under gcc (arm-wince-pe), but generated static link

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)

> > It was essentially my own mistake. After the Embedded C++ IDE crashed unexpectedly, > the .lib file was no longer present in the project settings (the project had not been saved) > so all the errors I got were caused by a missing .lib reference in the link stage! > I had to change my cross compiler target to "arm-wince-pe" because otherwise the > object/.lib files

Actually, the best thing do to would be to use __int64 *unless* it's not supported. So there needs to be a configure check... Jean-Marc Le mar 01/06/2004 à 14:50, Kenji Chan a écrit : > 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

Hi all, I'm quite new to Speex and i'm tryng to do a porting of it for my pocketpc platform.... The encodig time seem to be too hight, i think something goes wrong putting --enable-fixed-point --enable-fixed-point-debug --enable-arm-asm in project setting of EVC++ 3.0 (i've got EVC++ 4.0 too) i do my test with an Ipaq 3850 (206 MHz Intel® Strong ARM 32-bit RISC Processor) running

Hi everyone, For all those of you who always wanted to contribute to Speex, but didn't know what to do, I've just updated the list of things that could be done on: http://wiki.xiph.org/index.php/Speex The tasks range from maintaining a FAQ to writing a better perceptual enhancer. Some of the more complex things listed would even make a good university project! If you're interested in

Christian Buchner wrote: > Now here is where I have problems and not yet found a solution: I know very little about this, so take everything that follows with a large pinch of salt. > * the function names exported in the .lib created by gcc are not compatible > with the function name decorations that the VisualC++ embedded linker expects. Which version of gcc are you using? I know

Hi, I'm a Pocket PC developer and have created a audio translator application on this platform. I currently make use of an MP3 decoder engine, but due to heavy licensing fees I'm thinking of switching over to a patent free format. Vorbis presents the best approach. I read that tremor decoder has been especially optimized for embedded devices. I'd like to make use of this and

Hi I want to port speex to my pocket PC iPAQ1945 which has a Samsung processor 2410, an ARM9-based processor. I would like to write the specific optimized code for this chip. I had some experience at DSP chip and fixed-point coding but know nothing about embedded system and ARM. Could someone tell me some hint how to write optimized code for this pocket PC. If you can give me some links that will

Hi Rodrigo, I'm Fabio and i'm in your identical situation, i need Speex to run on PocketPC in real time mode for my tesis. I've to develop a sort of VoIP apllication for pocketPC... I recently discover speex (Only yesterday i joined this mailing list....) and I'm doing many test using mostly VC++ 6.0 but only because i'm still undestandig speex... I did many works with EVC++

Le sam 14/12/2002 à 01:03, Bernard Blackham a écrit : > I have a patch for libspeex, which optimises some of the loops in > vq_nbest and vq_nbest_sign that speeds up encoding - my results: Thanks for the patch. I applied it and it give me up to 15% in speed. Doesn't seem to change the results, which is a good thing (though you originally forgot a "used=0" in vq_nbest_sign).