More On Chrome's HTML Video Codec Change

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
Apparently Google has pissed off more than a handful of people with its decision to kill support for the H.264 video codec. How many people? I don't know but it was enough for the company to address those concerns on the Chromium Blog.

There has been a lot of discussion regarding this week’s announcement of upcoming changes to HTML video codec support in Chrome. The future of web video is an important topic, we welcome the debate, and want to address some of the questions raised.
 
Doesn't really matter much. They are only talking about HTML5 video tag. Most all of the H264 video we see today is played through Flash, and will continue to work. There's not going to be a lot of HTML5 H264 content anyway, given the alternatives.
 
I actually have to agree with Google that the basline standard should be the open alternative, not a propietary one that charges royalties.
 
Still, instead of making a unilateral decision, it might have been better to engage users support:
If the problem is the H.264 license, instead of fighting H.264, fight against the license.

H.264 R&D has long been paid back, the license owners could easily make it free now because it's not R&D anymore, it's just a milk cow. I'm sure many users would support that, rather than removing H.264 altogether which is a technology that seems to work well especially for professionals, now that hardware support is adequate.
 
I've worked with both live and on demand video streaming for about three years now. Before that I did transcoding as a hobby for about seven years.

There are layers of problems inherent in video streaming.

What player are you going to hit? On a deskop computer (Windows, Mac and Linux) the most common one is Flash which does both FLV and MPEG-4 Part 10 (AVC). It has rapidly become the defacto standard for streaming. With one MPEG-4 Part 10 compliant file or live stream you can deliver content to QuickTime, embedded QuickTime, Flash and all of the iPhone, iPad and iPod devices. If you have the right server (or combination of servers) you can do them all at the same time.

Mobile phones also have players. Most mobile phones support 3gp Rel 5 and 3gp Rel 6 content. There are some (fewer and fewer each day thankfully) that just cannot accept an ISMA complaint MP4 file like the desktop players can. Yes, I know that 3gp Rel 6 can have the internal compliance of H.264 and AAC (or AAC+) but the container is different and not all phones can work with that.

To further complicate matters not all players on phones are created equal. Some can do just about anything and some can do only a few. It depends upon what the manufacturer decided to add. We can talk about compliance until we are all blue in the face but they typically require the MPEG-4 Part 10 baseline standard for playback of streaming content. Further complicating the issue is what your carrier allows to come across their network, how saturated their network is and how compliant your phone's player is. Don't even try to use the standard player with an Android. Epic f'ing fail with compliant content.

Now with all of that out of the way I do not know of one mobile phone that can currently play WebM format including the Android. Yes there will probably be an app for that, (actually hardware support is becoming available via Google) but the manufacturer has to include that in their phone and find room for it on the silicon. Products that are not an iPhone or Android (issue solved via link above) will be left behind unless the manufacturers choose to support it, their legal teams get behind it, their engineers are able to integrate it and they choose to market it.

So unless you plan on purchasing a new phone that has WebM decoding ability you are going to be SOL with regard to WebM. You will still have the legacy content formats to fall back on but now the files will need to be encoded in MP4, WebM, 3gp Rel 6 and whatever other formats the player can best receive.

Oh, and also for the specific resolution your phone can handle if the carrier bothers to do that. Most do. They have server farms for just that. QCIF is the most common but I have seeing higher resolution and higher bandwidth stuff filter in over the past few years.

Now watch all of the legacy content that is going to pile up even further while WebM tries to play catch up. Yes you can do batch transcodes, but that takes testing and a lot of time when you have terabytes of data. It also assumes you have the source material. Avoid when possible transcoding from a previously transcoded file.

While this may be the greatest thing since the invention of Sliced Bread[tm], don't hold your breath on it hitting the mobile market anytime in the next one to one and a half years. And even when support is added to the phone the video has to be able to be delivered (server support) and not a lot of mobile compliant streaming servers can deliver the WebM format yet.

And just to clarify, streaming is not downloading. See also RTSP and RTMP for just two examples of streaming protocols. The purpose of a streaming server is to save bandwidth. Most people only watch part of a video. Why waste that bandwidth?
 
Google is doing the right thing here. We just need Microsoft and fucking Safari to get on board and everyone is all set. You cannot enjoy the amazing benefits of html5 and the beautiful <video> tags without a standard, free codec.

Transcoding and having multiple streams for different browsers is not something my shop or anyone else is going to do. Thats not what was promised, the browser makes need to man up and come together on a standard for the common good.
 
Thank you google for making sure that Flash remains entrenched for the long term. Really, thank you. :rolleyes:
 
I'm confused about something. One of the comments from Google's blog post said that H.264 is needed because its hardware accelerated and won't drain your battery as much as a software driven codec would. Is that true? I would think hardware acceleration would require more juice for the performance and cause the battery to drain quicker, no?

What am I misunderstanding?
 
What am I misunderstanding?
Dedicated hardware in cell phones, portable players and even regular computers can decode h.264 much more efficiently than an algorithm running on a general purpose CPU. The downside of course is that newer features/later revisions of the specification or different compression schemes (like WebM) fall back to software decoding, if it's even supported on the platform at all.

Software encoding/decoding of WebM is a very, very poor idea on the tens to hundreds of millions of devices that support h.264 in hardware. It is not practical for handhelds at all without quickly draining the batteries of those devices.
 
I have no hard facts but I would think that optimized dedicated hardware components would do a better job for less power than a CPU intensive equivalent.
CPUs and ICs have been integrating more and more functions and are yet less and less power hungry, although Intel processors seem to be getting less and less transistors, so we haven't reached the 1-billion bar yet that was planned by Moore's law! ^-^
 
I myself am glad that they don't want to make a proprietary (for profit) codec a web standard.
 
Back
Top