On 2013-11-23 [email protected] wrote: > Exif.Nikon3.LensType Byte 1 D G VR > Exif.Nikon3.Lens Rational 4 24-70mm F2.8 > Exif.Nikon3.LensFStops Undefined 4 6 > Exif.NikonLd3.LensIDNumber Byte 1 254 > Exif.NikonLd3.LensFStops Byte 1 F6.0 > > Sounds like we're missing out here entirely. > > Taking another lense I get readings like > > $ exiv2 -pt R20131106-1452.NEF | grep -i lens > Exif.Nikon3.LensType Byte 1 D G VR > Exif.Nikon3.Lens Rational 4 70-200mm F2.8 > Exif.Nikon3.LensFStops Undefined 4 6 > Exif.NikonLd3.LensIDNumber Byte 1 Nikon AF-S VR Zoom-Nikkor > 70-200mm f/2.8G IF-ED > Exif.NikonLd3.LensFStops Byte 1 F6.0 > > where indeed the ID matches to a string familiar to lensfun > and dt is happy. (Wondering if the firmware does some funny > stuff here? Somewhere this Id needs to be matched, right?)
The data type for LensIDNumber is "byte", the -pt option tells exiv2 to interpret the data before printing it, as opposed to -pv, which will show you the uninterpreted data. So it's probably not a firmware issue, but a failure of exiv2 to interpret the number for some reason. It sounds like these tags are generally poorly documented: http://www.exiv2.org/makernote.html ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
