On Fri, 24 Jul 2020 15:13:19 +0100
Laurence Tratt <[email protected]> wrote:

> On Thu, Jul 23, 2020 at 09:56:39PM +0200, Marcus Glocker wrote:
> 
> Hello Marcus,
> 
> > We read the current value of the white balance temperature auto
> > control (since this gets set correctly during the reset), and just
> > reset it again on the next cam start up after the video stream has
> > been started? By that we avoid the video stream on/off dance when
> > using '-c'.  
> 
> I missed an obvious scenario :/ "video -c reset" then "use the webcam
> in a browser" (or ffplay or whatever). Depending on your webcam, this
> won't appear to have done a full reset in such a scenario?

That's true and basically out of our control I would say ...

Anyway, matthieu@ came up with an idea yesterday which I like and also
think would be the better approach finally:

Instead of introducing the CLI parameter controls in video(1), we could
introduce videoctl(1) in base, same as we have with audioctl(1).  This
also gives us the possibility to only display the current video
parameters.

For things like the auto white balance temperature control we could
implement tweaks easier there, like only turning the stream on before we
set back auto white balance temperature to 1.

I also want to sound this idea here to check if somebody has objections
with that approach?

> 
> Laurie
> 

Marcus

Reply via email to