similar to: Speex settings and jitter

In my experience most of the jitter related issues are because people are using too small of audio buffer sizes that match the framing size of Speex - particularly in Windows. This isn't a problem with Speex, but as a programmer you should collect and append a few frames to match the size of your output audio frame buffer before attempting to play the sound. -----Original Message----- From:

Right - and I deal with that on the receiver end based on an approximation of sender's and receiver's responsiveness - the minimum latency I've been able to get into the system is about 150 ms. Of that, jitter buffering is about 40-100ms. I'd love to figure out how to get that down without killing myself on thread switching or Win32 kernel calls, but ms has to actually implement

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. Thank you all. Regards, Danny Chan -----Original Message----- From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] On Behalf Of Jean-Marc Valin Sent: Tuesday,

Since r12660, the speex_jitter_get with high latency doesn?t works, I have no sound. Before this release, the speex_jitter_get works in all conditions. speex_jitter_get return void, then I cannot know the reason of this problem. Regards Ouss -----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: dimanche 18 mars 2007 23:07 To: Ouss Cc:

Hi Jean-Marc, Thanks for your response. Given a worst case scenario, what is the "worst case" latency (in terms of Speex frames) that the jitter buffer algorithm will incur? We're trying to determine the worst case hard number. Sorry for unclear question below; what I was trying to ask is that given a worst case latency (which I'm asking in the first question) inherent in

I use the speex version of your jitter, and in speex_jitter_get, you always call the jitter_buffer_update_delay. -----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: dimanche 18 mars 2007 13:06 To: Ouss Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] Problem with the svn jitter buffer > I think that the new Jitter Buffer have a problem. > >

Hi, Is there are document where the interaction between all the configuration options of speex is explained? Speex seems to have CBR, VBR and ABR. You can also use SPEEX_SET_QUALITY (SPEEX_SET_VBR_QUALITY) and SPEEX_SET_BITRATE which I suppose can't be set at the same time. Is there a list of possible combinations somewhere? I also have another question related to jitter. To minimize jitter,

Hi, sorry for the repost again, but does anyone have a code snippet example of how to use the jitter buffer? Regards, Andy ----- Original Message ---- From: Andy Ngo <ndno72-speex@yahoo.com> To: speex-dev@xiph.org Sent: Wednesday, January 10, 2007 8:09:10 PM Subject: [Speex-dev] Sample snippet of how to use jitter buffer Hi, I searched around in the Speex manual and API but

Oh, I forgot to mention one thing. I currently append a few bits of custom information to each speex packet which I fetch out with things like speex_bits_unpack_unsigned(&sjJitter.current_packet, 1); It would be very usefull if the jitter buffer didn't actually decode the packet, but instead returned a pointer to it (or NULL if you should play silence and -1 if you should repeat the

Good question. I'm coming to the conclusion that using plain UDP and "home-grown" packet construction for transmitting the speex data (with timestamp/sequence counter) and implementing jitter control on the receiver end is an adequate implementation for a VoIP application. Assuming of course that I don't care about any interoperability issues with other applications etc. I was

Hi, I'd like know about anyone using the current jitter buffer in Speex. I'm planning on changing it to make it more general and I'd like some feedback about how to make it better. Also, let me know if you're doing anything serious with it and want to make sure I don't break your stuff. Basically, I want to make the jitter buffer easier to use with other codecs and reduce the

Hi, Our project is using the jitter buffer feature built in Speex. We noticed there are some latency when using the jitter buffer. Does anyone know what is the "worst case" latency inherent in the jitter buffer algorithm? I believe someone already mentioned that it's adaptive but is there a worst case hard number (in terms of 20ms Speex frames)? I'm not familiar with the

Thank you for a very good explanation which shed light on some of the questions that I had after reading the source code. Reading your text however, I wonder if I'm perhaps missing an important point on the proper use of the jitter buffer: ... > Now, clearly, if early_ratio is high and late_ratio is very > low, the buffer is buffering more than it needs to; it will > skip a frame

Hello, I'm using Speex1.1.11.1 source code. I enabled dereverb by speex_preprocess_ctl(). I try different dereverb_level and dereverb_decay values and it seems to not work. I generate some test files in CoolEdit using reverb or echo and then preprocess it by speex_preprocess(preprocess, input, NULL); and output is the same as input:(. Denoising and VAD works very good. I tried dereverb with

But that's what a jitter buffer will do, eventually - drop a packet. And it's better to drop a silence packet. Cheers, .a -----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: Wednesday, December 21, 2005 3:39 PM To: Alex Bakaev Cc: Shantanu Gramsci; speex-dev@xiph.org Subject: RE: [Speex-dev] Bitrate problem On Wed, 2005-12-21 at 15:29 -0800,

The jitter buffer would "freeze" under the following condition: - The sender and receiver are in sync. - The sender machine freezes for a few seconds while the receiver does not. - This causes all the packets sent by the sender to have a timestamp that is too low to be considered, meaning jitter_buffer_put ditches it before it checks if lost_count > 20 to reset. - The jitter buffer

-----Original Message----- From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] On Behalf Of Thorvald Natvig Sent: Monday, March 20, 2006 12:11 PM To: speex-dev@xiph.org Subject: Re: [Speex-dev] Who is using the jitter buffer? But I must say that it really does work well at the moment, at least from the "minimizing latency" point of view :) How do you timestamp the

Hello, I think that the new Jitter Buffer have a problem. It works perfectly when I call the speex_jitter_put every 20ms (on my lan) but in other case (with big latency on Internet connexion), it doesn't works. The old version is OK in all cases. Hope it will helps. Thanks Ouss -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

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