This is a great move...
Mpeg-LA has been bullying everyone for too long...
Google Removing H.264 Support in Chrome
101–110 of 358 posts
Re: Google Removing H.264 Support in Chrome
#102Earlier quoted context omitted.
Well i don't know. What i see : Adobe is gonna support webm. So having only one format is gonna be possible. Browsers who supported or were gonna support H264 : - Safari (5% market share) - IE9 (0% market share right now, probably around 15% in 3 years) - Chrome (around 13 %) Browsers who supports Webm : - Firefox (30% market share) - Chrome - IE9 will probably support it via codecs which is better than nothing The b…
> The big deal breaker i see is the mobile devices who natively support H264 You kind of buried this but this is the true deal breaker. There aren't (and probably won't be) hardware WebM decoders. And Firefox doesn't support WebM yet. You'll have to wait on version 4 (0% market share right now as you said for IE9).
There are already hardware WebM decoders, in fact they've just announced hardware encoders too.
They link to a relevant announcement in the linked blog post:
http://blog.webmproject.org/2011/01/availability-of-webm-vp8...
And the update rates of Firefox and Chrome and totally different from IE, especially since version 9 doesn't support XP.
Re: Google Removing H.264 Support in Chrome
#103I'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.
Speaking as someone who works for a browser vendor: There's a big difference between dropping support for entrenched technologies, and choosing which emerging technologies to support.
Certain formats and practices are already part of the web, for better or worse, and it's not fully within the browser vendors' power to change that. If any browser dropped Flash support, it would break thousands of popular web sites, and users would simply switch browsers.
What is within our power is to decide which emerging standards to support. Dropping H.264 in at this point won't cause users to flee the browser. And it does give us some chance of avoiding another patent-encumbered format becoming a de-facto standard on the web.
We don't control existing sites, but we do control our own actions which influence new sites. We can't alter the past, but we can change the future.
Re: Google Removing H.264 Support in Chrome
#104Earlier quoted context omitted.
> The big deal breaker i see is the mobile devices who natively support H264 You kind of buried this but this is the true deal breaker. There aren't (and probably won't be) hardware WebM decoders. And Firefox doesn't support WebM yet. You'll have to wait on version 4 (0% market share right now as you said for IE9).
> You kind of buried this but this is the true deal breaker. Well i mentionned it. I'm at least partially intellectually honest :) > Firefox doesn't support WebM yet. You'll have to wait on version 4 (0% market share right now as you said for IE9) That's totally true, but from experience and statistical evidence, i think firefox users are more inclined to upgrade their browser than IE user are. > There aren't (and pr…
> That's totally true, but from experience and statistical evidence, i think firefox users are more inclined to upgrade their browser than IE user are
Very true. Our site has had for a while only a couple percent of non 3.5+ Firefox traffic.
Re: Google Removing H.264 Support in Chrome
#105Google's assumption: People will add WebM encoding to their already complicated video workflows What will actually happen: Chrome will get served h.264 wrapped in Flash. Lose all round, then.
Which sucks for HTML5 video. Without Chrome, only about 5% of web users actually support HTML5 playback using h.264. Chart: http://videojs.com/2011/01/google-is-dropping-h-264-from-chr...
Two things could end the format war. 1. Apple adopts WebM (which requires WebM hardware for iOS devices) 2. MPEG LA removes all royalties from h.264
Re: Google Removing H.264 Support in Chrome
#106[deleted]
Re: Google Removing H.264 Support in Chrome
#107Earlier quoted context omitted.
Well i don't know. What i see : Adobe is gonna support webm. So having only one format is gonna be possible. Browsers who supported or were gonna support H264 : - Safari (5% market share) - IE9 (0% market share right now, probably around 15% in 3 years) - Chrome (around 13 %) Browsers who supports Webm : - Firefox (30% market share) - Chrome - IE9 will probably support it via codecs which is better than nothing The b…
And all the embedded chips in cellphones,m set top boxes and mp3 players are going to support WebM? Thats going to take a while - the lead time on new DSP families isn't quick. And how long before their are optimized open source libraries like ffmpeg and x264?
FFMPEG claimed to have the fastest VP8 decoder on the planet back in July:
Announcing the world’s fastest VP8 decoder: ffvp8
Re: Google Removing H.264 Support in Chrome
#108Earlier quoted context omitted.
Well i don't know. What i see : Adobe is gonna support webm. So having only one format is gonna be possible. Browsers who supported or were gonna support H264 : - Safari (5% market share) - IE9 (0% market share right now, probably around 15% in 3 years) - Chrome (around 13 %) Browsers who supports Webm : - Firefox (30% market share) - Chrome - IE9 will probably support it via codecs which is better than nothing The b…
And all the embedded chips in cellphones,m set top boxes and mp3 players are going to support WebM? Thats going to take a while - the lead time on new DSP families isn't quick. And how long before their are optimized open source libraries like ffmpeg and x264?
ffmpeg does already supports webm, and the encoder is quite good from what i gathered, since it's done by the same crew than x264
Re: Google Removing H.264 Support in Chrome
#109Long live Flash video?
Re: Google Removing H.264 Support in Chrome
#110Next move, suddenly youtube stops encoding in h.264 and youtube won't be able to be played on the iPad. And Android tablets look a LOT better.
You do know that the reason h.264 is better on iOS is because the hardware decoder, right?
Android doesn't even do hardware-accelerated graphics, let alone video decoding.