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…
Why doesn't Apple just include WebM support? It's an open codec...
Google Removing H.264 Support in Chrome
61–70 of 358 posts
Re: Google Removing H.264 Support in Chrome
#62One of the biggest criticisms against Microsoft over the years is that they suffer from Not-Invented-Here syndrome. Is it just me, or does Google seem to be increasingly heading down this path? Granted, Google tends to go down the open-source route, where Microsoft has tended not to, but I'm not sure that excuse holds up well over the long-term. Either way, I'm genuinely curious if anyone else feels this.
You're deriding Google for only supporting open standards that everyone can use instead of supporting closed formats that require you to pay money to a bunch of patent holders? Yeah, they sure are evil. I hate freedom, especially when it means I will have to add a command-line argument to my video encoding process!
Stop trolling. Your reply is off-topic. Parent was talking about a trend he is noticing, you're shouting about openness.
Re: Google Removing H.264 Support in Chrome
#63Earlier quoted context omitted.
Since when has Apple supported open standards simply because it makes sense to do so? Apple almost invariably chooses closed over open.
Apple is fully behind HTML5 - http://www.apple.com/html5/
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
#64I thought Chrome came bundled with Flash Player http://techcrunch.com/2010/06/25/google-chrome-flash/ ...which supports H.264 in an MP4 container... http://diveintohtml5.org/video.html ....so I'm not clear on what's actually happening here. Is Chrome going to just stop handing off MP4/H.264 from video tags to the bundled Flash Player even though it's there and can play it? Or will it stop bundling Flash Player? Or bu…
AFAIK they're not going to stop handing off video tags to Flash Player, because they never started doing that in the first place.
Re: Google Removing H.264 Support in Chrome
#65I'm looking forward to Google remaining consistent with their words and removing Flash from Chrome in the near future. You know, for the good of the users.
I'm sure they'll do that after Adobe sends an invoice to the Gnash project.
Re: Google Removing H.264 Support in Chrome
#66The 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…
Why doesn't Apple just include WebM support? It's an open codec...
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
#67Earlier quoted context omitted.
I'm just having a hard time understanding why they're ok with bundling the Flash player with Chrome, but not carrying an h264 decoder.
Because Flash is an established "standard", while the HTML5 tag is not.
H264 is an established standard. H264 is not the tag.
Re: Google Removing H.264 Support in Chrome
#68Earlier quoted context omitted.
I'm just having a hard time understanding why they're ok with bundling the Flash player with Chrome, but not carrying an h264 decoder.
Because Flash is an established "standard", while the HTML5 tag is not.
Google are not removing video tag support, they are removing the h264 codec. h264 is pretty damn well established and is actually a standard without the quotation marks, and an open one at that.
Re: Google Removing H.264 Support in Chrome
#69Earlier quoted context omitted.
> An open solution isn't the best interest of the users? An ubiquitous solution is in the best interests of users. My parents could care less about whether the video is encoded in H.264 or Ogg. They just want it to work on their iPad. > Surely this is just like Apple not supporting Flash in the hope that people go create HTML5 stuff which is open. It's not the same at all. Google, through YouTube and Chrome, helped m…
"de facto standard" is a meaningless, self-contradictory phrase that really boils down to saying "But this is the way we've always done it!" Standards are not de facto. Standards are things created by standards bodies. The word has an actual meaning. Trying to twist it to mean "the way we do stuff now" (as your argument for h.264 does) or "the way I want to do stuff" (as many arguments for HTML5 (which doesn't have a…
Whatever bro. WebM isn't and will never be a browser standard so I'm not sure what you're getting at. None of the codecs will as stated in the HTML5 Specification.
If you don't think de facto standards are important then you are clueless about the history of the internet and technology in general.
Re: Google Removing H.264 Support in Chrome
#70I'm the go-to guy in my office for html5 video(audio) and this just made my job that much harder. Shit, today I just found out that our videos arent playing on android devices now this