Date: Tue, 3 Mar 1998 21:36:43 +0100 (MET) From: Luigi Rizzo <luigi@labinfo.iet.unipi.it> To: james@miller.cs.uwm.edu (Jim Lowe) Cc: hasty@rah.star-gate.com, multimedia@FreeBSD.ORG Subject: Re: Video ioctl interface Message-ID: <199803032036.VAA24273@labinfo.iet.unipi.it> In-Reply-To: <199803031830.MAA07082@miller.cs.uwm.edu> from "Jim Lowe" at Mar 3, 98 12:30:00 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > I was trying to make vic use the brightness/contrast/etc controls which
> > are available on the meteor&bt848 and ran across a few probolems in
> > grabber-meteor.cc, ui-grabber.tcl, and also brooktree848.c !
>
> I have some patches for vic which will allow access to the controls
> for the meteor card. Do you want these? I sent them into vic@ee.lbl.gov
well, a quick summary of the vic problems:
- as you pointed out for the x11-grabber, the grabber name should
match what the tcl code expects, i.e. "meteor" for the meteor, "x11"
for x11, etc. otherwise the control panel will not be shown.
The main problem in the meteor grabber is that it adds a unit number
to the name. A quick workaround i implemented was to attach the first
one only. but people like amancio with tons of bt848 in his machine
this might be a problem :) and the fix is add calls lile
proc build.meteor1 w { build.meteor w } ;
proc build.meteor2 w { build.meteor w } ;
proc build.meteor3 w { build.meteor w } ;
in ui-grabber.tcl
- the ui-grabber.tcl you sent me has meteor and bktr panels mapped to
slicvideo, but the command names are different so i had to modify
them. on top of this there is the aforementioned problem of bt848
controls not accessible via the grabber device, and additionaly some
signed/unsigned thing which make the luminance and perhaps other
controls behave rather oddly.
> quite some time ago, but I don't think there has been a recent release of vic.
you bet... as a matter of fact, if only we (I mean people like you,
amancio, bill fenner, ...) could put together all the modifications we
have, it sure would came out a much improved version of vic.
e.g. one thing i don't like is some controls which are on the main menu
while they would be quite useful on the main windows.
> Yes, having the mixer (or control) capability would be a nice feature.
> There is always the problem of when to reset back to default values, but
> I suppose that could be solved by keeping an open count. The audio
or by adding a 'reset' command to the mixer.
> drivers seem to just leave whatever the last value of the mixer was.
this was also true in voxware, i think, and i asked amancio to
implement the same thing for the audio section of the bt848.
My idea is, if there a device that can be set and then you can forget
about it, there is no much point in forcing the user to keep it under
control of a process which does nothing.
devices of this kind are, in my opinion, all those who do not interfere
with the main digital data paths, e.g. audio mixer and sources/sinks,
home automation stuff, etc.
> I am not certain this is the correct thing to do. It makes debugging
> problems difficult if you don't have a common starting point.
the problem is only for the mixer. in my view, all devices using
cpu/memory/internal buses must be controlled by some process and shut
down on close.
> As Amancio suggested, a common multimedia interface for these devices
> would be very useful. I will try and dig up that old frame work we
> discuss some time ago and maybe we can work that into something
> useful. Do you think that old frame work is a reasonable starting
> point?
maybe... i don't remember the details well but have the mails archived.
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803032036.VAA24273>