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

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

  • 174 Replies
  • 37845 Views
Advertisements
I update now to latest 1.6.0. Also, no problem with 12s.
Which Mode do you use? Flash?

Hmm.. strange..
I did the last view test in Av Mode (set in CHDKPTP, the Camera was in M Mode). I use AV mode for sunset and M mode for sunrise.

EDIT:

I changed the ui_raw_hook_sleep=9000 and now I was able to shoot up to exactly 20 without shut down and with 21 the camera again went off.

also with latest (g1x-100e-1.6.0-5910-full) same problem.
« Last Edit: 25 / May / 2021, 14:56:17 by dolomiti_timelapse »
If you want to see a sunset or sunrise of Dolomiti Val Gardena shot with CHDK visit
Telegram: t.me/DolomitiTimelapse
Instagram: dolomiti_timelapse

*

Offline c_joerg

  • *****
  • 1103
I changed the ui_raw_hook_sleep=9000 and now I was able to shoot up to exactly 20 without shut down and with 21 the camera again went off.

I am also wonder that I doesn't have to change ui_raw_hook_sleep.
Maybe another parameter (IS, Driving mode, RAW+JPG,…)

M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), 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 reyalp

  • ******
  • 13290
I update now to latest 1.6.0. Also, no problem with 12s.
Which Mode do you use? Flash?

Hmm.. strange..
I did the last view test in Av Mode (set in CHDKPTP, the Camera was in M Mode). I use AV mode for sunset and M mode for sunrise.

EDIT:

I changed the ui_raw_hook_sleep=9000 and now I was able to shoot up to exactly 20 without shut down and with 21 the camera again went off.
It looks like waiting ~10s in the remote hook is the problem. The script calculates how long it needs to wait based on how much time all the work (shooting, processing the raw data, saving the file) took, so you probably want to leave some margin for variation.

But, this seems to confirm moving long waits to the raw hook probably addresses the problem, so the script could be updated to allow arbitrary lengths, as long as there's not some similar problem in the raw hook. I think I actually considered this early on, because blocking for a long time in the remote hook is quite sketchy, but didn't bother because it seemed to work.

You should be able allow arbitrary ui_raw_hook_sleep by changing the line (1991 in rawopint 0.25)
Code: [Select]
hook_raw.set(10000)
to
Code: [Select]
hook_raw.set(10000 + ui_raw_hook_sleep)

That said, rawopint metering will degrade with long intervals, since it bases exposure on the previous shot. For this kind of interval, it might be better to use camera AE, or take (and ideally, discard) a metering shot immediately before the real shot.

The first two romlogs refer to CntFlashTask0, which I don't recall seeing before. The name suggests it's either related to flash (strobe) mode, as c_joerg suggested, or possibly flash memory.

IIRC the MotionVector.c one has been seen before in connection with the remote hook. A quick search found https://chdk.setepontos.com/index.php?topic=13893.msg141682#msg141682 but I'll have to do some digging to find the details.
Don't forget what the H stands for.

The first two romlogs refer to CntFlashTask0, which I don't recall seeing before. The name suggests it's either related to flash (strobe) mode, as c_joerg suggested, or possibly flash memory.

IIRC the MotionVector.c one has been seen before in connection with the remote hook. A quick search found https://chdk.setepontos.com/index.php?topic=13893.msg141682#msg141682 but I'll have to do some digging to find the details.

Strange... I just tried it now but I can't access the flash settings (via menu or func.set) no matter what I try: flash retracted, popped up, with/without CHDK?! In Auto, the flash is not used either. Since I'm not using the flash for time-lapse, I don't care, but could that be why the camera is crashing?
What does CntFlashTask0 mean? is that a CHDK setting? By flash mode, do you mean when the flash is popped up?

I will try this out:
Code: [Select]
hook_raw.set(10000 + ui_raw_hook_sleep)

Thank you for this "fast fix"  ;)

I think the metering is not an issue as I don't want big ev changes to avoid flicker. normally ui_max_ev_change_e is set to 1.

EDIT

 :o :o

OMG: the reason was: the little plastic cover plate of the hot shoe... after I took it of I was able to access the flash settings... LOL
HAHA

I will try everything from scratch again... :haha
« Last Edit: 25 / May / 2021, 16:43:01 by dolomiti_timelapse »
If you want to see a sunset or sunrise of Dolomiti Val Gardena shot with CHDK visit
Telegram: t.me/DolomitiTimelapse
Instagram: dolomiti_timelapse


*

Offline reyalp

  • ******
  • 13290
Strange... I just tried it now but I can't access the flash settings (via menu or func.set) no matter what I try: flash retracted, popped up, with/without CHDK?
Is there something in the hot shoe? Using the hot shoe is known to affect CHDK in some cases, IIRC including where the Canon firmware thinks there's something there because of a cover or stuck switch.

CHDK on g1x has a hot shoe override setting to force the camera to see particular state if you need it.

edit:  :lol
Quote
What does CntFlashTask0 mean? is that a CHDK setting?
It's a task (like thread  or process) in the Canon firmware.

Quote
I think the metering is not an issue as I don't want big ev changes to avoid flicker. normally ui_max_ev_change_e is set to 1.
It will be behind, so if there's like clouds moving in front of the sun, the script will react to that 20 seconds later, which could easily be completely the wrong direction. Of course this can happen with short intervals too, but it's much less likely in this kind of scene.
Don't forget what the H stands for.

Is there something in the hot shoe? Using the hot shoe is known to affect CHDK in some cases, IIRC including where the Canon firmware thinks there's something there because of a cover or stuck switch.

CHDK on g1x has a hot shoe override setting to force the camera to see particular state if you need it.

edit:  :lol
Quote
What does CntFlashTask0 mean? is that a CHDK setting?
It's a task (like thread  or process) in the Canon firmware.

Quote
I think the metering is not an issue as I don't want big ev changes to avoid flicker. normally ui_max_ev_change_e is set to 1.
It will be behind, so if there's like clouds moving in front of the sun, the script will react to that 20 seconds later, which could easily be completely the wrong direction. Of course this can happen with short intervals too, but it's much less likely in this kind of scene.

Yes, a little plastic cap covering the contacts of the hot shoe (micro switch)  :-[
Everything now works as it should. Both using CHDKPTP and directly running the script on the camera now works with intervals higher than 11 seconds.

I owe you both a beer, do you have paypal?

At least today's sunset was one of the best.  :D I reduced the quality of the video to bring it below the 2MB limit (and then converted it from mp4 to mpg, which completely destroyed the remaining quality).
shot with Canon SX100IS and rawopint.lua, slightly overexposed for my taste.
If you want to see a sunset or sunrise of Dolomiti Val Gardena shot with CHDK visit
Telegram: t.me/DolomitiTimelapse
Instagram: dolomiti_timelapse

*

Offline reyalp

  • ******
  • 13290
Yes, a little plastic cap covering the contacts of the hot shoe (micro switch)  :-[
Everything now works as it should. Both using CHDKPTP and directly running the script on the camera now works with intervals higher than 11 seconds.
Just to confirm, it works *without* the ui_raw_hook_sleep modification?

Quote
I owe you both a beer, do you have paypal?
Honestly, seeing people do cool things with it is the best reward for working on this stuff.

Quote
At least today's sunset was one of the best.  :D I reduced the quality of the video to bring it below the 2MB limit (and then converted it from mp4 to mpg, which completely destroyed the remaining quality).
shot with Canon SX100IS and rawopint.lua, slightly overexposed for my taste.
Very nice. Have you thought about posting these outside IG?

The moon + clouds definitely gets bright at the end. May be able to offer suggestions if you post the log file.
Don't forget what the H stands for.

*

Offline c_joerg

  • *****
  • 1103
OMG: the reason was: the little plastic cover plate of the hot shoe... after I took it of I was able to access the flash settings... LOL
 

Interesting…

Yes, a little plastic cap covering the contacts of the hot shoe (micro switch)  :-[

But it's not an original part of the G1x, is it?
Could be a problem with my timelapse dolly. I haven't used it with 12s yet. https://chdk.setepontos.com/index.php?topic=13726.0

M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), 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


But it's not an original part of the G1x, is it?
Could be a problem with my timelapse dolly. I haven't used it with 12s yet. https://chdk.setepontos.com/index.php?topic=13726.0
Yes it is. You should have this part too.

Attached is a photo with the plastic cap in place. And a detail of the microswitch that may have caused the problem.

Maybe you can try this out too on your G1X. You may use just a toothpick if you can't find the original plastic cap to trigger the micro switch, then we could confirm this behavior on a second G1X.  :)
« Last Edit: 26 / May / 2021, 03:36:21 by dolomiti_timelapse »
If you want to see a sunset or sunrise of Dolomiti Val Gardena shot with CHDK visit
Telegram: t.me/DolomitiTimelapse
Instagram: dolomiti_timelapse

*

Offline c_joerg

  • *****
  • 1103
Yes it is. You should have this part too.

I have two G1x and no cap. But I bought them used.
The original cap of my M3 has a notch so that the switch is not switched.
I don't think your cap originally belongs to the G1x. It makes no sense for me to removing the cap when using the internal flash.
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), 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

 

Related Topics