similar to: Library split to be merged -- looking for a name

Hi, A while ago I mentioned I was considering splitting libspeex into two parts. I'm attaching a patch that does exactly that, but I haven't applied it to svn because I first want to have some feedback. That patch leaves the codec in libspeex and moves the other stuff (jitter buffer, AEC, preprocessor, ...) to libspeexvoip (I'm open to suggestions on better names). Some of the things

Hi everyone, In the 1.1.x branch, I've kept adding more stuff to libspeex: preprocessor, AEC, etc. I'm now considering moving all those to a separate library (libvoip, libspeech, whatever). Anyone on this list has good reasons I should consider for either splitting or not splitting libspeex? Cheers, Jean-Marc

I have sent the visual studio project files that compile the speex client to jean-marc directly (as an attachment), sometime this week, I will also upload the binary builds of static library files to my site www.phonestack.com. I am porting our LTP (lightweight telephony protocol) to some embedded systems. I require to run speex in an environment that doesn't support memory allocations. How

Hi, Can you please confirm/give any sample on the "tick" value to be passed to jitter_buffer_init ( int tick ) ? Is this: Tick = GetTickCount() ? Thanks -----Original Message----- From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] On Behalf Of Jean-Marc Valin Sent: Monday, September 17, 2007 4:29 PM To: speex-dev Subject: [Speex-dev] Libspeex splitting attempt

On Wed, 2006-06-28 at 11:34 +0530, Ashhar Farhan wrote: > I have sent the visual studio project files that compile the speex > client to jean-marc directly (as an attachment), sometime this week, I > will also upload the binary builds of static library files to my site > www.phonestack.com. Actually, Zen (illi on IRC) is the one handling the Windows stuff. I can't do anything with

I vote for splitting 'em off and documenting the great features of each. I've been using the codec for a while now and would be more likely to dig in to the additional features if they were offered as separate components so I could use them with other audio projects (as well as being more likely to use those features in speex, simply because they would be easier to dig in to at

Hello, some misc. cleanup patches for speexdsp, nothing big I'm not sure about how to submit patches, so this is a test balloon :) ultimately, I'd like to fix the FIXED_POINT issue, see http://lists.xiph.org/pipermail/speex-dev/2013-December/008465.html currently, I think the only way to find out how speexdsp has been compiled is to resample some bytes and observe the output; which is

Hi everyone, Just to let you know that version 1.2beta3 is out. The main change is the split into libspeex and libspeexdsp. Basically, libspeex keeps the codec (just like it was for 1.0.x) and libspeexdsp has all the new components. Other changes include a new jitter buffer algorithm and resampler improvements/fixes. This is also the first release where libspeex can be built without any floating

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, 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, I am an user of speex codec.Can I ask some question about the speexcodec 1.2beta2 on installed to linux(fedora 6) thanks! After I downloaded the latest version of codec then I type the commands to install : configure -prefix=/home/...../test -enable-shared -enable-static make make install then I try to compile my encode.c here is the encode.c of mine: =====================================

Hi all, I build successfully with speex-1.2rc2. And with speexdsp 1.2rc3, I build with i386, X86_64, armv7 and armv7s all passed. But when I build for ARM64 (for iPhone 6), it failed with: /Applications/Xcode.app/Contents/Developer/usr/bin/make all-recursive Making all in libspeexdsp CC preprocess.lo CC jitter.lo CC mdf.lo CC fftwrap.lo CC

Hello Tristan, Thank you. But I am using libspeex library. Does the speexdsp library be included in it? Or it needs to be installed separate. Appreciate the help. Thanks, Ankhit On Thu, Aug 20, 2015 at 11:43 AM, Tristan Matthews <tmatth at videolan.org> wrote: > Hi Ankhit, > > On Thu, Aug 20, 2015 at 12:06 PM, Ankhit Vivekananda < > ankhit.vivekananda at biscotti.com>

Hi, I'm using the Speex codec on my Blackfin-based board, and plain-C performance is pretty poor. Decoder is OK (something 25 MIPS for wide-band). But Encoder is not (wide-band quality 8, complexity 1): - 162 MIPS with Analog-Devices lib - 128 MIPS with 1.2beta2 (faster but not working) I don't worry that much, as it's not the optimized version, and everything is running in SDRAM.

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

----- Original Message ----- From: "Conrad Parker" <conrad at metadecks.org> To: "Vincent Burel" <vincent.burel at vb-audio.com> Cc: "Jean-Marc Valin" <jean-marc.valin at usherbrooke.ca>; <speex-dev at xiph.org> Sent: Thursday, November 13, 2008 1:18 AM Subject: Re: [Speex-dev] SPEEX on iPhone ? > 2008/11/13 Vincent Burel

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 all, I'm updating OpenEmbedded-core's speexdsp from 1.2rc1 (when it still was a part of the speex source tree) to 1.2rc3. I found out that building the new version for aarch64 fails in resample_neon.h (the target machine is OE-core's default qemuarm64 target). This is the error message: .../speexdsp-1.2rc3/libspeexdsp/resample_neon.h:148:5: error: impossible constraint in

Hello all, I'm a hardware person who has recently found himself thrust into a software role. So, please forgive any ignorance in the following questions. I've tried to do my homework reading the relevant manual pages and investigating the Doxygen documentation. :-) We're investigating acoustic echo cancellation solutions for a speech application. Our hardware will be a TI C64x+