Timing problems with "shoot_full_only" - page 4 - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: 1 2 3 [4]   Go Down

Timing problems with "shoot_full_only"

  • 34 Replies
  • 15308 Views
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: Timing problems with "shoot_full_only"
« Reply #30 on: 08 / December / 2012, 21:00:53 »
Advertisements
Quote from: lapser on 08 / December / 2012, 20:51:14
Quote from: philmoz on 08 / December / 2012, 18:52:05
Looks ok. My only concern is that the 'get_shot_count' name might confuse people in future, that it is somehow related to the total number of images taken by the camera, not just the number since last startup.
How about:
get_shot_counter()
get_raw_ready()
get_raw_count()
or my wife's name for it:
get_up_already()

get_session_shot_count()

or the Cobol version - get_shot_count_since_last_power_on() :)

Phil.
Logged
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)
*

Offline lapser

  • *****
  • 1093
Re: Timing problems with "shoot_full_only"
« Reply #31 on: 08 / December / 2012, 22:07:14 »
Quote from: philmoz on 08 / December / 2012, 21:00:53
get_session_shot_count()
That sounds like something the bartender would need before pouring you another drink.

How about:

get_shot_number()
It implies that it's not an actual count of anything. It's just a number.
(much easier for the bartender to understand, too)
Logged
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos
*

Offline lapser

  • *****
  • 1093
Re: Timing problems with "shoot_full_only"
« Reply #32 on: 08 / December / 2012, 22:21:57 »
I just tried my new code in continuous exposure mode on the G1X. It works perfectly, adjusting the exposure in between every shot, at over 2 shots per second! I added a check for continuous exposure mode and just leave shoot_full pressed the whole time.

The fastest I can get when releasing shoot_full_only after each shot is 1 shot per second.
Logged
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: Timing problems with "shoot_full_only"
« Reply #33 on: 08 / December / 2012, 22:31:59 »
Quote from: lapser on 08 / December / 2012, 22:21:57
The fastest I can get when releasing shoot_full_only after each shot is 1 shot per second.
Still better than was previously considered possible.    Will be interesting to try on other (less expensive) cameras.
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline lapser

  • *****
  • 1093
Re: Timing problems with "shoot_full_only"
« Reply #34 on: 08 / December / 2012, 23:54:51 »
Quote from: waterwingz on 08 / December / 2012, 22:31:59
Quote from: lapser on 08 / December / 2012, 22:21:57
The fastest I can get when releasing shoot_full_only after each shot is 1 shot per second.
Still better than was previously considered possible.    Will be interesting to try on other (less expensive) cameras.
Here's a link to the Powershot series where you can find the specs for any of them. The spec on the G1X is 1.9 shots per second continuous, and 2.4 for the SX260. The cheapest Elph 100 says it takes 3.4 shots per second. Maybe it has more to do with the size and weight of the mechanical shutter than the cost. But yes, it should be interesting.
http://www.usa.canon.com/cusa/consumer/products/cameras/digital_cameras

My code seems to be able to measure and change exposure between shots without slowing the camera down. It only takes about 10 msec to calculate according to my rough, tick_count measurements. I think I'm ok to optionally double the calculation time to be able to get a histogram of the entire picture, or a different specified area.

So time isn't an issue, but what about memory? The current shot_histo code allocates 1024 short int, or 2048 bytes. I'd need 4 times that for a full 12-bit histogram, and 4 times more for 14 bit.

Would it be acceptable to use 8K temporary memory instead of 2K? How about 32K? It would be faster to use int instead of short int. So is there 64K available for a histogram? It's only in use when a histogram is requested. You could get the shot_meter without using any extra memory.

Logged
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos
Pages: 1 2 3 [4]   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal