Looks like Mozilla wins this one.
Google Removing H.264 Support in Chrome
31–40 of 358 posts
Re: Google Removing H.264 Support in Chrome
#32Earlier quoted context omitted.
Wouldn't you already need to encode everything twice due to Firefox's lack of H.264 support?
For full compatibility, yes, but realistically there was no reason to use to WebM. With h.264 you cover the following: 1) All browsers with Flash players 2) Any "web connected" set top device/TV 3) About 50% of HTML5 video compatible browsers With this move by Google #3 falls to 25% or less. And they're looking to add WebM support to #2. At some point consumer demands you support both because their shiny new Macbook…
Flash will support vp8, that should level the playing field. IE can be extended to use vp8 also, google chrome frame should be a required install everywhere ;p
Re: Google Removing H.264 Support in Chrome
#33One 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!
Re: Google Removing H.264 Support in Chrome
#34Earlier quoted context omitted.
Wouldn't you already need to encode everything twice due to Firefox's lack of H.264 support?
For full compatibility, yes, but realistically there was no reason to use to WebM. With h.264 you cover the following: 1) All browsers with Flash players 2) Any "web connected" set top device/TV 3) About 50% of HTML5 video compatible browsers With this move by Google #3 falls to 25% or less. And they're looking to add WebM support to #2. At some point consumer demands you support both because their shiny new Macbook…
Still not quite sure I see the big deal.
Firefox has something like twice the browser share of Chrome. If you were OK sticking Firefox users with Flash video, I don't see how that's hugely different from sticking Firefox AND Chrome users with Flash video.
If you want to support all modern browsers, you used to have to do two encodings. After this announcement, you will still have to do two encodings.
Re: Google Removing H.264 Support in Chrome
#35What the hell? It's sad that Google's corporate strategy is starting to override what's in the best interests of it's users. Web video is finally, after so many years, actually encoded in H.264. Who besides YouTube uses WebM or Ogg? I'll be going back to Safari if this happens.
[deleted]
Re: Google Removing H.264 Support in Chrome
#36The message is that Google is serious about making VP8 competitive. It won't be removing H.264 support from Android and YouTube anytime soon, but this certainly changes the HTML5 video codec battle.
Re: Google Removing H.264 Support in Chrome
#37Interesting. YouTube must be a mess with all of these competing formats it needs to support. I assume it will eventually switch to WebM for both HTML5 and Flash by default and just use h264 for compatibility. Still, it must be horrific.
Nope. It was stored as h264 before they released webm (and then flash played it). When they released Webm, they started to convert all that stuff to VP8 (my guess is they should be through by now), so it's only VP8 now (via HTML5 or flash). End of story.
Re: Google Removing H.264 Support in Chrome
#38People should really blame MS and Apple for only supporting their own video codec here.
I am fully behind the decision of Mozilla, Opera, Google and others to support open and patent unencumbered video formats.
Can someone just look at the table at http://en.wikipedia.org/wiki/HTML5_video and really tell me that this mess isn't the fault of MS and Apple in the first place? Ogg is ready to play a big role and WebM is catching up. The only blocking factor here is Internet Explorer and Safari, not Chrome.
Re: Google Removing H.264 Support in Chrome
#39The 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...
Re: Google Removing H.264 Support in Chrome
#40One 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.
Yes, Google has an enormous reputation for NIH. Great technology companies often do.