similar to: Using speex (newbie)

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

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

Thank you for the answer but i've already read manual and examples and i'm doing same thing of your code, so, maybe you can give me a hint about the problem i have, that it is for sure in my code. A question: is it possible that i hear a "tick" because between two frame i call speex_bits_reset? (for this reason if i encode more than one frame together there is no

I all, I have a question about the use of conference rooms: can I, with a Voip telephone or softphone call some other telephone and invite them in a conference room? I read a lot of documentations about asterisk, but i can't find any example ! Thanks, best regard Fabio

David, Here's the trick ... do this just before your speex_bits_write(): speex_bits_insert_terminator(&bits); Then, when decoding, keep calling speex_decode() until it returns -1 or speex_bits_remaining(&bits) returns 0. Works for me, anyway. Tom David Barrett (dbarrett@quinthar.com) wrote: > > Hi, I'm using Speex and I want to pack multiple frames into a single >

On Saturday 10 April 2010 21.51.55 Jean-Marc Valin wrote: > All version after 1.0 are compatible with each other and with 1.0. Hi Jean-Marc and thanks for the quick reply. I have now looked at this further and got the idea to hard code the number of frames in the decoder temporarily as a test and voil?, it works! The problem seem to be some incompatibility in the termination handling. After

I tried feeding in the 3 encoded frame in ONE BLOCK, and calling speex_decode() 3 times in a roll. Only the 1st frames came out perfectly. For the other 2, I got "corrupt" frame warning. I was supposed to get 38 bytes consumed each frame (narrow-band, VBR off). I tried speex_bits_remaining() to peek on the # of bits consumed, and got variable (clearly wrong)#s returned. But if I

Hi list, I'm trying to figure out how to do the most compatible implementation that will work with as many versions of Speex as possible. I am streaming multi frame Speex blocks over a TCP connection which works fine as long as the version of Speex is the same on both sides. When using a newer Speex (1.1.?) to encode and an older version to decode (1.0.5), it does not work. The encoder

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Il 15/04/2010 01:30, Conrad Parker wrote: > >> But how can I know the size of each speex frame into a multiframe payload? > > use speex_bit_read_from() just once on the packet, then call > speex_decode() once for each frame. > > Conrad. Thanks for the reply, Conrad. What is not clear for me (and I didn't found it on the

I've just started testing Speex, and it seems very good so far. In testing the Speex decoder and simulating packet loss, I noticed that simply not calling speex_decode(st, NULL, output) when a packet is dropped doesn't appear to degrade the quality of the audio later on. The reason for this test is that in a real-time situation, you may not know right away when a packet is dropped

I thought it would be more update/better/faster, any thing wrong? In the future, would you use short, and forget about float? If so, I use 1.1.4, I wouldn't need to change my code in the future, right? You said, it's unstable, yes, I got compiling errors with MsVC6 and MsVC.net And I modified it a bit to get it compiled. Should I post the errors here? <p>-----Original Message-----

Ok, I'm using 1.1.4, so I should pass signed short(wav data) directly to speex_encode()? But the samplecode that comes with 1.1.4 shows me to put short in float array, and pass the float array to speex_encode() <p>-----Original Message----- From: owner-speex-dev@xiph.org [mailto:owner-speex-dev@xiph.org] On Behalf Of Jean-Marc Valin Sent: Saturday, April 17, 2004 6:25 AM To: speex

I'm confused about the format of the PCM/WAV data for speex_encode & speex_decode speex_encode(enc_state, input_frame, &bits); In the manual, it says "input_frame is a (float *) pointing to the beginning of a speech frame" (for encode) But I've found that in speexenc.c and testenc.c, short* is used instead of float* So, isn't it signed 16 bit samples(if

Jean-Marc Valin wrote: >>I believe it is adaptive, but no, I haven't used it, because it's >>coupled only to the speex codec. We're working on a generic >>application and codec-independent jitter buffer algorithm, for use in >>asterisk and iaxclient (at least). Some information is available at

Hello there I'm having trouble decoding speex frames when using 32KHz audio and quality setting 4. If I encode three frames and then decode the three frames then the speex_bits_remaining() still reports that there are bits remaining. All other band modes and qualities reports that the buffer is emptied. Here's an example that shows 4 bits remaing in the buffer after the frames have

Dear R users and developers, Would any of you be interested in giving a lecture about R and/or R use cases at the following free software conference that takes place in Amiens, France, next summer? We already had a talk on R last year by Yves Croissant (http://2006.rmll.info/theme_26?lang=en) but are still open to any submission this year. We expect some talks this year (to be confirmed) about

Ok, I figured it out. :) This seems to work: 1) Call speex_bits_read_from() once, specifying the location in memory of the compressed data, and the total length of that data. 2) Keep calling speex_decode() until speex_bits_remaining() returns 0. Then you don't have to keep track of the # of frames per packet, or the size of each compressed frame. It's done magically by the codec.

Hi Steve, thanks for the advice. I placed the appropriate functions outside the while statement but I still get this error at the while loop: First-chance exception at 0x004010fa in SPXDEC.exe: 0xC0000005: Access violation reading location 0x0000000c. Unhandled exception at 0x004010fa in SPXDEC.exe: 0xC0000005: Access violation reading location 0x0000000c. It looks like the same error. I've

Danny Chan wrote: >Hi Jean and Steve, > >Can you tell me whether the jitter filter / buffer is adaptive type, I >saw the description of speex_jitter.h say it is "adaptive", anyone of >the group has implemented it and confirm it. > > I believe it is adaptive, but no, I haven't used it, because it's coupled only to the speex codec. We're working on a

Hi, i'm using speex in a conferencing application and i have a little problem. I encode single buffer of 320 byte (160 short) and send it to destination where i play it. The problem is that between frame i hear a "tick" so, if i encode single frames, send it and play it, i heard like to be underwater (because there is a tick 8000/320 times/sec ), if i encode many packet all together