rawopint.lua: Fast, accurate intervalometer with raw exposure metering - page 10 - Completed and Working Scripts - CHDK Forum  

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

  • 126 Replies
  • 18709 Views
Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #90 on: 05 / January / 2019, 14:37:03 »
Advertisements
Just tried it with my M3, see the same think, never notice this before…
Can’t see it in some older runs…
I have also problems with upload csv files with worked in the past…
« Last Edit: 05 / January / 2019, 14:42:46 by c_joerg »
M100 100a, M3 101a, 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), 2*S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline Mlapse

  • ***
  • 184
  • A480 A490 S95 M10
Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #91 on: 05 / January / 2019, 14:47:33 »
Quote
I have also problems with upload csv files with worked in the past…
ah, but an image says more than a thousand words. you did one run, so no restart. 5 frames, looks the same to me too. if you would have restarted that whole floating away proces would happen again.
setting: M, same script settings as last csv
so i did 4 runs 2 with night shots (restarted at 26), then 2 in a cabinet with a light. (some 75 in total..guess where i restarted) i hope the slight variance in the "flat" period is due to 50hz lightsource..but can't be sure.
« Last Edit: 05 / January / 2019, 16:37:26 by Mlapse »
frustration is a key ingredient in progress

*

Offline reyalp

  • ******
  • 11896
Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #92 on: 05 / January / 2019, 17:26:05 »
Or am I chasing an impossible thing here, because the whole metering concept is different?
There will probably always be some difference.

Have you tried the "Use initial Ev as target" option? This should make the script try to keep the overall brightness of the scene similar to the first shot. There will still likely be some variation, but in scenes that aren't too extreme (e.g lots of under/over exposure, or big variation across the scene) it should be pretty close.

Edit: If you use BV/Ev shift with this setting, it should probably be set to "First"

Regarding posting CSVs, forum settings were changed a while back to only allow whitelisted extensions. I've asked acseven to add .csv.

« Last Edit: 05 / January / 2019, 17:29:16 by reyalp »
Don't forget what the H stands for.

*

Offline Mlapse

  • ***
  • 184
  • A480 A490 S95 M10
Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #93 on: 06 / January / 2019, 03:02:23 »
i tried bv/ev set at first and/or initial ev as target, but it did not help with this.
Quote
There will probably always be some difference.
it took me a bit longer, but i suppose you are right.
thanks for the help, could have been mucking with settings for days.
frustration is a key ingredient in progress


Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #94 on: 06 / January / 2019, 03:32:51 »
Have you tried the "Use initial Ev as target" option?
I always used this as default “false”.

This should make the script try to keep the overall brightness of the scene similar to the first shot.
There will still likely be some variation,
I never notice a big variation between a pre-shot and the first image with rawopint.
I made just a test with G1x and M3 with a gray image.
The pre-shot and the first image with rawopint have the same exposure, so no differences even with “Use_initial_Ev_as_target” = false.

But on M3 meter96 is around -96 and on G1x around 0. On the M3 the script increase now exposure to bring meter96 to 0.
If I watch the Histograms in Lightroom, the Histogram from G1x is always around the center. On M3 the Histogram of the first picture is in the center and on the last picture more to the right.
If I do an auto exposure in Lightroom, then Lightroom sets the exposure to around -1EV for the last image.

I thing, the neutral value on the M3 is around on step to high (may be also on M10).That makes the pictures 1 step higher exposed.

Regarding posting CSVs, forum settings were changed a while back to only allow whitelisted extensions. I've asked acseven to add .csv.
I would be very grateful for that…
« Last Edit: 06 / January / 2019, 07:40:02 by c_joerg »
M100 100a, M3 101a, 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), 2*S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline Mlapse

  • ***
  • 184
  • A480 A490 S95 M10
Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #95 on: 06 / January / 2019, 06:04:03 »
i noticed this behaviour first time on my s95, and i also have this with my a480 and a490. so it is not limited to the m series alone.
and it depends on light conditions how obvious it is, if i do a night shoot that is very or a bit more than very underexposed you can hardly tell that it gets brighter during the first few shots. for me it is most visible with clouded days and not overly sunny days.
« Last Edit: 06 / January / 2019, 06:17:09 by Mlapse »
frustration is a key ingredient in progress

Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #96 on: 06 / January / 2019, 06:48:52 »
i noticed this behaviour first time on my s95, and i also have this with my a480 and a490. so it is not limited to the m series alone.
On my S110 it’s a little bit different. If I do a pre-shot in AV (I only use AV) then the exposure is around 1/2EV higher. That can be seen on the histogram which is a little bit right. The script brings the histogram exact to the middle. This is different to what I descript in Reply #94.

But on all my cams: if I do a pre-shot in AV, the first picture with rawopint has the same exposure as the pre-shot. Then the script changes exposure.
You should run the script in AV mode. Then I would change the exposure correction in the Canon Menu.

and it depends on light conditions how obvious it is, if i do a night shoot that is very or a bit more than very underexposed you can hardly tell that it gets brighter during the first few shots.
Of course, if you set underexposure or overexposure control, the script has to change it to your settings.
M100 100a, M3 101a, 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), 2*S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline Mlapse

  • ***
  • 184
  • A480 A490 S95 M10
Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #97 on: 06 / January / 2019, 07:35:20 »
Quote
Of course, if you set underexposure or overexposure control, the script has to change it to your settings.
that is not what i wanted to point out, it still corrects itself. it is just less visible because it stayes fairly dark.
you can see that on the jpg a few posts back, if there is underexposure correction takes 4-5 frames. at proper exposure that correction takes 9-10 frames
« Last Edit: 06 / January / 2019, 07:42:53 by Mlapse »
frustration is a key ingredient in progress


*

Offline reyalp

  • ******
  • 11896
Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #98 on: 06 / January / 2019, 20:44:20 »
I stop the script by pressing the shutter(the only way on the m10)
You should be able to use MENU to stop the script gracefully. The M10 has a menu key, so if this doesn't work, there's a bug somewhere.

edit:
csv upload should be fixed.
« Last Edit: 06 / January / 2019, 21:01:41 by reyalp »
Don't forget what the H stands for.

*

Offline Mlapse

  • ***
  • 184
  • A480 A490 S95 M10
Re: rawopint.lua: Fast, accurate intervalometer with raw exposure metering
« Reply #99 on: 07 / January / 2019, 03:06:30 »
Quote
You should be able to use MENU to stop the script gracefully. The M10 has a menu key, so if this doesn't work, there's a bug somewhere.
after some testing, it does work, with ultimate if i press the menu key it can take up to a few seonds before it's processed, with rawopint it seems to only respond just after a shot has been made.
« Last Edit: 07 / January / 2019, 06:12:30 by Mlapse »
frustration is a key ingredient in progress

 

Related Topics