On Tue, 2005-02-15 at 14:59 -0500, Isaac Richards wrote: > > Guess I'll have to remove the vsync code from the Xv/XvMC output at well.
Well, I will confess to not knowing much about X11/Xv and vsync because I was always told that the X11 protocol provided no means for an application to be notified when the vsync pulse happened. Maybe that was crap. Maybe it wasn't at the time and something has happened to change that. Regardless, the Xv output on my framebuffer/matroxset mangled G400 looks nowhere near as good as DirectFB with it's direct CRTC2/TV-out support. Before you go taking this the wrong way again, this is not a criticism of MythTV. I understand that MythTV just uses a toolkit and the toolkit renders on some graphics device. It's just disappointing that the toolkit is not more flexible in what it will render on. Like I said, even SDL would suffice and it's pretty widely used. But Isaac, instead of making quips like "Guess I'll have to remove..." why not try a little educating instead. I am looking in the videoout_xv.cpp source but can't see anything that relates to the myth receiving notification of the vsync. Where does that happen? If I learn a little I might hack a little. I have some QT on DirectFB source on it's way to me right now from the author of the wonderful directfb G400 support so I might be able to help out here if I can just learn a bit about myth. b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
