Unfortunately this is what I am talking about.
I have the settings you suggest but I get generic lens name on some lenses while Full model name on others.
Sigma art 35 gives me generic
Nikon lenses also give generic names.
Tamron gives Full Lens Name
Take a look
Ofcourse I followed the exact same procedure in both cases
I'd like to add that in Lens Correction profile, the correct lens is auto-selected,
so it is just a matter of Description and not Recognition
I now understand. This was a KNOWN bug in earlier version of Lr6 but is now fixed. See the post here. Nikon lens EXIF not importing correctly
See here to fix it after you upgrade to 6.6.1 Lens metadata hidden for some cameras in Lightroom 2015.5 and 6.5
Today's Photos with both D810 and D4s.
Both cameras with Latest Firmware, importing NEF files with none developing, LR about box saying 2015.6.1 Release, Camera Raw 9.6
above lens: Sigma 35mm f/1.4 DG HSM Art for Nikon
above lens: Tamron SP 24-70mm f/2.8 Di VC USD A007N
above lens: Nikon AF-S 20mm f/1.8G ED
above lens: Nikon AF-S 50mm f/1.8G
I also tried the above in a brand new laptop with win10 (v1607), with brand new LR installation with no cached files
The data is not in the catalog as shown by the Metadata display but it should STILL be in the files as Lightroom does not change the NEF RAW files. Upload one of the NEF files to dropbox so others can see if there is a problem with the EXIF data in the file. Are you using any Nikon software to import the files into the computer?
I import straight from card reader to Lightroom.
As I stated I also tried a brand new pc, with brand new installation with no files, and imported these without alterations.
Here are the files: Dropbox - nef
Bob Somrak wrote:
This is the data that is recorded in EXIF using Exiftool for file GFK_6801 and as you can see it is the same as displayed by Lightroom so the data is not there to display. So far I didn't check the others. Also the lens Id is listed as UNKNOWN.
This is how I understand this is done Lightroom just displays the actual data in the raw files that the camera recorded. So this is a side effect of the camera not really knowing the full name of the lens. This is likely because Nikon's engineers can't fathom that anybody would be using a non-Nikon lens. I also wouldn't be surprised if the chip in the lens actually encodes this somehow and that Sigma, in contrast with Tamron, does not put their own name in that data. I guess Adobe could include a more complete list of lenses with actual manufacturer names and base the display on the lens ID or other metadata. They also have some of that info from the lens correction database that usually does recognize lenses from different manufacturers just fine. Could be a good feature request.
The lens ID is listed as unknown in the EXIF for the lens in the example so having a lens ID database would not work in this case.
If the data isn't there how come LR recognizes the lens and applies the correct Lens Profile when "auto" is selected
That is odd. I am out of ideas but maybe the resident EXIF guru John Ellis (you could contact him here johnrellis ) will chime in as solving EXIF problems seems to be one of his hobbies
To build on Bob's and Jao's comments, I haven't completely reverse-engineered LR with respect to lens information, but here is my understanding:
The inconsistencies you're observing are due to LR, not your camera or lenses.
For the purposes of determining the lens profile to apply in Develop, LR uses information stored in the proprietary MakerNotes fields that were written by the camera. Nikons store a numeric "Lens ID Number" field, which is supposed to uniquely identify the lens. For example, the Tamron SP 24-70mm f/2.8 Di VC USD A007N has Nikon Lens ID Number 254. LR (and ACR) look up that lens id number in its lens database to identify the lens profiles that are available.
But for the purposes of showing the lens in the Library Metadata panel, the Library Filter bar's Metadata browser, and searching by smart collections, LR will use the string value stored in the fields EXIF:LensModel or XMP:Lens if those fields are present, regardless of what's stored in the MakerNotes. Some cameras will also write the EXIF:LensModel field (but Nikons don't appear to)
This accounts for why the file Tamron2470_D810.NEF shows "TAMRON SP 24-70mm F2.8 Di VC USD A007N" in the Metadata panel, but the file Tamron2470_OLD.dng shows "24.0-70.0 mm f/2.8". The .dng has fields EXIF:LensInfo, EXIF:LensModel, EXIF:DNGLensInfo, XMP:LensInfo, and XMP:Lens, probably added by the conversion to DNG. If you use Exiftool to delete those fields, then LR displays "TAMRON SP 24-70mm F2.8 Di VC USD A007N" in the Metadata panel, just as it does for the .nef.
However, if the file is missing the EXIF and XMP lens fields, LR appears to be inconsistent in what it shows in the Library Metadata panel and browser. For example, Tamron2470_D810.NEF shows "TAMRON SP 24-70mm F2.8Di VC USD A007N", whereas Sigma35_D810.NEF shows "35.0 mm f/1.4", even though in the latter case LR correctly identifies the full name of the lens in Develop. I don't know what accounts for this inconsistency, other than just a software bug in LR. With capture time, for example, LR is notoriously inconsistent in how it handles files missing the capture-time metadata fields.
I think it would be better if LR consistently used in Library the same lens identification it used in Develop. You could file a feature request for that, but based on Adobe's complete lack of attention to Library metadata the past six years, I doubt they'd ever change the behavior.
For reference, here are dumps for the files in your Dropbox folder. For each file, there is the value of the Lens field in the Metadata panel, the values from the Lens Profile section in Develop, and the output of "exiftool -a -G". Note that the Composite fields output by Exiftool are not actually stored in the files -- Exiftool uses its own lens database to compute the full lens name shown in the Composite fields.