News for hackers. Stuff that matters.
Re:Google Removing H.264 Support in Chrome by bphogan on Tuesday January 11, 2011 @03:31PM (#2093332)
The choice has been made by many places to simply use h264 video via the HTML5 tag to hit the iPhone/iPad and then fallback to a Flash video player which can easily play the h264 source video. Content producers would rather encode videos once, which is why they moved to FLV in the first place. There's no incentive to use anything else here.

This hurts users. I am all for standards, but not for hurting users. And like it or not, content producers are using H264 because the devices people like to use can play that video back.

Re:Google Removing H.264 Support in Chrome by soofaloofa on Tuesday January 11, 2011 @03:49PM (#2093422)
You can equally argue that Apple's stance on video and on Flash is hurting users.
Re:Google Removing H.264 Support in Chrome by bphogan on Tuesday January 11, 2011 @03:58PM (#2093458)
Apple's stance on Flash does hurt users. But its stance on vodeo? Hardly. They chose an established, proven format that has hardware decoding capabilities. That means they could include it cheaply, and in a way that doesn't drain battery like a software decoder would.
Re:Google Removing H.264 Support in Chrome by KeithMajhor on Tuesday January 11, 2011 @10:22PM (#2094787)
Apple's stance on Flash hurts users _now_. But, I still envy my future self living in a world where Flash is dead. The same can be said about Google hurting users _now_. Pushing content producers towards an open and maintainable format has obvious long term advantages.
Re:Google Removing H.264 Support in Chrome by nkassis on Wednesday January 12, 2011 @12:25AM (#2095104)
That's exactly my view, both moves are good to me. HTML5 video is still young and barely used currently, it's the time to try to shape how it will be used. If you wait 5 years, h264 will be impossible to displace and everyone will have to get software with a license, hurting all of us even more.
Re:Google Removing H.264 Support in Chrome by bphogan on Wednesday January 12, 2011 @11:47AM (#2096715)
But again, H264 is not HTML5 video... H264 is a video codec that just happens to be used with the video tag on Mobile Safari and IE9. It's also how a majority of YouTube's videos are encoded currently, as well as many many other video uplod sites.

It's also the codec used on the Xbox360, the PSP, the PS3, and other pes of consumer electronics. It turns out that to reach the largest audience of consumer electronic devices and computer, H264 happens to be the best choice.

Video production workflows let content producers save as h264 videos.

The adult industry is using h264 videos on their web sites to serve their content to portable "more personal" devices.

I'd say h264 is pretty entrenched now.

Re:Google Removing H.264 Support in Chrome by redrobot5050 on Wednesday January 12, 2011 @07:23PM (#2098296)
Apple's stance is "why should we ship a product with known security holes out of the box and take the heat for it?"

Any user can install Flash. Apple is not depriving the user of anything.

If Google pulls the plug on H.264 on YouTube, they are depriving a lot of users of access. Mobile users (not just iOS users). Wii Users. Blu-Ray players/Web Top boxes.

Will it all eventually get straightened out? Yes, one way or another. But the sudden shift in strategy seems like Google isn't going to care one way or another to who they put out to pasture in order to establish a new de facto standard. It's very 1990s-era Microsoft of them.

Re:Google Removing H.264 Support in Chrome by simonsquiff on Tuesday January 11, 2011 @04:48PM (#2093697)
Apple didn't previously have Flash support in iOS and then remove it... taking something working out for ideological reasons is much worse than never adding something in for ideological reasons in my book.
Re:Google Removing H.264 Support in Chrome by KeithMajhor on Wednesday January 12, 2011 @05:33AM (#2095640)
http://venturebeat.com/2010/04/08/apple-bans-flash-to-iphone...

Apple could support flash for nothing... Adobe has tried to do it for them, with both direct flash support and this conversion tool. Apple is making a purely idealogical decision.

Re:Google Removing H.264 Support in Chrome by vegashacker on Wednesday January 12, 2011 @12:23PM (#2096857)
That article, "Apple bans Flash-to-iPhone conversions in apps", is no longer true. Apple relaxed the ban. See, e.g.,

http://venturebeat.com/2010/09/09/apple-loses-game-of-chicke...

Re:Google Removing H.264 Support in Chrome by yason on Tuesday January 11, 2011 @04:16PM (#2093544)
You rarely gain much unless you let yourself hurt a bit first and reap the benefits later.
Re:Google Removing H.264 Support in Chrome by foljs on Tuesday January 11, 2011 @05:21PM (#2093830)
Mind you, that could also be a line coming from one trying to screw you.
Re:Google Removing H.264 Support in Chrome by StavrosK on Tuesday January 11, 2011 @03:45PM (#2093395)
Why doesn't Apple just include WebM support? It's an open codec...
Re:Google Removing H.264 Support in Chrome by alanh on Tuesday January 11, 2011 @03:49PM (#2093425)
Keep in mind Apple devices have HARDWARE h.264 decoders. It may not be as simple as you think.
Re:Google Removing H.264 Support in Chrome by StavrosK on Tuesday January 11, 2011 @09:39PM (#2094691)
Hmm true. I wonder how different the hardware decoding is...
Re:Google Removing H.264 Support in Chrome by forgottenpaswrd on Tuesday January 11, 2011 @03:57PM (#2093453)
Because Apple uses h.264 in all their hardware. They have implementations on firmware so they could accelerate video on their iPhones, iPads, iPods, even making specific hardware for it.

This makes this videos to perform great on their hardware, fast and taking less resources(more battery),it lets them make things like editing video in real time on your phone, but only works for one codec.

If they use software codecs, all their competitive advantages are lost on mobile.

Re:Google Removing H.264 Support in Chrome by pohl on Tuesday January 11, 2011 @03:48PM (#2093421)
That would imply decoding in software. H.264 is currently decoded in hardware on those devices.
Re:Google Removing H.264 Support in Chrome by pospischil on Tuesday January 11, 2011 @04:02PM (#2093481)
From the bits and pieces that I have read, there are some very real patent questions still looming.

Jason Garett-Glaser put together a great comparison of h.264 vs VP8/WebM. Check it out here: http://x264dev.multimedia.cx/archives/377

His summary: the spec is really terrible, the performance leaves a lot to be desired (though, there is a lot of room for optimization), and it 'copies too much from H.264 for comfort'.

Re:Google Removing H.264 Support in Chrome by mbrubeck on Tuesday January 11, 2011 @04:44PM (#2093675)
This comment in response to that post makes an interesting point; the most similar bits are likely the most carefully vetted, and may be written deliberately to avoid patent infringement. Patents on standards can be very narrow; as long they cover exactly what's in the spec, then any implementer of the standard still has to pay up:

"Patents are about _details_ so the mere fact that something does something like something else, isn’t necessarily something at all.

As we’ve pointed out before, many codec patents are exceptionally easy to work around: They specify every little detail because it makes it _much_ easier to get through the examination but doesn’t harm the patent’s ability to read on the final standard because the standard specifics exactly the patented behaviour.

D_S, for all his undeniable H.264 experience isn’t an expert on patents or even the H.264 patents. We can assume that in cases where VP8 looks similar to H.264 those would have been exactly the cases where care was taken to differ in the right places. I’d expect the primary risks for VP8 to be anywhere _but_ there."

more at http://blog.gingertech.net/2010/05/20/vp8-adobe-is-the-key-t...

Re:Google Removing H.264 Support in Chrome by andybak on Tuesday January 11, 2011 @06:13PM (#2094035)
Sorry for the downvote but that was a very early analysis and the story has progressed a bit since. There's room for a more nuanced evaluation of WebM which I'd like to hear.
Re:Google Removing H.264 Support in Chrome by CountSessine on Tuesday January 11, 2011 @10:41PM (#2094838)
How do you know whether anything at all has advanced? One of the most knowledgeable authorities on video compression has called into question VP8's patent situation. Why is there any need at all to imagine a false opposite? Other than optimism?

The whole VP8/webm situation reminds me of when Microsoft tried to do the right thing and open-license VC1, but got clobbered by patent holders and had to reverse themselves.

Re:Google Removing H.264 Support in Chrome by ZeroGravitas on Wednesday January 12, 2011 @04:48AM (#2095569)
Dark Shakari's latest pronouncement on video encoding patents was to accuse someone of patenting his idea by reading commit logs, and argue at the same time that the idea was obvious to anyone and therefore not patentable. His evidence that it must have been copied? Because it didn't include some later changes he made. (Note this doesn't even pass a basic logic test, never mind constitute a sophisticated take on the current patent situation). He then retracted the accusation.

http://x264dev.multimedia.cx/archives/589

Update: Tandberg claims they came up with the algorithm independently: to be fair, I can actually believe this to some extent, as I think the algorithm is way too obvious to be patented. Of course, they also claim that the algorithm isn’t actually identical, since they don’t want to lose their patent application.

I still don’t trust them, but it’s possible it’s merely bad research (and thus being unaware of prior art) as opposed to anything malicious. Furthermore, word from within their office suggests they’re quite possibly being honest: supposedly the development team does not read x264 code at all. So this might just all be very bad luck.

Regardless, the patent is still complete tripe, and should never have been filed.

Re:Google Removing H.264 Support in Chrome by app on Tuesday January 11, 2011 @03:58PM (#2093461)
Re:Google Removing H.264 Support in Chrome by jbrennan on Tuesday January 11, 2011 @03:48PM (#2093418)
My guess is patents. And they already have great H264 implementations. And hardware support.

What would be the benefit, to them or their users, if they used WebM?

Re:Google Removing H.264 Support in Chrome by redthrowaway on Tuesday January 11, 2011 @03:47PM (#2093404)
Since when has Apple supported open standards simply because it makes sense to do so? Apple almost invariably chooses closed over open.
Re:Google Removing H.264 Support in Chrome by rradu on Tuesday January 11, 2011 @03:49PM (#2093426)
Apple is fully behind HTML5 - http://www.apple.com/html5/
Re:Google Removing H.264 Support in Chrome by jarek on Tuesday January 11, 2011 @05:01PM (#2093745)
Yes, in spirit too:

"This demo was designed with the latest web standards supported by Safari. If you’d like to experience this demo, simply download Safari. It’s free for Mac and PC, and it only takes a few minutes."

Come see web standards! Using a specific browser.

Re:Google Removing H.264 Support in Chrome by joubert on Wednesday January 12, 2011 @07:46AM (#2095943)
Hum, because they're showing the latest HTML features that Safari supports? Not all browsers support the same range of features for a particular HTML standard.
Re:Google Removing H.264 Support in Chrome by jarek on Friday January 14, 2011 @08:29PM (#2106160)
A couple of days later, I found this: How much HTML5 is there in Apple's HTML5 demos? http://blog.marcoos.com/2010/06/09/is-html5-by-apple-really-...
Re:Google Removing H.264 Support in Chrome by jarek on Wednesday January 12, 2011 @08:14AM (#2095998)
Any organization which denies access to its HTML5 pages to browsers that support them is not fully behind the spirit of HTML. The reason is clear and understandable — marketing their browser — but so are the implications.
Re:Google Removing H.264 Support in Chrome by ZeroGravitas on Tuesday January 11, 2011 @04:01PM (#2093475)
Yet the number one reason there isn't a codec specified in HTML5 is because Apple blocked it.
Re:Google Removing H.264 Support in Chrome by ubernostrum on Tuesday January 11, 2011 @06:38PM (#2094129)
Bullshit.

Multiple companies, including Apple (and Nokia, which ain't exactly a minor player in the mobile market) objected to HTML5 mandating support for a particular codec, largely on the grounds that we don't really know the patent situations of any of the allegedly-unencumbered codecs.

Meanwhile, multiple people objected on the grounds that mandating a current (or, really, several-years-old now since that's what it is) codec in a spec that's not expected to go final for at least a few more years, and which has an expected useful life of around a decade, is just frankly stupid. It'd be like having a spec used today mandate XBM as the standard image format because that was the least-proprietary thing available 15 years ago when early browsers were being written.

Re:Google Removing H.264 Support in Chrome by gloob on Tuesday January 11, 2011 @10:03PM (#2094743)
Multiple companies, including Apple (and Nokia, which ain't exactly a minor player in the mobile market) objected to HTML5 mandating support for a particular codec, largely on the grounds that we don't really know the patent situations of any of the allegedly-unencumbered codecs.

Now it's my turn to call bullshit. "We don't really know the patent situations of $x" could be used as an argument against ANY piece of software or standard $x. Unless there is real evidence for such concerns, it's FUD.

Re:Google Removing H.264 Support in Chrome by ubernostrum on Tuesday January 11, 2011 @10:13PM (#2094761)
There ain't no such thing as a free codec. At least, not as long as software patents exist.

Does Google want a Free, interoperable web? Then they should take the money they'd spend re-encoding all of YouTube into VP8 and instead spend it on lobbying to eliminate software patents. Then they could just use whatever's the best option from a technical perspective and we could stop having codec shitstorms every six months.

Re:Google Removing H.264 Support in Chrome by mbrubeck on Tuesday January 11, 2011 @10:39PM (#2094832)
"There ain't no such thing as a free codec."

This is what groups like the MPEG-LA want us to think, but I'm not so sure. The Ogg Vorbis codec used for WebM audio has been in use for a decade, and has shipped in dozens of software and hardware products, some from large companies with big pockets. MPEG-LA made the same vague threats about patent pools against Vorbis, but they never followed through.

Xiph.org conducted a patent search early in the Vorbis process, and believes Vorbis does not infringe on any patents. Google has done their homework on VP8 as well. If they did it right, then VP8 is no more vulnerable to unknown patent threats than any random piece of software. (Sadly, any random piece of software is somewhat vulnerable.)

For that matter, there's no guarantee that H.264 is invulnerable from patent trolls who aren't members of the licensing pool. MPEG-LA doesn't indemnify licensees against third-party patents.

Re:Google Removing H.264 Support in Chrome by ubernostrum on Wednesday January 12, 2011 @01:47AM (#2095260)
Sadly, any random piece of software is somewhat vulnerable.

Any random piece of software is vulnerable.

Look, if Google's serious about the threat software patents pose to openness, there's an obvious thing they should be doing, and it isn't "switch the video codec we use in our web browser". Until I see them doing some serious (i.e., big-money) lobbying to abolish software patents, I'm going to assume the whole openness thing is just marketing bullshit designed to play into geeks' stereotypes of them and Apple.

Re:Google Removing H.264 Support in Chrome by cookiecaper on Wednesday January 12, 2011 @12:04AM (#2095066)
Not that I disagree, but a "patent search" early in the process for Vorbis is not that comforting. Vorbis has been around for a while now and new patents are awarded that all the time that are used against prior art. Unless Google/On2 has an inside man at the patent office raising Vorbis as prior art, it's likely that someone could craft a patent specifically intended to target Vorbis, get it approved, and then sue lots of people. Trolls take this approach fairly often.
Re:Google Removing H.264 Support in Chrome by ZeroGravitas on Tuesday January 11, 2011 @04:09PM (#2093512)
Also, Apple used to be fully behind royalty-free standards for the web:

http://lists.w3.org/Archives/Public/www-patentpolicy-comment...

Apple believes that it is essential to continued interoperability and development of the Web that fundamental W3C standards be available on a royalty-free basis. In line with the W3C's mission to "lead the Web to its full potential," Apple supports a W3C patent policy with an immutable commitment to royalty-free licensing for fundamental Web standards. Apple offers this statement in support of its position.

It's powerful and persuasive stuff, worth reading in full. They only removed this statement from their website about 6 months ago.

Re:Google Removing H.264 Support in Chrome by extension on Tuesday January 11, 2011 @04:33PM (#2093618)
Have they said or done something that conflicts with this statement?
Re:Google Removing H.264 Support in Chrome by mbrubeck on Tuesday January 11, 2011 @05:30PM (#2093865)
Their implementations of the HTML5 <video> and <audio> draft standards work only with royalty-encumbered codecs. (The licensing is currently royalty-free for publishers and end users, but not for device manufacturers or browser vendors.)
Re:Google Removing H.264 Support in Chrome by extension on Wednesday January 12, 2011 @12:33AM (#2095117)
Have they ever proposed that those codecs be part of the standard?
Re:Google Removing H.264 Support in Chrome by rmc on Tuesday January 11, 2011 @05:24PM (#2093842)
Google were also opposed to a format in the spec, they claimed ogg theora was too large in file size. Why do you think they bought On2 and released WebM in the first place? There already was a free video code theora before.
Re:Google Removing H.264 Support in Chrome by scottbruin on Thursday January 13, 2011 @05:02AM (#2099360)
That's false. Read this: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-Jun...

MS didn't commmit to anything, Mozilla essentially blocked H.264 from becoming specified codec too. All had reasonably sound reasons to hold their respective position. Not everything can be explained as good vs. evil.

Re:Google Removing H.264 Support in Chrome by sid0 on Tuesday January 11, 2011 @04:25PM (#2093579)
You call this being "fully behind HTML5"? http://grab.by/grabs/0b694089e83975c385627b134ee8ece7.png

Even Microsoft's better than this.

edit: could whoever downvoted me explain why he did so?

Re:Google Removing H.264 Support in Chrome by tzs on Tuesday January 11, 2011 @04:59PM (#2093733)
That's not inconsistent with being "fully behind HTML5". That page is meant to show off how Safari handles various HTML5 features. If you view it in a different browser, it is not showing you how Safari handles those features. Hence, it makes perfect sense for it to try to limit itself to people using Safari.
Re:Google Removing H.264 Support in Chrome by sid0 on Tuesday January 11, 2011 @05:02PM (#2093751)
That page is meant to show off how Safari handles various HTML5 features.

Isn't the point of HTML that all browsers handle it similarly? If that link is restricted to one browser, it isn't better than all the "Designed for IE6" sites you used to see in the early '00s, and absolutely no evidence of Apple being "fully behind HTML5".

Re:Google Removing H.264 Support in Chrome by tzs on Tuesday January 11, 2011 @06:08PM (#2094016)
HTML5 is not a standard. It does not yet behave the same in all browsers that implement it. Different browsers implement different subsets of it.

The site you cite is meant specifically to show how Apple is doing with their HTML5 implementation. There is simply no point in viewing it in another browser. Viewing it in, say, Firefox would tell you nothing at all about how well Apple has implemented HTML5 in Safari.

This is completely different from the "Designed for IE6" sites. Those sites were generally presenting information that was useful to people regardless of which browser they were using.

Re:Google Removing H.264 Support in Chrome by sid0 on Wednesday January 12, 2011 @05:19AM (#2095627)
HTML5 is not a standard. It does not yet behave the same in all browsers that implement it. Different browsers implement different subsets of it.

And yet they're converging to implementing all of it.

The site you cite is meant specifically to show how Apple is doing with their HTML5 implementation.

Then it's a Safari demo, not an HTML5 demo. The Microsoft demos use HTML5 and yet work just fine in other browsers.

Those sites were generally presenting information that was useful to people regardless of which browser they were using.

How is seeing HTML5 working in Firefox or Chrome not useful to people?

Re:Google Removing H.264 Support in Chrome by tzs on Wednesday January 12, 2011 @02:08PM (#2097245)
> Then it's a Safari demo, not an HTML5 demo.

Correct, which is probably why Apple says: "The demos below show how the latest version of Apple’s Safari web browser, new Macs, and new Apple mobile devices all support the capabilities of HTML5, CSS3, and JavaScript".

Re:Google Removing H.264 Support in Chrome by drivebyacct2 on Tuesday January 11, 2011 @03:53PM (#2093438)
I love to hate on Apple's decisions, but this is just ludicrous.
Re:Google Removing H.264 Support in Chrome by hexley on Tuesday January 11, 2011 @03:51PM (#2093433)
Comment of the year right here, folks. +4 already too. Thank heavens its a throwaway, how embarrassing.
Re:Google Removing H.264 Support in Chrome by andybak on Tuesday January 11, 2011 @06:17PM (#2094046)
It's not exactly insightful but it does have some merit. Apple's approach is an odd mix of open and closed. You could describe it as 'strategically open'... (of course - this applies to Google too to a slightly lesser degree).

No company supports open-source if it directly conflicts with their perceived interests. Some companies just take a wider view than others.

Re:Google Removing H.264 Support in Chrome by hexley on Saturday January 15, 2011 @01:32PM (#2107455)
I'd like to see a compiled list of open technologies Apple has chosen vs closed. "invariably closed" my arse.
Re:Google Removing H.264 Support in Chrome by drivebyacct2 on Tuesday January 11, 2011 @05:10PM (#2093789)
Except that the same exact thing can be done with WebM. Native support in Chrome, Firefox and Opera. Flash fallback in IE. Ding.

The only legitimate concern with this is hardware decoding, largely in mobile devices.

Re:Google Removing H.264 Support in Chrome by slimier on Tuesday January 11, 2011 @11:09PM (#2094907)
However, the devices with the most users which don't have flash (read: iOS), can play h264, not WebM. That would make it likely to be more often h264 with flash fallback.
Re:Google Removing H.264 Support in Chrome by drivebyacct2 on Tuesday January 11, 2011 @11:25PM (#2094952)
"The only legitimate concern with this is hardware decoding, largely in mobile devices."

iOS can implement WebM, no problemo. The problem is, it will be pretty crummy.