4 ms·
Microsoft release a Firefox plugin enabling H.264 support
- woodall 16y agoThe plugin is Windows only. http://www.interoperabilitybridges.com/html5-extension-for-wmp-plugin http://www.interoperabilitybridges.com/html5-extension-for-w...
- sid0 16y agoIt should be fairly easy to use the same idea on other platforms.
- nextparadigms 16y agoI think it's obvious why thy did this. They don't want Google's open source WebM codec to become the norm so they're going to push even harder for h.264. The whole Internet is better off in the end if it's built only on open source and free stuff.
- xentronium 16y agoIt'd be trivial for them to implement any open codec support. Thus, no, it's not obvious.
- annon 16y agoWebM is not that great technically (http://x264dev.multimedia.cx/archives/377 http://x264dev.multimedia.cx/archives/377) and is unlikely to remain royalty-free if it ever takes off as there are many patents that could apply to it's code. H.264 will play in both flash and the browser. It's a standard codec that is used in most workflows already. On top of that, MPEG-LA has announced it will always be royalty free for video that is free to end users (http://www.macworld.com/article/153692/2010/08/h264_royalties.html http://www.macworld.com/article/153692/2010/08/h264_royaltie...). There's no reason for Firefox and Opera to not pick up H.264. It is the only choice that makes sense if HTML5 video is going to take off, and they are holding the web back. Thumbs up to Microsoft for actually trying to push us forward this time.
- tvon 16y ago> (...) and is unlikely to remain royalty-free (...) The argument that there may be lurking patent issues in WebM doesn't carry a lot of weight, I think, unless they are actually demonstrated. After all, couldn't you say that about absolutely any software?
- Locke1689 16y agoCiting from Jason's article that you obviously didn't take the time to read: "With regard to patents, VP8 copies too much from H.264 for comfort, no matter whose word is behind the claim of being patent-free. This doesn’t mean that it’s sure to be covered by patents, but until Google can give us evidence as to why it isn’t, I would be cautious."
- tvon 16y agoI'm not sure what you think is in those sentences that amounts to a verified patent infringement of some kind. You would think though that in the ~8 months since Jason wrote this some kind of specific claim might have surfaced? I'm not at all convinced WebM doesn't have patent issues, but I'm certainly not going to assume it does have patent issues because someone said it might have patent issues. Also, for what it's worth, the burden of proof is not on Google, that's not how patents work.
- sid0 16y agoI really don't know much about this, but I understand that VP8 was designed to deliberately avoid patents. (Thus some of the weird decisions Dark_Shikari comments on.)
- Locke1689 16y agoYou would think though that in the ~8 months since Jason wrote this some kind of specific claim might have surfaced? Nope. Personally I would wait until it's too late for the major players to back out before I make a patent claim. There's no 'statute of limitations' on patent claims. Laches may make things a tad more difficult but holding off until the actual specification is in use would probably hold up. I'm not at all convinced WebM doesn't have patent issues, but I'm certainly not going to assume it does have patent issues because someone said it might have patent issues. As Jason said in his article (and he's probably in one of the best positions to judge technical ingenuity in this area), it's very likely that it does have patent issues. That's not someone saying it might have patent issues, that's someone saying it probably does. Also, for what it's worth, the burden of proof is not on Google, that's not how patents work. In court. We're not in court. The claim is being made that we should use WebM mostly because it isn't patent encumbered (certainly not for technical reasons). This is a claim that Google should defend. Without support for this statement there's no reason to use WebM instead of H264.
- jamesaguilar 16y agoHow would WebM harm or H.264 help Microsoft? IMO no speculation like this is obvious without some kind of salable explanation of motive.
- socketpuppet 16y agoMicrosoft is a H.264 licensor, with one or more patens in the H.264/AVC patent pool. Having H.264 become the standard for publishing video on the Web will benefit them directly in terms of licensing fees.
- gxti 16y agoThey're not sitting around a conference table in an underground bunker, stroking their beards and cackling maniacally while trying to screw the open source community as hard as possible. Microsoft is a business. What business sense does it make to release this plugin?
- stingraycharles 16y agoJust thinking out loud, but if this codec becomes dominant, and is only released by Microsoft on the Windows platform, perhaps it's another reason to prefer Windows over OSX?
- gxti 16y agoApple adopted H.264 years ago -- it's basically all they use.
- natrius 16y agoAs a member of the H.264 patent pool[1], Microsoft makes money when people use H.264. If WebM becomes popular, Microsoft directly makes less money. [1] http://en.wikipedia.org/wiki/MPEG_LA http://en.wikipedia.org/wiki/MPEG_LA
- jamesaguilar 16y agoDon't they also have to pay licensing fees to MPEG-LA? What's the overall impact on the bottom line? IMO it would have to be pretty substantial for it to really be a driving factor in the decision-making.
- kprobst 16y agoI'm fairly sure they pay more than they receive in this particular case.
- natrius 16y agoI doubt they pay more for their use of H.264 than they receive from everyone's use of H.264. Providing the codec may cost them money, but it's far from obvious that it's an unprofitable act.
- ubernostrum 16y agoYes, and they also are hard at work on a Firefox extension that kicks puppies and steals candy from babies.
- jiaaro 16y agoI think this article overlooks the fact that outsourcing media playback to environment specific codecs (WM9/VLC/etc) has been around for ages. by the time html5 video is widespread each user will likely have several media plugins installed willing to play h264 video for them in any browser. I'm talking about quicktime, realplayer, vlc, and windows media, among others - This is SO not a big deal
- wmf 16y agoThe context here is that Mozilla specifically said they will not allow Firefox to use Windows's built-in codecs. MS found a workaround by rewriting <video> tags into <embed>.
- jbk 16y agoThe problem with this is that they replace the html5 <video> tag with an <object> one that WMP plugin will pick up. It should be not important, but are we sure it does comply correctly to all the <video> options and properties? I don't know why but I think not. Maybe I should activate my activex plugin that replace IE9 <video> tag into a VLC <object> and see how they take it?
- Locke1689 16y agoI think Mozilla's refusal to allow use of OS installed codecs is worse, though. I can see the justification for not providing support for the H264 codec in-browser but not allowing OS codecs seems like taking ideology over technology too far.
- buster 16y agoMotivation: Push H.264 on the web, give MS (and Apple) more money from license fees in the future.
- archangel_one 16y agoI doubt it. I think their motivation is to prevent WebM from replacing h.264 as the dominant web video format. Microsoft don't care about licensing fees - their cash cows will be earning them orders of magnitude more. But if WebM replaces h.264 then Firefox on Linux (or ChromeOS or whatever) will be able to play that quite happily, whereas I'm sure MS would prefer h.264 to remain dominant since it's patent-encumbered.
- buster 16y agoPreventing WebM to become dominant has the exact same outcome of more license income ;) Also, why shouldn't they care about license fees? Think about all encoders/decoders, all producers, all receivers, home cinema players. With more and more videos (VOD) moving into the web, this is only at the beginning. Once H.264 is established enough it's income for free!
- latch 16y agoI got a pit in stomach reading that....Microsoft just can't win. I'm sure they have business motives for this, but it really seems like a damned if you do, damned if you don't. They release a free plugin for Firefox, which'll help address the major issue surrounding HTML5, and the question we ask is if they've gone too far? Or why is it Windows 7 only? Really?!