opus - Sep 2013 - opus and chrome

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 calls directly. Maybe that's shadowing the problem
for the other tools. opusrtp doesn't need math directly, but as you see,
libopus.a does.

However, the autotools build does use whatever link line pkg-config
tells it to, and we should be including -lm there.

Bat, can you post your configure invocation command line, the output of
'pkgconfig --libs opus' and pastebin your config.log somewhere, please?

The failed line with 'make V=1' is also helpful in debugging.

 -r

hello all -

sorry for such a basic newbie question, but is opus now fully supported using
the latest google-chrome?

according to this link:

http://news.cnet.com/8301-1023_3-57577464-93/google-hitches-opus-audio-technology-to-webrtc-star/


"Chrome 27, making its way through the development pipeline, is helping to
advance the fortunes of a?new audio compression technology called Opus."



supposedly all chrome users need to do is to go here:

chrome://flags/#enable-opus-playback

and enable opus


however, according to this link: ?http://caniuse.com/opus??opus is not supported
yet. ? does anybody know ?


note that opus is not working (for me anyways) yet using this page:
http://xiph.org/~giles/2012/opus/


Thank you,
Mark Edwards
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.xiph.org/pipermail/opus/attachments/20130924/1be7216b/attachment.htm

>
> Bat, can you post your configure invocation command line, the output of
> 'pkgconfig --libs opus' and pastebin your config.log somewhere,
please?
>
> The failed line with 'make V=1' is also helpful in debugging.
>
> -r
>
Hi
This is the config line used for both 0.1.6 and 0.1.7 test builds:-
./configure --disable-dependency-tracking

And 'pkg-config --libs opus' (There is a hyphen, lol)
$ pkg-config --libs opus
-L/usr/local/lib -lopus  

And config.log is here ---> http://pastebin.com/raw.php?i=FxnX7Fvu

The whole output from 'make V=1' is here --->
http://pastebin.com/raw.php?i=eBytk16a

Mark Edwards wrote:
> supposedly all chrome users need to do is to go here:
>
> chrome://flags/#enable-opus-playback
>
> and enable opus
>
>
> however, according to this link: http://caniuse.com/opus  opus is not
> supported yet.   does anybody know ?
I don't think caniuse.com will report features that are still behind 
flags (as most people will not enable the flag).

The issue to follow is 
<http://code.google.com/p/chromium/issues/detail?id=104241>. There are a 
number of open bugs with the feature, and very little publicly-visible 
progress has been made since March. I don't know any more than you do 
about when it will be stable enough to enable by default.

On 2013-09-24 9:16 AM, bat guano wrote:
> This is the config line used for both 0.1.6 and 0.1.7 test builds:-
> ./configure --disable-dependency-tracking
> 
> And 'pkg-config --libs opus' (There is a hyphen, lol)
> $ pkg-config --libs opus
> -L/usr/local/lib -lopus
Alas the problem is still opaque to me. Like Greg said, it's linking to
the static version (without passing --static to pkg-config so it will
add -lm).

Does your peppermint system have a /usr/local/lib/libopus.so? Could you
have configured opus with --disable-shared?

 -r