Blizzard: HTML5 video and H.264 - what history tells us and why we're standing with the web [LWN.net]

Blizzard: HTML5 video and H.264 - what history tells us and why we're standing with the web

Posted Jan 25, 2010 19:46 UTC (Mon) by Oddscurity (guest, #46851)
In reply to: Blizzard: HTML5 video and H.264 - what history tells us and why we're standing with the web by coriordan
Parent article: Blizzard: HTML5 video and H.264 - what history tells us and why we're standing with the web

The way I understand it: nVidia's VDPAU doesn't even do all of the decoding
on the GPU, it just accelerates some parts like colour conversion,
deblocking and other parts of the inner loop.

So it's still software, part of which runs on the CPU as implemented in the
driver, and part of which ends up running on the GPU.

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:54 UTC (Mon) by drag (guest, #31333) [Link]

Yeah.

Like stated above there are 22 different companies involved in the Mpeg
group. And if the GSM folks are any indication of how these sort of industry
'IP' groups operate they do everything they can to shovel as many patents
into the pool as possible.

So it's likely that there are dozens and dozens of patents covering all
sorts of different aspects of the codecs, and software and hardware related
to the codecs. So even if the video card folks build codecs-as-hardware they
still only likely take a some patents out of the equation and not all of
them. Meaning that even with hardware acceleration your still not going to
escape from the licensing requirements.

Blizzard: HTML5 video and H.264 - what history tells us and why we're standing with the web

Posted Jan 25, 2010 21:02 UTC (Mon) by nhippi (subscriber, #34640) [Link]

> The way I understand it: nVidia's VDPAU doesn't even do all of the decoding
> on the GPU, it just accelerates some parts like colour conversion,
> deblocking and other parts of the inner loop.

I believe that is what the early VDPAU versions did. Later versions offload full decoding to the video card. Then again, this is based on external observations of cpu load rather than knowing what the VDPAU library really does..