In revision 930, I added support for setting zoom in mc:shoot. This can be set in camopts like the other values. There is also a zoomwait option which adds a delay after setting the zoom. This may be needed to avoid crashes, especially if you are also setting focus.
Example
!mc:shoot({zoom=10,sd=2000,zoomwait=200,camopts={{zoom=50},{zoom=100}}})
This sets the default zoom position to 10, subject distance to 2 meters, wait to 200ms. Camera 1 has zoom set to 50, camera 2 is set to 100.
The zoom number is in the camera zoom steps, which varies widely between models. Some older cameras only have 5 steps, while newer ones can have hundreds. If you want the same effective focal length, you'll need to figure out which zoom step corresponds to the desired focal length on each model.
I looked at setting zoom by EFL, but it would require support in CHDK code.
The reboot and shutdown options are basically the same, cameras go into play mode and then the reboot/shutdown command is sent. I'm puzzled because shutdown works perfectly 100% of the times, but reboot doesn't.
They do different things in CHDK code. A "soft" shutdown in CHDK should take care of retracting the lens just like if you had pressed the power button. A reboot is much less clean.
I doubt it's power related, since shutdown is OK and this camera is in a safe power source (not the one in conflict with the zoom option).
If you have many cameras of the same model (and firmware, since only 100A exists for A2500), and only one is affected, it suggests a hardware difference somewhere. Whether it's in the camera itself or external hardware is hard to guess.
The different groups of cameras could be affected by different electrical problems. For example, some might be caused by EMI, while others were supply voltage.
AV values will be eliminated and I'll compensate exposure with shutter speed.
Note G10 and SX150 do have adjustable apertures, so you may need to control those.
Canon processing is a bit too harsh with noise reduction and sharpening, but does a great job with distortion correction (which I think is what benefits the 3D reconstruction)
FWIW, you can control the sharpening of Canon jpeg a bit using the "my colors" custom setting, which can be controlled using propcases from script.
That's the reason I was hoping for an in-camera solution. The shooting conditions are always going to be the same, so I'll need to test the best values for each camera (but I believe that's external and not possible to implement in camopts, right?) Edit:I was referring to White Balance here
I think I didn't read your previous post carefully enough, I thought your WB problem was in raw processing. For jpeg, you can only set WB mode from script, and in modes other than custom, the cameras will still adjust the WB for each shot. To use custom WB, you'd need to set it individually on each camera.
There has been some work on finding ways around this:
https://chdk.setepontos.com/index.php?topic=12208.0It's possible this could be finished into a usable feature.
If you are using raw, you almost certainly need to come up with settings for each camera model externally. White balance can be set completely after the fact, so you wouldn't need to change the camera setting (as long as you can tell your raw software not to use camera WB). Using CHDK raw, you'd almost certainly need to do distortion correction. Some lens profiles and information in this thread
https://chdk.setepontos.com/index.php?topic=9268.0