similar to: Suggest exposing VAD info. from opus frame

Hi Jean-Marc, We're exposing the opus_internal_flags data structure so that we can access the value assigned to prevSignalType. Here's a snippet of our code: error = opus_encoder_get_internal_flags(vad->opus, &internalflags); if (error != OPUS_OK) { return OPUSVAD_OPUS_ERROR; } cur_signal_type = internalflags.prevSignalType; if

Hi Jean-Marc, Thank you for the valuable feedback. You're correct in that we focused on enabling this just for SILK. Because our solutions are focused on voice, we did not explore doing the same in CELT mode, but we can certainly look into the details of analysis.c. Regarding the concern of exposing internals, do you have a specific proposal in mind? We've been sharing this patch with

Hi. I found that DTX is always unavailable when DISABLE_FLAOT_API is not defined in OPUS_AUTO mode. As you know analysis_info.valid is alway true except NaN case and is_silence is alway true except digital zero signal case. In general, following condition will be alway true except exceptional case. (analysis_info.valid || is_silence) But in a code, there is a NOT expression in front of above

Hi. I experienced same issue reported in https://gitlab.xiph.org/xiph/opus/issues/2026 The problem is that there are periodical(400ms) noise during DTX when the noise changed dramatically. I have found that the VAD value of silk does not affects to the DTX decision. If the background noise suddenly changes(by excessive echo cancellation, mute on/off operation, etc.) the silk generate a voice

Hi Peter, There's two main issues with a patch like the one you're proposing. First, the data is only valid when SILK is being used and is essentially undefined in CELT mode. The second issue is that by exposing internals, it makes it impossible to improve these algorithms since it would break API compatibility. I'm not fundamentally against trying to expose some information, but

Hi, I'm reaching out because we'd like to contribute back to the project a patch that exposes the signal type of the audio packet when encoding the PCM audio to OPUS. We've found the Opus VAD algorithm to be exceptional in this regard and have written a library that leverages this information for audio end-pointing. Attached is the patch. Please let us know if you'd be willing to

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 Peter, Can you say a little bit more about what you're doing exactly with the information you're exposing and how? unfortunately, I don't have a concrete proposal in mind right now. That's in part because I don't quite understand the use case, but also because it's really hard to expose this kind of information in a way that both avoids breaking application with new

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

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

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

My data is speech sampled as pcm mono 32khz. I want to use vad for regulating the agc gain mechanism. So... if voice is not detected I just reduce the agc value in order to not amplify the 'silence' otherwise we just increase the agc value if it is below the minimum. Thanks, Daniel ----- Original Message ----- De: Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> Para: danflu at

Hi, I had the same experience. The VAD done in the encoder does not seem to work very well at all. However, the VAD done by speex_preprocess() works much better. You will also get better results if you enable the denoiser, I think. peex_preprocess_ctl(preprocess, SPEEX_PREPROCESS_SET_DENOISE, &denoise_enabled); speex_preprocess_ctl(preprocess, SPEEX_PREPROCESS_SET_VAD,

Hello Jean-Marc et al: On 07/06/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > > - Is there a reference somewhere (other than the source itself) that > > explains how the latest VAD algorithm works? > > Read the source, Luke :-) (sorry) Okay. I had to ask :-) > > > - Is it possible to obtain the VAD status of a Speex stream > >

Hello all: I am interested in using Speex for an application that streams audio from a (noisy) source, so I am interested in VAD and DTX operation. However, after browsing the archives of this list, I note that a number of people have not been satisfied with the operation of the VAD algorithm in Speex. This leads me to a few questions: - Is there a reference somewhere (other than the source

> - Is there a reference somewhere (other than the source itself) that > explains how the latest VAD algorithm works? Read the source, Luke :-) (sorry) > - Is it possible to obtain the VAD status of a Speex stream > asynchronously? The current API seems to imply that some kind of > polling is required to determine the voice/non-voice status. Don't understand your question.

you can use the marker bit on the RTP. - farhan On Tue, Aug 19, 2008 at 12:04 PM, Fabio Pietrosanti (naif) <lists at infosecurity.ch> wrote: > Hi all, > > supposing to have speex working at 3.95, when VAD/CNG is employed, which > is the size of those "silence" samples respect to voice samples? > > I am wondering if it could be possible to lower even the

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

Hello, I am trying to use the preprocessor VAD to encode at lower bitrate during silence periods. I am able to run the preprocessor and get the VAD flag for each frame, and I am quite happy with it's performance. I would like to know how to pass the preprocessor VAD flag to speex encoder -- basically, i want to force the encoder to generate comfort noise when preprocessor detects silence.

Hi List, i've set up a cisco 7912 for my asterisk box. I've had problems with VAD and CNG. After googling a bit, i've found an article about asterisk not supporting these two protocols, therefore it's better to turn them off. Since then i did not found answer to my two questions, maybe somebody here could help me: a) am i even able to turn off vad/cng on cisco 7912? SIP