similar to: SV: How to detect SpeexBits corruption

Tom Grandgent a ?crit : > You might not be doing anything wrong. Speex is stateful and can > get into a bad state sometimes. It's happened to me too, but not > recently. And I've seen such bugs reported on this list and fixed. > I suggest several approaches to solving the problem: Tom, can you give an example of how Speex can enter a "bad state"? I don't

You might not be doing anything wrong. Speex is stateful and can get into a bad state sometimes. It's happened to me too, but not recently. And I've seen such bugs reported on this list and fixed. I suggest several approaches to solving the problem: 1) Try compiling Speex without compiler optimizations and see if the problem still occurs. Most likely it will, but this is an

You're doing something wrong. Read the documentation and check speechenc/dec just one more time. If that wouldn't help I'd suggest posting samples of your source code and describe what platform/compiler/os you're using. //JT -----Ursprungligt meddelande----- Fr?n: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] F?r jesus Skickat: den 22 januari 2007 19:43 Till:

Hello, im using speex library on my vo ip project, but some times, after it works ok, it begins to play noises (like voice hits) decoding the packets of one source (the others sound ok). I finally found that reseting SpeexBits and decoder state it solves. If i cant avoid this problem, i wish to solve when it occours, but ?how to detect this? Please, if anyone has experiment this issue i

Jesus, Unfortunately, FFT and magic algorithms don't work (yet?). You might want to try this if you're not satisfied with Speex VAD: http://lists.xiph.org/pipermail/speex-dev/2008-August/006860.html It won't perform any miracles, but I think it works pretty well and is easy to tweak. Tom >---- Original Message ---- >From: jmorion at toomeeting.com >To: speex-dev at

I wrote a speex parser, which we use inside of asterisk and iaxclient. It can parse a stream of speex data into individual packets: See static int speex_get_samples(unsigned char *data, int len) (and it's 2 helper functions) in http://iaxclient.svn.sourceforge.net/viewvc/iaxclient/trunk/iaxclient/lib/libiax2/src/iax.c As it's written, it just looks at a bunch of speex data, and tells

I was curious if you had ever peeked at a Teamspeak voice packet? I already have large chunks of the protocol torn apart. I believe the voice packets are the last big hurdle. As I know nothing about speex encoding, it is proving difficult to figure out the start of the actual voice data and/or any voice specific state data contained within the packet. If you have any information and are

Ohh...nice. I actually thought I was emailing Jean-Marc and didn't expect anything back from the list. In fact once I got a reply back saying it was waiting mod approval for list submission, I though it would be dropped. Your reply is both unexpected and much appreciated. I'm checking it out right now!! Thanks, Greg On Sat, 2007-03-17 at 12:00 -0400, Steve Kann wrote: > I wrote

Thank you, but I am thinking about trying to move VAD implementation from 1.1.12 to 1.2. I'm not sure about how difficult it could be (maybe impossible due to Jean Marc has disappear). Have you tried this? Cecile. 2009/8/10 jesus <jmorion at toomeeting.com> > Hi Cecile, > > it seems it is a tabu theme, or nobody uses VAD on speex. I've tried > with external EasyVAD

Le mer 12/03/2003 à 23:46, Daniel Vogel a écrit : > >From the sample encoder/ decoder demo in the documentation it seems that I > only have to call speex_bits_reset before encoding a new frame. Is this > still the case if I reuse the SpeexBits to both encode and decode different > streams? I'm not sure I fully understand you question... what speex_bits_reset is to make the

speex_bits_init_buffer(), clears the buffer. -----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: Saturday, December 09, 2006 11:20 AM To: Miles, Stewart Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] New function for manipulating SpeexBits How's that different from the current speex_bits_init_buffer()? Jean-Marc Miles, Stewart a ?crit : >

Hi Marian, I took a brief look at RFC 5574 and as far as I understand, you can simply do it like this: SpeexBits b; speex_encode(state, some320bytePCM1, &b); speex_encode(state, some320bytePCM2, &b); After that, get the encoded data with speex_bits_write and put it in your packet. Mark -----Original Message----- From: speex-dev-bounces at xiph.org [mailto:speex-dev-bounces at

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

It would be nice to have the following function added to the speex bits... void speex_bits_read_from_buffer( SpeexBits * const bits, void * const buff, const int buf_size) { bits->bytes = (char*)buff; bits->buf_size = buf_size; bits->nbBits = buf_size << 3; bits->bytePtr = 0; bits->bitPtr = 0; bits->owner = 0;

>From the sample encoder/ decoder demo in the documentation it seems that I only have to call speex_bits_reset before encoding a new frame. Is this still the case if I reuse the SpeexBits to both encode and decode different streams? Thanks, -- Daniel, Epic Games Inc. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe

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.

> both at the same time. Basically, you can see SpeexBits as just a string > of bits that can be accessed using a set of functions. Does that answer > your question? Yes, thanks! -- Daniel, Epic Games Inc. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

Hi, I've attached a patch against SVN r14645 which adds GCC visibility information to all symbols exported from libspeex.so and libspeexdsp.so. It includes a configure.ac change to test that both the compiler flags and __attribute__((visibility)) works, and if so will #define EXPORT __attribute__((visibility("default"))) and if not #define EXPORT I've attached a diff output

Jean-Marc, The following patch makes the above two read functions const correct. Cheers, Erik diff --git a/include/speex/speex_bits.h b/include/speex/speex_bits.h index a26fb4c..234ec53 100644 --- a/include/speex/speex_bits.h +++ b/include/speex/speex_bits.h @@ -77,7 +77,7 @@ void speex_bits_reset(SpeexBits *bits); void speex_bits_rewind(SpeexBits *bits); /** Initializes the bit-stream