similar to: opus_encode_native return 3 with setup_resample

Hi Is it possible to cross-compile opus-tools with mingw and Ubuntu? So far I have done this:- # prepare $ mkdir $HOME/source $ mkdir $HOME/builds $ export PATH="$PATH:$HOME/mingw-w64-i686/bin" $ PKG_CONFIG_PATH="$HOME/builds/lib/pkgconfig" # Install ogg $ cd $HOME/source $ svn co http://svn.xiph.org/trunk/ogg $ cd ogg $ ./autogen.sh && ./configure

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

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

This is the config line used:- PKG_CONFIG_PATH=3D"$HOME/builds/lib/pkgconfig" LDFLAGS=3D"-L$HOME/builds/li= b" CFLAGS=3D"-I$HOME/builds/include" ./configure --prefix=3D$HOME/builds --= host=3Di686-w64-mingw32 --disable-stack-protector @xubuntu:~/builds/bin$ wine ./opusenc -V opusenc opus-tools 0.1.5 (using libopus 1.0.1) Copyright (C) 2008-2012 Xiph.Org Foundation

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

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

hi,All, I want to know whether Opus has AEC features like Speex? Thanks 2012/10/17 <opus-request at xiph.org> > Send opus mailing list submissions to > opus at xiph.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.xiph.org/mailman/listinfo/opus > or, via email, send a message with subject or body 'help' to

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

Hi! I haven't looked into the code yet, but the patch uses different coding conventions like "if(" and "if ("; like wise "){" and ") {". My personal taste is to have spaces after keywords, but that's just me. I'd prefer a consistent coding style. Regards, Ulrich >>> Michael Graczyk <mgraczyk at google.com> schrieb am 26.04.2016

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 think I might have kind of, sort of found a bug in opusenc. But do correct me if I am worng. :) When converting an FLAC file that contains RG tags written by bs1770gain the resulting opus file has a way, way too high RG value. I am talking >90dB(!). Here is the metaflac output of the flac file: % metaflac --block-number=2 --list bs.1770/test.flac METADATA block #2 type: 4

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

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

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

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

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 Wed, 2014-02-12 at 14:29 +0000, Ian Malone wrote: > On 12 February 2014 13:02, Alice Wonder <alicewonder at shastaherps.org> wrote: > > Hello, > > > > I am new to using opus but so far I really am loving it. At 16kbps > > spoken content sounds fabulous. > > > > I am using opusenc on 64-bit linux - mostly with flac input. > > > > The one

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi to everybody. First of all I hope this is the right place to discuss such an (nitpicky) issue. I've just been testing the current Opus release and for mere curiosity compared its performance to WMAPro with CD quality music at low bitrates (48 kbit/s). While Opus generally does a very good job, I found one particular example (a high pitched