Originally posted by Svartalf
View Post
Announcement
Collapse
No announcement yet.
Google Opens Up VP8, Launches New Container Format
Collapse
X
-
Originally posted by deanjo View PostOne place I do think where VP8 does have a future are areas where codecs such as realmedia, Bink and possibly divx are used. It is better at least then those solutions in terms of image quality.
Comment
-
here we go already on the Apple and MPEG-LA issue: http://www.electronista.com/articles...l.to.fee.webm/
Comment
-
Originally posted by deanjo View PostThat won't happen for quite a long time I'm afraid if at all even with no patent issues at present.
Linux has a lot of very powerful media tools and streaming stuff right now, but it's just that nobody can really use them or support them out of the box since the codec issues make life difficult.
The tools for dealing with VP8 are already ready to be shipped. Gstreamer, support, is already here and if you install the VP8 plugins then Linux WEbkit-based browsers like Epiphany and Midori already 'just work' with Google's stuff.
To improve it they would most likely have to start looking at techniques that are already patented and that closes that road down.
Like was mentioned before VP8 encoder was heavily optimized for high PSNR scores... which look good on paper and on graphs when your trying to sell people proprietary codecs.. it's not a good approach in practice. If they tweak the current stuff and make the encoder more suited and take some 'psy' optimizations into account then it will easily beat most of the commercial H.264 encoders out there.
They also have to contend with device manufacturers and not many will bring out a new product to support an inferior format to what they presently have now.
VP8 already is optimized for the DSPs and SIMD devices found in mobile devices. There is nothing magical about hardware that means that to support H.264 you can't support accelerating VP8 and visa versa.
'ASICs' are not some magical thing that must never be touched and device makers don't design chips and in actuality have almost nothing to do with the the design and fabrication of the vast majority of the chips in their devices.
What actually happens is device makers pick out a reference platform from companies like Texas Instruments and then copy that design as much as possible to a formfactor that will fit in the shape they want.
Seriously. That's how it works.
The majority of big 'handset makers' and OEMs out of Asia actually have very little technical expertise when it comes to designing integrated circuits. They take a SoC from Ti or FreeScale, take a reference platform from one of them or third party company and then figure out how to manufacture it cheaply. They don't hack on the software if they can help it (and when they do it sucks unless they license from some software development firm). They specialize heavily in the manufacturing and industrial design and that is their bread and butter.. the less they actually have to touch the chip design or software design on the devices they ship the better off they are.
It's those SoC (System on a Chip) is were 'acceleration' comes from. It's just one big 'chip' that has the majority of the functionality you need to build a embedded system. This is done to keep prices low and keep things low-power.
Look at Google's hardware partners:
* AMD
* ARM
* Broadcom
* FreeScale
* Imagination
* Logitech
* Marvel
* Mips
* Nvidia
* Qualcomm
* Texas Instrument
* VeriSilicon
* ViewCast
Can you pick out the companies that make the SoC's that go into the majority of Smartphones and other 'multimedia' handhelds?
Well... It's not 'ARM'. They just design processors that people license to integrate into their SoC products.
It's Qualcomm, FreeScale, Broadcom, and Texas Instruments. Not companies like HTC or even Apple.
For it to truly be adopted in large masses it still has to provide a superior solution in capabilities to the status quo.
By that time it is very likely that the MPEG-LA group will have something out to eclipse h264 and once again the gap widens between the opensource alternatives. If VP8 debuted at the same time as h264 it might of had a fighting chance in mass adoption but the market is firmly entrenched in h264 already.
We saw this with mp3 and ogg years back. MP3 was already widely adopted and ogg remains a obscure item that few devices support.
Apple could of easily supported Ogg if they wanted to. Hacked versions of the ipods have been able to play Ogg Vorbis just fine from the first generation up. But they wanted AAC instead.
And why do you think that Apple wanted AAC instead of Ogg?
Same reason they are compaigning against open codecs like Theora or VP8.
It's because Apple is a member of MPEG-LA. They make money from people licensing H.264 and AAC patents.
Comment
-
Originally posted by drag View PostI don't think so at all, actually.
Linux has a lot of very powerful media tools and streaming stuff right now, but it's just that nobody can really use them or support them out of the box since the codec issues make life difficult.
The tools for dealing with VP8 are already ready to be shipped. Gstreamer, support, is already here and if you install the VP8 plugins then Linux WEbkit-based browsers like Epiphany and Midori already 'just work' with Google's stuff.
They have to do the same sort of stuff to VP8 that they did for Theora's newer versions and the big improvements they got there.
Like was mentioned before VP8 encoder was heavily optimized for high PSNR scores... which look good on paper and on graphs when your trying to sell people proprietary codecs.. it's not a good approach in practice. If they tweak the current stuff and make the encoder more suited and take some 'psy' optimizations into account then it will easily beat most of the commercial H.264 encoders out there.
That's Apple's crack I smell around here?
VP8 already is optimized for the DSPs and SIMD devices found in mobile devices. There is nothing magical about hardware that means that to support H.264 you can't support accelerating VP8 and visa versa.
'ASICs' are not some magical thing that must never be touched and device makers don't design chips and in actuality have almost nothing to do with the the design and fabrication of the vast majority of the chips in their devices.
What actually happens is device makers pick out a reference platform from companies like Texas Instruments and then copy that design as much as possible to a formfactor that will fit in the shape they want.
Seriously. That's how it works.
The majority of big 'handset makers' and OEMs out of Asia actually have very little technical expertise when it comes to designing integrated circuits. They take a SoC from Ti or FreeScale, take a reference platform from one of them or third party company and then figure out how to manufacture it cheaply. They don't hack on the software if they can help it (and when they do it sucks unless they license from some software development firm). They specialize heavily in the manufacturing and industrial design and that is their bread and butter.. the less they actually have to touch the chip design or software design on the devices they ship the better off they are.
It's those SoC (System on a Chip) is were 'acceleration' comes from. It's just one big 'chip' that has the majority of the functionality you need to build a embedded system. This is done to keep prices low and keep things low-power.
Look at Google's hardware partners:
* AMD
* ARM
* Broadcom
* FreeScale
* Imagination
* Logitech
* Marvel
* Mips
* Nvidia
* Qualcomm
* Texas Instrument
* VeriSilicon
* ViewCast
Can you pick out the companies that make the SoC's that go into the majority of Smartphones and other 'multimedia' handhelds?
Well... It's not 'ARM'. They just design processors that people license to integrate into their SoC products.
It's Qualcomm, FreeScale, Broadcom, and Texas Instruments. Not companies like HTC or even Apple.
I'm very aware of "How it works". I'm also aware of many formats that DSP's that are capable of handling and even officially supporting it still has very little to do with adoption. The end implementation however is upon the end device manufacturer. I am aware of the companies involved. They are the same players as usual, nothing out of the ordinary there. And as in the past they have supported successfully adopted formats and they have also supported dud formats.
That should not be very difficult as the status quo for streaming video is pretty lousy. The fact that I can take Theora, as lousy at is is, and get better quality then the majority of H.264 or VC-1 video out there is a testament to that.
The vast majority of the market is 'Flash Video' and even Adobe is supporting VP8.
Apple coming out and dominating the player market is what killed Ogg for consumer devices. Otherwise if you actually pay attention most half-way decent players support Ogg and even Flac actually. I have no problem playing Ogg Vorbis on the majority of 'Mp3 player' I have come across, except ipods and Sony stuff.
Apple could of easily supported Ogg if they wanted to. Hacked versions of the ipods have been able to play Ogg Vorbis just fine from the first generation up. But they wanted AAC instead.
And why do you think that Apple wanted AAC instead of Ogg?
Same reason they are compaigning against open codecs like Theora or VP8.
It's because Apple is a member of MPEG-LA. They make money from people licensing H.264 and AAC patents.
Comment
-
Originally posted by Apopas View PostWhat patents does VP8 infring?
Comment
Comment