Based on your previous posts about multicam.lua etc, I assumed you planned to control the cameras with a single instance of chdkptp.
I did not mean to imply it would provide more functionality. The point is wrapping chdkptp in autoit adds a substantial amount of complexity, and requires a substantial amount of time writing and maintaining "glue" code.
The glue to chdkptp at the minute purely AutoIt "Send(this that or the other)" to the chdkptp command line. ...Could that be made fundamentally slicker / easier to maintain using IUP?
......but if you call code directly, it can make handling return values or data from the camera a lot more convenient than trying to parse chdkptp output.
In summary, if I set an aperture override, say by an on the fly function addition to multicam.lua (or directly add to camera side script code) - when/where is the aperture override applied if subsequently shooting using cmds.shoot_hook_sync() ?
Other,hadn't really expected to be thinking of implementing a ptp based trigger so neither do I particularly understand how the tonumber(mc.args)) of wait_tick(tonumber(mc.args)) ends up the correct number on the different cams...a brief overview of pctime / cam tick logic would help me read the relevant multicam functions.
If a higher precision clock were available, you'd probably want to make a script command that let you schedule a shot to begin at a certain precise time using the remote hook, rather than doing the wait in Lua. The stuff in this thread http://chdk.setepontos.com/index.php?topic=8312.100 might be helpful.
Started by DBgit
« 1 2 »
Started by gkguru
« 1 2 »
General Help and Assistance on using CHDK stable releases
Started by Dirk
Started by oneaty
« 1 2 »
Completed and Working Scripts
Started by bugbear