decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
IETF standardizes the Opus audio codec as RFC 6716 | 142 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Microsoft & Opus
Authored by: Gringo_ on Wednesday, September 12 2012 @ 09:56 AM EDT

Actually, with the purchase of Skype, Microsoft inherited Skype's development effort on the Silk codec, which Skype had open-sourced and taken to the IETF for standardization. That very same codec was taken up to become a part of Opus, which is based on two codecs, Silk for narrow-band (speech) and CELT for broadband (music).

So now Microsoft can be classified a major contributor to Opus. Does this make Microsoft more likely to adopt Opus broadly? It think it just might!

[ Reply to This | Parent | # ]

IETF standardizes the Opus audio codec as RFC 6716
Authored by: Anonymous on Wednesday, September 12 2012 @ 03:30 PM EDT
Looking at the technical details Opus might be attractive for
mobile devices because of its low latency and good midrange
performance. At extreme low bitrates its performance is worse
than existing codecs, and at high sample rates it is no better.
Add to this some evil will be waiting to test in the law courts
whether it infringes some alleged Intellectual Froppery.

Opus' fate predicted: http://xkcd.com/927/

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )