Specifying codecs for the web

Posted Dec 13, 2007 0:40 UTC (Thu) by jamesh (guest, #1159)
In reply to: Specifying codecs for the web by gmaxwell
Parent article: Specifying codecs for the web

I'm not sure where the Microsoft comment came from as MSFT is not a member of WHATWG or the W3C, and they already ship Xiph codecs in various products.

Where are you getting your information? Microsoft is a W3C Member. In fact a Microsoft employee is listed as a co-chair of the HTML Working Group in the charter.

As the vendor of the most widely used web browser, any standard that didn't take their opinion into account would be doomed to slow or no uptake.

to post comments

Specifying codecs for the web

Posted Dec 13, 2007 1:11 UTC (Thu) by gmaxwell (guest, #30048) [Link] (2 responses)

Ah. My error. I asked someone involved with the W3C and I must have misunderstood his answer.

While I made an error in that detail the important message I was trying to convey, that MSFT
has not publicly protested the inclusion of the Ogg codecs as baselines for HTML5 and that the
article was incorrect to claim otherwise, still stands.

Microsoft already ships Ogg container codecs in a number of products and has for a long time.
I think they are too wrapped up with the grim realities of using known patented codecs right
now to worry about Theora.

Ultimately this is an area where the free world and Microsoft have interests in common, and
this time Microsoft might actually realize it, if not quite well enough to actually give their
public support.

Specifying codecs for the web

Posted Dec 13, 2007 4:59 UTC (Thu) by intgr (subscriber, #39733) [Link] (1 responses)

Huh, really? Whatever happened to WMV?

Specifying codecs for the web

Posted Dec 13, 2007 11:33 UTC (Thu) by cortana (subscriber, #24596) [Link]

I have not heard about MS using Theora anywhere; however I believe that DirectPlay uses Vorbis
and Speex for voice communications.