similar to: DTX Seems to be Wrong for 10ms Frame Size

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

The email might have been blocked due to the attachment size, here?s a link to it. https://www.dropbox.com/s/r9j7l3cbb02ob7i/opusDtx_noiseFix1_inOut.zip Pascal On 26/06/14 19:02, "Pascal Huart (phuart)" <phuart at cisco.com> wrote: >Hi Jean-Marc, >Thanks for the fix, the reconstructed signal is now much better. >Unfortunately there are still discontinuities which show

Hi Gonzalo, Thanks for reporting this DTX issue. It should now be fixed in git. Can you confirm this it is indeed the case? Cheers, Jean-Marc On 19/05/14 10:20 AM, Gonzalo Mariano (gmariano) wrote: > Hello: > > > > We noticed that opus reconstructed noise is pulsing with a 400ms pattern > when dtx is enabled in silk mode. This is independent of the background > noise

I downloaded test vectors from opus-codec.org site. The site indicated that the test files are intended for verifying that the Opus decoders are operating properly. I assume I could also use them to verify my encoder implementation, right? For example, use testvector01.dec as input to my encoder and compare its output bitstream with the corresponding testvector01.bit bitstream file. Any idea

Hello: We noticed that opus reconstructed noise is pulsing with a 400ms pattern when dtx is enabled in silk mode. This is independent of the background noise level and is found with speech + non-speech period test files as well as variable level noise-only test files. This issue can be reproduced with opus v1.1 using this command: ./opus_demo voip 16000 1 25000 -dtx input.bin

On 2019-04-01 3:37, Gustaf Ullberg wrote: > Hi everyone, > > Some time ago, I sent a pull request > <https://github.com/xiph/opus/pull/107> to the Opus github page. > Jean-Marc asked me to post it to the mailing list so everyone can have a > look at it. > > You can find the description and code changes below. Please let me know > if you have any questions or

Benjamin, Thanks for the prompt response. Are there other recommended methods to verify encoder implementations? Regards, Chris From: benjamin.m.schwartz at gmail.com [mailto:benjamin.m.schwartz at gmail.com] On Behalf Of Benjamin Schwartz Sent: Sunday, November 10, 2013 1:53 PM To: Wang, Chris Cc: opus at xiph.org Subject: Re: [opus] Questions Regarding Opus Test Vectors On Sun, Nov 10,

Hi, I want use opus DTX to save bandwidth in my half duplex VOIP project, so i require help for below questions 1)what is opus DTX and documents to study DTX. 2)if opus DTX is enable do i need send comfort noise or completly drop silence detected frame. 3)How extactly OPUS DTX works with RTP protocol. 4) how to test with OPUS demo binary Thanks & Regards Vittalprasad B R 8722397247

Yes, good point. I added the checking of prev_mode for Silk DTX to avoid using stale data from the Silk state. The PR is updated, and I'm attaching an updated patch. /Gustaf On Tue, 9 Apr 2019 at 12:42, Mark Harris <mark.hsj at gmail.com> wrote: > On 2019-04-08 4:55, Gustaf Ullberg wrote: > > Thank you Mark. > > > > I agree and have now updated the pull request

Hi everyone, Some time ago, I sent a pull request <https://github.com/xiph/opus/pull/107> to the Opus github page. Jean-Marc asked me to post it to the mailing list so everyone can have a look at it. You can find the description and code changes below. Please let me know if you have any questions or concerns. Best regards Gustaf Ullberg In WebRTC, we would like to be able to

Thank you Mark. I agree and have now updated the pull request with a new commit, addressing your comments. Please take a look. /Gustaf On Fri, 5 Apr 2019 at 11:41, Mark Harris <mark.hsj at gmail.com> wrote: > On 2019-04-01 3:37, Gustaf Ullberg wrote: > > Hi everyone, > > > > Some time ago, I sent a pull request > > <https://github.com/xiph/opus/pull/107>

On Sun, Nov 10, 2013 at 10:41 AM, Wang, Chris <cwang at sonusnet.com> wrote: > I downloaded test vectors from opus-codec.org site. The site indicated > that the test files are intended for verifying that the Opus decoders are > operating properly. I assume I could also use them to verify my encoder > implementation, right? For example, use testvector01.dec as input to my

When encoding using the Opus multistream API, is it possible for opus_multistream_encode() to return 0? For example, what happens if multiple streams are being encoded, each with DTX enabled and all streams emit DTX packets at the same time? What about the case of a single stream with DTX enabled? Thanks Kevin O'Connor -------------- next part -------------- An HTML attachment was

I'm working on an opus codec for the asterisk voip app. Googling DTX found: https://bugs.chromium.org/p/webrtc/issues/detail?id=4559 To paraphrase, if there's silence long enough, opus enters Celt-only mode, which has no DTX. Is this still correct ? And is the suggested work-around effective? sean -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, When we pass around 9K samples of only ambient noise (no voice), the encoder which is enabled FEC+DTX is detecting only some 140 frames as non-voice (returning only TOC, no frame content). We were expecting all or more to be identified as non-voice. Our idea was to check how the decoder re-generates the original ambient noise during the silence duration (when we feed NULL to decoder) when

> 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, I changed the VAD sensitivity by varying VAD_SNR_FACTOR_Q16 and now it shows the difference in silence frames. Thanks Suresh On 4 October 2016 at 17:57, Suresh Thiriveedi <sthiriveedi at gmail.com> wrote: > Hi, > > When we pass around 9K samples of only ambient noise (no voice), the > encoder which is enabled FEC+DTX is detecting only some 140 frames as > non-voice

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

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

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