supplierdeeply

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

  • 82 Replies
  • 12200 Views
Advertisements
Version 0.25 uploaded to the first post.

Is there any limitation about number of parameters?  ;)

Would be interesting to have an option in parameters, start_hour=-1 than start_min and start_sec are not seen.
For beginners it might be helpful to have a rawopint version with a simple UI...


*

Offline reyalp

  • ******
  • 11542
Is there any limitation about number of parameters?  ;)
CHDK only looks at the first 4 KB of the script. So rawopint is getting fairly close at ~3.3 KB

Quote
Would be interesting to have an option in parameters, start_hour=-1 than start_min and start_sec are not seen.
So, a scripting language for the script menu?  :D

One thing I would like to do is to add more types to the CHDK menu system. So you could have a shutter speed input with the same UI as the CHDK override, zoom that knows the cameras actual zoom range, time in one field of hh:mm:ss etc.

That would make it easier to understand and more compact.
Quote
For beginners it might be helpful to have a rawopint version with a simple UI...
Yes, but I'm not sure which ones to remove, and I don't want to maintain even more versions...

The other thing I've thought about is making a tool to generate the configuration offline.
Don't forget what the H stands for.

So, a scripting language for the script menu?  :D

Just a sub menu…

Yes, but I'm not sure which ones to remove,

I have some rawopint versions with different UI. I never removed the option; I put them as constants in beginning of script. For me that's okay.

I couple of parameters I calculate like Max Tv
Interval >= 4s; Max Tv = Interval - 2s
Interval < 4s  Max Tv = Interval /10

The most important parameter which I normally use is shots, interval, max ev change, ISO min/max, over threshold / weight, display mode and waring LED.
For threshold, limit and weight I use in 99% defaults.


I don't want to maintain even more versions...

I can understand that well…

*

Offline reyalp

  • ******
  • 11542
Duplicate HDMI related post removed. See https://chdk.setepontos.com/index.php?topic=13481.0
Don't forget what the H stands for.


Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #74 on: 10 / August / 2018, 02:15:41 »
Here's one of my attempts at the last lunar eclipse. Unfortunately, the moon is much overexposed in the end. Since the parameters probably did not set correctly…


Especially for such recordings, there should be a simpler solution. For example, I would allow -1 for the Overexposure threshold. In this case, the overexposure would have the highest priority and the exposure would always have to be reduced. That would be similar then what lapser has suggested with his regulation on pmax.

*

Offline reyalp

  • ******
  • 11542
Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #75 on: 08 / September / 2018, 22:26:35 »
edit:
It seems ND control may fail in quick mode on some cameras.
From https://chdk.setepontos.com/index.php?topic=13228.msg138067#msg138067 ND control in "quick" should work on ND-only cameras (because rawopint sets the Av propcase), but not cameras with ND + Iris.
Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 11542
Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #76 on: 10 / September / 2018, 16:17:52 »
Additionally I had a chance to test a EOS M3 from a friend.

Take care about continuous mode of M3. The camera limits this mode to 1000 shoots!
It occurs to me that it would be possible to release shoot_full every 999 shots. There might be a relatively long gap if it spends time flushing the buffer.
Don't forget what the H stands for.

Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #77 on: 11 / September / 2018, 03:03:33 »
It occurs to me that it would be possible to release shoot_full every 999 shots.

I have already thought about that. That would be a good idea precisely because the M3 always opens and closes its aperture in quick mode.

There might be a relatively long gap if it spends time flushing the buffer.

The time at the M3 is quite long. But better a big gap at a break off. I would not do that in general, but over an option.

Using the aperture as well for time-lapse would be a great idea. Including ND we had a 4 way holy grail!
The question is whether you first open the aperture or the ND (at a sunset). Here is the procedure for a 3 way holy grail. 
https://lrtimelapse.com/tutorial/true-holy-grail-auto-ramping/


*

Offline Mlapse

  • **
  • 58
  • A480 A490 S95
Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #78 on: 22 / September / 2018, 18:07:02 »
I just tested this script and I am really impressed with the quality of the night shots, they look much crisper than with canon's settings.

Is it possible to use the same reference shot for every time the camera starts or does it always start with making a reference shot and optimise from there?
« Last Edit: 22 / September / 2018, 18:28:14 by Mlapse »

*

Offline reyalp

  • ******
  • 11542
Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #79 on: 22 / September / 2018, 19:16:06 »
Is it possible to use the same reference shot for every time the camera starts or does it always start with making a reference shot and optimise from there?
I'm not really sure what you mean.

The first exposure is based on whatever the Canon firmware would have used, either auto or manual. I think CHDK menu overrides should work too, but not sure it has been tested.

For every subsequent shot, it analyzes the raw data of the preceding shot and calculates a target exposure that would result in the scene being "perfectly" exposed as defined by the script options.

The target exposure calculation is essentially deterministic, i.e. target = f(scene), independent of Canon settings or anything that happened before. However, the shot-to-shot change is limited to keep the results smooth. This based on the change in the preceding exposures and how large a change is needed to achieve the target.

The result of this is that the script takes some time to "settle" from the initial, Canon firmware calculated shot to the script calculation. For Canon auto exposure under normal lighting, the change usually isn't big. If you start at night, or used manual settings, it could be quite large.

Because the exposure is calculated based on the previous shot, the script works best for fast intervals and/or scenes that don't change too rapidly.

It would be possible to make the script use a throw-away initial shot to meter the scene, but I'm loath to add more options unless someone has a real use for them.
Don't forget what the H stands for.

 

Related Topics