I have a strange problem with darktable or lensfun. I have a Viltrox 16 mm lens, lens ID: “Viltrox AF 16/1.8 Z”. There is already this lens included in lensfun database, Sony version: “Viltrox 16mm F1.8 FE”. Even if I manipulate misc.xml to exactly match this string, darktable shows “unknown lens”. And correction does then not work.
The only workaround so far is to keep the original misc.xml and then manually select “Viltrox 16mm F1.8 FE”.
This matching however should work and I don’t know why it does not. Does anyone know?
Hm, OK. So might perhaps be a problem regarding the lens ID. I would suggest to do a search on “lensfun exiv2” in this forum, as there are quite some topics with respect to lens recognition issues. You may always override lensfun using an exiv2.ini (Windows) or .exiv2 (Linux) configuration file (there are also quite some topics covering that) as long as the the software has trouble to recognize the lens. So I assume, that this issue will be solvable.
Have you resolved this issue? I have the same problem with pictures taken with Nikon z6ii and Viltrox 16mm. Darktable does not recognise the lens and when I try to apply the lens correction module I get the issue “camera/lens not found”. I don’t even find this len in the drop down.
Yeah, I’m afraid we really might have a bug w/ native Z lenses in exiv2 - there is no substitution mechanism via the config file, and the unknown value is not parenthesized so dt can detect and fall back to something else (i.e. Exif.Photo.LensModel).
Btw, I believe the image information panel on the left does show these lenses as “Viltrox AF 16/1.8 Z” and “Viltrox AF 20/2.8 Z”, no? So exiv2 and dt seem to do their job, i.e. the fallback works.
Thank Viltrox for not putting in consistent strings between mounts (Sony E/Nikon Z/Fujifilm XF) so they can be leveraged consistently by Lensfun. The way things are, I think one workaround would be to locally hack your misc.xml so the <model> matches the Z-mount strings. You’ll have to do it every time you update the db, or perhaps create copies of the lenses you own in a new file in your user config (e.g. $HOME/.local/share/lensfun/viltrox.xml) for a permanent change.
Also, ask Lensfun to implement an aliasing mechanism.