I update now to latest 1.6.0. Also, no problem with 12s.Which Mode do you use? Flash?
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.
Quote from: c_joerg on 25 / May / 2021, 14:09:00I 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.
hook_raw.set(10000 + ui_raw_hook_sleep)
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?
What does CntFlashTask0 mean? is that a CHDK setting?
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.
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: QuoteWhat does CntFlashTask0 mean? is that a CHDK setting?It's a task (like thread or process) in the Canon firmware. QuoteI 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. 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.
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
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
Yes it is. You should have this part too.
Started by rosspian
Started by reyalp
Completed and Working Scripts
Started by Stephan
« 1 2 »
General Help and Assistance on using CHDK stable releases