similar to: 1.1 api suggestion

OK, I'll try to do *something* about it. It'll be either "support the 1.0 ABI" or "make sure the link will break". While the former would be nice, I'm not sure I want to really want to force 1.2 to have the same ABI as 1.0.x. More on this when I have some time to think about it. Suggestions are welcome. Jean-Marc Le lun 19/04/2004 à 02:18, Conrad Parker a

On Mon, Apr 19, 2004 at 02:46:44AM -0400, Jean-Marc Valin wrote: > OK, I'll try to do *something* about it. It'll be either "support the > 1.0 ABI" or "make sure the link will break". While the former would be > nice, I'm not sure I want to really want to force 1.2 to have the same > ABI as 1.0.x. More on this when I have some time to think about it.

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

openh323 speexcodec.cxx has: BOOL SpeexCodec::EncodeFrame(BYTE * buffer, unsigned & length) { // convert PCM to float float floatData[SAMPLES_PER_FRAME]; PINDEX i; for (i = 0; i < SAMPLES_PER_FRAME; i++) floatData[i] = sampleBuffer[i]; // encode PCM data in sampleBuffer to buffer speex_bits_reset(bits); speex_encode(coder_state, floatData, bits);

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

When I just copy the microphone input buffer to the output buffer the sound plays OK. But if I encode and decode the buffer through Speex I get a high pitched constant tone in the background. I actually do hear my voice speaking when I talk, but it's faint and much quieter than the tone. Here's what my data looks like: Input is the first 5 floats of each input buffer. Output is

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

Hi All, I'm very new to speex and in fact handling audio at all, it seems I have run in to a problem I seem unable to fix. I'm trying to take audio from a microphone using alsa, then encode it as speex and save to disk. I have been wondering if it has something to do with endian type, but speexenc and speexdec works fine. Currently I have the following setup: Platform:

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

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

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 >

Hi, I am writing a program that should be able to compile using speex version 1.0.1 and speex version 1.1.4, but a I am getting some trouble to encode with one version e decode using the other. The program is taking care of the change in both speex_encode and speex_decode. The sample being coded or decoded has changed from float to short. To test it, I have modified the sampleenc.c that

Hi, Speex is progressing and I've started thinking about the next 1.2 release (don't hold your breath). Though the bit-stream won't change, the API likely will. The API for 1.1.x already differs from 1.0.x because the speex_encode and speex_decode now use shorts instead of floats. Now, since I'm changing the API anyway, I thought I might as well fix things that might be annoying

Hi everyone, Our team is working on a realtime voice communication application. We are using openAL 1.1 to capture the samples and then encode them using speex. On the remote machine we decode the samples and play them using openAL again. Capture and play formats for the samples is AL_FORMAT_MONO16 and frequency is 22050. we are using wide band encoding/decoding. The encoding sample

I need to compile with version 1.1.4 because this is the one distributed with Mandrake 10 and it is my desire to let my application compile in this distribution and be compatible with other ones. Fl?vio Jean-Marc Valin wrote: >Why do you want your app to with with 1.1.4 in the first place. It's a >old unstable version and its API has been changed since then. > > Jean-Marc >

Thank you for such a quick response. The only reason I started with Char buffers is because WaveIn and WaveOut on Windows XP accept/emit WAVEHDR structures, which store audio data in LPSTR, which is Char*. typedef struct { LPSTR lpData; DWORD dwBufferLength; ... } WAVEHDR; When I was going from Char to float and back looked very wrong to me as well, but I was just not

Alright noted, I changed me code so that the state is created in the constructor and destroyed in the destructor of the object. However I'm still getting the same issue although I'm sure that would have bit me sooner or later. The new code is as follows. virtual Enigma::u8* Encode(Enigma::u8* inputBuffer,size_t inputSize, size_t& outputSize) { short *in=(short*)inputBuffer;

I have (finally) posted my Speex wrapper classes. They are at: http://www.grandgent.com/spx/tgAudioCodec.zip I followed your recommendations and they worked fine with 1.1.0. However, I'm still having the same problem with 1.1.7 that I had the last time I tried to upgrade. I'm using the same code with both versions, except for calling speex_encode_int instead of speex_encode, and

Hello, I know my question has been asked before because I spent the last week searching the web for how to use Speex in combination with WaveIn/WaveOut and I ran into a few posts, but none of them answer the question. There is still a lot of confusion how to use WaveIn/WaveOut and Speex by junior developers such as myself. Even after examining code for SpeexDec and SpeexEnc, I cannot get clear