As always, adding more complexity will make it harder to test.
An idle thought: With something like the chdkptp remoteshoot glue, it would be possible to create a GUI that lets you visualize what the script is doing and change settings in real time.
Situations where clouds keep pushing in front of the sun are extremely difficult.
I had already considered another option: to deactivate the exposure control for a certain time using an external USB switch or to only allow a control for overexposure.
However, this isn't true in the other direction: For a given positive exposure change N, all pixels with values above (overexposure threshold - N) will pass the threshold, and this number can be easily obtained from the histogram. So the exposure algorithm can take the exposure change calculated from other inputs, calculate how many additional pixels would be pushed into over-exposure, and adjust accordingly to keep it below the limit.
rs "D:/sunset/input/" -script=D:/sourcecode/rawopint_rs.lua -shots=3 -int=12
rs "D:/sunset/input/" -shots=3 -int=12
the script works fine (on camera and via CHDKPTP) for less than or equal to -int=11 but for greater or equal than -int=12 (12seconds, value 120 in camera) the camera simply goes off in that moment where the camera should take the second picture of the series. There is a little noise when the camera goes off which is the IS unit dropping. No lens retracting, no AV change, no "shutter" movement. The camera simply goes off. I tried a lot of different settings but nothing changed this misbehaviour at all. If the shutter speed is quite high, e.g. 10 sec the camera does the same misbehaviour but starting at a interval of 10+12=22 seconds.
!require'extras/devutil'.init_cli() -- add debug commands, only needed once per sessiondromlog
the script works fine (on camera and via CHDKPTP) for less than or equal to -int=11 but for greater or equal than -int=12 (12seconds, value 120 in camera) the camera simply goes off in that moment where the camera should take the second picture of the series.
I’m actual running 1.5.0 5399 on my G1x 100e. I never run rawopint together with CHDKPTP. What does it mean ‘on camera’? Running the script without CHDKPTP and starting script from SD card?If I run rawopint v0.25 with 12s interval (value 120) I have no problems. All other params are default.
The camera shutting off usually means it crashed. Can you get a romlog: https://chdk.fandom.com/wiki/Debugging#Camera_crash_logs_.28romlog.29 ?
I suspect this crash probably has something to do with waiting in the remote hook. You can try putting some of the delay in the raw hook instead, by setting ui_raw_hook_sleep. The menu currently only allows up to 100ms, but if you set it from the glue script, you should be able to use values up to about 9000 (it needs to be less than the raw hook timeout, which is currently set to 10s).If this works, I can adjust the script to do the majority of the wait in the raw hook and only use the remote hook to keep the interval precise.Note that ui_raw_hook_sleep doesn't add to the interval. It effectively makes the script act like shooting took longer, so in order to maintain a the interval set with -int, it must be shorter than the interval and all the overhead of shooting, metering etc.So if the theory is correct, you could use something like -int=20 and ui_raw_hook_sleep=9000
Interesting. Maybe I should try 1.5.0 5399...
Started by rosspian
Started by reyalp
Completed and Working Scripts
Started by Stephan
« 1 2 »
General Help and Assistance on using CHDK stable releases