x404.co.uk
http://www.x404.co.uk/forum/

Google axes Jobsian codec in name of 'open'
http://www.x404.co.uk/forum/viewtopic.php?f=19&t=12048		 Page 1 of 1
Author:  forquare1 [ Wed Jan 12, 2011 6:21 am ]
Post subject:  Google axes Jobsian codec in name of 'open'
Quote:
Google has announced that its Chrome browser will no longer include support for H.264, the patent-encumbered video codec favored by Apple and Microsoft. Future versions of Chrome will only include support for the open source and royalty-free WebM and Ogg Theora codecs.


Continue reading here

Not sure on this one. It could either really push the web to more open formats, or it could damage Chrome's popularity, especially around non-techy types.
Author:  l3v1ck [ Wed Jan 12, 2011 7:45 am ]
Post subject:  Re: Google axes Jobsian codec in name of 'open'
The latter I suspect.
People just want their browser to "work".
Author:  jonbwfc [ Wed Jan 12, 2011 8:34 am ]
Post subject:  Re: Google axes Jobsian codec in name of 'open'
Funny they're axing the non-proprietary, standards-based H264 codec on grounds of 'openness' but keeping Chrome's built-in Flash video player. Could it be that Google don't have a direct competitor to Flash, they have a site that brings in a lot of ad revenue based entirely on Flash and the whole 'openness' thing is utter bullox? Oh, you know, I think it might. Not that a lot of Flash video will play anyway because inside the FLV 'container' it's encoded in H264 anyway.

Jon
Author:  Linux_User [ Wed Jan 12, 2011 11:56 am ]
Post subject:  Re: Google axes Jobsian codec in name of 'open'
Open source, royalty-free codecs FTMFW.
Author:  big_D [ Wed Jan 12, 2011 12:41 pm ]
Post subject:  Re: Google axes Jobsian codec in name of 'open'
The problem is, h.264 is already a standard. Most video cameras nowadays record directly in h.264...

Add to that, that h.264 and Google's own codec are lossy, that means users of Chrome will get an inferior version of the video... It also means a lot more work for website operators, to include multiple versions of the film.
Author:  jonbwfc [ Wed Jan 12, 2011 1:58 pm ]
Post subject:  Re: Google axes Jobsian codec in name of 'open'
There is also some... debate as to the actual legal status of WebM. MPEG-LA claim that WebM infringes on several of their patents that were implemented in H.264. If they are right, Google have OS'ed things they had no right to and in theory they would have to withdraw WebM, take the source code down and attempt to redress the damage i.e. effectively stop other people from using it afterwards.

The idea that H.264 has all these legal tangles while WebM floats free as a butterfly is utterly spurious (and, frankly, an invention of some of the more vociferous OS activists). Anything that involves a corporate entity at any point is going to have legal hassles at some point or other.

big_D wrote:
The problem is, h.264 is already a standard. Most video cameras nowadays record directly in h.264...

Also there is a massive population of devices out there that have built in H264 hardware decoding and pretty much none that have hardware WebM decoding. I doubt it'll be popular if using it takes us back to the days of smartphones with a five hour battery life.

Jon
Author:  jonbwfc [ Wed Jan 12, 2011 10:04 pm ]
Post subject:  Re: Google axes Jobsian codec in name of 'open'
An Open Letter from the President of the United States of Google.

And they say Americans don't understand irony.
Author:  paulzolo [ Fri Jan 14, 2011 2:39 pm ]
Post subject:  Re: Google axes Jobsian codec in name of 'open'
big_D wrote:
The problem is, h.264 is already a standard. Most video cameras nowadays record directly in h.264...

Add to that, that h.264 and Google's own codec are lossy, that means users of Chrome will get an inferior version of the video... It also means a lot more work for website operators, to include multiple versions of the film.


This happens anyway - with OGG Vorbis being the codec of choice for Firefox for the moment - it seems that WebM may be the codec of choice for those at a later date. The whole <video> tag is a freaking mess. One codec should be all that is necessary. I’m quite happy for it to be h.264 because I feel it gives a better picture. However,m if it was just OGG or just WebM, we’d at least only have to work to one codec.

Anyway, it’s just as likely that non h.264 browsers will just use a Flash wrapper to play the h.264 content anyway, propping up Flash in all its heavenly glory.

http://daringfireball.net/2011/01/pract ... idealistic
Author:  Linux_User [ Sat Jan 15, 2011 3:30 pm ]
Post subject:  Re: Google axes Jobsian codec in name of 'open'
I don't think Flash needs propping up TBH - it's installed on about 97% of machines anyway*.

*according to Steam.
Page 1 of 1 All times are UTC
Powered by phpBB® Forum Software © phpBB Group
https://www.phpbb.com/