similar to: Required help regarding Opus audio codec's build & run

Hi, I have downloaded the latest stable version *1.0.2 opus audio codec* from the following link: http://www.opus-codec.org/downloads/ *Details of OS & CPU:* OS : Microsoft Windows XP CPU : intel core 2 Duo cpu I am using Microsoft visual C++ 2010 Express to build the codec (opus.vcxproj available in the package downloaded). I am able to build it & could generate the application

Hi, I have downloaded the latest stable version *1.0.2 opus audio codec* from the following link: http://www.opus-codec.org/downloads/ *Details of OS & CPU:* OS : Microsoft Windows XP CPU : intel core 2 Duo cpu I am using Microsoft visual C++ 2010 Express to build the codec (opus.vcxproj available in the package downloaded). I am able to build it & could generate the application

Hi, I have downloaded the latest stable version *1.0.2 opus audio codec* link: http://www.opus-codec.org/downloads/ *Details of OS & CPU:* OS : Microsoft Windows XP CPU : intel core 2 Duo cpu I am using Microsoft visual C++ 2010 Express to build the codec (opus.vcxproj available in the package downloaded). I am able to build it. With the executable opus_demo.exe , I tried to encode

-- Joshua Bowman Silverback Networks (559) 305-3770 silverbacknet at gmail.com www.silverbacknetworks.net -------------- next part -------------- src/analysis.c | 6 +++--- src/mlp.c | 3 +++ src/opus.vcxproj | 5 +++++ src/opus.vcxproj.filters | 15 +++++++++++++++ src/opus_demo.vcxproj | 4 ++++ src/opus_demo.vcxproj.filters |

Hi, I am interested in this part of the answer: "Make sure both are also linked to the same libopus (opusenc could be using the system libopus 1.0.x while opus_demo is from git)" I dowloaded a tarball distrib of libopus (1.1-beta),build and installed it,and afterwards did the same with opus-tools (0.1.7),using the former installed libopus library (also using libogg 1.3.1). When I execute

I suspect the main difference is due to time alignment of the samples and the exact trimming at the beginning and at the end of the encoded files. I also note that there's a missing "--" in front of "bitrate" and only one "-" instead of two for cvbr in your opusenc command line. Make sure both are also linked to the same libopus (opusenc could be using the system

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

--- src/opus_demo.c | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/src/opus_demo.c b/src/opus_demo.c index 72506b5..5a75679 100644 --- a/src/opus_demo.c +++ b/src/opus_demo.c @@ -245,14 +245,14 @@ int main(int argc, char *argv[]) double bits=0.0, bits_max=0.0, bits_act=0.0, bits2=0.0, nrg; double tot_samples=0; opus_uint64 tot_in, tot_out; - int

Hi, I have found differences in quality between opus_demo and opusenc/opusdec. I used for both applications the same raw pcm file,16 bit,48khz,litle endian. i use libopus 1.1-beta and opus-tools-0.1.7. The command for opus_demo is: opus_demo audio 48000 1 64000 -cvbr -framesize 10 in.pcm out.pcm For opusenc/dec: opusenc --raw --raw-chan 1 bitrate 64 -cvbr --framesize 10 in.pcm in.opus

Dear Christian van Bijleveld, You can use any of the below DSPs of Texas Instruments 1. TMS320C674x - This supports floating point implementation of opus 2. TMS320C66x - This supports both floating and fixed point implementations 3. TMS320C64x - This supports only fixed point implementation Regards, Mahantesh On Mon, May 13, 2013 at 10:12 PM, <opus-request at xiph.org> wrote: >

Hi Sakharam, I see 2 potential issues with what you are doing. 1. ./opus_demo -e voip 48000 2 16 music_orig.wav testcase30.opus in above command, "16" for bits/sec seems too low. I'm no audio expert, but just cant convince myself you can get any reasonable audio data with 16 bits/sec. FYI, I was able to encode and decode with 16 bits/sec, but when I played the decode file with

I didn't expect this, is it normal? When you use inbandfec, and have packet losses, you end up with more audio samples than you started with. With short frame (2.5), the FEC isn't supposed to do anything but it shouldn't do that should it? and 20mS frame, should do 'something' but? add audio? I'm using opus_demo for this. Here's the steps (I have my test audio in

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 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 I used opus_demo to clarify how opus works, I try this command: opus_demo -e" audio 8000 1 8000 -cbr /somedirectory/pcm_mono_ochomil.raw /somedirectory/test.opus And I get the file test.opus, then comes the first problem, this file hasn't header so i can't reproduce it using an external tool, how can i add a header to this file Then when i trie to run opus_demo -d 8000 1

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

Still can't reproduce. What OS and compiler version? Jean-Marc On 21/04/15 02:48 AM, Suresh Thiriveedi wrote: > Hi, > > There is no change in the compiler flags. I'm using as it is from the > original code. No change in the Makefile and I believe it is using the > floating point only by default. > > We are using 8k samples and mono so the commands is as follows.

Hi Looks like 1.1 version is sensitive to the system architecture/compiler/kernel version. Below is my observation in various linux system I have. As you mentioned, you are not observed the crash in your system, can you please share your system details. And also please comment on the below table/observations. *Machine IP* *optimization flags* *RHEL version* *kernel version* *gcc version*

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

I just tried decoding with v1.1: ./opus_demo -d 48000 2 opus_encoded_crash.opus out.pcm and I see no issue (including with valgrind). Does the same command-line create problems for you? What compile flags did you use? fixed-point or float, any assembly, ...? Could be assembly here, or even a compiler bug wouldn't be unheard of. Cheers, Jean-Marc On 20/04/15 07:27 AM, Suresh Thiriveedi