If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

It sounds like a good project, but I'd also be willing to work with him on the VP8 OpenCL port (not mentor/mentee necessarily, just working together). If the OpenCL Gallium state tracker gets finished, there's no real need to get a VP8/Gallium state tracker up and running. We should be able to extract the needed performance out of the OpenCL version without having to translate it to a state tracker. And then the BSD/Solaris/etc. people can benefit from the work as well.

I would like to have a VDPAU video decoder simply so that people that write video players (mplayer, VLC, etc.) do not have to adapt to Yet Another Video Backend. Additionally, finishing and deploying pipe_video_context has been a todo item for years, and it'd be nice to actually complete that.

I would like to have a VDPAU video decoder simply so that people that write video players (mplayer, VLC, etc.) do not have to adapt to Yet Another Video Backend. Additionally, finishing and deploying pipe_video_context has been a todo item for years, and it'd be nice to actually complete that.

So a related question: If a VDPAU state tracker is developed for Gallium, is it possible to do a pass-through to an appropriate library?

Basically the video application would interface with VDPAU, VDPAU would actually be a state tracker, but it would just pass all VP8 decoding duties on to the VP8 decoding library which would just use OpenCL to do the work?

It isn't the most efficient way of doing things (VDPAU state tracker -> libvpx -> OpenCL state tracker -> TGSI), but it would possibly ease the initial development burden, since someone wouldn't also have to bring up a codec-specific video decoder at the same time they do the VDPAU work.

Then, any codecs which have OpenCL/GLSL implementations available could be quickly brought up in st/VDPAU, and in the future pure Gallium versions could be made if performance is an issue.

So a related question: If a VDPAU state tracker is developed for Gallium, is it possible to do a pass-through to an appropriate library?

Basically the video application would interface with VDPAU, VDPAU would actually be a state tracker, but it would just pass all VP8 decoding duties on to the VP8 decoding library which would just use OpenCL to do the work?

It isn't the most efficient way of doing things (VDPAU state tracker -> libvpx -> OpenCL state tracker -> TGSI), but it would possibly ease the initial development burden, since someone wouldn't also have to bring up a codec-specific video decoder at the same time they do the VDPAU work.

Then, any codecs which have OpenCL/GLSL implementations available could be quickly brought up in st/VDPAU, and in the future pure Gallium versions could be made if performance is an issue.

But this would only work if we had an OpenCL st on galium, which we do not have unfortunately.