Il 14/03/2013 18:44, Pascal de Bruijn ha scritto:
>
> I'm afraid we had to break this again :(
>
> slr-tamron.xml: <model>Tamron 17-50mm f/2.8 XR Di II LD</model>
>
> Exif.PentaxDng.LensType Byte 4 Tamron AF
> 17-50mm F2.8 XR Di-II LD (Model A16)
>
> So the problem seems to be the Model A16 suffix :(
>
> So looking into the Exiv2 sources:
>
> { 0x04e6, "Tamron SP AF 17-50mm F2.8 XR Di II" },
> { 0x07e6, "Tamron AF 17-50mm F2.8 XR Di-II LD (Model A16)" },
>
> So to be honest I'm not sure how to proceed with this.... I'm tempted
> to think this should be resolved on lensfun's end with aliases instead
> of fuzzy matching....
>
> The temporary workaround would be to create a local """alias""" by
> copying the lensfun entry with a different name.
>
> If you place the slr-custom-tamrom.xml into:
> ~/.local/share/lensfun/slr-custom-tamron.xml
>
> Lens correction should work again.
Hi,
I fear the problem is commit c7cd6bb7019d833cece3821993f19ff9d5a9d782
(11/03/2013) where Ulrich changed fuzzy search to normal search (line 724).
Sincerely I don't understand why fuzzy search was removed... commit
message says "more consistent behavior of gui and auto-detection" but I
have not found issue using fuzzy detection. Am I wrong?
Entry duplication in lensfun database is other possible way, but imo, if
fuzzy search works without side effects, there is no reason to go this way.
Ivan
Ivan
------------------------------------------------------------------------------
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
