similar to: Linux opus-tools static builds.

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

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

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

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 using the opus-tools package from the current Debian (it says it is 0.1.2). The output of opusinfo is strange: $ opusinfo demo01.opus Processing file "demo01.opus"... New logical stream (#1, serial: 0000456a): type opus Encoded with libopus 1.0.1-rc3 User comments section follows... ENCODER=opusenc from opus-tools 0.1.5 Opus stream 1: Pre-skip: 356 Playback

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

>On 11/20/2013 03:37 PM, O'Connor, Kevin wrote: >> I have an application I intend to use Opus for that involves creating >> recordings of two-party conversations where each party is saved as a >> separate channel. Audio may be later processed or analyzed on a >> per-party basis so if audio in one channel affects the other channel, it >> could create problems.

Hello, I have problems with encoding FLAC-Files with embedded pictures. Currently i use opus-tools 0.1.7 with libopus 1.1-rc2. After encoding opusinfo shows WARNING: Unknown picture type in METADATA_BLOCK_PICTURE comment 12 (stream 1): 1768776039 WARNING: Invalid mime type length in METADATA_BLOCK_PICTURE comment 12 (stream 1): 1697607790 bytes when 5562 are available When i play the files with

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,

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

On Wed, Sep 25, 2013 at 3:28 PM, bat guano <batguano999 at hotmail.com> wrote: >> >>I think you're missing -lm (the math library) when linking. There are some LIBM related changes in the git history >>so this might have already been solved since 0.1.7 >> > Hi > opus-tools-0.1.7 has compiled OK now with Peppermint Three OS... > with this configure:- >

Le 19-12-18 à 12 h 29, Marc Lavallée a écrit : > 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

Since the opusenc and opusinfo changes were independent I split them up and landed the opusinfo changes (with updated mapping family numbers). - Mark On Thu, Sep 6, 2018 at 4:22 AM, Mark Harris <mark.hsj at gmail.com> wrote: > Hi Drew, > > Sorry for the delay. > > FYI the patch that you attached is not your latest version. This > thread that you replied to is an older

On Wed, Sep 25, 2013 at 3:53 PM, bat guano <batguano999 at hotmail.com> wrote: > > > > > > Google says it's maybe something to do with the "linking process" which > might be caused by the gcc compiler. > > Can something be done with the opus code to overcome this, or shall I > compile on a different/better/newer OS? > > > > > Hello

<div id="contentDescription" style="line-height:1.5;text-align:justify;text-justify:inter-ideograph"> <div>Thanks to your reply.</div><div><br></div><div>So part of the wiki is out of date? Beside Opus-tools, I also concern about the spec, optimization and future work in wiki. Could you tell me about if they are out

On 2019-08-27 8:15 a.m., 陈伟旭 wrote: > I had found a Opus TODO list in > https://wiki.xiph.org/index.php?title=OpusTodo > > The item "Opus-tools" interest me. And here is my question about "Port > opusdec to libopusfile/libopusurl": It looks like this was done a couple of years ago, primarily in commit e9bbfacf0a1bbade70005fa730cc50e838baaa32, and part of the

Hi Marc, In order to use the ambisonics API, if you haven't already, you will need to activate the enable_ambisonics build flag during configuration. Then, when encoding the file, make sure to manually select mapping family 3 since opus does not auto-detect ambisonic files. Let me know if you have any questions! Cheers, Andrew On Tue, Dec 17, 2019 at 7:16 PM Marc Lavallée <marc at

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