similar to: opus-tool installation guide

hello all - this is probably something simple, but i am on-the-road and cant find a quick solution. ?i cant seem to get the opus toolset to recognize the ogg library. ?i was able to successfully get opus to work with FFMPEG, but not the toolset. when i go to install opus-tools, i get the following message: No package 'ogg' found i would like to have opusenc working, since i have 700k

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'm having a problem compiling opus-tools-0.1.7. Version opus-tools-0.1.6 seems to compile OK. I've tried with opus-1.0.3 and opus-1.1-beta. The errors are like this:- "undefined reference to `sqrtf'" etc. This OS is Peppermint Three, similar to Ubuntu 12.04. It uses:- gcc --version gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 Google says it's maybe something to do

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

Thanks for your help, I will follow that, so in order to sum up I need: - libopus 1.0.3 compiled as static or shared library - libogg 1.3.1 compiled as static or shared library - opus-tools 0.1.7 and then follow the example in opus-tools opusenc.c to get things ready, because if I try to compile opus-tools, this ask for me for the speex library, and other things I think that that will we all.

Hi, Dear alls I had encounted a problem in using opus-tool-0.2-opus-1.3(download from www.opus-codec.org, Win64 binaries: opus-tools-0.2-win64.zip). First, I use opusenc to generate a opus file which input is a 9-channels wav file. The opusenc can work. Then, I use opusdec to transform the generated opus file to wav file, but opusdec can't work. I received the error message: failed to open

Hi, Seems like it's not linking with libm. I suspect it has to do with linking statically with libopus.a (is that intended?). Maybe opus-tools relies on the fact that libopus is linked with libm and doesn't explicitly add it? Greg? Jean-Marc On 09/24/2013 06:09 AM, bat guano wrote: > Hi > I'm having a problem compiling opus-tools-0.1.7. > Version opus-tools-0.1.6 seems to

Which one of the various libraries on xiph.org allow me to create an Opus file? The 3 or so libraries on the Opus download page all seem to be for reading files, converting and/or encode/decode streams. I have device that outputs a stream of Opus 'frames' and I need to save them into an Opus file. -- Tony -------------- next part -------------- An HTML attachment was scrubbed... URL:

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 >

On 2013-09-24 5:46 AM, Jean-Marc Valin wrote: > Seems like it's not linking with libm. I suspect it has to do with > linking statically with libopus.a (is that intended?). Maybe opus-tools > relies on the fact that libopus is linked with libm and doesn't > explicitly add it? Greg? Indeed. The opus-tools build explicitly adds -lm for opusdec and opusenc because they use math

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

On 23/02/15 10:30 AM, Tony wrote: > I __think__ opus-tools' opusenc has code which can be used as a > template/sample for how to create an .Ogg file with Opus content. As > expected, it makes use of libopus and libogg. Sadly that's the best option currently. As you say it's a bit complicated, although oggenc has a lot of extra support for controlling encoder options you

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

opusdec -V opusdec opus-tools f2a2e88 (using libopus unknown) I've got an opus file encoded from a .wav off a cd, 44100Hz: opusinfo 2-24-Overture_in_C_\(In_Memoriam\).opus Processing file "2-24-Overture_in_C_(In_Memoriam).opus"... New logical stream (#1, serial: 38134f1f): type opus Encoded with libopus unknown User comments section follows... ENCODER=opusenc from opus-tools

Hi Some Linux programs are 'static'. For example, these FFmpegs here ---> http://ffmpeg.gusari.org/static/ If we compile with Linux opusdec & opusenc & opusinfo & opusrtp using only static libraries libogg.a & libflac.a & libopus.a Are the four opus-tools programs then genuinely 'static', so that they will work on *any* Linux OS? $ ./opusenc -V opusenc

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

Hi All, First time poster to this group, please ignore my ignorance? I?m trying to use Opus 1.1 on a 400MHz MIPS 24k CPU (AR9331, specifically, like in the Arduino Yun). I?ve successfully built (I think) opus-1.1 and opus-tools-1.8 and they run, but are dog slow. opus-1.1 does have the ?enable-fixed-point option set, as this chip only has soft-float. My short test file (less than one

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