From owner-freebsd-stable Sun Mar 22 07:03:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08903 for freebsd-stable-outgoing; Sun, 22 Mar 1998 07:03:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA08894; Sun, 22 Mar 1998 07:03:33 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Sun, 22 Mar 1998 10:01:58 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA23322; Sun, 22 Mar 98 10:01:55 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id KAA12630; Sun, 22 Mar 1998 10:01:29 -0500 Message-Id: <19980322100129.35396@ct.picker.com> Date: Sun, 22 Mar 1998 10:01:29 -0500 From: Randall Hopper To: Joao Carlos Mendes Luis , Amancio Hasty Cc: multimedia@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fxtv vs Stable Mail-Followup-To: Joao Carlos Mendes Luis , Amancio Hasty , multimedia@freebsd.org, stable@FreeBSD.ORG References: <199803220221.NAA18775@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803220221.NAA18775@godzilla.zeta.org.au>; from Bruce Evans on Sun, Mar 22, 1998 at 01:21:39PM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Joao Carlos Mendes Luis: |// /* If TDEC is on, may be a while before old trash gets written on */ |// if ( c->fps != c->fps_max ) |// memset( c->drv_buf, '\0', |// g.w * g.h * c->pix_geom_list[ c->pix_geom_idx ].Bpp ); | |Why do you need to clear the buffer ? I alluded to this in my last msg: |decimation is enabled. At that time, it clears out the driver buffer so |that you don't see a stale last frame from the last capture up until the |first frame of the requested capture finally comes along. "Fxtv" doesn't need to do it necessarily. It just needs to be done. Otherwise, the frame residing in the driver buffer for potentially up to a full second will be the one from the last capture, potentially minutes or hours old. A stale buffer is fine if app is processing the frame on interrupt, but when it knows there's no way it can keep up, having signals issues 30X/sec is pointless extra overhead just for bookkeeping the first frame. Better to just sample as fast as possible up to 30X/sec, and clear the buffer before starting. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message