CraigBennett
Leading Member
With each update of FoCal Pro, I have decidedly not like using this program. I cannot get repeatable results. It is not stable on my MacBook Pro 10.8.2.wombat779 wrote:
Unfortunately not. I was very careful to exactly duplicate my lighting conditions between sessions, and still got wildly different results. The issue at the time seemed to be that FoCal's contrast detection algorithm was not good (e.g., I could clearly see with my own eyes that an image was badly out of focus, but FoCal was giving a high sharpness score to that image). In particular, red/purple axial CA seemed to make FoCal think images were sharp. The inability to do mirror lockup was also a big problem, since it meant that some lenses NEVER produced sharp enough images with my setup for FoCal to use. I'll also note that in the 2 or 3 days of using it, I probably experienced 10 or 15 crashes in the software (often requiring several attempts to get a test to complete), which doesn't exactly inspire confidence. This was a few weeks ago, so maybe things are somehow improved now.yray wrote:
There has been a number of posts about needing different lens fine tune adjustments on a D800 in artificial and natural light. This might be your issue with FoCal.
As to your point, though, I generally agree that the variables involved in AF (light, distance, zoom, subject etc.) probably make fine-tuning in advance a bit of a waste of time unless gross errors are obvious. To me, AF doesn't seem so precise that there is a single "magic" fine tune value for each lens that will always work. I think the better approach is just to go out shooting, see if you have a repeated issue with your common subjects (e.g., focus is regularly on the nose instead of the eye, etc), then make small corrections as needed. That way you arrive at a value that works the best for your shooting as a whole, rather than a fine-tuning session that optimizes sharpness for one particular scenario that doesn't reflect your real usage. Just my thoughts anyhow.
Horshack's DotTune method is easy and the results makes sense to me.
Regards,



