| |||||||||||||
Blizzard: HTML5 video and H.264 - what history tells us and why we're standing with the webBlizzard: HTML5 video and H.264 - what history tells us and why we're standing with the webPosted Jan 25, 2010 19:34 UTC (Mon) by Imroy (guest, #62286)In reply to: Blizzard: HTML5 video and H.264 - what history tells us and why we're standing with the web by nhippi Parent article: Blizzard: HTML5 video and H.264 - what history tells us and why we're standing with the web
I don't know about all of those pieces of hardware, but I'm sure the nVidia and ATI implementations are simply running on the GPU - I seriously doubt they would devote so much effort and chip area to having a squillion little processing units, and then add separate MPEG-1/2/4 video decoders in hardware as well. So the decoders are still software. And they'd be licensed of course.
Oh, and I can't find anything about this "DECODE264" instruction.
(Log in to post comments)
Blizzard: HTML5 video and H.264 - what history tells us and why we're standing with the web Posted Jan 25, 2010 19:43 UTC (Mon) by Cyberax (✭ supporter ✭, #52523) [Link]
"I seriously doubt they would devote so much effort and chip area to having a squillion little processing units, and then add separate MPEG-1/2/4 video decoders in hardware as well."
Yet they do exactly this. And the main reason is power consumption. Specialized ASICs are still faster even compared to GPGPU.
Blizzard: HTML5 video and H.264 - what history tells us and why we're standing with the web Posted Jan 25, 2010 20:47 UTC (Mon) by nhippi (subscriber, #34640) [Link]
> Oh, and I can't find anything about this "DECODE264" instruction.
It was a joke. The latest intel processors already have AESDEC and AESENC so..
|
|||||||||||||