similar to: OS X opusenc/opusdec?

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

1. For starters, 32 bit support is deprecated in the next version of Mac OS X. Other things like Hardened Runtime ( https://lapcatsoftware.com/articles/hardened-runtime-sandboxing.html) may not be relevant, but to make things compatible, apps need to be compiled with an SDK > 10.7. The 64 bit is the big thing. 2 & 3. I want static and can't figure out how to get it to compile. Why

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

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

On Aug 07 08:30:31, hans at stare.cz wrote: > On Aug 07 00:41:52, petrparizek2000 at yahoo.com wrote: > > ????#1. To test encoding at low bitrates, I encoded a sine sweep at 12 kbps > > with Opusenc and then decoded the resulting file with Opusdec. > 1) Opusenc --bitrate 12 --downmix-mono Sweep50.wav Sweep50.opus Why are you using a stereo file containing the same sweep in both

Hi I am an Audacity (http://audacity.sourceforge.net/) developer and I'd like to see Audacity reading and writing Opus files as easily as it does others. What would you recommend as a way forward for this? I am thinking that (Win) we should ship opusenc.exe and opusdec.exe and send command line stuff to them; that way we wouldn't need to dip into your code and as you update we would

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

Hello, I understand it would be better to post several messages with separate topics but I hope I don't cause too much mess if I put it all in a single message this time. To be clear, recently I've been testing Opus Tools under Windows and these are my questions/observations. ????#1. To test encoding at low bitrates, I encoded a sine sweep at 12 kbps with Opusenc and then decoded

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

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

On Aug 07 00:41:52, petrparizek2000 at yahoo.com wrote: > ????#1. To test encoding at low bitrates, I encoded a sine sweep at 12 kbps > with Opusenc and then decoded the resulting file with Opusdec. What sine sweep exactly? How did you obtain it, and how exactly did you encode and decode it? Jan > The strange > thing was that even though the output wave file was at 48 kHz, it

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

On Aug 07 10:08:43, petrparizek2000 at yahoo.com wrote: > > What sine sweep exactly? > > An exponential sweep. It started slightly below 24 Hz and ended almost at 24 > kHz. And it was 50 seconds long. > > > How did you obtain it, > > I used Angelo Farina's "Aurora" modules. One of them is called "Generate > sine sweep". Can you please

Dear authors of Opus, currently, the manpages that come with opus-tools are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on the

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

hello all - since i am such a newbie, i thought i would be the ideal person to put together a guide on how i got the opus tools working. ?i am using virtualbox and a new centOS-linux virtual-machine. i chose to use the minimalist centOS iso file so there would be no pre-installed packages. any suggestions or improvements to this guide would be most appreciated. ?? also, wish to express my

using iTunes i've noticed that AAC is very good at re-encoding own lossy sound. let's test Opus! neroaacenc.exe -q 0.75 -if 000.wav -of 001.m4a neroaacdec.exe -if 001.m4a -of aac001.wav wavdiff.exe 000.wav aac001.wav Comparing 000.wav - aac001.wav... Max diff: -17.3867dB RMS diff: -33.0851dB Mean diff: -32.4582dB opusenc.exe --bitrate 512 "000.wav" 001.opus opusdec.exe 001.opus