On 20/9/20 6:31 am, jys wrote:
That said, if the exiv2 tool is showing a proper lens name *somewhere* in its output, then it's possible that darktable could improve its use of the API to make sure it gets the best name string available. If you create a feature request issue for this on the darktable github tracker, it would be good to include a file which demonstrates that condition (the name being available, but not used by darktable).
I can do this but would like to check one thing. If this same issue is occurring in Digikam also ie. lens name = "173", would this not indicate the issue is not Darktable?
For that workaround, you would need to actually change the model name to whatever darktable is displaying in the image info module... "173" in this case. It's not a pretty hack, but should make the matching magic happen. Just remember to discard the change if/when the problem gets fixed upstream.
Hmm. Yeah I was looking at that in the wrong order. I've copied the entire lens data to a new section and changed the model names to 173 which now works perfectly. As I've copied it the old one will work when it is resolved. Dakin ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
