similar to: Questions Regarding Opus Test Vectors

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,

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

Dear all, When I install the current version of opus-tools on my Ubuntu system, I have the following problem: When I try to open the test vector 'testvector01.bit', I got the error message 'Decoding complete. This doesn't look like a Opus file'. When I open the 'testvector01.bit.opus' the decoding works fine, but the tool opus_compare mentioned, that the number of

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>

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

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

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

While porting opus 1.2.1 to esp32, my compiler had a grumble (error) about possible use of uninitialized variables in decide_dtx_mode() Existing code: --------SNIP--------- /* Decides if DTX should be turned on (=1) or off (=0) */ static int decide_dtx_mode(float activity_probability, /* probability that current frame contains speech/music */ int

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

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

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

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

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;

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 all, I'm using speex through my own python wrapper based on ctypes. In my application I'm forced to process relatively large chunks of audio data (250ms). I was able to supply sufficiently large buffer to the SpeexBits structure and then encode using (code snippet) _speex.speex_bits_reset(byref(self.bits)) for i in range(0, len - self.frameSize, self.frameSize):

Hi... I have a rather large dataframe that I'm trying to remove rows from. I'm issuing the command: dtx[-which(dtx$rdate > "2008-06-16"),] and it tries to print out over 170,000 lines of output. So...I did: options(max.print=1e6) and ran it again. It worked, but when I did a: which(dtx$rdate > "2008-06-16") it tells me that all the data I thought I deleted

Dear Speex Developers, We are currently using the basics features of Speex 1.1.10 on our little embedded ARM processor and it works great! However, we hit a brick-wall when trying to use echo cancellation or the pre-processor; our CPU (no FPU) jumped to above 90%. Are there any plans in the immediate future to optimize the VAD/DTX and pre-processor code of Speex (convert to fixed-point, ARM