similar to: Compile error (svn 10743)

Hi, I've received svn 10743 revision. But there are compile errors at three files with VS2005. Please check these reports. Sohn, Platform system engineer. ============================================================================= 1. modes.c - nb_mode_new() SpeexNBMode * nb_mode; nb_mode = (SpeexNBMode *) speex_alloc (sizeof (SpeexNBMode)); if (nb_mode == NULL) return NULL;

Please, I need your help! I'm not able to compile.... typedef struct { } PCMMode; static PCMMode ; int pcm_mode_query(const void *mode, int request, void *ptr) { /*const PCMMode *m = (const PCMMode*)mode;*/ switch (request) { default: speex_warning_int("Unknown nb_mode_query request: ", request); return -1; } return 0; } /* Default mode

Hi I am currently trying to port speex v1.1.6 to a microcontroller with very limited memory (<64Kbyte RAM). what I found when initialising the encoder, a chunk of 32Kb was attempted to be alloced, which failed: src/nb_celp.c: void *nb_encoder_init(const SpeexMode *m) { /* snip */ st = (EncState*)speex_alloc(sizeof(EncState)+8000*sizeof(spx_sig_t)); /* snip */ } same goes for the

> > Please, I need your help! > > I'm not able to compile.... > > > typedef struct { > > } PCMMode; > > It's wrong in pure C, there must be at least one field. Then just add int dummy. Actually, this code is pretty much useless at the moment, so you can simply remove it from the build and it'll work. > 2All: can't compile libspeex from trunk

Hi Alfred, First thing I'd like to ask is whether you're trying to achieve real-time performance, as I find it very unlikely that Speex could run in real-time on a micro-controller. Regarding bufSize, no you can't just make it the size you like. Now, it's possible to decrease the amount of memory allocated if e.g. you only use complexity 1. You can also assume that the stack is

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

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

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

To close debian bug #271052, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=271052 I went ahead and did the following: $ diff -u ../original/speex-1.1.6/libspeex/nb_celp.c libspeex/nb_celp.c --- ../original/speex-1.1.6/libspeex/nb_celp.c 2004-07-15 01:16:52.000000000 -0400 +++ libspeex/nb_celp.c 2005-02-27 08:24:49.000000000 -0500 @@ -1746,6 +1746,21 @@ st->submodeSelect =

Actually, in all the examples I've seen, people are using "Copyright" and not "License". Any reference for the change you're proposing? Also, pcm_wrapper.h is gone in svn, so it's a non-issue now. Jean-Marc Le mercredi 10 mai 2006 ? 11:06 +0200, Stepan Kasal a ?crit : > Hello, > in order to compile sppex on my Fedora, I had to do the following >

Hi Maitland, I think your solution is probably the best implementation you could do for SPEEX_GET_QUALITY. However, unless you have something against that, I think removing it would be better, as in many cases (e.g. VBR), the call just doesn't make sense). This would of course break the API (not the ABI), but given the fact that it was never implemented, any app that uses it is already broken

Hello, in order to compile sppex on my Fedora, I had to do the following changes. Please consider installing them to the main tree. Thanks for your work, Stepan Kasal --- /usr/src/redhat/SPECS/Speex.spec 2006-02-15 13:13:48.000000000 +0100 +++ /usr/src/redhat/SPECS/Speex.spec.new 2006-05-10 11:00:25.000000000 +0200 @@ -6,7 +6,7 @@ Name: %name Version: %ver Release: %rel -Copyright: BSD

I have been using the Speex NB mode with an 11025 kHz signal, without adjusting the framesize, and it's been sounding just fine to me. However I was wondering what the best way to make 11025kHz would be. I also have an audio driver that uses 2kB buffers, and the NB framesize of 160 doesn't divide evenly into that so I end up having to shovel tails of buffers around which isn't too

Hi, If I use --enable-fixed-point-debug I can't use --enable-fixed-point and vice versa? Because when I try to copile with these two option an error occur as follows: gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I.. -I/home/liselene/projects/speex/speex-1.1.11.1/bin-fixed/include -g -O2 -MT modes.lo -MD -MP -MF .deps/modes.Tpo -c modes.c -fPIC -DPIC -o .libs/modes.o

> Sorry if this a repost but I want to create the > smallest Speex library possible to be put in TI's > TMS320 DSP. I'm only interested in one configuration: > 5.97 Kbps narrowband. What part of source code can I > remove? Currently, when I compiled the version 1.1.12 > libspeex.a library with the TI TMS320 and > Fixed-Integer options, I get around 522Kb. You mean

On Tue, 2005-12-06 at 16:30 -0400, Liselene Borges wrote: > Hi, > > If I use --enable-fixed-point-debug I can't use --enable-fixed-point > and vice versa? Because when I try to copile with these two option an > error occur > as follows: No, you really need to enable both. This is a bug in 1.1.11 and I just fixed it in svn. I haven't tested the fix, so can you confirm

Jean Marc, >> 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

>> > Sorry if this a repost but I want to create the >> > smallest Speex library possible to be put in TI's >> > TMS320 DSP. I'm only interested in one >> configuration: >> > 5.97 Kbps narrowband. What part of source code >> can I >> > remove? Currently, when I compiled the version >> 1.1.12 >> > libspeex.a library

> 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