From owner-freebsd-multimedia Mon Mar 23 03:55:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29367 for freebsd-multimedia-outgoing; Mon, 23 Mar 1998 03:55:53 -0800 (PST) (envelope-from owner-freebsd-multimedia@FreeBSD.ORG) Received: from jmurray.async.vt.edu (root@207-172-52-217.s217.tnt1.brd.erols.com [207.172.52.217]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29359 for ; Mon, 23 Mar 1998 03:55:49 -0800 (PST) (envelope-from jmurray@jmurray.async.vt.edu) Received: from jmurray.async.vt.edu (jmurray@localhost [127.0.0.1]) by jmurray.async.vt.edu (8.8.5/8.7.3) with ESMTP id GAA23442; Mon, 23 Mar 1998 06:55:47 -0500 (EST) Message-Id: <199803231155.GAA23442@jmurray.async.vt.edu> X-Mailer: exmh version 2.0zeta 7/24/97 To: Randall Hopper cc: John Murray , multimedia@FreeBSD.ORG Subject: Re: fxtv problems In-reply-to: Your message of "Sun, 22 Mar 1998 12:28:21 EST." <19980322122821.15635@ct.picker.com> From: John Murray Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Mar 1998 06:55:42 -0500 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 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