elizabeth_mcmahon_6967477's profile

8 Messages

 • 

180 Points

Fri, Dec 12, 2014 8:02 AM

Closed

Solved

Lightroom: Can't import Nikon D750 raw files that have been modified by Nikon Transfer

I have a Nikon D750 and neither Lightroom nor Photoshop will recognise the NEF files! Am I doing something wrong? So frustrating that I can only shoot in JPEG if I want to use either program, thanks in advance.

Official Solution

Adobe Administrator

 • 

16K Messages

 • 

296.7K Points

7 y ago

Also, does it work if you import the raw files directly from the camera or card directly from Lightroom, bypassing the Nikon software? They may be damaging the files in some way.

1.3K Messages

 • 

22.5K Points

7 y ago

Unfortunately Nikon have changed their file format again and failed to offer DNG as an optional file format. You should update Lightroom and Adobe Camera Raw to the current versions.

8 Messages

 • 

180 Points

7 y ago

Thanks, I have updated both Lightroom and PS, I'll try updating Camera Raw and see what happens then...thanks for the support..

4.5K Messages

 • 

76.3K Points

7 y ago

Even if the NEF file format is the same as other recent Nikon camera models, Lr will not read it if it doesn't recognize the camera model. Ditto for ACR.

As John said, you have to be using the most recent version of ACR for Photoshop to open your files, but the most recent version of Lightroom should open them natively - if it doesn't, your files may be damaged, especially if you transferred them using Nikon Transfer (did you?).

8 Messages

 • 

180 Points

7 y ago

Yes, I've always opened them using the Nikon transfer and never had a problem! I have been using LR and Nikon for years and it's only since I bought the D750 that I've come across this problem. All my software is up to date, including Camera Raw and I'm still having the same problem.

I'll try transferring todays shots with only Lightroom and see how that goes...thanks for your help.

4.5K Messages

 • 

76.3K Points

|> "it's only since I bought the D750 that I've come across this problem"

This utility will fix your D750 NEFs if they've been corrupted by Nikon Transfer (and I'm betting they have been).

http://owl.phy.queensu.ca/~phil/exift...

50 Messages

 • 

556 Points

TransferNX is intermittently working for me and I cannot get any Adobe product to recognize the NEF files from my D750.

50 Messages

 • 

556 Points

I tried the Phil Harvey fix and nothing happened.

458 Messages

 • 

6.7K Points

If Nikon TransferNX2.10.2 is only working intermittently, that suggests you may have a problem with your card reader. This can corrupt images. You might like to try another card reader, or connect your camera directly.

Bob Frost

50 Messages

 • 

556 Points

Bob, I used my camera to import it worked great! Thanks! New MBP on the way. I tried to import through LR CC initially but only 10% of the images were recognized, so I used TransferNX and it worked fine. I never had problems with my d7000, LR4 and PS CS6. That workflow was faster and flawless. I have all my updates but still can't get thing back to normal. Any suggestions for another way to manage?
Thanks,
Bobby

Adobe Administrator

 • 

16K Messages

 • 

296.7K Points

7 y ago

Both Lightroom 5.7 and Camera Raw 8.7 for Photoshop CS6/CC support this camera. What versions are on?

50 Messages

 • 

556 Points

Adobe Labs says they support it but I have yet to get it to work 100% of the time. I've had to import using Nikon Transfer and if it doesn't corrupt the files in the process i am able to move on. I just started using Adobe CC two weeks ago and have updated everything and still not getting 100% of my images recognized.

Adobe Administrator

 • 

16K Messages

 • 

296.7K Points

Do you have the final release of Camera Raw 8.7.1 installed? Can you confirm the version you have installed: http://blogs.adobe.com/crawlspace/201...

If you're using Nikon transfer, make sure you're using the latest version. Older versions corrupt the raw files so Photoshop and Lightroom can't read them.

Sr. Product Manager, Adobe Digital Imaging

50 Messages

 • 

556 Points

Yes to all of the above. I'm wondering if there is a software/hardware conflict. Those things used to happen in the past. I'm getting s new MacBook Pro soon so I'll be able to rule that out.

Adobe Administrator

 • 

16K Messages

 • 

296.7K Points

You could post one of your raw files you're having trouble with for us to help troubleshoot. Again, if you're using Nikon transfer, make sure you're using the latest version. Older versions corrupt the raw files so Photoshop and Lightroom can't read them.

Sr. Product Manager, Adobe Digital Imaging

50 Messages

 • 

556 Points

My new MBP is transferring from the card reader without an issue right now. Which means either my Mini had a bad card reader or there was a software/hardware issue D750,ACC SD card reader issue. The Mini was a Mid 2011 5.2. It still transfers my D7000 SD cards fine so I'm betting on something conflicting between ACC and the Mini's SPECS. Ideas?

8 Messages

 • 

180 Points

7 y ago

Hi Jeffrey, those are the versions I have! I've manually updated both and the app updates automatically. I've imported a couple of shots through Lightroom as opposed to the Nikon software this morning by converting to DNG but I'd really like to use the workflow I've always used....very frustrated right now. Thanks for getting back to me..

Adobe Administrator

 • 

16K Messages

 • 

296.7K Points

7 y ago

Can you post one of the raw files you're having trouble with so we can try to troubleshoot? (use dropbox or Creative Cloud and post the sharing URL here)

8 Messages

 • 

180 Points

7 y ago

It does now Jeffrey, if I bypass the Nikon software it will import and convert to DNG..I can live with that as I've only been using the software to import to a folder on an external drive. I'm back to being able to shoot and import in RAW so I'll delete the Nikon software and just use Lightroom to import and organise. Thanks everyone for your help and feedback, I really appreciate it...Liz

4.5K Messages

 • 

76.3K Points

7 y ago

Make sure you fix the broken raw files Elizabeth (see one of my comments above).

And you're welcome :-)

8 Messages

 • 

180 Points

7 y ago

Thanks Rob, I will. I shot everything in both RAW and JPEG when I realised that there was a problem with the new camera files so I do have JPEG backups too..

458 Messages

 • 

6.7K Points

7 y ago

The problem is that Nikon Transfer is updated regularly by Nikon as part of their updates to NikonViewNX. The latest update is 2.10.2. And just as Camera Raw in LR and CS has to be updated to deal with each new camera, so does NikonViewNX. If you are using an older version of Nikon Transfer, it won't know the details of the D750 or any of the recent Nikon cameras, so it can't transfer it properly, and strange things can happen!

I use Nikon Transfer for all my camera imports and have done for years, without any problems. But I do update it regularly whenever new versions come out. So images taken on my new Nikons transfer fine into LR or CS. I started using it back in the days when the Import function in LR was very flaky. And it still does some things during transfer that LR doesn't. So I continue using it. And by opening the images in NikonViewNX after transfer, it allows me to permanently rotate any images that have been wrongly rotated in camera. LR only makes temporary rotations in its catalog, not in the nefs.

As others have pointed out, Phil Harvey of ExifTool fame, has produced a utility that corrects some nefs that have been copied by old versions of NTransfer, but he needs before and after copies of the transferred files of each camera to work out the corrections.

Bob Frost.

50 Messages

 • 

556 Points

I tried the Phil Harvey fix to no avail. Ended up dragging and dropping the files from my SD card. Then and only then would Adobe CC recognize the files. Nikon released a firmware update today but it had nothing to do with file recognition as near as I could tell.

8 Messages

 • 

180 Points

Thanks Bob, I've been importing straight into LR and converting to DNG since last week but it's not a totally satisfactory solution. I still prefer the import routine with Nikon, I'll update Nikon transfer and ViewNX tonight and see how that goes. Thanks, Liz

8 Messages

 • 

180 Points

Once again, thank you Bob. I deleted all the Nikon files off my main iMac, then re-installed from the disc (that came with the 750) then updated from the Nikon site...tedious but successful! I can now download using Transfer 2 again. Much happier with this solution as I import and store to two different external drives and it's much easier to do than using LR import......thanks.

50 Messages

 • 

556 Points

Elizabeth, interesting that I use to use LR to upload and manage everything with no issues. Since I started using the D750 it's been a problem and none of the RAW files are being read. I started using Transfer 2 directly from the camera and it uploaded fine. But, Adobe Loader/Bridge and LR will no longer work. Has using the DNG converter been a good experience for you?

50 Messages

 • 

556 Points

7 y ago

Seriously, this really isn't solved. Seems to me it should be labeled, " Work around Solution"

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

The take-away here is that if you insist upon using Nikon software for ingestion instead of Lightroom, you have to keep the Nikon software up-to-date. I would categorize that as a Nikon issue because leaving the Nikon software out of the workflow allows Lightroom to work with no errors.
Adobe Photography Products

Quality Engineering - Customer Advocacy

50 Messages

 • 

556 Points

It took two attempts to get the files to import with a new MBP, it helped but when designating to save to a new folder in LRCC the folder was shown as missing. it still didn't function like it should.
When I was using LR4 and the Mac Mini the RAW file import from my D7000 had zero issues!
Nikon Transfer 2 imported my RAW files from the D750 camera body using the Mini via USB connection. After the import the files were then recognized in LRCC.
All my software is up to date, including firmware for the devices and Apple Mac's. I'm banking on a software/hardware conflict between ACC apps, Apple computer hardware and the D750, in some combination.
I tested the card reader in the Mini using a couple different SD card and camera combinations. The only time problems exist are when I use the up to date ACC apps and import from my D750 SD cards(which happen to be Lexar Pro series)
The problem exists when using LR, Adobe Loader/Bridge, Mac Mini's card reader and importing files from the SD card used in my D750. I have 100% success using LR4, Mac Mini and the SD cards used with my D7000 on my Mini but when I try to use Bridge/Loader I get an error every time I attempt to do an import...so far.

4.5K Messages

 • 

76.3K Points

You realize "Bridge/Loader" needs the latest version of ACR (8.7 or better) in order to read D750 raw files, right?

50 Messages

 • 

556 Points

Yes I do, like I indicated before, I have updated everything, including a more powerful computer. ACR updates are what allows Bridge, Photoshop and LR to understand the newest cameras inner work.
My computer background isn't as a professional but I've built enough Windows based PC's as a hobby for gaming and home use. I understand the need for hardware to be up to date as well as software. I worked for the military doing the same, my last job was as a communications superviser or "Signal Officer" for a SOF signal detachment where most of my people weren't just tech geeks they were "Über Geeks" (their words not mine). I fully understand the need for tech to be at 100%.

4.5K Messages

 • 

76.3K Points

If you have the requisite software, and problem not due to Nikon Transfer nor faulty hardware, then I give up. Lotsa people are importing D750 raws without incident, so it sounds like you are having a problem that not everybody is.. Sorry I could not be more help.

PS - I know you said you "updated everything", but did you double-check the ACR version number afterward?

Summary - you can import them with Lightroom v5.7 (or 5.7.1), but not with ACR vX, right?

4.5K Messages

 • 

76.3K Points

7 y ago

I'm all for making the distinction between - "OP has gotten around the problem" and "the problem no longer exists".

It's aggravating to report a bug, and have it be marked "Solved" when the reported problem still exists, whether you've found a way around it or not.

I really don't know whether this problem is best blamed on Nikon, but perhaps Adobe could at least detect it and offer a better error message..

4.5K Messages

 • 

76.3K Points

7 y ago

If problem was card-reader, then marking it "Solved" makes more sense. If problem is Nikon Transfer incompatibility, then "Solved" is overstating it.. - I mean, if the incompatibility still exists, then it hasn't really been solved..

Adobe Administrator

 • 

16K Messages

 • 

296.7K Points

The solution isn't for Adobe to fix. If it works correctly with the latest Nikon software and fixes, then we considered solved.

Sr. Product Manager, Adobe Digital Imaging

4.5K Messages

 • 

76.3K Points

Fair enough Jeffrey, but it would save a lot of poor souls if you at least detect the wonky files and provide a better error message - I'm guessing that would not take much effort. As it stands, people don't know to update Nikon Transfer until after they've fallen down the hole and spent a bunch of time in the forum etc.

50 Messages

 • 

556 Points

Installing from the provided CD/DVD is what most users do. The better solution, in my opinion, is to go to the tech website (for your camera, printer, etc.)and download the latest software for your device. An individual should get the most up to date version that way.

4.5K Messages

 • 

76.3K Points

I think most people understand the latest versions of software are available via the internet.

But in this case, people who don't upgrade unless problem with old or compelled by features in new, just don't imagine the problem they are experiencing in Lightroom could be due to their transfer utility. Detection of problem would be a courtesy to such users, and be one less thing to occupy space and time in the forums.. - if too much trouble, then ta-heck with it - users beware.. (but if not too much trouble, why not detect known problem?).

Regardless, the phrase "solved" means to me:
* remedial action has been taken (successfully).

And so to me, this problem has not been solved. I suppose if you only have a few choices for markings, then "solved" may be better than other choices, but "not our problem" would be a more accurate choice I think.