Bug #1373
Tamron SP 24-70mm F/2.8 Di VC USD not recognized properly
100%
Description
Tamron SP 24-70mm F/2.8 Di VC USD is not recognized by exiv2.
Running it on Linux Mint:
exiv2 0.25 001900 (64 bit build)
Copyright (C) 2004-2015 Andreas Huggel.
processing a canon cr2 image by exiv2 -pt /home/achim/Bilder/NasRaw/2018-10-30-Abstract/_MG_3210.CR2 |grep -i 'lens\|model\|make'
it reads out a "Exif.CanonCs.LensType Short 1 Sigma 24-70mm f/2.8 IF EX DG HSM"
Exif.Image.Make Ascii 6 Canon
Exif.Image.Model Ascii 21 Canon EOS 6D Mark II
Exif.Photo.MakerNote Undefined 42614 (Binary value suppressed)
Exif.MakerNote.Offset Long 1 996
Exif.MakerNote.ByteOrder Ascii 3 II
Exif.CanonCs.LensType Short 1 Sigma 24-70mm f/2.8 IF EX DG HSM
Exif.CanonCs.Lens Short 3 24.0 - 70.0 mm
Exif.Canon.ModelID Long 1 (2147484678)
Exif.Canon.LensModel Ascii 74 24-70mm
Exif.Photo.LensSpecification Rational 4 24/1 70/1 0/1 0/1
Exif.Photo.LensModel Ascii 8 24-70mm
Exif.Photo.LensSerialNumber Ascii 11 0000000000
Files
History
Updated by Robin Mills about 3 years ago
- Category set to lens
- Status changed from New to Assigned
- Assignee set to Robin Mills
- Target version set to 0.27
- % Done changed from 0 to 50
- Estimated time set to 1.00 h
This is almost identical to #1372 and you can fix it for yourself with the file ~/.exiv2 If you need further assistance from me, please supply a test image.
Updated by Achim Kilchert about 3 years ago
- File _MG_2194.JPG _MG_2194.JPG added
Robin Mills wrote:
This is almost identical to #1372 and you can fix it for yourself with the file ~/.exiv2 If you need further assistance from me, please supply a test image.
Yes please assist.
I can't manage to read out the lens ID. Attached you'll find an image. As far as I can see using exiv2 Canon does not store the lens ID in the EXIF data.
Updated by Robin Mills about 3 years ago
- Status changed from Assigned to Closed
- Priority changed from High to Normal
- % Done changed from 50 to 100
I see you are using Exiv2 v0.25. This feature was added in Exiv2 v0.26
$ curl -O http://dev.exiv2.org/attachments/download/1253/_MG_2194.JPG % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1496k 0 1496k 0 0 1879k 0 --:--:-- --:--:-- --:--:-- 1885k $ exiv2 -pt --grep lens/i _MG_2194.JPG Exif.CanonCs.LensType Short 1 Sigma 24-70mm f/2.8 IF EX DG HSM <--- Sigma Lens Exif.CanonCs.Lens Short 3 24.0 - 70.0 mm Exif.Canon.LensModel Ascii 74 24-70mm Exif.Photo.LensSpecification Rational 4 24/1 70/1 0/1 0/1 Exif.Photo.LensModel Ascii 8 24-70mm Exif.Photo.LensSerialNumber Ascii 11 0000000000 $ exiv2 -pv --grep lens/i _MG_2194.JPG 0x0016 CanonCs LensType Short 1 137 <--- this is the number 0x0017 CanonCs Lens Short 3 70 24 1 0x0095 Canon LensModel Ascii 74 24-70mm 0xa432 Photo LensSpecification Rational 4 24/1 70/1 0/1 0/1 0xa434 Photo LensModel Ascii 8 24-70mm 0xa435 Photo LensSerialNumber Ascii 11 0000000000 $ cat ~/.exiv2 [canon] 137=Tamron SP 24-70mm F/2.8 Di VC USD <--- Assign it here $ exiv2 -pt --grep lens/i _MG_2194.JPG Exif.CanonCs.LensType Short 1 Tamron SP 24-70mm F/2.8 Di VC USD <--- Happiness Exif.CanonCs.Lens Short 3 24.0 - 70.0 mm Exif.Canon.LensModel Ascii 74 24-70mm Exif.Photo.LensSpecification Rational 4 24/1 70/1 0/1 0/1 Exif.Photo.LensModel Ascii 8 24-70mm Exif.Photo.LensSerialNumber Ascii 11 0000000000 $
Updated by Achim Kilchert about 3 years ago
Great! Thanks. It works for exiv2. BUT
Unfortunateley:
Darktable still sees a Sigma 24-70mm f/2.8 IF EX DG HSM, at least for existing images it has imported already.
Also re-importing a folder didn't change the behaviour.
(By the way, how do I install the latest version of exiv2? I extracted it temporarily in some local folder.)
Updated by Robin Mills about 3 years ago
I don't think you can "install" exiv2 into darktable. You have to get a build of darktable that uses exiv2 v0.26. You'll have to check with their web-site. Or you may be able to build darktable with the exiv2 v0.26 sources. You can use the utility lsof
to find out which version of exiv2 is being used by darktable.
rmills@rmillmbp-ubuntu:~$ lsof | grep exiv2 | grep darktable darktable 3583 rmills mem REG 8,1 2676904 664173 /usr/lib/x86_64-linux-gnu/libexiv2.so.14.0.0 rmills@rmillmbp-ubuntu:~$I've just installed darktable with
$ sudo apt install darkable
and it's using libexiv2.so.14 which is Exiv2 v0.25. I straightened up the numbering with Exiv2 v0.26 and the library is libexiv2.so.26.
My Linux VM is Ubuntu 18.04 LTS and it was created a few weeks ago for Exiv2 v0.27 development. So it's mostly unpolluted.
rmills@rmillmbp-ubuntu:/usr$ find . -type f | grep libexiv2 | grep -v -e share ./local/lib/libexiv2lib.so.0.27.0.1 <--- That's the Exiv2 v0.27 RC1 (which I'm developing) ./lib/x86_64-linux-gnu/libexiv2.so.14.0.0 <--- That's Exiv2 v0.25 (delivered by the Linux Gods) rmills@rmillmbp-ubuntu:/usr$I don't think I can say anything much more about this. You'll have to ask the folks at darktable (with whom I have a friendly working relationship).
Updated by Achim Kilchert about 3 years ago
Thanks a lot for your assistance. I'll try to forward the issue to the darktable guys. Hopefully they will launch another release soon.
I'd assume they always include the latest libexiv2 libraries into their builds.
Updated by Robin Mills about 3 years ago
Hard to say. Pascal has been very active in back-porting Exiv2 changes into earlier versions. It's possible that libexiv2.14 (Exiv2 v0.25) has the code to read ~/.exiv2.
You'd be doing me a favor by downloading and using Exiv2 v0.27 RC 1 from http://exiv2.dyndns.org All feedback is helpful. It will not harm your existing darktable installation.