Am 10.03.2013 19:37, schrieb Torsten Bronger: > Hallöchen! > > Ulrich Pegelow writes: > >> [...] >> >> The key problem as of today is an automatic detection that is way >> off and which the user fails to observe. > > So if the needed calibration data is in the DB, the user can > successfully use it? In other words: the current situation is > annoying but not a blocker? > > If this is true, LensFun must be changed in my opinion. I don't > like too much magic in library-using code to evade issues in that > library. To a certain extent one cannot avoid it; but blacklisting > or Levenshtein are kludges. > >> A few ideas: >> >> 1) we could go back to the strict search rules. A lens would only >> be accepted from the database if there is an exact match. > > In my opinion, this is the way to go. >
I principally agree here. Have to admit, I never had a look how the search algorithm in lensfun actually works. Certainly it should be robust against whitespace and robust against upper/lower case, maybe it already it. If not, that might be implemented. In the end it would be absolutely reasonable for the user to select his camera/lens combination manually if auto-detection fails. Ulrich > LensFun is under-maintained. But the one thing which is easy to fix > is LensFun's DB. Through ~/.local/share/lensfun, every user can do > it, too. So my suggestion is that whenever someone comes with > failed auto-detection, we submit patches for LensFun copying the > <lens> entry under the alias name, marking it as such. As soon as > somebody implements aliases in LensFun, those entries can be > collapsed to an alias line. > > As a side note, I really wonder where those naming problems come > from. Probably the lens name was derived with an ancient exiftool > version, or by copying the text on the packaging of the lens, or > whatever. But if almost all LensFun clients use exiv2 today, maybe > the current lens names in LensFun should be simply *replaced* with > their exiv2 equivalents. It can only improve things. > > Just my 2p. > > Tschö, > Torsten. > ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
