On Mar 8, 2006, at 8:28 AM, Patrice LACOUTURE wrote:
It is important to me. I'm currently working on a small tool that does
essentially the same as PTLens, but on DNG files:
* scan a folder of DNG files and for each:
* identify the lens used, the focal length, the focus distance, the
aperture
* use (some of) these info to determine Adobe Camera Raw's Chromatic
Aberration settings from some sort of lens database (user-definable)
* set these correction values directly into each DNG file (so next
time I open it I got the right correction automagically!)
(and possibly do other things, like recover edges from raw, apply
Author and copyright informations, extract the JPG preview image into
a separate folder, start a custom PS action, and so on).
It could be useful, although the edge recover, Author and copyright
application, and JPEG preview extraction is already covered, and if
you use CS2/Bridge/Camera Raw then the custom PS action is already
covered too.
Of course, chromatic aberration also varies with focus distance and
focal length setting in the case of zooms. So your lookup and
calculation tables are going to be complex to begin with. Subject
distance is not recorded as far as I'm aware. So there are limits to
how effective the solution can be.
What mostly annoys me today is that 3rd party lenses are not
identified correctly (e.g my Sigma 18-125 is seen as a Pentax 28-80).
This is because the third party manufacturers don't license the mount
and interface, they backwards engineer it.
This tool will be protected by tens of patents filed in most countries
in the world, with a street price somewhere between US$ 150 to US$ 200
(I'm willing to buy all pentax lenses) ;-)
Hmm. "Tens of patents" filed in most countries in the world won't
protect you at all since you've already distributed the idea, without
filing first, on a public forum. And I can see that the price of your
software is going to be in the four digit US$ range to pay off all
those patent attorneys... ;-)
Godfrey
