Are you saying that you still get distorted JPEGs at the tele end of zoom? Here's a user that claims otherwise. The changes mentioned in the linked post are now part of the CHDK 1.3 release for the a2500.
Can you compare JPEGs made
- after zooming with set_zoom
- after zooming manually
?
I am saying that 2 people (me and my friend ) see distorted jpeg and cameras running the latest up-to-date chdk version (meaning the "fix" is applied).
We tested jpeg and dng formats.Dng format shows less distortion than jpeg BUT dng photos are like ~ 20mb in size.
Every dng file needs like around 10secs to get downloaded. 64cameras = 64 photos = 640secs to download ONE set of photos. That's around 10mins.
So we forget dng.
Let's talk about jpeg now.If i throw little numbers in set_zoom , and by little numbers i mean up to 10-15 , distortion is handled.If we throw numbers from 20 and up , distortion is NOT handled.
3d modelling program is confused and cant produce correct model.
We did several tests today.The golden number for us is zoom = 20 . At that point distortion can't be handled unfortunately.
And since we have 64 cameras to handle(=zoom in/out) i seriously don't care what is the behavior with manually zooming
Only light in the tunnel is a setting we found in 3d modelling program about "calibrating" cameras by using some pattern and distortion correction algorithms..a bit complicating procedure and a bit cheap way to solve the problem.
I will check the thing you mentioned about iso and cameras menu as soon as i am back at studio.
About "setting custom white balance"..how do you mean it?How can been done?
Thanks for your input.