similar to: Quick survey for Speex 1.2

> Another issue is the memory allocations distributed so many places that > it's hard to provide a single memory initial function interface. > > In a VoIP case on ARM, the total memory size for speex codec should be > known at the inital stage since all the memories are allocated > at the initial stage. If you want everything in the same big block, all you need to do is

> /* FIXME: This VAD is a kludge */ > .. and it shows (or hears?) unfortunately. I've run a few tests with it > with my users, and they complain that it misdetects too often... In both > directions. Non-speech is detected as speech more often than before, and > more important it also doesn't detect speech as good as before. > I'd really like to see this

>That's a totally different topic. I do intend to reduce the wb memory >usage, just like I did with the narrowband for 1.2beta1. Still, don't >know where you take this 160k Word32 number (640 kB). I don't think >wideband requires anywhere near that amount of memory. Sorry, it's 160kB. What do you think? and any suggestions for memory reduction? Lianghu On 11/16/06,

Hi All, Another issue is the memory allocations distributed so many places that it's hard to provide a single memory initial function interface. In a VoIP case on ARM, the total memory size for speex codec should be known at the inital stage since all the memories are allocated at the initial stage. In my current implementation, all the memory allocations are collected together to form

I am trying to compile speexclient.c. I downloaded all the files to ~/speex- 1.2beta1/include When I call ./compile.sh I get the following errors, speexclient.c: In function 'main': speexclient.c:164: error: 'SPEEX_PREPROCESS_SET_ECHO_STATE' undeclared (first use in this function) speexclient.c:164: error: (Each undeclared identifier is reported only once speexclient.c:164:

Hi everyone, I've recently done some major internal changes in Speex aimed at reducing RAM (by nearly a factor of 2!) and improving quality of the fixed-point. In doing so, I might have accidently broken a few things. I'd like to hear feedback on the current svn code to make sure I fix any regression before the next release. I'm already aware that --enable-vorbis-psy is broken and

For a streaming application like VOIP, you collect 20 ms of samples, feed this through the encoder, stick it in an RTP packet, and send if over the network. On the receive side you feed packets through a jitter buffer to the decoder, and then copy the output audio to your output device. Speex runs efficiently on most compilers, so the real-time requirement is not a big deal, as long as you

Hi, I am bring SPEEX up on Analog Device's Blackfin (using Visual DSP++ tool set). The floating point was too slow on this fixed-point processor so I am going for the integer version. The floating point library build was very clean, but when I build with FIXED_POINT defined, the compiler exits when it find this discrepancy in \libspeex\cb_search.c : ".\libspeex\cb_search.c",

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

hi, I am using speex1.2beta2 on a TI 54x on narrow band I have been trying to get speex to work for a while now, and it's been a real teeter-totter ride. For a long time I noticed that I will get a project to work and then without changing any code and programming it to an eprom/flash the project will not work. It turns out it was a value called innov_save. I found this bugger by zero

Hi everyone, I'm about to release version 1.2-beta1 (which I could have called 1.1.13), which includes many, many changes. It would help if everyone could give the svn version (http://svn.xiph.org/trunk/speex/) a try and see if it works fine. I'll check my email next week when I'm back from some vacations and if nothing bad has been reported, I'll make the release. Have fun,

Hi Jean-Marc and list, Is the spx_fft function in fftwrap.c a standard fft function? void spx_fft(void *table, spx_word16_t *in, spx_word16_t *out) When I say standard, I mean the input "in" is 128 point short data for example and the output "out" is 128 short complex value which is stored in 256 short array with real and image part. Looks like the function did some

I wish Speex could come with instructions on how to build libspeex_armce.lib. ________________________________ From: speex-dev-bounces@xiph.org on behalf of speex-dev-request@xiph.org Sent: Mon 11/13/2006 3:01 PM To: speex-dev@xiph.org Subject: Speex-dev Digest, Vol 30, Issue 15 Send Speex-dev mailing list submissions to speex-dev@xiph.org To subscribe or unsubscribe via the World

Hi, Indeed I too have troubles implementing echo removal, I like ask kindly to Jean-Marc (or any other) if him can put a source code demo to show us how to use effectively echo removal API and parameters in real case scenario. A big thank you! Roberto -----Messaggio originale----- Da: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] Per conto di hs Inviato: marted? 11 ottobre

Hello, I have an (Access violation reading location) on line 115 in the fftwrap.c : out[i] = scale*in[i]; with i = 1193 Only with preprocessor active Systems : Visual studio 2005, XP, WB 16000 Hz, last svn. Hope it helps you. Ouss -----Original Message----- From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] On Behalf Of speex-dev-request@xiph.org Sent: dimanche 22 octobre

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

Hi, I just downloaded http://www.speex.org/download/speex-1.1.4.tar.gz and tried to build it but the file denoise.c seems to be missing from the archive. Can you fix this or is it better to get everything from cvs? Another question, when will a stable version of 1.1 be released. I'm interested in the preprocess features but I would also like a stable encoder/decoder :-) Best regards, Chris

okay that questioned is answered, thank you. I am interested in using speex in a VOIP application. do i need to put it in into the ogg contianer format in order to encode/decode and send it? or will it work "as is"? if the latter then: "the packet is larger than the allocated buffer" message: whats your recomendaton for fixing that? i was thinking simply getting the size of

Hi all: How to use jitter.c, I see this file is not include in the lib. Sorry for this newbie Q.

Probably the level of your signal is too low and/or you're just not letting it time to adapt. Jean-Marc Le mercredi 19 juillet 2006 ? 19:00 -0400, ac2491@columbia.edu a ?crit : > On closer looks and debugging I always end up in > > speex_echo_cancel function with comment > /* Temporary adaption rate if filter is not adapted correctly */ > > > Does this give any clue