similar to: Help with OpusEnc

On 2014-02-11 8:27 PM, Ben wrote: > New to list and Opus Codec. Welcome1 > One of the things I've noticed while encoding is that Opus reports a float with an 'x' along with "realtime". This is intended to measure the cpu performance of the encoder. The float is the number of seconds of audio data processed divided by the number of real-time seconds since encoding

On 2014-02-12 12:11 PM, Ralph Giles wrote: > On 2014-02-11 8:27 PM, Ben wrote: > >> New to list and Opus Codec. > > Welcome1 > >> One of the things I've noticed while encoding is that Opus reports a float with an 'x' along with "realtime". > > This is intended to measure the cpu performance of the encoder. The > float is the number of

Hello Tony, opusenc from opus-tools works for me.. Just tried it successfully on my x86_64 Ubuntu Trusty 14.04 box. I was just able to do $ sudo apt-get install opus-tools $ opusenc music_48kbps.wav music_48kbps.opus I remember also being able to compile opus-tools (git://git.xiph.org/opus-tools.git) some time ago. Regards, Vish On 23 February 2015 at 12:30, Tony <yellowjacketlite at

(Moving from offlist discussion.) I''m interested in opinions... Assume there are four single vcpu domains A, B, C, D, running on a 2-CPU physical machine. We wish to test for time skew on domain A. Assuming B, C, and D are all running some workload that attempts to fully saturate the (single) cpu. 1) Should the affect on domain A be essentially the same regardless of what load

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

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

Hello! I encoded a voice file (48kHz) with opusbin\opusenc.exe with the standard settings and decoded it. The output was amazing. I could not hear any loss at all. Then i encoded the same file with opus_demo.exe and standard settings and then decoded it. The output had a sizzling noise, even when I used full bandwidth. I think I have played around with any of the settings in opus_demo.exe,

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

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

The opusenc tool automatically adds metadata - even if you don't specify any. For example, these tags are created by default on my files: ENCODER=opusenc from opus-tools 0.2 ENCODER_OPTIONS=--bitrate 6 --comp 10 --framesize 60 --padding 0 I've tried using `--discard-comments` but that has no effect. I've tried using `--comment ENCODER=` but that adds a duplicate tag. My limited

>>> Terence Eden <terence.eden at gmail.com> schrieb am 19.04.2020 um 12:48 in Nachricht <12670_1592540909_5EEC3EEC_12670_238_1_CABV2FHjaGEd4u4r7BfHaAyj=P1wP_8z7u7pWuMHy hV6XqSXVA at mail.gmail.com>: > The opusenc tool automatically adds metadata - even if you don't specify > any. > For example, these tags are created by default on my files: > ENCODER=opusenc

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

Hi, I've put some work in a small GUI that makes transcoding files from .wav to .opus more comfortable and faster. It's a small C#-Windows-Application and is described and available for download at [1]. At the moment it's still more in an alpha state, there might be some bugs. So for example one problem is, that I can't shut down the opusenc.exe, if I want to quit the GUI.

On Sun, Dec 15, 2013 at 9:42 PM, Carsten Mattner <carstenmattner at gmail.com> wrote: > 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

Hi, I've been using the command line opusenc/opusdec tools for a while now to encode/decode files. The next version of OS X changes a few things, so I was looking to recompile these tools using a version of the OS X SDK > 10.7 (needed for apple's "hardened runtime") but had no luck. How can I compile a static version of opus tools on OS X that doesn't depend on any other

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

On 15 November 2013 18:27, John Buckman <john at magnatune.com> wrote: (sigh, once more I accidentally replied off-list...) > 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? >

Le 19-12-18 à 12 h 29, Marc Lavallée a écrit : > Hi Andrew, > > I suspect that the configure option should be enable-ambisonics > (instead of enable_ambisonics), but for each of opus, libopusenc, > opusfile and opus-tools git repos (on master branch), when I try > "./configure --enable-ambisonics", I get this error message: > > configure: WARNING: unrecognized

Hello All, This is my first appearance to the opus mailing list. My name is Michael Mehari and i am a researcher at Ghent University mainly on cognitive radio networking. Recently i am working on a demo scenario on self adjustable wireless audio conferencing and i selected opus for the audio encoding and decoding part. specifically the applications (i.e opusenc and opusdec) from opus-tools