Date: Tue, 07 Oct 1997 17:27:43 -0700 From: Amancio Hasty <hasty@rah.star-gate.com> To: Randall Hopper <rhh@ct.picker.com> Cc: multimedia@freebsd.org Subject: Re: [video] bktr clipping Message-ID: <199710080027.RAA07470@rah.star-gate.com> In-Reply-To: Your message of "Tue, 07 Oct 1997 20:05:01 EDT." <19971007200501.26657@ct.picker.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>Unobscured and PartiallyObscured (i.e. let the X server clip when clipping >is required). I like that solution as for X doing the right thing for our scenario (hardware clipping) it does not . The best approach so far is to take the whole video capture process to the X server and there I can take care of the exposure problems . However, there is only one gotcha : how can I tell the server to process the video stream bear in mind that the X server is event driven so I can't kick off a routine and expect it to do single capture or continous capture without going thru the event loop in the X server. Cheers, Amancio >From The Desk Of Randall Hopper : > Amancio, it's probably not worth your time to juice up the driver > clipping code at this point. I haven't yet found a decent event-driven way > to keep an exposed region definition up-to-date with X (polling the X > server's window list every 10th of a second ain't decent IMO). News, list, > FAQ, and O'Reilly searches thus far haven't turned up anything > satisfactory. > > I've got a question posted to c.w.x.i386unix and c.windows.x so we'll > see if someone else has a trick up their sleeve. > > If nothing else, I'll do the next best thing in the next version and > flip Fxtv in and out of XImages mode as the video window moves between > Unobscured and PartiallyObscured (i.e. let the X server clip when clipping > is required). > > Randall
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710080027.RAA07470>