similar to: static only builds shared with 1.0.3

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, We just released Opus 1.1-beta and Monty wrote a nice demo showing off all the new features, including many improvements over the alpha release: http://people.xiph.org/~xiphmont/demo/opus/demo3.shtml As usual, the code can be downloaded from: http://opus-codec.org/downloads/ In addition to 1.1-beta, we also released 1.0.3, which includes a

Xiph.Org is pleased to announce that we've released Opus 1.2. The 1.2 release includes: . Speech quality improvements especially in the 12-20 kbit/s range . Improved VBR encoding for hybrid mode . More aggressive use of wider speech bandwidth, including fullband speech starting at 14 kbit/s . Music quality improvements in the 32-48 kb/s range . Generic and SSE CELT optimizations .

Good Morning; Iam asking whether any one have knowledge about is it possiple to incorporate a psycoacoustic model?(specifically?I mean ?MPEG-1 psychoacoustic model 1) into the CELT codec(any version even older versions of the coder,?no matter) Iam using version 0.3.2. Kind Regards; Osama. -------------- next part -------------- An HTML attachment was scrubbed... URL:

I am using mvs 2012 but the .sln provided is of msv 2010 so on opening .sln it tries to update libraries which is successful but I am unable to build (compile) it as it gives series of errors. I am pretty new to these things so can anyone tell me if I am doing anything wrong or how to create(.lib and .dll) files so I can use them in my project. Please forgive me if I have asked something foolish.

> > Are you sure?? No, I'm confused. :-/ With shallow clones:- opus PACKAGE_VERSION="aee4d80" opus-tools PACKAGE_VERSION="7c3f522" Something's gone wrong. opus-tools is broken. configure: error: Package requirements (opus>= 1.0.3) were not met: Requested 'opus>= 1.0.3' but version of Opus is aee4d80

Hi, a first set of results can be downloaded here <http://trac.tools.ietf.org/wg/codec/trac/wiki/TestingResults> http://trac.tools.ietf.org/wg/codec/trac/wiki/TestingResults More will be added soon. Thanks to Patrick Schreiner and Alfons Martin, who did the tests. With best regards, Christian Hoene Symonics GmbH Sand 13 72076 T?bingen Tel +49 7071 5681302

> No comments? Mostly no. There are no presets because the encoder is smart enough to act intelligently by default. The exposed knobs are exposed only for those who know they actually need them. This is pretty much how Xiph encoders have always been. The programming API is a bit different, because there are more use cases for streaming. Monty

Hello! Trying to compile, build, install and run Opus. My config: Ubuntu console (Windows 10 app). First problem, configure says openssl is missing. My system says that i have openssl already. Which openssl does it need? Using aptitude, i've installed everything with openssl name in it. That's tons of files and gigabytes of data. But it worked somehow. Second problem, flac-1.3.2 -

The RSpec Development Team is pleased to announce the release of RSpec-1.0.3. == Changes This is the compatibility release! * Compatible with autotest!!!! (As of ZenTest 3.6.0 - see below) * Compatible with edge rails (as of r6825). * Compatible with jruby (since release 1.0.1) See http://rspec.rubyforge.org/changes.html for more detail. == About RSpec RSpec is a framework which provides

-----BEGIN PGP SIGNED MESSAGE----- [ Sorry for sending this twice; I sent it to the vorbis-dev list by mistake. ] The ALBUM, ARTIST, TITLE, and TRACKNUMBER tags aren't sufficient for classical music. MP3 muffed it, but since Vorbis is so flexible, I'd like to propose that ogg123 recognize and display the following optional tags, instead of giving an error message that it doesn't

-----BEGIN PGP SIGNED MESSAGE----- [ Sorry for sending this twice; I sent it to the vorbis-dev list by mistake. ] The ALBUM, ARTIST, TITLE, and TRACKNUMBER tags aren't sufficient for classical music. MP3 muffed it, but since Vorbis is so flexible, I'd like to propose that ogg123 recognize and display the following optional tags, instead of giving an error message that it doesn't

Hi All, We have some optimizations for x86-64 and SSE enabled CPU since encoding Opus stream on server side is time sensitive. The optimization is based on opus-1.0.3, and after 1.1 is released we have to merge the changes. The question is can we share back the optimizations to Opus repository? If yes, how can I do? Thanks, XM -------------- next part -------------- An HTML attachment was

Hi I think the gits have gone belly up... @xubuntu:~$ git clone git://git.xiph.org/opus.git Cloning into 'opus'... fatal: read error: Connection reset by peer @xubuntu:~$ git clone git at git.xiph.org:/opus.git Cloning into 'opus'... Permission denied (publickey,keyboard-interactive). fatal: The remote end hung up unexpectedly

It does not; Vorbis needs only lap consecutive frames, and the timing was constructed so that the 'timestamp' of a vorbis frame actually points to the middle of the frame data. When you combine a starting frame with the subsequent frame, the data you get back is from the starting timestamp forward. Because Opus needs to preroll a larger amount, that trick wouldn't work with Opus.

hi folks apologies for sending a commercial mail. I am the CEO of http://talk.to - a unified messaging product. We are still in early stages of launch. We intend to build in voip capabilities in our product. Our product is intended to work in browsers and on all mobile platforms. We are looking for someone who can provide us an ARM-Neon optimized version of Opus for use on mobile platforms so

This patch adds a static bitrate allocation for ambisonics encoded with the multistream API. We allocate 4 bits to the mono channel (channel index 0) for every 3 bits allocated to other channels. The allocation is static because it does not depend on the input audio. This patch also forces the underlying encoders to use CELT only for ambisonics. -- Thanks, Michael Graczyk -------------- next

Hi everyone, We finally made it! Opus is now standardized by the IETF as RFC 6716 (http://tools.ietf.org/html/rfc6716). See the announcements at: https://hacks.mozilla.org/2012/09/its-opus-it-rocks-and-now-its-an-audio-codec-standard/ http://www.xiph.org/press/2012/rfc-6716/ Feel free to spread those around :-) We're also releasing both 1.0.0 (same code as the RFC) and 1.0.1, which is a

Hello!, i've just compared the 1.0.3 release with the master branch on a BeagleBone Black (AM335x 1GHz ARM Cortex-A8 with NEON floating-point accelerator) and Arch Linux ARM. At the moment I dont no why, but I see that 1.1 is much slower in encoding. Are there any default changes, that I missed and could explain this? Normaly I suggested a better performance with 1.1 and the ARM

Yes, it's basically an intrinsic aspect of the mathematics. If you seek into the middle of an Opus stream, that's about how long it takes before the audio converges to be correct. On Jan 17, 2014 2:13 PM, "Brendan Bolles" <brendan at fnordware.com> wrote: > On Jan 7, 2014, at 11:11 AM, Brendan Bolles wrote: > > > The closest thing to a standards document for

Hi everyone, We finally made it! Opus is now standardized by the IETF as RFC 6716 (http://tools.ietf.org/html/rfc6716). See the announcements at: https://hacks.mozilla.org/2012/09/its-opus-it-rocks-and-now-its-an-audio-codec-standard/ http://www.xiph.org/press/2012/rfc-6716/ Feel free to spread those around :-) We're also releasing both 1.0.0 (same code as the RFC) and 1.0.1, which is a