Talk:Autoexposure - Revision history

Alexlp: /* I think "Exposure" parameters in the adminweb.html has a bad name. I propose another name - "Shutter" ( The time an image is exposed). */

2005-12-17T13:43:16Z

I think "Exposure" parameters in the adminweb.html has a bad name. I propose another name - "Shutter" ( The time an image is exposed).

← Older revision		Revision as of 13:43, 17 December 2005
Line 31:		Line 31:

	== I think "Exposure" parameters in the adminweb.html has a bad name. I propose another name - "Shutter" ( The time an image is exposed). ==		== I think "Exposure" parameters in the adminweb.html has a bad name. I propose another name - "Shutter" ( The time an image is exposed). ==
			--[[User:Alexlp\|Alexlp]] 07:43, 17 December 2005 (CST)

85.202.197.95 at 13:41, 17 December 2005

2005-12-17T13:41:21Z

← Older revision		Revision as of 13:41, 17 December 2005
Line 28:		Line 28:

	How to run autoexposure when php/perl-script get image from camera with some options???		How to run autoexposure when php/perl-script get image from camera with some options???


			== I think "Exposure" parameters in the adminweb.html has a bad name. I propose another name - "Shutter" ( The time an image is exposed). ==

218.1.46.46: autoexposure, static images and web-scripting

2005-12-09T12:49:57Z

autoexposure, static images and web-scripting

← Older revision		Revision as of 12:49, 9 December 2005
Line 24:		Line 24:

	--[[User:Andrey.filippov\|Andrey.filippov]] 21:27, 29 November 2005 (CST)		--[[User:Andrey.filippov\|Andrey.filippov]] 21:27, 29 November 2005 (CST)

			== autoexposure, static images and web-scripting ==

			How to run autoexposure when php/perl-script get image from camera with some options???

Andrey.filippov: /* Autoexposure working */

2005-11-30T03:27:25Z

Autoexposure working

← Older revision		Revision as of 03:27, 30 November 2005
Line 22:		Line 22:
	1 - Web interface control for the autoexposure (on/off, parameters, monitoring). Monitoring - it will be useful to have exposure and frame rate status update on the main page (i.e. once a second). Current exposure both as absolute time and a fraction of the frame period (maybe just as bar indicator, not numeric percents). When the streamer is running it is also nice to the it status and frame rate (in percents of the sensor frame rate - to see if any frames are dropped). It also might be as a variable length barm not a number.		1 - Web interface control for the autoexposure (on/off, parameters, monitoring). Monitoring - it will be useful to have exposure and frame rate status update on the main page (i.e. once a second). Current exposure both as absolute time and a fraction of the frame period (maybe just as bar indicator, not numeric percents). When the streamer is running it is also nice to the it status and frame rate (in percents of the sensor frame rate - to see if any frames are dropped). It also might be as a variable length barm not a number.
	2 - Plot histograms into a small (i.e. 256x256) png file in the camera when periodically requested by the web page - watching live histogram (as standard in many cameras now) can be useful not just for the customers, but for developing/testing automatic exposure/gain/iris adjustment algorithms.		2 - Plot histograms into a small (i.e. 256x256) png file in the camera when periodically requested by the web page - watching live histogram (as standard in many cameras now) can be useful not just for the customers, but for developing/testing automatic exposure/gain/iris adjustment algorithms.

			--[[User:Andrey.filippov\|Andrey.filippov]] 21:27, 29 November 2005 (CST)

Andrey.filippov at 03:27, 30 November 2005

2005-11-30T03:27:07Z

← Older revision		Revision as of 03:27, 30 November 2005
Line 1:		Line 1:
			== preface ==
	As it is not just automatic exposure adjustment but .. (can not find - I already wrote that somewhere)		As it is not just automatic exposure adjustment but .. (can not find - I already wrote that somewhere)
	I suggest making some interpreter of the automatic brightness adjustment scripts - with many adjsutable parameters and image conditions/goals it is probably not possible to have a one-size-fits-all adjustment algorithm.		I suggest making some interpreter of the automatic brightness adjustment scripts - with many adjsutable parameters and image conditions/goals it is probably not possible to have a one-size-fits-all adjustment algorithm.

Andrey.filippov: Autoexposure working

2005-11-30T03:24:46Z

Autoexposure working

← Older revision		Revision as of 03:24, 30 November 2005
Line 12:		Line 12:

	--[[User:Andrey.filippov\|Andrey.filippov]] 00:34, 24 November 2005 (CST)		--[[User:Andrey.filippov\|Andrey.filippov]] 00:34, 24 November 2005 (CST)

			== Autoexposure working ==

			Today I tried the code for the basic autoexposure that Spectr made and it really works - feature long waited by us and our customers.

			So now it will be great to see the following follow-up features to be implemented too:

			1 - Web interface control for the autoexposure (on/off, parameters, monitoring). Monitoring - it will be useful to have exposure and frame rate status update on the main page (i.e. once a second). Current exposure both as absolute time and a fraction of the frame period (maybe just as bar indicator, not numeric percents). When the streamer is running it is also nice to the it status and frame rate (in percents of the sensor frame rate - to see if any frames are dropped). It also might be as a variable length barm not a number.
			2 - Plot histograms into a small (i.e. 256x256) png file in the camera when periodically requested by the web page - watching live histogram (as standard in many cameras now) can be useful not just for the customers, but for developing/testing automatic exposure/gain/iris adjustment algorithms.

Andrey.filippov at 06:34, 24 November 2005

2005-11-24T06:34:38Z

← Older revision		Revision as of 06:34, 24 November 2005
Line 10:		Line 10:
	# range parameter is allowed to change before failure is reported		# range parameter is allowed to change before failure is reported
	# results are provided to the client javascript that controls the overall process		# results are provided to the client javascript that controls the overall process

			--[[User:Andrey.filippov\|Andrey.filippov]] 00:34, 24 November 2005 (CST)

Andrey.filippov at 06:34, 24 November 2005

2005-11-24T06:34:08Z

← Older revision		Revision as of 06:34, 24 November 2005
Line 2:		Line 2:
	I suggest making some interpreter of the automatic brightness adjustment scripts - with many adjsutable parameters and image conditions/goals it is probably not possible to have a one-size-fits-all adjustment algorithm.		I suggest making some interpreter of the automatic brightness adjustment scripts - with many adjsutable parameters and image conditions/goals it is probably not possible to have a one-size-fits-all adjustment algorithm.
	What syntax to use so it will be intuitive, and easy to interpret?		What syntax to use so it will be intuitive, and easy to interpret?
			--[[User:Andrey.filippov\|Andrey.filippov]] 00:34, 24 November 2005 (CST)

			OK - this can probably be solved in the following way:

			# at each given moment only on of the parameters will be adjusted - exposure, gains, "curves" (digital gain) or (later) iris
			# some flexibility to define goal function and hysteresis ("don't care" region)
			# range parameter is allowed to change before failure is reported
			# results are provided to the client javascript that controls the overall process

Andrey.filippov at 05:51, 24 November 2005

2005-11-24T05:51:09Z

New page

As it is not just automatic exposure adjustment but .. (can not find - I already wrote that somewhere)
I suggest making some interpreter of the automatic brightness adjustment scripts - with many adjsutable parameters and image conditions/goals it is probably not possible to have a one-size-fits-all adjustment algorithm.
What syntax to use so it will be intuitive, and easy to interpret?