[mythtv] RE: [mythtv-commits] mythtv commit: r7569 by danielk
john.p.harvey at btinternet.com
Sun Dec 4 22:35:27 UTC 2005
I was looking at this to see if we could use the chromaosd stuff for
the PVR 350 which only supports Xv not XvMC. The main reason is that the osd
drawn by X is much nicer than the blended Xv one which flickers horribly.
The attached patch appears to work for me.
Is there any reason to not implement it for Xv as well, especially since
enabling it in the settings table tries to use it but it breaks horribly.
> -----Original Message-----
> From: mythtv-commits-bounces at mythtv.org [mailto:mythtv-commits-
> bounces at mythtv.org] On Behalf Of mythtv at cvs.mythtv.org
> Sent: 25 October 2005 00:07
> To: mythtv-commits at mythtv.org
> Subject: [mythtv-commits] mythtv commit: r7569 by danielk
> Author: danielk
> Date: 2005-10-24 23:06:36 +0000 (Mon, 24 Oct 2005)
> New Revision: 7569
> Changeset: http://cvs.mythtv.org/trac/changeset/7569
> References #512.
> This implements a basic chromakey OSD.
> For it to be enabled, you must have this in your
> xorg.conf "Devices" section:
> Option "XvmcUsesTextures" "false" # use 3d engine for overlays
> And you have to insert a "UseChromaKeyOSD","1",hostname setting in
> the settings table.
> This currently makes no claim to efficiency, this clears the a
> buffer to the chromakey color w/borders, and then plops the OSD
> on top of it; creating an RGB OSDSurface or creating a specialized,
> chromakey painting, OSD blend function would probably be much
> faster. What this does make a claim to is not being too disruptive
> to the rest of the code.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 529 bytes
Desc: not available
Url : http://mythtv.org/pipermail/mythtv-dev/attachments/20051204/3b05925c/xv_chromaosd.obj
More information about the mythtv-dev