similar to: Royalty-free codecs at the IETF

Hi everyone, I'm pleased to announce version 0.6.0 of CELT, with many quality improvements. This includes better stereo coupling, better handling of transients, and better handling of highly tonal signals. In addition, packet loss robustness has been improved through the optional use of independent (intra) frames. CELT now supports a larger dynamic range, suitable for encoding 24-bit audio

Hi folks, here's a press release (yes, sorry, sorry) regarding what's going on with Xiph at the current IETF meeting. Every time we're asked 'why haven't you standardized any of your codecs through the IETF?' we explain that we've been trying for coming up on ten years. This release is about the latest step. If we (along with the other companies supporting

Hi folks, here's a press release (yes, sorry, sorry) regarding what's going on with Xiph at the current IETF meeting. Every time we're asked 'why haven't you standardized any of your codecs through the IETF?' we explain that we've been trying for coming up on ten years. This release is about the latest step. If we (along with the other companies supporting

Hi everyone, For the past few months, we have been working with the IETF to form a new working group dedicated to standardising truly free audio codecs. Following the BoF (meeting) we had in Stockholm a few months ago, we have addressed several issues and we will be having a second BoF *tomorrow* in Hiroshima. Everyone interesting in the matter can participate virtually and give input. The

Hi everyone, For the past few months, we have been working with the IETF to form a new working group dedicated to standardising truly free audio codecs. Following the BoF (meeting) we had in Stockholm a few months ago, we have addressed several issues and we will be having a second BoF *tomorrow* in Hiroshima. Everyone interesting in the matter can participate virtually and give input. The

Today at 17:40-19:40 Eastern Standard Time (22:40-00:40 UTC) the IETF will be holding a Birds of a Feather session to discuss creating a working group for developing a next generation video codec for Internet use. Remote participation is open to everyone. This would be an effort somewhat similar to what we used to create the Opus audio codec. The IETF provides an open standardization process and

Today at 17:40-19:40 Eastern Standard Time (22:40-00:40 UTC) the IETF will be holding a Birds of a Feather session to discuss creating a working group for developing a next generation video codec for Internet use. Remote participation is open to everyone. This would be an effort somewhat similar to what we used to create the Opus audio codec. The IETF provides an open standardization process and

Today at 17:40-19:40 Eastern Standard Time (22:40-00:40 UTC) the IETF will be holding a Birds of a Feather session to discuss creating a working group for developing a next generation video codec for Internet use. Remote participation is open to everyone. This would be an effort somewhat similar to what we used to create the Opus audio codec. The IETF provides an open standardization process and

Hi everyone, Just to let you know that CELT 0.8.1 is out. It's mostly a bugfix release. The bit-stream is compatible with 0.8.0 with the only exception that CELT no longer supports weird frame sizes that have prime factors above 5. This shouldn't really affect anyone. For those of you unaware of the current effort to standardize an audio codec at the IETF, we have recently created 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 .

Hi everyone, Here's a follow-up on the two BoFs we've had about doing royalty-free codecs at the IETF. Well, the good new is that the proposal is now in IETF last call until January 20th (see below). No final decision has been made, so it's important to get as much support as possible for the Working Group proposal. You can see the ongoing discussion on the mailing list archive:

Hi everyone, Here's a follow-up on the two BoFs we've had about doing royalty-free codecs at the IETF. Well, the good new is that the proposal is now in IETF last call until January 20th (see below). No final decision has been made, so it's important to get as much support as possible for the Working Group proposal. You can see the ongoing discussion on the mailing list archive:

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

Hi, Next week at the developers meeting, I'm chairing a BoF session on improving our performance tracking and benchmarking infrastructure. I'd like to make the most out of the 45 minute slot. Therefore, I'd like to start the discussion a bit earlier here, giving everyone who can't come to the BoF a chance to put in their 2 cents. At the same time, I hope this will also give me a

fast enough, and data transfer costs for video servers are low enough, and video codecs such as RealVideo 10 and VP6 are good enough that online video is practical today. For people who already have DSL, cable modem, or other broadband Internet connections, the biggest barrier to their being able to view any movie Hollywood has ever produced simply by pointing and clicking at some link on the

On Sun, 29 Apr 2001, RJ Atkinson wrote: > At 06:26 27/04/01, Tom Wu wrote: > >For those of you who were following the discussion about the new draft > >and implementation of SRP-based password authentication in OpenSSH, I > >promised to have Stanford issue the IETF an official, explicit, > >statement reiterating the unencumbered royalty-free licensing terms. > >The

2008/5/24 Ivo Emanuel Gon?alves <justivo at gmail.com>: > > I received a comment from the IESG that we should have some sort of > list to describe how Ogg mapping strings translate to codec parameter > strings, so I went ahead and compiled a table with all known Ogg > codecs, and I would like feedback in case I inserted an error > somewhere. > > The draft is located

Hi everyone, I've made several posts recently about CELT being "replaced" by the Opus codec ( http://opus-codec.org/ ) and I thought it was time to give an update on what's going on. As many of you know, I've been involved at the IETF on this new Opus codec, which essentially merge (a modified version of) Skype's SILK codec with CELT. This is more than just two codecs

For those of you who were following the discussion about the new draft and implementation of SRP-based password authentication in OpenSSH, I promised to have Stanford issue the IETF an official, explicit, statement reiterating the unencumbered royalty-free licensing terms. The new statement is now available from the IETF's IPR page. Tom

Hello list, We have recently introduced the codecs (optional) parameter on the Ogg media types for easier identification of encapsulated codecs in conditions were it's not feasable to examine the streams directly. I received a comment from the IESG that we should have some sort of list to describe how Ogg mapping strings translate to codec parameter strings, so I went ahead and compiled a