Date: Sat, 27 May 2000 22:46:24 -0400 From: Randall Hopper <aa8vb@nc.rr.com> To: multimedia@FreeBSD.ORG Subject: Re: TV Users - Let me bounce this off you Message-ID: <20000527224624.A31185@nc.rr.com> In-Reply-To: <392E231D.BA8C1519@rostock.zgdv.de>; from runge@rostock.zgdv.de on Fri, May 26, 2000 at 09:09:17AM %2B0200 References: <20000525210340.A44725@nc.rr.com> <392E231D.BA8C1519@rostock.zgdv.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Thomas Runge:
|Well, making complicated things esier is almost always a good idea :-)
|
|But it's necessary to specify a good API, which lets you make simple
|things easy, but doesn't stop you making more complicated tasks.
Agreed. If sufficient interest (and interested developers) popped up, that
was going to be the next thread. (Though doesn't look like we're going to
get critical mass for this one.)
|I didn't have a look into the Video4Linux API, but wouldn't it be
|a good idea to support that?
I did a quick browse of their docs, and AFAICT it's an app-driver
(i.e. userland-kernel) interface spec. It doesn't appear to abstract the
machinizations necessary for talking to X11 or for example. So the scope of
this userland driver would likely be a superset of whatever driver
interface is used, be it V4L/V4U or bktr.
Though you make a good point. If we're planning on switching the low-level
driver interface to V4U anytime, we should do that first so we don't need a
massive rewrite for yet another userland service built on top.
|And how about supporting multiple output sources?
Do you mean multiple capture cards in one machine? I'm not completely sure
I know what you mean, because doesn't bktr currently support that
(/dev/bktr{0,1,...}, /dev/tuner{0,1,...})?
--
Randall Hopper
aa8vb@nc.rr.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000527224624.A31185>