similar to: Royalty-free codecs at the IETF

Hello, I would like to point everyone's attention to a proposal to create a new IETF working group dedicated to standardising unencumbered audio codecs. There will be a BoF at the next IETF meeting (26-31 July) in Stockholm to discuss that. I encourage those interested in taking part in the mailing list discussion ( https://www.ietf.org/mailman/listinfo/codec ) and/or attending the BoF in

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, 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

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, Where can I get a royalty-free copy of the spinner.gif or some other AJAX activity icon? I don''t want to swipe one without asking. Thanks, Jason

Hi! Sorry for being somewhat offtopic but I'm hoping someone can help me. I need to download some music I can use in a one-time non-commercial multimedia presentation (technically speaking I'll be demo-ing ogg123 :-)). I don't care what it is, only it musn't suck and be somewhat suitable for general audience. RMS's speeches simply don't cut :-) So far all music I found on

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

I thought people on this list might be interested in the Xen Developer Summit in Edinburgh in October (alongside LinuxCon EU and a bunch of other confs). Lars tells me that they are going to be advertising more widely next week so if you are interested now would be a good time to sign up. Ian. -------- Forwarded Message -------- Dear Community member, the schedule for the Xen Project

On 5/31/07, Alfred E. Heggestad <aeh@db.org> wrote: > Could you let me know where to insert this statement in the xml > document? I'm no expert, but I recommend adding it in the Full Copyright Statement section. More or less like this: Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as

We (the NLUUG) are organising a conference in Amsterdam this September. During this SANE conference we have reserved an evening for a Free Software Bazaar. We invite many people to participate in this gathering of Free and Open Source software groups. The name "Bazaar" obviously originates from Eric Raymond's article: A place where software developers gather. A unique opportunity

On Sat, Oct 17, 2009 at 9:47 PM, Conrad Parker <conrad at metadecks.org> wrote: > Are you aware of the discussions about a codec working group, and will > you be coming to the next IETF meeting (Hiroshima, Nov 8-13)? No, I wasn't, and no, I won't be attending. > http://tools.ietf.org/html/draft-valin-codec-guidelines-00 I've had a look at that. One thing that jumped

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:

Hmm, I know what you mean. I've actually taken these sentences out of Monty's specifications. The first one refers to the page size of max. ~64 kByte and the second one to the logical subdivision of packets into segments of 255 Byte size. I'm not sure how to rephrase that properly though. Maybe it's good as it stands: that it is recommended to have 4-8 kByte size, but expected more

Hmm, I know what you mean. I've actually taken these sentences out of Monty's specifications. The first one refers to the page size of max. ~64 kByte and the second one to the logical subdivision of packets into segments of 255 Byte size. I'm not sure how to rephrase that properly though. Maybe it's good as it stands: that it is recommended to have 4-8 kByte size, but expected more

I have a data frame named "database" with panel data, a little piece of which looks like this: Symbol Name Trial Factor1 Factor2 External 1 548140 A 1 -3.87 -0.32 0.01 2 547400 B 1 12.11 -0.68 0.40 3 547173 C 1

Hi, [Apologies to all you US-types for the spam!] The deadline for BoF proposal has now been set as two weeks from now: Thursday 22nd March 2012, 12:00 BST. We currently have no BoF proposals, so please do send some in! J We also have space for lightning talks, and will run a lightning talk session if there is enough interest. Please send lightning talk proposals to the same address