similar to: DTX and VAD doesn't work on one of my computers.

Dear Jean, Thank you so much for reply my message. I am sorry the function return 38 is speex_bits_write(). This function doesn't work on one of my computers. But after I add the function speex_preprocess(), it works well. I am wondering what is the possible reason? What the function speex_preprocess() does? Another problem I have now is when I enable dtx and vad with function

hi there, I am new to mailing list so excuse me if I don't obey to the 'netiquette'. i am writing voice chat and speex is in the root of it. i write it in Java and use JNI to link with 'C'-based Speex 1.2beta. [I know of JSpeex but there are not implemented some features] recently i decided to use DTX feature of speex as well. the code follows. The problem is that no matter

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

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

Hi there, I enable DTX and VAD in speex_encode to detect whether there is silence in voice data. But the same programme got different result on my computers. The function speex_encode always return 38 on one of my computers although it is silence. On all other computers the function speex_encode return 1 when it is silence. It means DTX and VAD doesn't work on particular OS or PC. Do anyone

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 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

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

On Tue, 2003-04-15 at 11:31, Jean-Marc Valin wrote: > > How do i detect whether there is silence in media using speex? > > Is there any API which decides that the audio data only contains > > silence? > > Basically i will have PCM linear data, I want to know whether it is > > complete silence. > > Well, the best way is probably to turn VAD *and*

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, We are in the process of debugging a voice quality issue for a client of ours that is a VoIP services provider. The client uses a softphone that runs on a pjsip stack. When placing a call using the softphone, it negotiates the use of G729 codec with the remote endpoint (ptime = 20ms). The endpoint transmits RTP packets with encoded G729 payload. VAD/DTX is enabled. We see that the last

Hello! I'm working on adding VAD (silence suppression) to my branch of VOCAL. I've read through the Speex docs and see mentions of VAD/DTX, but I am not sure quite how to use it. For instance, on the transmitter side..do I need to detect the silence somehow and bypass speex encoding, or can speex tell me that the packet is all silent and should not be transmitted as part of it's

Hello, The way you describe how the jitter buffer should be implemented makes me wonder: How does the jitter buffer works when there is no transmission? Let's say my "output" thread gets a speex frame from the jitter buffer every 20ms. What happen when there is no frame that arrived on the socket? No frames at all for a pretty long time (ie many seconds). This is my case because I

> How do i detect whether there is silence in media using speex? > Is there any API which decides that the audio data only contains > silence? > Basically i will have PCM linear data, I want to know whether it is > complete silence. Well, the best way is probably to turn VAD *and* DTX on. Then when there's silence, the speex_encode function will return zero, which

Hello, I am trying to use the DTX feature of speex to tell if the user is speaking. I have VBR, DTX and VAD turned on, but the function speex_encode always returns a non-zero value. It is my understanding that it should return a zero value when the encoder detects silence? Could anyone give me any clues to help figure out why this isn't working for me? I am using the 1.13 version of speex on

Hi, I have a few questions about the speex_jitter_buffer when used with DTX here goes: I want to use the speex_jitter_buffer with muliple streams (multi client) and with DTX so that clients will only transmit data when they are actually saying anything, but Im unsure of how the ticking is handled. I have 1 x SpeexJitter struct per client stream Im using portaudio and Im planning on

As I understand it, there are two separate ways to get VAD information from Speex: 1) Using the encoder. 2) Using speex_preprocess(). I present the following observations from an application developer's perspective. They may be wrong, in which case I would appreciate corrections. - The two VAD systems are implemented differently. - speex_preprocess()'s VAD provides more accurate

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

> So far, I've noticed that --dtx alone doesn't seem to do anything, but --vad does > and the combination --dtx with --vad does more. The lone exception is for wide > and ultra-wide coding at quality 0, --vad, alone, makes the file slightly larger. > At all other sized the ordering is always: plain==--dtx, then --vad, then --vad > with --dtx. All you say look normal to me.

Hi Jean, > Actually, Speex has Packet Loss Concealment (PLC) > builtin. If a packet > is missing, instead of repeating the previous one, > just try decoding by > passing NULL instead of the SpeexBits struct. > Thanks, I have made the above changes and the effect seems to be better now. > > I think jitter buffering is more correct way to > solve > > this problem