From owner-freebsd-multimedia Fri Apr 17 00:44:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28803 for freebsd-multimedia-outgoing; Fri, 17 Apr 1998 00:44:13 -0700 (PDT) (envelope-from owner-freebsd-multimedia@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA28609 for ; Fri, 17 Apr 1998 07:43:45 GMT (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA08348; Fri, 17 Apr 1998 08:04:00 +0200 From: Luigi Rizzo Message-Id: <199804170604.IAA08348@labinfo.iet.unipi.it> Subject: Re: vic tuner patches work great, mostly To: dwhite@resnet.uoregon.edu Date: Fri, 17 Apr 1998 08:04:00 +0200 (MET DST) Cc: multimedia@FreeBSD.ORG In-Reply-To: from "Doug White" at Apr 16, 98 04:34:54 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > TSIA. The brightness is a bit wacky - it rolls over in the middle of the > slider, from bright to dark. i know. And the funny thing is, it works fine with the meteor. I am pretty sure it is some signed/unsigned problem in interpreting the value. Either the meteor or the brooktree should be fixed (and I am afraid that probably the meteor will have to be changed, since too many people use fxtv... > BTW, what does `Thre' mean? It's some sort of threshold on quality but > I'm not sure. right. The routine in vic to determine if a block has changed computes a partial difference and then compares it with a threshold. In the original sources (grabber.h ?) the threshold is fixed at 48, I wanted to experiment a little bit with different ones, because in some situations (e.g. poor lighting, or neon lights) the output of the camera can be very noisy and it pays to raise the threshold. > And someone needs to fix the vic port -- it blows up if the qcam-grabber > is built on my machine. I have to go in and hand-remove it from the > build. is this after the qcam driver removal in 2.2.6 ? I am still having the qcam driver compiled in into 2.2.1 and it seems to work. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message