search for: run_vectors

If opus_compare doesn't exist or isn't executable, tests failed normally which could be misleading. So test for existence and mode to avoid this ambiguity. --- tests/run_vectors.sh | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/tests/run_vectors.sh b/tests/run_vectors.sh index 1cc445d..116a743 100755 --- a/tests/run_vectors.sh +++ b/tests/run_vectors.sh @@ -57,6 +57,11 @@ else exit 0 fi +if [ ! -x $OPUS_COMPARE ]; then + echo ERROR: Compare program...

...failed normally which could be misleading. So test for existence and mode to avoid this ambiguity. -- Aur?lien Zanelli Parrot SA 174, quai de Jemmapes 75010 Paris France -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Check-if-opus_compare-is-executable-in-run_vectors.s.patch Type: text/x-patch Size: 0 bytes Desc: not available Url : http://lists.xiph.org/pipermail/opus/attachments/20130527/3177ffc6/attachment.bin

This patch lets you pass paths for opus_demo and opus_compare to the run_vectors.sh script. The motivation for this was for my aarch64 patches (forthcoming), which I've been testing under qemu. I want to run an emulated opus_demo, but a native opus_compare, so the script completes in a reasonable amount of time. --- tests/run_vectors.sh | 4 ++-- 1 file changed, 2 inser...

...data.c ./celt/tests/test_unit_dft.c ./celt/tests/test_unit_mathops.c ./celt/tests/test_unit_entropy.c ./celt/tests/test_unit_types.c ./celt/tests/test_unit_rotation.c ./celt/tests/test_unit_laplace.c ./celt/tests/test_unit_mdct.c ./celt/tests/test_unit_cwrs32.c ./autogen.sh ./win32/config.h ./tests/run_vectors.sh ./doc/build_draft.sh ./doc/build_oggdraft.sh Thanks! -- Sergey Ulanov

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

...gt; >> >> >> > >> > 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 is there plans to make the NEON optimisations on ARMv...

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

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

...;>> >>> > >>> > 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 is there plans to make...

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

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