[mythtv] MythUI OSD branch and the way forward

[Gavin Hurlbut]

On Tue, Mar 23, 2010 at 12:04 AM, Mark Kendall <mark.kendall at gmail.com> wrote:
> Option 6 - Drop XVideo/XvMC support and standardise around OpenGL
>
> There are numerous ways of approaching this but I would clean up the
> current OpenGL video code, standardise around GLSL for shader support
> (UI effects, deinterlacing, colorspace conversion), remove OpenGL code
> based around immediate mode (for OpenGL ES compatability), provide
> colourspace conversion only support for ARB_fragment_program (for
> older OpenGL implementations which will probably not be capable of
> using any advanced video shaders anyway) and use OpenGL as the
> 'frontend' for VDPAU.
>
> It's probably worth dropping Direct3D support as it offers nothing
> above and beyond OpenGL and simply represents duplicated code (esp.
> around supporting HLSL).
>
> There is then also a separate debate to be had around the Qt painter....
>
> Option 6 - Drop support in stages
>
> Move to Option 2 for the 0.24 release and Option 6 for 0.25.
>
> Option 7 - Maintain a legacy branch
>
> Cut a stable 'Legacy' branch with XVideo support and move to Option 6
> for 0.24 (assuming it's ready). Provide X weeks/months/years of legacy
> support...

OK, I'm confused.. which Option 6 above were you planning on going forward with?

I'd like to put in a short word for support for VA API in your first
Option 6, whether above or below VDPAU.  This will give support to
several other chipsets, including the dreaded GMA500 that is in so
many tiny Atom boxes.  I have one here that I hope to get the frontend
code working with sometime after 0.23.  Obviously, I'd like to work
with whoever is necessary to make this happen, but I'm willing to do a
bunch of the heavy lifting on that.  I don't want to break your work,
of course :)

OpenGL does sound like a good methodology to me.