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:

Hi Conrad, Thanks a lot for the info. This is exactly what I needed. We want to use speex in our IP telephony client and I was indeed trying to put together a GUI configuration screen. Best regards, Chris > On Tue, May 20, 2003 at 06:04:39PM +0200, Chris Flerackers wrote: >> Hi, >> >> Is there are document where the interaction between all the configuration >> options

Hi, I'm trying to cover all Speex configuration options to set quality/mode/bitrate in my application and I was wondering if the following all makes sense: - abr_bitrate - use average bitrate and set it using bitrate parameter - SPEEX_SET_ABR - cbr_bitrate - use constant bitrate and set it using bitrate parameter - SPEEX_SET_BITRATE - cbr_mode - use constant bitrate and

I'm running a: for band in n w u do for quality in 0 1 2 3 4 5 6 7 8 9 10 do for complexity in 3 do for vad in "" "--vad" do for dtx in "" "--dtx" do echo speexenc -${band} --quality ${quality} --comp ${complexity} ${vad} ${dtx} input.${band}.wav

The audio frame speex generates sounds pretty terrible most of the time, and I don't use it for jitter correction instead I just use it for dropped packets - so I usually drop the late packet. It sounds acceptable as long as I drop less than 5% of traffic (dropping 2 in a row makes a bad robot noise, so I reset the stream in that case). The good news is that on an unsaturated DSL line jitter

Hi all, I have recently added Speex support to my app (http://sbooth.org/Max/) and am in the process of creating a GUI for the user to control the codec parameters. I am new to Speex and as such I am not really sure which parameters are more important than others, and deserve prominent placement, etc. Is there a recommended GUI for people to follow or use as an example? Stephen

Could a method be added to use the VAD from the preprocessor to send the packet with the 'dtx_enable' flag in it, so the decoder on the other end knows it's in dtx mode? (and SPEEX_GET_DTX_STATUS returns 1) At the moment, I can hack around it by doing something like: if (VAD for prev frame && ! VAD for this frame) { iArg = 0;

Jean-Marc Valin wrote: >>Heh. I guess after playing with different jitter buffers long enough, >>I've realized that there's always situations that you haven't properly >>accounted for when designing one. >> >> > >For example? :-) > > I have a bunch of examples listed on the wiki page where I had written initial specifications:

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, I am looking how to setup speex codec in codecs.conf for 8 Kbps and 6 Kbps. In config file are many parameters for setting. I don't know what is need to change for narrowbad like 8 Kbps and 6 kbps. Any suggestion? [speex] ;0-10 quality => 4 ;0-10 complexity => 4 ; true / false enhancement => true ; true / false vad => false ; true / false vbr => false ; 0 = off, otherwise,

Hello, in my project im using speex 1.2rc1 and the preprocessor VAD seems to only separate complete silence from not complete silence frames. The Speex Manual, you can read "The voice activity detector (VAD) provided by the preprocessor is more advanced than the one directly provided in the codec." but if you go to the source code in preprocess.c line 995 "/* FIXME: This VAD

Hi All, I've run into a small hiccup in encoding my audios with Speex. When I encode audience laughter and applause with 'speexenc' (version 1.0.1), the result is quite acceptable... until I enable VBR. Then it distorts horribly. My understanding of VBR is that it frees the encoder to vary the number of bits emitted to better maintain the quality requested, and so I would have

Jean-Marc Valin wrote: >>OK, I'm actually about ready to start working on this now. >> >>If people in the speex community are interested in working with me on >>this, I can probably start with the speex buffer, but I imagine >>there's going to be a lot more work needed to get this where I'd like >>it to go. >> >> > >And where

> Err, unless I'm totally wrong, there are a few race conditions. > > Assume the buffer is full of packets newer than the current pointer, and > one that is at the current pointer. > > get and put start at the same time. > > get will find the correct buffer index. Now, just after it finds it's > index, assume we switch to the put thread. > > Put needs

Jean-Marc Valin (jean-marc.valin@hermes.usherb.ca) wrote: > > > I've been using Speex in my voice-over-IP program on Win32, in > > wideband (16kHz) mode. I just starting using VBR recently and > > have run into something that might be a problem within Speex: > > Are you turning on DTX in addition to VBR? Also, what version are you > using. As of 1.0, DTX is

Jean-Marc Valin wrote: >>In particular, (I'm not really sure, because I don't thorougly >>understand it yet) I don't think your jitterbuffer handles: >> >>DTX: discontinuous transmission. >> >> > >That is dealt with by the codec, at least for Speex. When it stops >receiving packets, it already knows whether it's in DTX/CNG mode.

Hello, I'm try to run speex on some ARM processor. I'd like to cut away some speex features including VBR, ABR and preprocessor while still supporting VAD/DTX. But I've found some puzzles in the source code regarding VAD as below, 1) there are VAD related codes in the source file preprocess.c. Will VAD still work If I don't use the source file preprocess.c? 2)The speex manual

Hi, I found this message concerning VAD and was wondering whether VAD has been ported to fixed-point in the latest version? Thanks, SingHui ---------- Forwarded message ---------- From: Jean-Marc Valin <Jean-Marc.Valin@usherbrooke.ca> Date: Jul 22, 2005 1:02 AM Subject: Re: [Speex-dev] Fixed-point To: gue baja <gue_baja@yahoo.com> Cc: speex-dev@xiph.org Hi Baja, Here's a quick

Hi Marc, Thanks for your quick response. So if VAD is enabled then VBR will be enable although it's a special VBR. How about take out the VAD code from the VBR and remove the code else? Lianghu On 10/24/06, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > > > 1) there are VAD related codes in the source file preprocess.c. > > Will VAD still work If I

Hi,I'm having performance issues encoding with speex on an iphone4 + iOS5. The same code yields excellent results on iPad2 + iOS5, Mac OS X 10.6 as well as Windows 7. The call to speex_encode_int is takes 0.0065 to complete. Because encoding is so latent the receiver incurs underruns. Here is my speex setup: ? ? unsigned val = 0; ? ? /**? ? ?* Initialize the encoder in narrow band mode.? ?