From owner-freebsd-multimedia  Sun Mar  2 06:07:02 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id GAA12490
          for multimedia-outgoing; Sun, 2 Mar 1997 06:07:02 -0800 (PST)
Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id GAA12468
          for <multimedia@freebsd.org>; Sun, 2 Mar 1997 06:06:56 -0800 (PST)
Received: from ct.picker.com by whqvax.picker.com with SMTP;
          Sun, 2 Mar 1997 9:05:52 -0500 (EST)
Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1)
	id AA14544; Sun, 2 Mar 97 09:05:50 EST
Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4)
	id JAA18837; Sun, 2 Mar 1997 09:03:24 -0500
Message-Id: <19970302090324.40461@ct.picker.com>
Date: Sun, 2 Mar 1997 09:03:24 -0500
From: Randall Hopper <rhh@ct.picker.com>
To: Amancio Hasty <hasty@rah.star-gate.com>
Cc: multimedia@freebsd.org
Subject: Re: Restarting CONTINUOUS/updating during CONTINUOUS
References: <19970224210138.28839@ct.picker.com> <199703020404.UAA00713@rah.star-gate.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.61
In-Reply-To: <199703020404.UAA00713@rah.star-gate.com>; from Amancio Hasty on Mar 03, 1997 at 08:04:52PM
Sender: owner-multimedia@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Amancio Hasty:
 |In order to change the geometry , you must first stop the capture process.
 |In the case of the SVIDEO extensions , you must:
 |1.  first stop the capture process,
 |2.  issue the new SVIDEO parameters
 |3.  reissue a geometry call

 |>                     ioctl( video, METEORSVIDEO, &meteor_video );
 |
 |	*THIS WILL NOT WORK*

 |>                     ioctl( video, METEORSVIDEO, &meteor_video );
 |>                     ioctl( video, METEORSETGEO, &geo );
 |
 |Now this is more like it 8)

     The driver does a nice job of modeling the device as a set of capture
parameters that you set up first, and then you initiate capture.  

     To hide details associated with the ordering implicit in driver's
building of the RISC program, what about rebuilding the program from
scratch using the driver parameters each time a "parameter set" ioctl is
received.

     On that thread, which attributes can be set while capture is in
progress (i.e. during 1 frame, N frames, or continuous acquisitions), and
which required that the capture be stopped before they can be set?
(contrast, brightness, input, format, etc.)?  Browsing the driver, I see
any old CAP_MASK checks are commented out, except for those in the start
and stop capture flows (unless I missed something), but wanted to check
that what this implies is actually true in general.

Thanks,

Randall