9 ms·
I've been trying to refrain from commenting on these stories the last few days, but oh well. This whole debate is stupid and of course WebM exclusivity is the
by cookiecaper 16y ago
I've been trying to refrain from commenting on these stories the last few days, but oh well.
This whole debate is stupid and of course WebM exclusivity is the right way to go. Mozilla supports it, Chrome supports it, Opera supports it, Flash will be supporting it in the near future, meaning any of the other desktop browsers will support it.
The only reason people are complaining is that their iPhones have H.264 hardware acceleration. Well, dude, you'll just have to deal with software decode for some videos. The world does not revolve around iOS, no matter how much you want it to.
There is no good reason to support H.264 -- WebM provides roughly equivalent features and quality and MPEG-LA will be out for blood ever more as the clock ticks down on H.264 patents.
Everyone knows that there is no valid argument here for supporting H.264 other than "but... that'll decrease the battery life on my iPad or iPhone! :(". That's life, man; technology moves forward and old things get obsoleted, even mind-blowingly shiny things made by Apple.
I find the pointless hipster-fanboy whining to be pretty grating, personally.
- mikeryan 16y agoThere is no good reason to support H.264 What? Except for the fact that as a video site, all of my existing video is already in H.264. All of my encoding tools support H.264. Every other device I need to stream that video content too including mobile devices, tablets, Connected TV's, Blu-Ray players and Over the Top boxes (Roku, Boxee) support H.264 (generally at the hardware level).
- cookiecaper 16y agoThe same argument applies to video sites. We shouldn't be held back and stuck on a proprietary format just because you don't want to write a script to go through and re-encode everything to WebM. H.264 heretofore has been "the standard", so of course most existing devices will have better support for H.264 video than for the not-even-one-year-old WebM. Google and Mozilla are attempting to change that to avoid a repeat of GIF or even MP3. The argument boils down to "I don't want to put in the effort to switch to the new stuff, and my old stuff likes the old stuff better anyway, so Google is a jerk for trying to make the old stuff less common." And that's just a silly argument that could easily be applied to any number of things in technology, which is a very fast moving field. Things change a lot in this space and it's just one of those things you have to accept. Google has not obliterated or disabled your H.264 decoders. You are welcome to keep H.264 video around all you want (according, of course, to your license terms with the MPEG-LA). Removing native support from Chrom(e|ium) does not mean that all H.264 video is now magically broken or unplayable. If you are happy with H.264, you are free to continue to use it.
- mikeryan 16y ago"I don't want to put in the effort to switch to the new stuff, and my old stuff likes the old stuff better anyway, so Google is a jerk for trying to make the old stuff less common." - No the argument is that H.264 is still a much better supported format which works much better with an existing workflow, tools and media players (and a negligible licensing cost). Re-encoding to WebM does me no good if a large section of my target devices don't support it. If they support H.264 but not WebM I'm sticking to H.264, and happily paying the relatively negligible licensing fees. You also seem to be underestimating the complexity of re-encoding a video library. Its a massive and costly undertaking and hardly just taken care of with a shell script. You generally don't "re-encode" existing H.264 video to WebM. You re-encode baseline video at a higher bitrate down to WebM or H.264 at various bitrates. Frequently these source baseline videos are not stored as digital files - they are multi GB in size. We work with the UFC and re-encoding their content at one point required them re-sending digital tapes to the encoding house so they have high quality source video. Let alone the actual process. Even if you own your own encoding tools you generally need to re-encode, QA the resulting video, push it all out to your CDN and then change every link you've got point to the new video URL. If you're not encoding your own video but using an existing service you frequently have to pay for both bandwidth and encoding costs to redo your video you often pay per-minute of video. Its an extremely costly undertaking.
- cookiecaper 16y agoIt's a script to run ffmpeg over your video directories, scp/ftp/whatever it out to your CDN, and update a database somewhere (or use permalinks that don't care if the extension changes, or just keep the old extension on the filename even if it's not accurate anymore -- your users aren't seeing it anyway). It's definitely a scriptable undertaking if your application has any sanity. I recognize that there is an associated transitory cost, like the extra disk space and bandwidth used, but, again, such costs are inherent in working in a quickly developing field of technology. HTML5 is new, still only a draft, and most browsers' support is adequate but not really "mature". Things are going to be changing with regard to HTML5 video, canvas, etc. now and in the future -- you may want to stick with Flash video or links to video files until HTML5 stabilizes further. As stated, if you don't think it's worth your while to transcode to WebM, no one here is forcing you. You are totally free to keep everything H.264 and give Chrome users a Flash fallback.
- abdulla 16y agoLet's rephrase this: "Except for the fact that as a web site, all of my existing HTML already works in IE6. All of my HTML tools support IE6. Every other device I need to view web content content too including Windows mobile devices, Windows tablets, and Microsoft Web TVs support IE6." These same arguments have been used before, imagine if they were successful at deterring open, royalty-free innovation --- where would we be now?
- 9oliYQjP 16y agoThis is a standard negotiating tactic. Google will back down once they prove that WebM is a real threat to MPEG-LA's business model. They'll do this because you'll find Google getting an exclusive sweet deal from MPEG-LA for streaming h.264 on YouTube (which is what they really care about). Once that happens, h.264 will be back in play on Chrome, leaving FireFox and Opera as the odd browsers out. Which, incidentally, is great for Google because users of those browsers will just switch over to Chrome.
- jrockway 16y agoBy similar logic, Chrome is just a ploy to get Microsoft to make Google the default search in IE, and Android is just a ploy to keep Apple using Google Maps on the iPhone. This could be true, or it could actually be that Google wants people to use a format that works on Linux, OS X, and Windows. Not everything is a conspiracy or a ploy, you know.
- VengefulCynic 16y agoIgnoring the cost in ignoring the revenue from millions of iOS users, let me focus instead of the looming legal question of WebM. If Google were to indemnify WebM users (sites who encode in WebM, developers who release decoders, OEMs who release hardware decoders), I would be much more willing to embrace WebM. As is, there is a very cogent argument to be made that the MPEG-LA group has already suggested that some of their patents may be encapsulated in WebM and users could be opening themselves up to lawsuits as co-defendants with Google. H.264 isn't free, but it's a known cost and licensing from MPEG-LA indemnifies you from any legal costs that might be associated with patent trolls popping up to sue you to death.
- cookiecaper 16y agoThis point has already been discussed a lot, but I'll just review it quickly for you. Basically, if you use any software at all, you can't go around living your life in constant fear of patent threats. WebM is probably safer than most because you have a big entity to fight most of your battle for you, presuming such a battle ever materializes. Of course it's possible that MPEG-LA will be angry to see their H.264 revenue stream run consistently drier and sue in hopes of retaliation and a declaration that all WebM users must pay MPEG-LA royalties anyway. There's no guarantee that this will happen, however, and that MPEG-LA hasn't made an attempt to "nip this in the bud" demonstrates that they may not be all that certain they have a case here. Google released WebM explicitly to circumvent the restrictions with H.264 so I suspect they did their due diligence and deviated from the H.264 patents in the necessary ways, but as above, there's nothing you can do if you irritate a group that has money and lawyers and wants to try their hand at milking something out of you. That's a general fact of life whether you use WebM or not. If you're really worried about the FUD MPEG-LA puts out to scare you into paying protection money, then I guess you are free to pay that, if it makes you feel happier. But "Google shouldn't promote free standards because it might make someone angry and then they might sue you" is just not a very solid argument -- we can't refuse to do anything because someone might sue us. There will always be vultures out there, and we can't stop progress because of them.
- kenjackson 16y ago
- crab 16y agoThis is a very civil and reasonable comment that adds much to the discussion. Undoubtedly your analysis will go far towards halting the propagation of pointless and inflammatory threads on this topic and will ensure that any future discussions will be ideologically pure. Hail Hitler.
- toddheasley 16y agoI've been trying to refrain from commenting, too, so that's one thing that we have... had in common. > ...of course WebM exclusivity is the right way to go. Mozilla supports it, Chrome supports it, Opera supports it, Flash will be supporting it in the near future... First of all, including Opera in the list of those in favor of WebM is a lot like including Iceland in the Coalition of the Willing. If you live in Iceland, you probably overestimate Iceland's importance, but it undermines the intent of making a list in the first place. The flip side of this is that, while Internet Explorer probably won't support WebM unless Google indemnifies adopters, IE is almost as irrelevant as Opera in the arenas of both web video and The Future. Here's where we really are: * Apple likes H.264 for the following reasons: * The licensing and liability is known, and Apple can afford to pay. They don't care if web video ends up being a high stakes poker table, because they're a high roller. * H.264-encoded video looks better than WebM video and takes up slightly less space. * Most current graphics silicon supports hardware decoding of H.264, which allows for video playback that is both gorgeous and economical. * Mozilla liked Theora because they can't or won't pay to license H.264, and Theora was the only open source candidate they could find to run in the election. Free is more important than good. * Google likes WebM for the following reasons: * They can control its development. * It is, so far as anyone knows, unencumbered by patents, so no licensing. I say "so far as anyone knows" because that's what Google is saying by not indemnifying WebM adopters. If you're worried about a theoretical MPEG-LA licensing gotcha, then you have to be equally worried that, if/when WebM adoption is significant, patent trolls won't show up with claims of infringement. At least with H.264, the licensing terms have been stated. YOU personally may not be worried about either scenario, but you're probably not weighing whether you should produce graphics chips that decode WebM. Does anybody on this forum want to argue whether the chipmakers who've pledged to do WebM decoding aren't nervously watching to see if more Android hardware makers get sued? By not indemnifying adopters, Google is essentially picking an open source fight in a crowded bar and then ducking out the side door. >The only reason people are complaining is that their iPhones have H.264 hardware acceleration. Well, dude, you'll just have to deal with software decode for some videos. The world does not revolve around iOS, no matter how much you want it to. That is a very big component to the complaining: I can't watch your idealism on my iPad for the duration of a 6-hour flight. And you're right, the world does not revolve around iOS, but the video world does revolve around H.264 right now. If you're not shooting with actual film, then your video workflow literally starts and ends with H.264. And maybe more to the point web video does revolve around iOS devices, because iOS users watch orders of magnitude more video than anybody else. > WebM provides roughly equivalent features and quality If by "features" you're excluding fast, economical encoding and decoding and by "quality" you're excluding picture quality. "Roughly equivalent" is just weaseling around admitting H.264 looks and works better. Someday... who knows? Someday GM might make a better car than Toyota, but for now, GM is stuck saying things like "[our] quality can't be beat by Toyota." > I find the pointless hipster-fanboy whining to be pretty grating, personally. And the hipster-fanboys doing the pointless whining harbor deep suspicions that people who are willing to trade their audio and video playback quality today for the open source promise of adequate video someday don't really care much about audio or video.
- abdulla 16y agoThe other thing that bothers me is that people are screaming blue murder as if they had no alternative choice of browser. If you don't like Chrome's decision (or Firefox's, or Opera's), use another browser. You can still choose to use Safari or IE.
- ugh 16y agoH.264 hardware is everywhere, you shouldn’t imply that it is only in iPhones.
- bonaldi 16y ago> This whole debate is stupid and of course WebM exclusivity is the right way to go. This whole debate is stupid and of course WebM exclusivity is the wrong way to go. An "of course" is a really lame way to enter a debate, because it says that everyone take the debating so far seriously are idiots, which I don't believe the rest of HN are. The other alternative is that it's much more nuanced than "of course" allows, you just haven't understood the debate. > The only reason people are complaining is that their iPhones have H.264 hardware acceleration No, people are complaining for many other valid reasons. Like: the digital video world runs on H.264, it has deep, complicated, expensive internal toolchains to support it, legacy archives encoded in it, basically entire businesses built around it. The video production world is far larger and more complex than you're picturing it. A "script" isn't nearly enough to do what you're talking about; suggesting you just need to point ffmpeg at a hard drive of stuff has dramatically underestimated the scale of what's involved. Or, reasons like: they want the video tag to succeed, and this decision essentially entrenches Flash for another five years at least. In an h.264 world the video tag had the combined support of three major desktop browsers, iOS, Android, a tonne of shipping mobile and embedded hardware, a Flash fallback and crucially it was an easy implementation for all the video content producers, with no re-encoding required. That's plenty enough to give it a good beachhead and momentum away from all Flash all the time. In a WebM world, you have the support of Firefox, Opera and Chrome. No shipping mobile support. No shipping embedded support. No shipping Flash implementation. No video producer support. No video toolchain support. And it's a small technological step backwards, to boot! > I find the pointless hipster-fanboy whining to be pretty grating, personally. I find underinformed freetard passive-aggression to have no place here, personally.
- prodigal_erik 16y agoCodecs have come and gone all the time. Your best bet for the web as late as 2007 was transcoding to VP6. How could anyone invest in a toolchain that can't support any codec other than H.264, knowing such a poor design wouldn't have been viable just a few years before? Did they think the industry wouldn't agree on any improvements, ever?
- bonaldi 16y ago
- Tloewald 16y agoAll the arguments against h264 apply equally to proprietary fonts only more so (since they're not even free as in beer for the next few years). If font-family can designate a non-free/open font then video can designate a non-free/open codec.
- cookiecaper 16y ago<video> in fact can specify a non-free codec. This isn't about the types of codecs that should be allowed to be included in <video>, it's about the types of codecs a browser vendor will support out of the box. Fonts are much smaller than video decoders so they can be sent over the wire, making the whole licensing and distribution thing the problem of the person using the font on his site. Fonts are all decoded by the same free code, whether that font is free or not. There is no facility to transmit a decoder for the use of <video> tags on your page, and no one would do that anyone because it would be a huge nightmare to make sure you're sending one that can run on the user's platform, the browser would be forced to allow execution of an arbitrary binary block that could very well just be posing as a video decoder, and then all sites would have to pay for the rights to distribute the license. It just doesn't work. The browser has to include the decoder locally, so the browser vendor has to decide if he's going to pay for the license for a H.264 decoder or not.
- crab 16y agoThis isn't about the types of codecs that should be allowed to be included in <video>, it's about the types of codecs a browser vendor will support out of the box. This is extremely misleading, as three out of the five major desktop browsers refuse to allow you to play anything except what they support out of the box, meaning that what is "allowed" and what is "supported out of the box" are the same thing. In those browsers you can specify a non-free codec, but you're not free to actually play it. The browser has to include the decoder Also misleading, as this is not a requirement of the specification, but an implementation choice made by certain browser vendors.