I downloaded and installed the latest Adobe DNG Converter with the intention of updating the set of lens profiles to which I have access from RT. However, when I go to the Transform tab and click the “LCP file” radio button under “Profiled Lens Corrections”, it takes me to a menu of folders containing only very old profiles - for example, the Nikon folder includes only a limited set of lenses with older-vintage DSLRs as well as some old Coolpix and Nikon 1 models.
No doubt I’m missing something that should be obvious. I’d appreciate any and all help in figuring this out.
I think there are no more recent cams / lenses (like Nikkor Z) from Nikon as they have lens correction embedded. So Adobe doesn’t have any need for creating lcp.
Edit: I think it also doesn’t matter if the cameras in the list are older than yours, as long as it’s the same sensor size. E.g. if there is a profile made with a D3300 you don’t have to redo it with a D7500.
Yes, that is indeed the file that I have for Nikon. My bad: had I looked at folders for other companies, which I did just now, it would have been apparent that those do have recent lenses included, so the issue is Nikon-specific.
If Adobe is relying on Nikon-specified corrections, do I understand correctly that those are embedded in the NEF file? If so, does RT know how to read those? I have recently been working with files captured with the new Nikkor Z DX 24/1.7 lens, and there is linear distortion and illumination falloff apparent that RT is not correcting, regardless of which radio button I select in “Profiled Lens Correction”.
I’m on Nikon Z too. At the moment RT can’t use the embedded profiles. I don’t think it can do so with any manufacturer at all. I also don’t see that this is been worked on atm.
Not a show-stopper, as so far the available manual corrections for distortion and vignetting have been sufficient. If at some point I run into a lens with strong mustache-profile linear distortion I might need to wrestle with the Adobe lens profile creator utility.
My personal difficulty with the images required for a lensfun profile was those for CA. I could find virtually nothing locally that fit the bill, subject-matter-wise. Even if I had, I suspect a guy shooting a bunch of photos of a public / commercial building might garner a bit of local law enforcement attention. Maybe not, but just sayin’ …
I ended up creating a few profiles using the Adobe tool and it wasn’t particularly difficult. I shot the images in my kitchen / dining room.
One debatable (?) “easier” aspect is that one set of photos is all that’s needed for all corrections* at a given focal length. However, I ended up with several sets of profiles, each for a specific focal length. I don’t know how they can be combined / created into one profile for all focal lengths (with extrapolation, I’m sure) but apparently they can be as I’ve seen them. But I found no info on that process online nor in the documentation. The Adobe tool is deprecated but still workable.
* That is, the same set of images will work for CA, vignetting and geometric distortion.
That might indeed work and I thought about it, but never went back and researched the structure well enough to convince myself. That may well be how it’s done, though. Maybe the focal lengths are searched / matched or interpolated as needed. Not sure how that works.
That’s why using the lensfun library is helpful, it’ll take a list of corrections for various focal lengths of a lens and interpolate between the closest two for the as-shot focal length.
Maybe it’s too early? As I understand it, people are still trying to decipher Nikon’s metadata.
Isn’t there a kind of lens correction in RT based on comparing the embedded JPG with the raw? I don’t use RT, so I don’t know if / how well it works in practice. And surely, extracting the correction data instead of estimating it based on analysing the embedded JPG is a much better method, if it’s available.
Its just users here on the forum. It doesn’t have anything to do with the editor (yet). We are trying to figure out what the numbers are and what formula is being used. When that’s figured out, any editor can take that information and use it.
Here also I rather meant the function to use embedded lens correction in DT in general, which I think was introduced in 4.2? However, I will monitor the progress and see if I can support with my only Z-Lens I have.
