FWIW, I found something better. A function that cancels the retract timer.Second function call after the "AC:SStoreLensT" or "AC:SStoreLens" log string.
Quote from: c_joerg on 23 / January / 2019, 02:09:14Should I found the functions here?chdk/trunk/platform/sx50hs/sub/100c/funcs_by_xxxNot yet.QuoteWhat exactly I have to call on my SX50 (100c) in lua?call_func_ptr(0xFF049EB4)You can make a test script that only has that single line and execute it in playback mode (obviously, the lens has to be extended when you run the script).
Should I found the functions here?chdk/trunk/platform/sx50hs/sub/100c/funcs_by_xxx
What exactly I have to call on my SX50 (100c) in lua?
I would like to try this with my other cameras (G1x 101a, G1x 100e, S110 103a, SX230 101a) as well. I'm still not clear how I get the address…
Index: platform/g1x/sub/100e/funcs_by_address.csv===================================================================--- platform/g1x/sub/100e/funcs_by_address.csv (revision 5154)+++ platform/g1x/sub/100e/funcs_by_address.csv (working copy)@@ -595,6 +595,7 @@ 0xff0977ac,j_PTM_BackupUIProperty_FW 0xff0977b4,PTM_RestoreUIProperty_FW 0xff099ec4,UIFS_CancelStoreLensTimer_FW+0xff099f1c,cancel_lens_retract_timer 0xff09a0d4,PB2Rec 0xff09a114,Rec2PB 0xff09a978,task_InitFileModules
I've attached a patch that contains the addresses for all supported DIGIC II ... 5 cameras.
This could be turned into a feature,
The method only works if the retract delay is set to 1 minute on the Canon UI.
This could be turned into a feature, but I could not decide on my own how to implement it.
- The script wrapper could simply call this function: that would mean the script author would need to make sure the call is made after every rec->play transition.- The above logic could be implemented in CHDK core. In this case, the script command would enable/disable the retract override.Since I don't write any serious scripts, I'd need the opinion of others who do.
if the logic can be implemented simply and reliably in the core
Quote from: srsa_4c on 20 / March / 2019, 14:09:39- The script wrapper could simply call this function: that would mean the script author would need to make sure the call is made after every rec->play transition.- The above logic could be implemented in CHDK core. In this case, the script command would enable/disable the retract override.Since I don't write any serious scripts, I'd need the opinion of others who do.My initial reaction is scripts using this would probably be controlling rec/play transitions anyway, so requiring them to call the function isn't much burden. It also keeps things simple.
It could also support a menu option like the "disable LCD off...", but this seems like a very limited use case that probably doesn't need a menu option.
I can't see of any reason to do this that does not involve running a script.
but also concerned about battery life might find a use for it.
Because of the 24-day problem…https://chdk.setepontos.com/index.php?topic=13714.0Would the following solution also work?You switch to recording mode every 55s and briefly press the shutter button halfway
Started by Jim
Started by cocuyo
Started by mpf
General Discussion and Assistance
Started by pigeonhill
Started by mirax7