similar to: Quality difference between opus_demo.exe and opusenc.exe

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

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

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

Hello! I am running opus_demo.exe with the following cmds: -e audio 48000 1 16 -cbr m:\test\test1.raw m:\test\test1.opus When I open the .opus file with a hex editor, I see only

Hi Jean The problem is that for using this package I need to use all the libs like ogg, even Speex?, no, and also where i can find an easy example like opus_demo.c to create the .opus file Greetings Toni 2013/10/28 Jean-Marc Valin <jmvalin at jmvalin.ca> > Hi Toni, > > The package you want is opus-tools. You can get it from the download > section. For file distribution,

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

--- 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 all! Using the code in opus_demo.c I write a c program for encode and decode the audio from one microphone, I can encode and decode raw audio into .opus file, but really is not an opus file because i need to add the "OpusHead" and the "OpusTags". In order that any opus player can play that file. So I only need in my c program how to add this streams to my file an how to

Hello OPUS, It appears to me that multi-frame packets are not supported by opus_demo.c (e.g. 30ms packest containing 3 10ms frames), can you confirm. However RF6716 does support such packets. Thanks Cliff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20131121/56bab79a/attachment.htm

On 2013-10-21 5:08 AM, Antonio Juan wrote: > 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 opus_demo doesn't support .opus files. It uses a special raw format just for testing. You want opusenc and opusdec from the opus-tools package. -r

Hi all, New to list and Opus Codec. I've been using it on a beagleboneblack with 'arecord'. One of the things I've noticed while encoding is that Opus reports a float with an 'x' along with "realtime". Where can I look up where this calculation is derived? It got me looking and I've noticed that when I record something from a known source (in testing)

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

My file is 3 hours long, so decoding takes around 5 minutes on an average computer. That is a bit too long unfortunately... Am 23.12.2011 20:38, schrieb Steve Checkoway: > On Dec 23, 2011, at 10:54, Hermann Weber<hermie.weber at gmx.de> wrote: > >> And how many frames does Speex need to "recover"? >> Or is that not predictable? > No idea. My guess is not

Are there comparable presets or recommendations for opusenc vbr parameters? lame --preset standard --> opusenc ??? lame --preset extreme --> opusenc ??? I have used opusenc without custom vbr parameters and the files were much smaller than for lame's standard preset but I can't answer if that's comparable or the result was lossier in opus. Hearing tests of course show no

Sorry, it seems I have only replied to Lakhdar, not to the newsgroup. Below is my reply to Lakhdar, and I would like to make it more clear now, using some pseudo values for simplicity: I read bytes 1 to 124 from my encoded spx file. I decode themt and get the values: ---Frame 1---- -293 -8234 2134 17 ---Frame 2---- -9323 -732 189 2329 Both frames are just perfect as I need them. But now when I

The docs for opusenc at https://mf4.xiph.org/jenkins/view/opus/job/opus-tools/ws/man/opusenc.html don't mention any way to specify the track number metadata. Is there an undocumented way to do this, or this feature not available? Or is the "track number" meant to be a "comment" ? More people at Magnatune are downloading our opus files, so this came up... -john

> No comments? Mostly no. There are no presets because the encoder is smart enough to act intelligently by default. The exposed knobs are exposed only for those who know they actually need them. This is pretty much how Xiph encoders have always been. The programming API is a bit different, because there are more use cases for streaming. Monty

I compiled the latest (git master) of opus, libopusenc, opusfile and opus-tools: $ opusenc --version opusenc opus-tools 0.2-8-g4976421 (using libopus 1.3.1-4-gad8fe90d) I tried to encode a 3rd order Ambisonics wav file with the standard Ambix (ACN-SN3D) format; opusinfo is reporting : Streams: 16, Coupled: 0     Channel Mapping Family: 255 Map: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14,