> > Just aliasing all the Exiv2 names will make autoselection work in most > practical cases though.
Well, but cluttering the database with lens names is not a proper solution. > >> For example Darktable could automatically select the correct profile in >> it's GUI but the user would have to manually enable the lens correction >> tool to apply the changes. > > Without aliasing, autoselection will fail often, and enabling lens > correction is already optional, it's not enabled by default. > > The problem with fuzzy autoselect remains, that we could accidentally > autoselect the wrong lens, where the user does not notice the wrong > correction is being applied. So I failure to properly correct, > actually becomes adding imaging defects. > But how can this accidently happen if the user sees the automatically chosen lens string and THEN enables the correction? I assume the user knows if the shown lens is correct or not. > Regardless, this is a discussion that primarily needs to be hand with > the lensfun maintainers. > That's why I am here ;) currently I do the maintenance stuff around the database and SVN on Berlios. One way to improve the matching with the fuzzy search would be to evaluate the score returned with the search result. If the score is high you know the search result matches quite good. Have you tried this? For me this gives a very good indication about the search result quality. At least I could not find an example where the fuzzy search returned wrong entries with a high score. Sebastian ------------------------------------------------------------------------------ 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
