similar to: opusenc -- no track number metadata?

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

This seemed to be the best place to let you guys know.... Magnatune.com's entire catalog is now downloadable in Opus format, with full metadata (small and large cover art) at 128k stereo. A few comments: 1) I'm really impressed by your metadata implementation. It's very cleanly done, and the multiple artwork idea is fantastic. One suggestion: I couldn't find an example in the

> If you pass --genre multiple times, it will actually encode multiple GENRE tags in the file. Not sure how many players will properly handle such a thing, though (my prediction: not many, though I think VLC will concatenate them into a comma-separated list). My mistake, I didn't read the man page carefully enough, which does state this: > Set the genre comment field to genre. This

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

On Sep 20, 2013, at 1:19 PM, Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: >> I wasn't sure what bit rate was appropriate for "Very high quality" >> with opus, i.e. something that was "commonly indistinguishable from a >> WAV file". Any advice on that is appreciated. > > I would tend to recommend using around the same bitrate for Opus as

On Wed, 2014-02-12 at 10:21 -0800, Timothy B. Terriberry wrote: > Alice Wonder wrote: > > I found a solution. If I add the metadata_block_picture to the flac file > > I use as input, opusenc copies it over and at least in totem (linux > > movie player) it displays when playing the Opus file. > > You can also add it to the Opus file directly with the --picture >

John Buckman wrote: > Magnatune.com <http://Magnatune.com>'s entire catalog is now > downloadable in Opus format, with full metadata (small and large cover > art) at 128k stereo. As a long-time fan of Magnatune and what you're trying to do, this is pretty awesome. > 1) I'm really impressed by your metadata implementation. It's very > cleanly done, and the

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

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

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

Hi! Playing with Opus 1.3 I converted a tone sweep with a sample rate of 96kHz (just for fun). Before I had converted that from WAV to FLAC, and to Vorbis without problems. With Opus I noticed that the file size for 48kHz and 48 kbps compared to 96kHz Vorbis at 31kbps is about double the size and it sounds even worse (than Vorbis) (there is a lot of noise in the lower frequencies when a low

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,

Hi! Excuse the delay, but I had to deal with a corrupted NTFS file system that ate many important files on an USB stick... The FLAC version of the original is almost 6MB and it can be downloaded slowly from this time-limited link: https://sbr5vjid0jgmce4q.myfritz.net:40262/nas/filelink.lua?id=0ba5a10529a6fe7b On the meaning of a logarithmic sweep: If you use foobar2000 and the

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,

Unfortunately, ambisonics aren't exposed in opusenc yet, thus the trouble. They're an API-only feature, but it's a good time to discuss what such a command-line interface would look like, notably: how to specify multiple streams & stream order, select the mapping family, coupled channels, and how to specify the matrix (for family 3). Likewise, there's no multistream support at

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

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

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 options: --enable-ambisonics Thanks for your help. Marc Le 19-12-18 à 11 h 52, Andrew

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