Hi everyone, I'm pleased to announce that the IETF has just approved for Opus to become a standard. I'll still take a few more weeks of editing before it's published as an RFC, at which point we'll release version 1.0. From now on, we'll be replacing the use of the CELT name with Opus and I'd like to encourage everyone to switch to Opus in their applications. Note that Opus can do everything that CELT could, so this should not be causing major problems beyond updating to the new API (mostly a matter of changing the celt_ prefix to opus_). Cheers, Jean-Marc
Jean-Marc, Congratulations again for this great success! Will there be a development list site where we can ask technical questions? Or should we continue to use this (CELT) list? Thanks again for the great work! MikeH -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20120731/0f2aefbf/attachment-0002.htm
Hi Mike, On 07/31/2012 04:40 AM, Mike Hooper wrote:> Will there be a development list site where we can ask technical > questions? Or should we continue to use this (CELT) list?Actually, we're planning on simply renaming this list. From the information we have now, the RFC (and thus the 1.0 release) should be out in around 2-4 weeks. Let us know if there's anything else that's missing from the opus-codec.org site. Cheers, Jean-Marc