P: Lens metadata field missing on import

I recovered my previous (Lr 5.7.1) library and went back to working there - thus wasting my subscription for now...
Hence my frustration!

Lightroom CC 2015.5. Nikon NEF files loaded after 3-12-15 do not have the LENS information in the EXiF file showing in the Library module for pictures taken with the same lens and camera. The LENS information does show in the exif files when looking at the picture on the camera. What has Adobe lost?

I managed to uninstall LR6.5 and installed 6.4 and then just read the metadata from file again. That solved the exif lens metadata issue. Now need to wait for the next update as 6.5 is messing up metadata.

Massively frustrated!!
I have been holding off buying CC for months but finally went for it a few days ago and now on the first import of new images I find I loose the EXIF data for the lens in the Library module. Grrrr...
Filtering my images by lens is something I do frequently, and in the case of this job, is important.
Rant Mode = Off (now)

So, Mr Adobe, went can I expect a fix? And, will it display the lens information for the images I just imported?
Thanks

Hello,

Not sure if this has been reported before. I always use developer view options (Ctrl + J) so I can see the common attributes and exif data. However, Lightroom is not showing lens information or the name of the lens used when choosing common photo settings / Lens / Camera + Lens / Camera + Lens setting. This was not happening before, but happening now with the 6.5 update.

Please can this be fixed in the next update?

Many thanks,

Manzur

As Steve posted several comments back:

Unless you need brand-new camera support, the workaround is to roll back to LR 6.4/2015.4 by uninstalling LR 6/2015 completely--but leave the preferences, don't delete them, then reinstall LR 6/2015, then the .4 update patch, both of which can be downloaded from here: 

http://blogs.adobe.com/lightroomjournal/2013/06/keeping-lightroom-up-to-date.html#lrcc2015

IMHO, for now this is the best solution to the problem. I mean, Adobe doesn't move fast, and even if they do come up with a "fix" who know what else they may break as evidenced in this 2015.5 update?? Go back to 2015.4, like I did, and wait until Adobe fixes this. And even then, I'd wait to see what other bugs they may introduce in the next fix.

I agree, can we please stop cluttering this thread with DNG vs NEG etc discussions. I want to be informed about the fix for this and please vote to get this fix. Any other discussions are only distracting. I subscribed to this thread because I want to know when it is fixed and not get my maibox full with age old DNG vs native RAW discussions

My initial post was not about the merits or drawbacks of DNG; it was, instead, a comment about the bug in Lightroom that seems to obscure lens information. Nevertheless, the discussion about the merits of DNG is an important one. RAW formats are proprietary and closed -- the Nikon cameras I use produce NEF files that are unique to Nikon; they are hardly open format, and should Nikon go bust (which, given the declining sales of DSLRs in the face of competition from other devices, is a real possibility), the NEF format might well be orphaned. This has happened before, and with formats that we all thought at the time might have a fairly long life. (I have old Word for DOS files archived -- and these cannot be opened by current version of Word. The same is true of a host of other file formats we blithely assumed would be readable in the future.) When I print images, I seek out papers and inks that have a long life; when I create a digital image, I hope that I can anticipate some of the changes that might render my images inaccessible. The NEF format is closed and inaccessible; the DNG standard is open and published. Does that mean that DNG is always superior to NEF? No, of course not. But I want my images to be available in five, ten, or fifty years. And so I hedge my bets -- I do both. Some will no doubt groan at this profligate use of hard drive space -- but the cost is relatively small.That said, I return to the problem of Lightroom and lens information, which seems to have nothing to do with the choice of NEF or DNG, and everything to do with a bug that Adobe needs to fix quickly.

Having the checksum built in to the file format is indeed useful; knowing that a file is corrupt lets you know when you should restore an earlier version of the file from backup. The earlier you know this, the better.

You don't need to convert your files to DNG in order to do this though; I'm currently writing an application that indexes your files and keeps a database with a validation checksum for each one.

I agree with Matt, if a file is corrupt, it is corrupt.  All "integrity checking" does is verify the obvious.