Date: Mon, 23 Mar 1998 06:55:42 -0500 From: John Murray <jmurray@vt.edu> To: Randall Hopper <rhh@ct.picker.com> Cc: John Murray <jmurray@vt.edu>, multimedia@FreeBSD.ORG Subject: Re: fxtv problems Message-ID: <199803231155.GAA23442@jmurray.async.vt.edu> In-Reply-To: Your message of "Sun, 22 Mar 1998 12:28:21 EST." <19980322122821.15635@ct.picker.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Sounds like the driver's never firing off a signal to indicate it's done > capturing a frame (no clue why). > > Ok, well first thing's first. If you haven't already, grab the latest > released versions of the bktr driver and Fxtv: > > ftp://rah.star-gate.com/pub/bt848.tar.gz > http://multiverse.com/~rhh/fxtv > > and see if you see the same result. Well I had the most recent drivers and fxtv so that wasn't a cause. > > If not, next thing: In Fxtv, put a printf at the top of the frame > completion signal handler (the driver issues this signal): > > static void TVCAPTUREFrameDoneSigHdlr() > { > + printf( "TVCAPTUREFrameDoneSigHdlr\n" ); > S_frame_done_count++; > #ifdef linux > > When you freeze a frame, run with direct video disabled, or capture movies, > you should see one printf per captured frame. My guess is, with your > current setup, you won't see this (again, no clue why yet). But this'll > help pin down whether it's a driver or an app bug. Well as you predictied that didn't do any thing. I didn't mention befare but running with direct video disabled dosn't work, but that seems fit with the other problems. -- John Murray - jmurray@vt.edu johns@tmbg.org - http://www.acm.vt.edu/~jmurray Unofficial Pritchard Hall Page->http://www.cslab.vt.edu/~jmurray/pritchard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803231155.GAA23442>