Oh and also, was there a way to just apply this particular change (extension of possible exposures list) to my old CHDK, so that I don't have to redo all custom menus etc? I've seen the .patch file in the attachment but wasnt sure how to use it.
Patch files are used to modify the CHDK source code. It's a way to work on things on one computer and when its done, allow you to merge your changes back into the master copy of the source code. Very handy when working on a project with multiple people writing code. But I also use them with my personal code - scripts & core CHD stuff - which I maintain in a version control system (svn).
Having said that, you do not have to redo your menu setups and other customizations each time you load a new release of CHDK. Once you have your bootable SD card formatted correctly, you only need to "unzip" the most recent CHDK distribution file to the SD card root (making sure to select the option that uses or "preserves" the folder structure in the zip file). This means you do not need to repeat the complete original installation process you followed (STICK?) - that will wipe out all your customizations and reformat everything from scratch.
One small exception to the above can happen when moving between CHDK versions ( 1.0.0 -> 1.1.0 -> i.2.0 -> 1.3.0 ). Even there, I think there was an atempt made to automatically use the old config files in the new version.
I seem to remember the old CHDK that I had was setting the corect AutoISO with the same menu settings - it just didn't have exposures slower than 1/8.
I'll take a look but there has been nothing changed in Custom AutoISO since it was added (other than the conversion from real to market ISO some time ago). I've looked enough at the code to be somewhat afraid to touch anything there.
In fact, problems with the working of that function (
Is Custom Auto ISO working for the A640 under 1.2?) were the reason I got started on a
"small" script to replace it. Hundreds of hours later it looks like this :
KAP_UAV_Exposure_Control_ScriptAt some point I think it would be good to recode the AutoISO portion of that script in "C" and replace the existing code.
FWIW : CHDK AutoISO was added to core CHDK back when the German and International version of CHDK were merged. At that time, the CHDK-DE version had a lot of "experimental" code. I'm pretty sure the function would not get added today without a lot more work and testing.
Let me know if you think you'll have the time to implement those other changes you were mentioning, if so I will not yet customise this current version but instead wait for the final one. Many thanks in advance!
Like I said above, go ahead with your customizations. You will not lose them if you are just updating the CHDK core code.
tl;dr : can you reload the CHDK 1.3.0 version for you camera from the autobuild (which will not have the extended shutter speeds) and verify that it sets the exposure correctly ?
