Linked by Thom Holwerda on Fri 14th Jan 2011 22:33 UTC
Google I didn't plan on this, but there's really nothing I can do. Unless you want me to write about the upcoming ten billionth download from the iOS App Store, you'll have to settle for this. On the Chromium blog, Google has clarified its decision to drop H.264 support from the Chrome web browser, and in it, Google basically repeats the things that those concerned about the future of video on the web have been saying for a long time now: H.264 on the web kills innovation.
Thread beginning with comment 458722
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[8]: Reasonable overview
by brichpmr on Mon 17th Jan 2011 21:04 UTC in reply to "RE[7]: Reasonable overview"
brichpmr
Member since:
2006-04-22

"WebM, arguably, doesn't solve anything....just another solution to a non-existant problem, imho.


And I thought you were actually trying to engage in a debate over the issue... If you are content with sticking your fingers in your ears and screaming LA-LA-LA-LA then I am fine with ignoring you.

Let me know if you change your mind.
"
Whether one is using an Android device or an iPhone, I would assert that the best available video experience is due to the availability of hardware-accelerated H.264. Unless anyone can make a compelling argument for WebM as a replacement now.....not in some imaginary future...well....Hmmm..

Reply Parent Score: 1

RE[9]: Reasonable overview
by lemur2 on Mon 17th Jan 2011 22:28 in reply to "RE[8]: Reasonable overview"
lemur2 Member since:
2007-02-17

Whether one is using an Android device or an iPhone, I would assert that the best available video experience is due to the availability of hardware-accelerated H.264. Unless anyone can make a compelling argument for WebM as a replacement now.....not in some imaginary future...well....Hmmm..


Have you actually tried each one, or are you just guessing?

iPhones and Android phones have smallish screen resolutions. While WebM is very slow to encode, it is faster at decoding than H.264 is. Although a device such as an iPhone really needs hardware acceleration to decode H.264 even at iPhone screen resolutions, the same is not necessarily true of WebM.

WebM decoding first became available in Android around December last year with the release of Android 2.3 Gingerbread. Even then, Google warned that Gingerbread doesn't include the Aylesbury improvements.

http://gigaom.com/video/gingerbread-android-webm-vp8/
The first version of Android will ship with libvpx 0.9.2, which is a slightly outdated version of WebM. Support for the newest WebM release 0.9.5, code-named Aylesbury, will be pushed out with a maintenance release, according to Google’s WebM product manager John Luther. Users will be able to access every WebM video stream or file with the WebM release included in Gingerbread, but the coming update should help with the format’s playback performance and memory footprint, amongst other things.


Aylesbury was released in October last year:
http://blog.webmproject.org/2010/10/vp8-codec-sdk-aylesbury-release...
Aylesbury offers a 20-40% (average 28%) improvement in decoder speed.

So, in order to compare what is available right now, you would have to compare an iPhone side by side with an Android 2.3 (Gingerbread) phone with the WebM maintenance update installed which includes Aylesbury code.

Let me guess ... you didn't do that.

So you are just guessing.

Reply Parent Score: 2

RE[10]: Reasonable overview
by brichpmr on Tue 18th Jan 2011 00:33 in reply to "RE[9]: Reasonable overview"
brichpmr Member since:
2006-04-22

"Whether one is using an Android device or an iPhone, I would assert that the best available video experience is due to the availability of hardware-accelerated H.264. Unless anyone can make a compelling argument for WebM as a replacement now.....not in some imaginary future...well....Hmmm..


Have you actually tried each one, or are you just guessing?

iPhones and Android phones have smallish screen resolutions. While WebM is very slow to encode, it is faster at decoding than H.264 is. Although a device such as an iPhone really needs hardware acceleration to decode H.264 even at iPhone screen resolutions, the same is not necessarily true of WebM.

WebM decoding first became available in Android around December last year with the release of Android 2.3 Gingerbread. Even then, Google warned that Gingerbread doesn't include the Aylesbury improvements.

http://gigaom.com/video/gingerbread-android-webm-vp8/
The first version of Android will ship with libvpx 0.9.2, which is a slightly outdated version of WebM. Support for the newest WebM release 0.9.5, code-named Aylesbury, will be pushed out with a maintenance release, according to Google’s WebM product manager John Luther. Users will be able to access every WebM video stream or file with the WebM release included in Gingerbread, but the coming update should help with the format’s playback performance and memory footprint, amongst other things.


Aylesbury was released in October last year:
http://blog.webmproject.org/2010/10/vp8-codec-sdk-aylesbury-release...
Aylesbury offers a 20-40% (average 28%) improvement in decoder speed.

So, in order to compare what is available right now, you would have to compare an iPhone side by side with an Android 2.3 (Gingerbread) phone with the WebM maintenance update installed which includes Aylesbury code.

Let me guess ... you didn't do that.

So you are just guessing.
"

I'm not 'guessing' that native H.264 video has been all-but-perfect on my iphones for years. I've spent time this week comparing WebM video in Firefox 4 with H.264......the former will need more than a 'maintenance update' to cut it for me....ymmv.

Reply Parent Score: 1

RE[10]: Reasonable overview
by dtahiti on Wed 19th Jan 2011 10:16 in reply to "RE[9]: Reasonable overview"
dtahiti Member since:
2011-01-13


So, in order to compare what is available right now, you would have to compare an iPhone side by side with an Android 2.3 (Gingerbread) phone with the WebM maintenance update installed which includes Aylesbury code.

Let me guess ... you didn't do that.

So you are just guessing.


I am not sure you'll find somebody in this forum to try what you suggest as so many people have Android 2.3 today (sarcasm.. ) : 0.4 % of Android users as of today. (http://developer.android.com/resources/dashboard/platform-versions....)
That maintenance update will likely happen one day for the Nexus S but I don't think this day has come yet. And either they're hiding because they won't say a single bad thing about WebM, either they don't care that much about WebM to have tried that.

I don't own an Nexus S, but Anandtech reviewed it and tried to play some WebM content. It was not good. Let me quote it :
Android 2.3 also supposedly adds WebM and VP8 support, though I’ve had no success playing back any test videos and am working on encoding some smaller ones to try on the Nexus S. One video played back using the android video player had audio but had no video, other videos played back in the browser showed controls but never started playback.


Link : http://www.anandtech.com/show/4059/nexus-s-and-android-23-review-gi...

Edited 2011-01-19 10:17 UTC

Reply Parent Score: 1