Hi, Personnaly, i have 4 lens & 2 of them have name problem with lensfun database :
1) Canon EF-S 55-250 : exiftool 20130303_0011.CR2| grep -i lens Lens Type : Canon EF-S 55-250mm f/4-5.6 IS Lens Model : EF-S55-250mm f/4-5.6 IS Lens : 55.0 - 250.0 mm Lens ID : Canon EF-S 55-250mm f/4-5.6 IS Lens : 55.0 - 250.0 mm (35 mm equivalent: 86.5 - 393.2 mm) In Lensfun database is "<model>Canon EF-S 55-250 f/4-5.6 IS</model>" I think it's a bug in lensfun database as it's the single canon lens without "mm" after the lens... 2) Sigma 30mm 1.4 DC HSM exiftool 20130302_0079.CR2| grep -i lens Lens Type : Canon EF 17-35mm f/2.8L or Sigma Lens Lens Model : 30mm Lens : 30.0 mm Lens ID : Sigma 30mm f/1.4 EX DC HSM Lens : 30.0 mm (35 mm equivalent: 47.2 mm) In dartable , information about the pcture, this lens is name as "Sigma 15-30mm f/3.5-4.5 EX DG Aspherical" > Very strange as Lens Type & Lens ID aren't the same & darktable report something else : i dont' known where is the issue. What do you thing ? Regards Le dimanche 17 mars 2013 à 16:06 +0100, Sebastian Kraft a écrit : > Am 17.03.2013 15:27, schrieb Torsten Bronger: > > Hallchen! > > > > Sebastian Kraft writes: > > > >> [...] > >> > >> Your proposal was to add aliases in the database. But this will be > >> quite specific to the library used by applications and fill the > >> database with highly redundant information. Not a good solution > >> IMO. > > > > In my opinion, it is not redundant. On the contrary, it is valuable > > information. If somebody could provide us with a complete aliases > > list, the problem would be solved for good. (New LensFun entries > > will use exiv2 names anyway.) > > > >> Maybe we should start creating an alias.xml like it was proposed > >> somewhere in this thread. Then we will see how many lenses are > >> actually concerned and can better decide how to solve this in a > >> clean way. > > > > I think this is the best solution. The only problem is, how do we > > get the aliases? We will have to hope that people running into this > > problem will find their way to the mailing lists. > > > That's exactly the point I don't like about this approach as it yields > to a constant fixing of aliases and names. > > Maybe a more intelligent search like Markus Jung recommended can solve > most of the problems. But then it's the question who implements this, as > I won't have time for such a quite big task. The database search code in > Lensfun is not an easy thing to understand and modify. > > > Anyway... should we decide to collect critical lenses in an alias.xml > file as a first step? > This will help to get an overview and list of how many lenses are > actually causing problems. > AFAIK currently only the Tamron 17-50 would be on this list. > > If we ever find more lenses and have more example cases the decision > could be made if fixing the search would help or introducing alias names > is the better solution. Rewriting the search algo or restructuring the > database only because of one odd lens name is a bit too early I think. > > 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
