similar to: Samples per frame.. fixed or variable with configuration?

You definitely need to have separate decoders for separate streams. It has been mentioned before that inter-frame state is critical to achieving the level of quality for bandwidth that Speex offers. This differentiates it from iLBC, a codec whose claim to fame is that it treats each frame independently. I'm not sure what's hard about maintaining multiple decoder states, unless you are

What does it sound like if you try to use only one decoder state for multiple streams? Tom Grandgent wrote: >You definitely need to have separate decoders for separate streams. >It has been mentioned before that inter-frame state is critical to >achieving the level of quality for bandwidth that Speex offers. This >differentiates it from iLBC, a codec whose claim to fame is that

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'm only doing one frame using speex_encode_int greatly simplifies my code I'm not sure why the sample I was working off of was converting the shorts to floats then calling the other encode/decode methods. Based off of your suggestions I tried the following but I get the same result. virtual Enigma::u8* Encode(Enigma::u8* inputBuffer,size_t inputSize, size_t& outputSize) {

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

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.

Assuming one prefers to use the speex_encode_int() and speex_decode_int() when available, but fallback to speex_encode() and speex_decode() if an older version if the lib is installed, how does one best make the determination? The only thing I can see to do is call speex_init_header() and look at the result. Even at compile time it seems one must compile a test app that outputs that data and then

Changing from using floats to shorts did fix the high pitched tone problem. I'm having other problems but I'll look into it more first. SteveK wrote: > > On May 21, 2006, at 6:33 PM, Kevin Jenkins wrote: > >> 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 >>

Hello, I intend to make a speex port for freescale DSP56F800/E. I downloaded the source code, but I not realize which function are called in which order for encode after calling speex_encode (or speex_encode_int) and speex_decode (or speex_decode_int). Could anybody help me on this? Thanks in advance Alexandre Penna

This patch will export new speex functions in the generated library, such as speex_encode_int as well as the preprocessor, echo-cancellation and jitterbuffers. The ordinals used matches the 1.1.6 release from the speex.org website, so any new library created with this def file should be binary compatible with that one. -------------- next part -------------- Index: speex.def

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:

Hi, i know this question has already been asked, i've checked mailing list logs but ... I didn't figure out the solution for my question. I want to use basic functionnality of speex, only VAD, no pre/post filter, even no VBR. But i *really* want to use less mem/cpu i can. So in which format should i pass data to speex_encode(_int) , float or short ? I quickly looked at the source code

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, I'm using speex 1.1.10 and writing a program similar to sampleenc. I need to use the fixed point library as I'm eventually porting to ARM processor but I encountered a problem with speex_encode_int(), which I used in place of speex_encode(). I gave it a short instead of a float (manual says it takes a short for the audio - 2nd parameter) but the compiler says it could not convert the

Hello I´m making a class using prototype''s class.create(), like this: var onewClass = Class.create(); onewClass.prototype = { initialize : function(array) { this.variable = "fooo"; this.array = array; }, function1 : function() { this.array.each(function(element){ alert(element);

Hi Tom, Thanks for your reply, I'm having a few difficulty's following you advise. You mention that I should be calling 'speex_encoder_int' & 'speex_decoder_int', I'm having problems finding these functions in the speex header. I am currenlty calling speex_encoder_init & speex_decoder_init in my test code, I have repeated the relevent bits of the example

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

Hi Jean-Marc, randoms, I've been playing with the 1.1.x api, more specifically modifying code to conditionally build against the 1.0.x api or the 1.1.x api. Code written for 1.0.x builds, with a few warnings, against 1.1.x. The major API change is of course that the type of PCM buffers has changed from float to int. This causes a few warnings related to speex_encode() and speex_decode()

The way I do this is to compute the number of frames (by dividing the size of my input by the number of bytes per frame and then calling speex_encode_int() that many times. Something like speex_bits_reset( &bits ); for( n = 0; n < num_frames; ++n ) { speex_encode_int( enc_state, (int16_t*)input_tail,