similar to: recommended opus bitrate / opusenc setting for general?

Everything above 96kbps on that table is speculative, as the highest multi-participant listening testing done was at 96kbps. Here's the results from that test, if you're curious: http://listening-test.coresv.net/results.htm As you can see, at that rate Opus ranged from slightly perceptible to imperceptible. Also importantly, note how few of the donors were able to give significant

On Sat, 2015-10-24 at 22:16 -0700, Thomas Daede wrote: > Everything above 96kbps on that table is speculative, as the highest > multi-participant listening testing done was at 96kbps. Here's the > results from that test, if you're curious: > > http://listening-test.coresv.net/results.htm > > As you can see, at that rate Opus ranged from slightly perceptible to >

Well, with stored music files, with close to transparency bitrate, you don't really need Opus. Now compare it with Vorbis when streaming on a low bandwidth connection with real-time latency... 2015-10-25 2:01 GMT-02:00 Christoph Anton Mitterer <calestyo at scientia.net>: > Hey. > > I just wondered,... which is the recommended bitrate and further > settings of opusenc (like

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

This patch to opus-tools adds optional support to WavPack lossless format as input to opusenc. Like support to FLAC, it depends on an external library, libwavpack, and may be disabled on configure. Lucas Clemente Vella (1): Reading input from WavPack files. Makefile.am | 7 +- configure.ac | 37 ++++++++ src/audio-in.c | 71 ++++++++------- src/opusenc.c | 19 +++- src/opusenc.h

Christoph Anton Mitterer <calestyo at scientia.net> wrote: > So basically, with 100 kB/s or say 128 kB/s one should be more or less > safe and very close to transparency, right?! Yes, assuming you mean kb/s (kilobits, not kilobytes, per second), and no more than 2 channels (stereo). > > Are there any bitrates recommended (e.g. for quality or performance > reasons)? E.g. that

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

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

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

This patch adds a new option "channel-mapping" to opusenc which sets the channel mapping family used by the multistream encoder. Please let me know whether adding this option is worthwhile and whether the help string is okay. I tried to keep it short but accurate. The error message for an unimplemented channel mapping is "Error cannot create encoder: request not implemented".

You asked in the Vorbis list, but your text only mentions OGG. The codec commonly used in OGG containers that is limited to 48 khz is Opus. Maybe you are trying to use the wrong codec (i.e. Opus instead of Vorbis)? Using a 44.1 khz wav file, I was able to encode a 192 khz ogg-vorbis file with the following command: $ oggenc --resample 192000 input.wav Of course, if your original material is

I am interested in being able to encode a single Opus stream using several CPU cores. I get a raw audio input and "opusenc" can transcode it at 1200% speed (Raspberry PI 3B+). It saturates a single CPU core, but the other three are idle. Is out there any project to add multithreading options to "opusenc", or something in that line? Looking around, I have found this:

Hi guys, as MP3 and Opus have very similar objectives, I think the original poster's question was a valid one: Why does Opus have more artefacts in the lower frequency ranges than MP3 has? The spontaneous suspect that lower frequency artefacts may be more noticeably than higher frequency artefacts seems plausible, also. Is it a matter of energy (which is higher for higher frequencies)? When

user {''username'': uid => 501, gid => ''staff'', comment => ''comment'', ensure => present, home => ''/Users/sysop'', shell =>

When experimenting with Opus encoder, I took a random FLAC file, encoded it, heard it, and heard the original file. When hearing the opus encoded file, I thought it was a flute solo, but when I heard the original, I nearly fell off my chain when I noticed the piano I couldn't hear from the Opus in the first time. Now I know there is a piano, I can hear it in the Opus file, but it is much

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

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,