From owner-freebsd-multimedia Sun Mar 15 14:23:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15979 for freebsd-multimedia-outgoing; Sun, 15 Mar 1998 14:23:00 -0800 (PST) (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 OAA15963 for ; Sun, 15 Mar 1998 14:22:55 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id VAA18760; Sun, 15 Mar 1998 21:54:59 +0100 From: Luigi Rizzo Message-Id: <199803152054.VAA18760@labinfo.iet.unipi.it> Subject: Re: Video ioctl interface To: rhh@ct.picker.com (Randall Hopper) Date: Sun, 15 Mar 1998 21:54:59 +0100 (MET) Cc: hasty@rah.star-gate.com, james@miller.cs.uwm.edu, multimedia@FreeBSD.ORG In-Reply-To: <19980315134210.12544@ct.picker.com> from "Randall Hopper" at Mar 15, 98 01:41:51 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 1) Are we sure it's really worth the effort at this point? i think so. there are (luckily) not too many apps using the old API, and the programmers of those apps are still around... > 2) I'd like us convert to this model: > > Applications -> Capture Library -> Capture Devices > Applications -> Tuner Library -> Tuner Devices > > All device I/F abstracted through a common userland library/libraries. this is a question of personal preference of course, but i am generally against libraries unless they provide some significant functionality (i.e. they do more than shuffling parameters), and function names are reasonably short... Another obstacle could be that a too high level library makes porting to other systems harder. I mostly agree with other items... > 11) Remove any arbitrary ordering requirements for setting up parameters > before capture (as much as possible) > - Parm set calls just test whether parm is valid for its own range > - Start capture determines whether the entire parameter set is > valid together to start capture (i.e. inter-parameter checks), > and if so, configures the card and starts capture i tried to achieve this same goal with the audio driver :) > 12) API to parse Teletext and Intercast data, and to attribute the data nicely > so all apps don't know how to parse this stuff. Use generic attribute > and attribute value lists. for teletext it might be reasonably easy, but intercast format... as far as i know is proprietary and undocumented... Plus, there have been applications for along time now that use VBI only as a raw carrier for the most disparate applications/formats, so in the end i don't know how general such a library could be. 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