Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Chrome Google Media Microsoft Technology

Microsoft Makes Chrome Play H.264 Video 535

nk497 writes "Chrome users will be able to play H.264 video — thanks to Microsoft. The software giant today unveiled the Windows Media Player HTML5 Extension for Chrome, which will let users of the Google browser play H.264 video after it was dropped from Chrome over licensing issues. 'At Microsoft we respect that Windows customers want the best experience of the web including the ability to enjoy the widest range of content available on the internet in H.264 format,' said Claudio Caldato, Microsoft interoperability program manager."
This discussion has been archived. No new comments can be posted.

Microsoft Makes Chrome Play H.264 Video

Comments Filter:
  • Memory Leak (Score:5, Informative)

    by Utopia ( 149375 ) on Wednesday February 02, 2011 @01:20PM (#35080756)

    Microsoft's H.264 addon for Firefox has a bad memory leak.
    See http://www.neowin.net/forum/topic/971988-memory-leak-in-html5-extension-for-windows-media-player-firefox-add-on/ [neowin.net]

    So this might be bad for Chrome.

  • Re:Downright evil (Score:1, Informative)

    by RightSaidFred99 ( 874576 ) on Wednesday February 02, 2011 @01:26PM (#35080850)
    x264 is not a patent trap, its patent implications are well known. WebM, on the other hand, is a patent trap - nobody knows who's going to come out of the woodwork to sue over some small piece of it that someone has a vague patent over.
  • by Anonymous Coward on Wednesday February 02, 2011 @01:27PM (#35080868)

    Theora is also quite useful, given that the Wikimedia projects only accept free formats. You're not going to be able to upload your video in H.264 there, and they're a big enough player for this to actually matter.

  • Re:Downright evil (Score:5, Informative)

    by A beautiful mind ( 821714 ) on Wednesday February 02, 2011 @01:35PM (#35080968)
    Bullshit. Let me break it down:

    Patent risk from submarine patents: neither h.264 nor WebM offers any protection from it.

    Patent risk from MPEG-LA for h.264: significant, as it can decide to raise prices / start charging for content at any time. Bait and switch is their strategy.

    Patent risk from Google for WebM: none, they offered irrevocable indemnification [webmproject.org]:

    Google hereby grants to you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable ⦠patent license to [infringe VP8 patents owned by Google].

  • Re:Priorities (Score:5, Informative)

    by MHolmesIV ( 253236 ) on Wednesday February 02, 2011 @01:43PM (#35081054)

    Yes. Microsoft is a patent holder in the H.264 patent pool.

  • Re:OS (Score:4, Informative)

    by rwv ( 1636355 ) on Wednesday February 02, 2011 @01:58PM (#35081284) Homepage Journal

    every browser should rely on the codecs installed on the OS

    If browsers rely on OS codecs, then distributions of Linux would need to license H.264 and other proprietary codecs. The fact that these codecs are encumbered by patents (making them non-free) makes this an unlikely scenario.

    Or would you, as a user, prefer to deal with purchasing licenses for every computer you want to install a particular codec onto? I doubt you would want this burden, so why suggest that Linux distributions should bare it?

    Really... the winning solution (for users) is for a codec that is not encumbered by patents to become the de-facto standard. By enabling H.264 in Chrome on Microsoft platforms, Microsoft is trying to make a patent encumbered codec the de facto standard so that it (meaning Microsoft) can collect licensing fees in the future.

"Ninety percent of baseball is half mental." -- Yogi Berra

Working...