rawopint.lua: Fast, accurate intervalometer with raw exposure metering

  • 82 Replies
  • 14334 Views
Advertisements
This very timelapse appears to have been done with av=4.
Yes, that’s the reason of the stars. Overexposure and an aperture more than the lowest…
I did not set aperture, so probably I should set it to the lowest value for sky timelapse?
I think, there is no reason for sky timelapse to close the aperture. Typical, the first think what I am doing when I have too much light I use the internal ND.

Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #21 on: 02 / September / 2016, 10:40:53 »
Attached a log file from my SX50 with an Interval from 2.5s.
The run was only made with Canon RAW.
It looks like that the get_exp_count does not work correct at this run. I didn’t notice this before. Since I use the log file for deflicker, I had more notice about this.

For example, exp 46 (or 64, …) is twice in the log file and exp 47 is missing. But RAW File 47 is there. No RAW File is missing. This is happening about 30 times in around 300 pictures.

Update:
I attached another run from the SX50 without Errors (Moon run, also only RAW and Interval = 2,5s). This run was made in continues mode. I thought this also from the other run. EXP ist OK.
So the problem may be having something to do with the quick mode….
« Last Edit: 03 / September / 2016, 04:33:30 by c_joerg »

*

Offline reyalp

  • ******
  • 11583
Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #22 on: 03 / September / 2016, 13:21:02 »
It looks like that the get_exp_count does not work correct at this run. I didn’t notice this before. Since I use the log file for deflicker, I had more notice about this.
This sounds like the typical file counter problems we see on a number of cameras.  The CHDK "pause for filecounter" workaround is only enabled if CHDK raw or remote capture is enabled.

You may be able to work around this using the "raw hook sleep" option in the script. This adds a fixed delay before the log line (with the image number) is written to the log.

Quote
No RAW File is missing. This is happening about 30 times in around 300 pictures.
Missing files would only happen for CHDK raws: if the number isn't incremented in time, a file gets overwritten.
Don't forget what the H stands for.

Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #23 on: 03 / February / 2017, 01:47:21 »
I would like to take a time-lapse with the M3 and my EF-S 10-18. Unfortunately, the ISO does not work yet.

If I just want to change only the exposure time, does  the following workaround would help?

ISO manually to 100
Code: [Select]
ui_sv_target_mkt=100 "Target ISO"
ui_sv_max_mkt=100 "Max ISO"

and in the code:

Code: [Select]
if (ui_sv_target_mkt ~= ui_sv_max_mkt) then
  set_sv96(self.sv96)
end

and as well for the get_prop(props.SV) stuff to avoid error messages.


*

Offline reyalp

  • ******
  • 11583
Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #24 on: 03 / February / 2017, 02:08:29 »
I would like to take a time-lapse with the M3 and my EF-S 10-18. Unfortunately, the ISO does not work yet.
The fix in the port is probably very simple.
Quote
If I just want to change only the exposure time, does  the following workaround would help?

ISO manually to 100
Code: [Select]
ui_sv_target_mkt=100 "Target ISO"
ui_sv_max_mkt=100 "Max ISO"

and in the code:

Code: [Select]
if (ui_sv_target_mkt ~= ui_sv_max_mkt) then
  set_sv96(self.sv96)
end

and as well for the get_prop(props.SV) stuff to avoid error messages.
Without trying it, I think that should work. The exposure might be off somewhat, but it will be by a fixed amount, probably 2/3 of stop.
Don't forget what the H stands for.

Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #25 on: 11 / February / 2017, 12:45:29 »
I'm still trying to get rawopint on the M3 to run. Since the Black Level = 2047 is, I get however about 1EV over-exposed images.
I keep my G1x on a white monitor and start rawopint, then I get already with the first recording a neutral image (exposure metering medium-weighted). All other pictures will not be changed. So as I would expect.
If I do the same with the M3 (presumably also with the M10), then the first picture is also neutral. However, rawopint then regulates the following images to + 1EV.
I guess the problem is due to the neutral value of the M3 (rawop.get_raw_neutral). I have not really understood the calculation yet.
The cameras have the following values
Code: [Select]
M3 Black Level = 2047 White = 16K Neutral = 4197
G1x Black Level = 511 White = 16K Neutral = 2891
If I look into the rawopint log file, then it looks to me as if the neutral value of the M3 (around 3100) Close to the G1x.

I could probably work around the problem if I would set ev_shift to -1EV. However, I would like understand the stuff.

What I also do not understand how the M3 from a range of 2K - 16K more dynamics than the G1x with 512 - 16K. But this is a very different issue

« Last Edit: 11 / February / 2017, 13:19:21 by c_joerg »

*

Offline reyalp

  • ******
  • 11583
Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 11583
@reyalp
I still want a log for the battery temperature ;)
This is easy to add, but out of curiosity, what is it useful for?
Don't forget what the H stands for.


This is easy to add, but out of curiosity, what is it useful for?

What is the optical temperature useful for?
I find it interesting to know how the temperatures change over time. If I operate my cameras in the underwater housing they are already very hot. I have a run since the sensor temperature is above 80 degrees Celsius. During this run I would have already been interested in how warm the battery was. Maybe there is a battery temperature at which the camera turns off? I have some batteries that do not have a temperature sensor. Could it be dangerous to use these batteries at high temperatures?

I looks like, that my G1x, S110 und SX50 can run with an Interval from 1s (Only RAW, Tv < 0.01s) in continuous mode. I used my fastest SD card. It differs from card to card by around 200ms (All cards minimum class 10).  For save condition I would not go faster than 1.1s Interval.

 

Related Topics