similar to: opus_compare

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

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

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 insertions(+), 2

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

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

Thanks for the answer. I'll take a look at this tool and verify my implementation. But I'd like to clarify the moment. If the following is applied for a test vector Reference Float Point Encoder --> Reference Float Point Decoder --> Float Point Output Reference Fixed Point Encoder --> Reference Float Point Decoder --> Fixed Point Output And then, if Float Point Output and

For some reason the attachment did not go through. Re-attaching. From: Mukund Raman Sent: Wednesday, April 01, 2015 6:12 PM To: 'opus at xiph.org' Subject: Opus multi-stream/surround: Audio corruption on decoded content Hello Everyone, I am using the opus 1.1 multistream APIs to encode a 5.1 surround stream on the server, stream it to client, decode it and capture the pcm data. I

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

Hello Everyone, I am using the opus 1.1 multistream APIs to encode a 5.1 surround stream on the server, stream it to client, decode it and capture the pcm data. I noticed that there was severe corruption/attenuation on one of the channels(specifically Back/Rear Right). This would appear to be the last channel in the stream. I am attaching an image of the PCM dumps from the original and the one

Viswanath Puttagunta wrote: > a. Simplest use case to validate this optimization for correctness. > b. Simplest use case to validate this optimization for performance. > > Would prefer something like opusdec that can be executed on command > line. The easiest thing to use is probably opus_demo (opusdec does a bunch of extra things, plus for interactive use we care about both the

On 24 November 2014 at 14:53, Viswanath Puttagunta <viswanath.puttagunta at linaro.org> wrote: > > On 21 November 2014 at 18:06, Timothy B. Terriberry <tterribe at xiph.org> wrote: > > > > Viswanath Puttagunta wrote: > >> > >> a. Simplest use case to validate this optimization for correctness. > >> b. Simplest use case to validate this

On 24 November 2014 at 17:48, Peter Robinson <pbrobinson at gmail.com> wrote: >>> >> a. Simplest use case to validate this optimization for correctness. >>> >> b. Simplest use case to validate this optimization for performance. >>> >> >>> >> Would prefer something like opusdec that can be executed on command >>> >>

Hey Kevin! Once you start dropping under (I think) 32kbps, the codec naturally starts losing stereo separation for the benefit of quality. If you really want perfect stereo at 16kbps CBR (this is horrifically low in my opinion) you might be better off splitting the audio and encoding each part at 8kbps CBR. Or, there may be a magic "enforce 100% stereo" one could pass? (doesn't look

Hi! So here is what I got with different encoder settings; still not sure what the "best" setting is. 6kbps seems to add distortions, so I tried 12kbps. MP3-Original: LAME 3.99r, 120kbps, 44100Hz, Stereo, VBR V5 (22:23, 19.8MB) Opus (--raw-rate 44100 --bitrate 56 --vbr --comp 5): (44:45?, 23.4MB): Broken Opus (--bitrate 56 --vbr --comp 5 --ignorelength - %d): (22:23, 12.1 MB, 74kbps)

Hi Drew, I've had some time to dig more deeply into your patch. Here's some more in-depth comments: 1) I note that your OpusMSEncoder struct in private.h adds a subframe_mem[] that's not in opus_multistream_encoder.c. I assume it's due to a merge problem (that field was removed some time ago), but can you confirm/fix the issue? 2) I noticed your patch adds many OPUS_EXPORT

Hello, I've been using Opus on an STM32 M4 platform for speech coding in mono mode. I thought I'd try stereo for grins to see if I can handle the CPU load, and I'm getting a return code of -1 from opus_decode_float (using CBR and 40ms frames). I decided to try the opusenc and opusdec tools to just see how the command line apps would behave. I am getting decoded audio, but I am

On 21 November 2014 at 18:06, Timothy B. Terriberry <tterribe at xiph.org> wrote: > > Viswanath Puttagunta wrote: >> >> a. Simplest use case to validate this optimization for correctness. >> b. Simplest use case to validate this optimization for performance. >> >> Would prefer something like opusdec that can be executed on command >> line. > >

Hi Drew, We're getting there... Some minor comments: 1) The public header file should not have an #ifdef ENABLE_EXPERIMENTAL_AMBISONICS since that would require the user code to define it. 2) Why do you have #define MAPPING_MATRIX_C ? 3) Looks like MAPPING_MATRIX_MAX_SIZE is not longer useful, right? 4) Even though it's not strictly necessary here, please add parentheses to the

Hi, Just to let everyone know that RFC 8251, aka "Updates to the Opus Audio Codec" has 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

Yes, yes, I can reproduce it now, but only on platforms that define a 16-bit int by default (SA_Q15 is an opus_int rather than opus_int32). What system are you compiling this for? On Tue, Nov 21, 2017 at 8:34 PM, Chandrakala Madhira < chandrakala.madhira at soctronics.com> wrote: > Hi Logan, > > Please find attached the input stream we are using testing. > > Thank you, >