search for: mdemoss

The example in the documentation demonstrates using speex_bits_reset before encoding and decoding each frame. " speex_bits_reset(&bits); speex_encode(enc_state, input_frame, &bits); nbBytes = speex_bits_write(&bits, byte_ptr, MAX_NB_BYTES); " What happens if this is not done? I think I'm missing the point of having a SpeexBits object.

Thanks, it makes more sense to me now. Does speex_bit_read_from also append in that manner? Jean-Marc Valin wrote: > speex_bits_reset is before encoding, not decoding. If you don't call it, > then everything you encode will be appended so it will grow without end. > As for the point of the SpeexBits struct, it's there as a sort of "array > of bits" to it's easy

/input_frame/ is a /(float *)/ pointing to the beginning of a speech frame What is the range on the floats in the input_frame that speex_encode() needs? The library that I'm using to get the sound gives me floats that are between -1.0 and +1.0. I was assuming that this is also the case for speex, but I don't see it documented. I'm thinking now that maybe this is not the case for

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

The API reference says it is "+-2^16 range." Which is right? I've yet to successfully encode or decode anything. Jean-Marc Valin wrote: >It is documented and the range is +-32767 > > Jean-Marc > >Le mardi 07 juin 2005 ? 11:59 -0500, Matt DeMoss a ?crit : > > >>/input_frame/ is a /(float *)/ pointing to the beginning of a speech frame >>