similar to: Speex 1.2beta3 is out!

Hi all, I am a newbie here and just started using speex in our lab. During compiling my voice application with windows-compiled version provided today, I am getting "unresolved external symbol _speex_wb_mode". I am probably missing some setting with VS6.0 linker... (I am a bit new to windows too) If anyone could point it out, I would appreciate it. - Tim -----Original Message-----

Hi All, We are using speex for linphone in blackfin fixed point platform. The speex version we are using is svn-14525. If we don't disable vbr by "--disable-vbr", the sound quality will be very bad in linphone. But if we disable it, sound will be perfect. I noticed in the speex.org, there is a comment like this: > >Speex 1.2beta3 is out >December 11, 2007 >The most

Jean-Marc, Frank, I have stumbled across a similar situation regarding optimization. I seem to have a similar setup as Frank does with a fixed 48khz in and out. The wideband mode and ultra-wideband modes are really what I?m looking for. I have a test application that reads audio, downsample to 16kHz (or 32kHz), speex encode, speex decode, upsample back to 48kHz, and playback. If I remove

Greetings to All! Now I am trying to run speex on TI DSP... I need only coder+decoder+AEC. Bitrate 8000bps. Building with floating point support. What can i do, to reduce RAM consumption? I mean very serious RAM optimisations. Deleting not used structure fields, etc... May be I can do something with alloc... Help me to determine that it is possible to throw out. What is best result(in RAM

Hi Jean-Marc, after some problems with getting svn to work here I finally made it. Problem is, you write that I cannot use libspeex and libspeexdsp at the same time now -- because I use a "live" system (mic-in -> speex_enc -> speex_dec -> headphone out) and I can run the AD1836 audio codec on 48 kHz only, I cannot use my program now (because I use speex resampling...) So I

Do you have the WIN32 macro defined in your code that includes speex.h. If not, try defining that and let me know if it works. Cheers, Jean-Marc Tim Na wrote: > Hi all, > > I am a newbie here and just started using speex in our lab. > During compiling my voice application with windows-compiled version provided > today, I am getting "unresolved external symbol

Hi Aymeric, > 2 questions: I count 4 :-) > * Do you "feel" that the current svn is enough stable Yes. I'm planning on releasing it as 1.2beta3 this week. Even in normal time, I try to keep svn in good shape so it is almost always better than the last release. And even when it breaks, Speex bugs tend to be very obvious and easy to reproduce (no segfaults that happen once a

Hi, when I compile with FIXED_DEBUG enabled, I get an error -- both when make tries to build testenc.o and when I try to link my app against the speex lib: lorenz@panelmaker:~/Blackfin/tests/speex_loopthrough$ make bfin-uclinux-gcc -c -g -I/home/lorenz/include -o main.o main.c bfin-uclinux-gcc -gl -elf2flt -L/home/lorenz/lib -o speex_through main.o -lspeex_debug -lspeexdsp -lm

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

On 12/13/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > > I am a newbie here and just started using speex in our lab. > > During compiling my voice application with windows-compiled version provided > > today, I am getting "unresolved external symbol _speex_wb_mode". > > I am probably missing some setting with VS6.0 linker... (I am a bit new

Hi, I have problems compiling speex 1.2rc1: > /opt/studio/SOS11/SUNWspro/bin/cc -DHAVE_CONFIG_H -I. -I. - > I.. -I../include -I../include -I.. -I/opt/csw/include -I/opt/csw/ > include -xO3 -xarch=v8 -I/opt/csw/include -c skeleton.c > /bin/bash ../libtool --mode=link /opt/studio/SOS11/SUNWspro/bin/cc - > xO3 -xarch=v8 -I/opt/csw/include -xarch=v8 -L/opt/csw/lib -o

Hi everyone, I'm currently looking into using speex in an embedded project using an ST ARM-device (STR9 family) just with internal memory (96kbyte) and no O/S. Does anyone know if the optimizations included in the code for ARMv4 and ARMv5e are appliable to this device? I would also need to strip down libspeex pretty hard to fit into the available memory. I just want to use a fixed bitrate

I'm currently working on packaging the latest version of speex for Fink, a Mac OS X package manager. Our current speex version is at 1.1.6, and several new programs require a newer version, which is why I'm working on the update. When 1.2b3 was released and some symbols were offloaded to libspeexdsp.1.dylib, this broke the library on OS X since libspeex.1.dylib kept the same install

Hi Jean-Marc, Am 17.04.2009 um 13:35 schrieb Jean-Marc Valin: > It should be using getopt1.c when getopt isn't available.c. Can you > check why it doesn't? In any case, that's only required for the Ogg > tools, not for the library. config.log says ac_cv_func_getopt_long=no ac_cv_header_getopt_h=no ac_cv_lib_gnugetopt_getopt_long=no LIBOBJS='

-----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: Tuesday, June 19, 2007 6:38 PM To: Michael Shatz Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] Blackfin inline assembler and VisualDSP++ toolchain >> Yes, data footprint in the new version is quite manageable. Still I would >> wish better documentation for speex_alloc_scratch(). >

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.

On 12/3/07, Erik de Castro Lopo <mle+la@mega-nerd.com> wrote: > I just checked and there is nothing needed in configure.ac. > > In the Makefile.am that creates the shared library you need to add > "-no-undefined" to the LDFLAGS variable like this: > > libspeex_la_LDFLAGS = -no-undefined @WHATEVER_WAS_THERE_BEFORE@ Which symbols will it export? I think default

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

Hi Mark, Code below: int16_t* samples; int16_t* fbSilenceFrame; void *fSpeexState; float eng(0.f); int speexFrameSize(0); speex_encoder_ctl(speexState, SPEEX_GET_FRAME_SIZE, &speexFrameSize); for (int i = 0; i < speexFrameSize; i++) { eng += samples[i] * samples[i]; } if (eng / speexFrameSize < 3.f) { memcpy(samples, silenceFrame, speexFrameSize * sizeof(int16_t)); } where

David Hogan a ?crit : > That said, we don't use the supplied project. We simply compile in > the speex .c files. You could easily replace the Win32 build files > with a readme showing which .c files NOT include in your project > file. > > If you'd like, I'd be happy to produce a readme file on how to make a > VC project file for speex. Although this approach would