search for: testvector

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 samples are not identical in my decoded file and in the reference...

Greetings! I have a 127 long vector with all different character entries. I need to generate another vector that is 6 times a long and the second one and has the following structure: NA "foo" "a unique string" NA "bar" "blah" NA "foo" "another unique string" NA "bar" "blah" ..... This has to be repeated 127

Hello, I have a data.frame > names(popA) [1] "Year" "Series" "Age" "WM" "WF" "HM" "HF" "BM" [9] "BF" "IM" "IF" "AM" "AF" "Yr" how do i loop over a subset of variables in this frame to create a vector of

Hello to All Members of this Group, Can I get the Test Vectors in .wav format for different sampling rates in order to Test the Ogg Vorbis Encoder Code ? If possible Forward the Link where I can get effective testvectors to Test the Encoder. Please Reply As soon as possible . Thanks & Regards , Maulik Desai Embedded Engineer - Embedded Division eInfochips Ltd. Work: +91-79-26563705 x 201 Cell: +91-9898-204291 Email: maulik.desai@einfochips.com <mailto:maulik.desai@einfochips.com> ----...

...worse when i use FIXED_POINT define. I also tried to avoid saturation changing the following line in arch.h: #define SCALEOUT(a) ((a)*(1/CELT_SIG_SCALE)) to #define SCALEOUT(a) ((a)*(1/(2*CELT_SIG_SCALE))) The result audio doesn't saturate anymore but it's still completely broken. My testvector is: freq: 44100 channels: 1 I chose: frame_size = 256 and bytes_per_packet = 46. Does anybody else have this problem? ?Can someone help me finding the problem? Regards Riccardo Riccardo Micci Senior DSP Engineer, Wireless Group Cambridge Consultants Science Park, Milton Road Cambridge, CB4 0...

...] [1]: https://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

Hi, I checked the ODG (Objective Difference Grade) scores for a few reference vectors using the PQEvalAudio Tool and found that some of them show ODG scores as high as -3.5 If we look at the range as described in the link below, it looks unacceptable. http://www-mmsp.ece.mcgill.ca/documents/Software/Packages/AFsp/PQevalAudio.html Am I missing something or are these scores valid? Thanks and

.../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. Is there plans to support ARMv8/aarch64 NEON intrin...

Hi, I am looking at the conformance test using opus_compare and the test vectors and I am a bit confused about FEC. Is there a way to validate that a decoder processes LBRR frames correctly? Thanks, Alexis

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

...th the application 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

Dear all, is the program opus_compare capable of comparing each decoder output or is it only capable of comparing the decoded testvectors? Or in other words: Can I use the opus_compare for comparing the decoder output when I have encoded and decoded arbitrary speech files? With best regards, Martin -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20150...

...been approved by the IETF: https://tools.ietf.org/html/rfc8251 This 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

...oogle.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 OK, this took about 2 hours.. but all tests passed successfully. Please let me know what the next steps are.

...HZta8hOsoVWA4UjHXEakpTrNk/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...

...ED_POINT define. I > also tried to avoid saturation changing the following line in arch.h: > #define SCALEOUT(a) ((a)*(1/CELT_SIG_SCALE)) to #define SCALEOUT(a) > ((a)*(1/(2*CELT_SIG_SCALE))) > The result audio doesn't saturate anymore but it's still completely broke= n. > My testvector is: > freq: 44100 > channels: 1 > I chose: frame_size =3D 256 and bytes_per_packet =3D 46. > > Does anybody else have this problem? ?Can someone help me finding the > problem? > > Regards > Riccardo > --------------------------------------------------------------------...

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