similar to: com object building...

so, having a speex frame, how do i know where is each sample if i don't know how many bits per sample are being used. Isn't there any info besides the data ? On Wed, Jul 15, 2009 at 7:21 PM, Alexander Chemeris < Alexander.Chemeris at sipez.com> wrote: > Hi, > > Speex RTP payload does not have any header (except RTP header), > as per speex-rtp RFC. > > On Wed, Jul

>Stephen Bannasch wrote: > >> I'm getting this error trying to build speex on MacOS X 10.5.6: >> >> ./configure: line 21256: syntax error near unexpected token `FFT,' >> ./configure: line 21256: ` PKG_CHECK_MODULES(FFT, fftw3f)' > >Why are you compling from Git? If you grab a release tarball you should >never see an error like that.

Jean-Marc, I was wondering if you could add a check to ensure that memory is actually allocated during the nb_encoder_init and sb_encoder_init functions. We have been looking at using Speex on a DSP and noticed that if we didn't allocate a large enough heap space memory segment that the DSP would crash. I would recommend something like: if (!st->stack) fprintf(stderr,"ERROR

There is experimental echo cancellation code. Look in speex_echo.h and mdf.c. Unfortunately there's no sample code, and I don't think anyone's had much luck getting the echo cancellation to work at all. Would anyone like to prove me wrong? I'd love to see this work! I know it's really hard but just tonight the person I was talking to asked me, "Is there ever

IIRC, under ARM, I believe I was having issues with --without-libogg. I resorted to just downloading libogg sources, setting up my cross-compilation environment, and cross compiling it per the general build directions (./configure, make, make install), then went back to building speex -- everything worked like a charm for me then. So -- Conrad. *Make sure* that you have libogg cross-compiled and

On 12/20/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > Sorry, been busy with maintenance on Valin 2.0 and 3.0 :-) Just applied > your fix to the assembly. Can you confirm it works fine? Yep, it works fine. Thanks. > About including > assembly directly (.asm/.s instead of gcc inline asm), I'm OK in > principle if someone can show me how to do that cleanly

Hello , I had downloaded latest tar.gz of speex sources. I am trying to build it on windows , by using the Visual C project files. (dsp/dsw) with libspeex I did succeed. When I try to build speexdec (using the (dsp/dsw project files under win32/speecdec) I get the follwoing message dialog : "browse for project ogg_static" what to do ? regards sting

Hi, This patch make libogg detection a bit smarter if you're trying to cross-compile. What I want is to be able cross-compile Speex without OGG - right now it is not possible without som hacking of Speex build scripts, because if cross-compiling enabled speex silently assume that you have libogg compiled and installed. Such behaviour was used (as far as I could imagine) because with

Hello! The question is: "Does Speex support multiple channels?" Speex is reported to encode only mono and stereo signals. But I found 'nb_channel' defined in <speex_header.h> among the Public Attributes. Does this mean that it is also possible to store more than two channels in one single speex-file? Maybe it will be possible in the next future...? TIA -- Mch --- >8

I'm getting this error trying to build speex on MacOS X 10.5.6: ./configure: line 21256: syntax error near unexpected token `FFT,' ./configure: line 21256: ` PKG_CHECK_MODULES(FFT, fftw3f)' Thanks for any tips. Details ... I'd like to use speex with ffmpeg but when I run ffmpegs configure with: --enable-libspeex I get: ERROR: libspeex not found Soo ... I

Hi Jean-Marc, Not exactly. Under cross-compiling you circumvent this standard way by blindly assuming that it is present. That's what I recall. Patch we used to fix this is attached. On Thu, Oct 22, 2009 at 08:31, Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> wrote: > The way the libogg check is actually not something that's under my > control. It's installed on the

? is there any speex code in place that may help enable variable speed playback ? or perhaps another open source project has some code for this ? variable speed playback for voice messaging is an attractive feature, that would be well recieved for sure ! thx for any reply, Mark Tom Harper <tharper@sightspeed.com> wrote: At 12:35 PM 10/6/2004, Matthias Granberry wrote: >There is

Good day everyone, I'm trying to run .speex audio files in VLC. So I found a link to libspeex in VLC website, and I downloaded the package. Anyway, I don't know how to install it from now, once it's in a tar.gz format. Do I have to extract the files and paste it in VLC folder? P.S.: I'm using Win7. Thx a lot. Best regards, Ulisses -------------- next part -------------- An

Quoting Greger Burman <greger at mobile-robotics.com>: > The reasons I have posted these questions are: 1) To find out if Speex can > take advantage of SIMD extensions. If you define _USE_SSE, CELT is already able to use SSE instructions. You must be careful on Windows though because it doesn't support C99 var-arrays and alloca() isn't properly aligned for SSE, so you have to

The off dependencies are only for speexenc and speexdec, as far as I recall. If you omit those targets, you shouldn't have the ogg dependency issues. On Feb 10, 2010, at 22:21, Jean-Marc Valin <jean-marc.valin at usherbrooke.ca > wrote: > Unless you want to work on files (rather than RTP), you don't need any > of the stuff that uses ogg.h > > Jean-Marc > >

Something to look into perhaps is Trolltech's 'qmake' tool. It fills the role of something like autotools or now defunct imake. As far as I understand, you can indeed use it for projects that don't do anything with the Qt libraries. Now, it may not have the support for multiple targets that it sounds like are needed for speex, and I know it doesn't have as comprehensive of

On Fri, Oct 3, 2008 at 7:15 AM, Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> wrote: > 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

1. You pass in half the samples as the 'bits' arg. Speex looks at 1 frame worth of those bits and decodes them, decoded result in 'pcm'. 2. You pass in exactly 1 frame of data as the 'bits' arg. Speex looks at 1 frame worth of those bits (which is all there, exactly), decodes them, stores decoded result in 'pcm'. 3. You pass in 2 frames of data as

Ok! If there are indeed cross-compiling targets defined, then vs2005 projects probably should be maintained. In any case, this is all up to Jean-Marc, since he's the one that actually has authority to change it :) Jean-Marc -- what's your opinion? On 11/28/07, Aron Rosenberg <arosenberg@sightspeed.com> wrote: > > I pulled the test directory from 2003, but everything else

Hi, Thanks! can this program generate speex.lib instead of libspeex.lib?? the OpenSpeak link to speex.lib instead of libspeex.lib I can compiled the libspeex.lib but not speex.lib. Correct me if I am wrong Thanks ----- Original Message ----- From: "Alexander Chemeris" <ipse.sipx@gmail.com> To: <alex@gorex.com.hk> Cc: <speex-dev@xiph.org> Sent: Tuesday, May 29,