On Sun, Mar 17, 2013 at 1:36 PM, Colin Adams <colinpaulad...@gmail.com> wrote: > On 17 March 2013 12:28, Sebastian Kraft <m...@sebastiankraft.net> wrote: > >> Ok, what we have so far: >> >> Strict search won't work as lens names are not standardized and differ >> in some parts of the name. See Tamron 17-50. >> >> Fuzzy search won't work as lens names sometimes only differ by one last >> letter. See Canon 70-200 I...III >> >> So none of the search algorithms works reliably and even modifying the >> algorithms would not help. It's just a conflict of requirements. Or do >> you see any possible improvements in the algorithms? > > Why can't the lensfun database store the lens ID, and the application > (e.g. darktable) read the lens ID directly from the EXIF data? Then > there would be no ambiguity.
If it only were that simple... LensID conflicts are very common... Since the camera brands (Canon/Nikon), do not assign IDs to Sigma/Tamron lenses. So Sigma/Tamron/etc just take a certain ID, which later maybe used by another brand as well... Exiv2 already has some heuristics in case of a lensid conflict to figure out which particular lens is actually being used for a particular lensid. I think they primarily use min/max focal an min/max aperture to differentiate. So this mess is very messy :( Regards, Pascal de Bruijn ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
