From owner-freebsd-multimedia Fri May 30 11:20:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00394 for multimedia-outgoing; Fri, 30 May 1997 11:20:14 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA00383 for ; Fri, 30 May 1997 11:20:05 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id TAA20995; Fri, 30 May 1997 19:45:56 +0200 From: Luigi Rizzo Message-Id: <199705301745.TAA20995@labinfo.iet.unipi.it> Subject: Re: bt848 status, comments and diffs To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 30 May 1997 19:45:55 +0200 (MET DST) Cc: multimedia@freebsd.org In-Reply-To: <199705301551.IAA00399@rah.star-gate.com> from "Amancio Hasty" at May 30, 97 08:51:11 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-multimedia@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >From The Desk Of Luigi Rizzo : > > > The source _frame_ rate is always 30 (25 for PAL), the source > > _field_ rate is always 60 (50). Now the manual page seems to confuse > > fields and frames, which makes tests necessary to get the correct > > interpretation :) > > Well, tests over here have shown that for NTSC the source frame rate > is 30 or 60. I will have to test a little bit more tonite when I get > home . It's a matter of definitions of course. In the broadcast video language, a "frame" is made of two "fields", interlaced. Now, our interface (ioctl()) to the meteor/bktr video grabber only lets you ask for: a) odd+even fields, interlaced; this is 30 different pictures (which are full frames) per second; b) odd fields only; call them frames or fields, this is 30 different pictures per second; c) even fields only; this is 30 different pictures per second; It is fine to me to allow a video mode which lets you get d) any single field (odd or even); this gives you 60 different pictures per second; it's just that I cannot see how to differentiate between a) and d) when asking a scaled (say, 320x240) sequence. To tell the truth, in /sys/i386/ioctl_meteor.h there is a #define METEOR_FIELD_MODE 0x80000000 /* Field cap or Frame cap */ flag, but it is never used, either in the meteor or in the brooktree driver. In other words, if you are getting 30 pictures per second, interlaced, when requesting odd+even fields at 640x480 (or perhaps even down to some smaller size, say 328x248), I don't see why you should suddenly get 60 pictures per second just because you reduced the scaling to 320x240. Sounds like a very odd interaction between image size and frame rate, and frankly, even if the previous drivers acted this way, I prefer the picture rate to stay the same, no matter how I scale the image! 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/ _____________________________|______________________________________