search for: opus_testvector

...1e4d340a9e71a5ca2c5d4d53f4ee072e84afda271ca opus-1.3-rc2.tar.gz 4f3d69aefdf2dbaf9825408e452a8a414ffc60494c70633560700398820dc550 opus-1.3.tar.gz +65b58e1e25b2a114157014736a3d9dfeaad8d41be1c8179866f144a2fb44ff9d opus-1.3.1.tar.gz 94ac78ca4f74c4e43bc9fe4ec1ad0aa36f38ab90f45b0727c40dd1e96096e767 opus_testvectors-draft11.tar.gz 94ac78ca4f74c4e43bc9fe4ec1ad0aa36f38ab90f45b0727c40dd1e96096e767 opus_testvectors.tar.gz 6b26a22f9ba87b2b836906a9bb7afec5f8e54d49553b1200382520ee6fedfa55 opus_testvectors-rfc8251.tar.gz -- 2.17.1

...s://docs.google.com/document/d/1L6csATjSsXtzg_sa1iHZta8hOsoVWA4UjHXEakpTrNk/edit?usp=sharing > > Even though this primarily affects the encoder, as a sanity check, it's always good to make sure the test vectors still decode correctly. Get them from <http://opus-codec.org/testvectors/opus_testvectors.tar.gz> and use > tests/run_vectors.sh <build path> <test vectors path> 48000

...tzg_sa1iHZta8hOsoVWA4UjHXEakpTrNk/edit?usp=sharing >> >> >> >> > >> > Even though this primarily affects the encoder, as a sanity check, it's always good to make sure the test vectors still decode correctly. Get them from <http://opus-codec.org/testvectors/opus_testvectors.tar.gz> and use >> > tests/run_vectors.sh <build path> <test vectors path> 48000 > > OK, this took about 2 hours.. but all tests passed successfully. > Please let me know what the next steps are. Is there plans to support ARMv8/aarch64 NEON intrinsics too? Also i...

...t for Opus in WebRTC, Tom Flanagan has added support for .opus files in the HTML <audio> element, similar to what Firefox has. It's currently behind a switch, so you'll need to pass --enable-opus-playback to M25 or M26 to evaluate. I tried some the files https://people.xiph.org/~greg/opus_testvectors/ in yesterday's Chrome Canary. It looks like the gain header and surround channel mapping isn't implemented yet, but basic playback seems to work fine. This is great news! https://code.google.com/p/chromium/issues/detail?id=104241#c33 -r -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4...

Hi, I'm working on porting libopus and I'd like to get information how to test Opus Encoder properly. There is information in RFC6716, that Opus Decoder's test files (http://opus-codec.org/testvectors/opus_testvectors.tar.gz) were created specifically to exercise all aspects of the decoder. Using these files, a custom implementation of libopus can be verified to be sure the Opus decoder operates properly. Is there any test files created specifically to exercise all aspects of the encoder? If not, can you reco...

...cation set to voip instead of restricted-lowdelay and a lower bitrate (e.g., 24000 instead of 96000). Even though this primarily affects the encoder, as a sanity check, it's always good to make sure the test vectors still decode correctly. Get them from <http://opus-codec.org/testvectors/opus_testvectors.tar.gz> and use tests/run_vectors.sh <build path> <test vectors path> 48000

...means that the two changes that were previously behind a --enable-update-draft option are now enabled by default in git. If needed (not sure why), they can still be disabled using --disable-rfc8251 The changes require a new set of testvectors, which are available at https://www.opus-codec.org/docs/opus_testvectors-rfc8251.tar.gz You can expect a 1.3-beta release in the near future, with a final 1.3 hopefully before the end of the year. Cheers, Jean-Marc

...cument/d/1L6csATjSsXtzg_sa1iHZta8hOsoVWA4UjHXEakpTrNk/edit?usp=sharing > > > > > > > Even though this primarily affects the encoder, as a sanity check, it's always good to make sure the test vectors still decode correctly. Get them from <http://opus-codec.org/testvectors/opus_testvectors.tar.gz> and use > > tests/run_vectors.sh <build path> <test vectors path> 48000 OK, this took about 2 hours.. but all tests passed successfully. Please let me know what the next steps are.

...4UjHXEakpTrNk/edit?usp=sharing >>> >>> >>> >>> > >>> > Even though this primarily affects the encoder, as a sanity check, it's always good to make sure the test vectors still decode correctly. Get them from <http://opus-codec.org/testvectors/opus_testvectors.tar.gz> and use >>> > tests/run_vectors.sh <build path> <test vectors path> 48000 >> >> OK, this took about 2 hours.. but all tests passed successfully. >> Please let me know what the next steps are. > > Is there plans to support ARMv8/aarch64 NEO...

Hello, I received feedback from engineers working on NE10 [1] that it would be better to use NE10 [1] for FFT optimizations for opus use cases. However, these FFT patches are currently in review and haven't been integrated into NE10 yet. While the FFT functions in NE10 are getting baked, I wanted to optimize the celt_pitch_xcorr (floating point only) and use it to introduce ARM NEON