NikonGear'23
Gear Talk => Processing & Publication => Topic started by: Kim Pilegaard on December 19, 2016, 10:40:20
-
Following the latest update of my Mac now running OS X El Capitan 10.11.6, it seems that Capture NX2 is broken.
I have been a happy user of NX2 for many years and have been reluctant to change to another system, since NX2 was quite sufficient for me.
Now when I open a NEF file with NX2, the picture I get is only partly opened - about 2/3 of the frame is just coloured stripes.
Has anyone else experienced this? Is there any solution to the problem, or do I have to start learning something new (e.g. Photoshop or Lightroom)?
-
The situation is even worse!
It seems that opening a file in NX2 now damages the NEF file.
I dowloaded NX-D, and files I had previously tried to open with NX-2 now look like this. Fortunately, I still have the original files on my Memory Card from the camera.
-
That is bizzare.
Nikon ought to warn users about this issue. Nikon states that the software is OS X 10.11.6 compatible so something is fishy.
-
Never had this, but somethig serious is happening. :o
You said that you still have the photos on the canera's card.
Try to open them with any type of viewer and see if the photos are not corrupted already on the camera's card. I have that on one of my cameras just due to a bad card... and nothing else.
Please note that NX2 stopped being upgraded and newer cameras are not supported.
If they are ok, make some copies to the hard disk in different locations.
Do tottally clean the previously NX2 instalation, not only putting it on trash, use appdelete or similar apllication and reinstall.
Open the files in one of the locations and see.
Still happening? Forget NX2, and use something else
-
I better make sure that the files on the memory card are OK. I will do that tonight. If the files were corrupted in the camera, it is not due to CNX2.
-
Also try another SD card. Try to look at a few of the images in the camera as well. That should help in the elimination process.
-
Fortunately, the NEF files on the card are fully intact.
So it must be something related to the software I used: Nikon Transfer, Nikon View NX2, and/or Nikon Capture NX2.
I noticed that the problem was most severe in the beginning of the downloaded lot of pictures. The last part of the downloaded pictures was taken in DX format, and they were fully intact. Also nothing was wrong with the preview part (jpeg).
-
Did you just check the photos in camera or did you download it elsewhere and checked?
-
I copied the files from the card to the MacBook without using Nikon Transfer. I then opened the files in Photoshop without any problems.
-
I copied the files from the card to the MacBook without using Nikon Transfer. I then opened the files in Photoshop without any problems.
Clean and reinstall all Nikon software
-
A long shot but are you using an old version of Nikon Transfer? I had a few unimportant NEF(s) damage by the version of Nikon Transfer that came with an older camera (D2H/D300s). I loaded the version of Transfer from the D800 and never had the problem again.
Dave Hartman
I don't have CNX-2 on my MAC as it came to me with El Capitan already installed. I still have CNX-2 on my Windows 7 computer.
[EDIT: to be safe always use the version of Nikon Transfer that came with your newest camera or a version that is newer that that. ]
-
Kim, if you haven't already done so clear the cache for NX-2 and NX-D. If you are *familiar* with the Library folder in Finder, feel free to look in Application Support and in Caches for any Nikon caches as well. Then restart your Mac.
Copy the originals from the SD card to a different folder on your Mac using either Finder or Transfer from within ViewNX2.
Use Quick Look to check the newly downloaded photos: https://support.apple.com/kb/PH18813?locale=en_US (https://support.apple.com/kb/PH18813?locale=en_US)
If they look ok then try viewing them in View NX2 or C-NX2
Edit: Forgot to add the David is correct to warn against using Nikon Transfer - Use Nikon Transfer 2 only. It is included with View NX2 and View NX-i.
-
The problem with NX2 is that it interferes / writes into the NEF file; apparently this isn't the case anymore with NX-D which keeps changes in a sidecar file. NX2 is neither supported or maintained anymore, this is danger zone when operated under a new OS.
-
Thanks to all for good advice.
I cleaned up everything and re-installed VNX2 and CNX2 from my backup. Apart from the normal problem of CNX2 freezing up from time to time, everything works OK.
The conclusion is that something must have gone wrong during the transfer. BTW, I used Nikon Transfer 2 all the time.
I am considering moving to Lightroom, although I find it more convenient having the editing information stored in the NEF files rather than having a catalog to take care of, complicating the moving of edited files from one computer to another.
I briefly tried View NX-i and Capture NX-D, but I really don't like them.
-
Thanks to all for good advice.
....
I am considering moving to Lightroom, although I find it more convenient having the editing information stored in the NEF files rather than having a catalog to take care of, complicating the moving of edited files from one computer to another.
...
I recommend you to have an in depth review of Lr. Indeed, the Lr catalog keeps all changes outside the NEF file and within the catalog. Nevertheless, all more proficient Lr users set their Lr parameters up to ALSO keep the sidecar files together with the image libraries. So if something goes wrong with the Lr catalog, or, if you have to export your images to another application the NEF file has always his sidecar companion. Interfering with the NEF file integrity is a not so innocuous activity, but I leave it up to you .... 😊
-
The problem with NX2 is that it interferes / writes into the NEF file
Well, most of us do save the original NEFs and never put them into any converter. Only copies get converted and edited.
But in all these years and years and years I've never had anything go wrong with a NEF due to being converted and edited in NX2. YMMV, of course. The NX2 edits are written to a contained area of the NEF file. The raw data is not altered.
-
To add to Andrea's comments, my biggest gripe with Ps are the huge files left when you save layered .psd.
Also, no matter which software you use corruption can occur. That is why a backup copy of the original should never be opened or even renamed.
My oldest edited NEFs are now 10 years old. I like being able to open any of them up and editing a new version using skills learned over the past decade.
-
Original / copy, you name it. Lr allows you to store directly away a second copy of the downloaded file. But, this is not the subject. Interacting in a RAW file is practice that even Nikon avoids now. Up to you to qualify the former method as risk free.
-
Does anyone reading this thread know to install the latest Nikon Transfer 2 for Windows. I used to be able to download the latest Transfer 2 from the Nikon download center. I can't find it today. Now I find I'm using the version installed by the last version of VNX2. When I check for updates I'm told there are none. Perhaps the only way to get it is to install ViewNXi?
Is it time to dump VNX2 for safety since it's not maintained? The version of Transfer that came with it can write to the NEF. Perhaps old versions of Transfer write to the wrong area of newer NEF(s)?
I rename NEF(s) when I save them with CNX2 just in case so I don't over write the original.
Dave Hartman
-
Does anyone reading this thread know to install the latest Nikon Transfer 2 for Windows.
Dave Hartman
A few versions back, Transfer 2 was included with ViewNX2, and that seems to be true for ViewNXi. On my Mac, Transfer 2 can be called up from within ViewNX2/i or as standalone.
-
I upgraded my Mac to Sierra 10.12.2 this morning and experienced the same problem with my files as you did Kim. I am using the the latest editions of View NX-1 and Nikon Transfer 2. To my mind, the problem is that the latest Mac upgrade is not compatible with the latest Nikon software.
As always seems to be the case, Nikon lags behind Mac upgrades, but incompatibility issues like this have heretofore not cropped up for me. Fortunately, the shots seem not to be lost, and I believe the complete NEF files are hiding behind these stripes because I opened them in Photoshop Bridge and the full files initially appeared but then the stripes soon appeared thereafter.
When those crack software support people at Nikon get it together to support Sierra 10.12.2 sometime in 2017, I'll wager these files will open just fine. By then, I probably will have completely stopped using Nikon software so compatibility will be moot. Iridient and Photoshop here I come!
I am beginning to really hate Nikon software. >:(
-
I am beginning to really hate Nikon software. >:(
You, me and a whole lot of other folks!! I've held back from upgrading my MacBook pro because I do not want to lose the old Capture NX2. Sooner or later I will have to abandon that strategy because nothing will work on Mountain Lion any more. I kinda hate Apple too for constantly making us upgrade. There is no way to keep a stable platform for 5 years or so.
The whole photo software thing in general is beginning to get me down. I'm tired of converting and editing raws in klunky, tedious software. But I don't really want to shoot JPGs either. These days I find that I'm still making lots of photos but they are just sitting there on the hard drive, unconverted and unedited. Why does this have to be so much work??
[end rant]
Sorry, I got a little rant-y there !!! ;D ;D ;D
-
The whole photo software thing in general is beginning to get me down. I'm tired of converting and editing raws in klunky, tedious software. But I don't really want to shoot JPGs either. These days I find that I'm still making lots of photos but they are just sitting there on the hard drive, unconverted and unedited. Why does this have to be so much work??
[end rant]
Yes! I too am collecting too many files on my hard drives waiting for some way to make things easy again (i.e. limiting complexity without losing capability while being sufficiently intuitive to bring a smile to my face and avoid excessive grinding of my teeth). Last week, I spent about ten hours going through a Photoshop tutorial from Lynda.com and while that program sometimes makes me feel like I'm drowning in quicksand, the lessons actually opened a door and let in some light. Hooray!! 8)
-
I am beginning to really hate Nikon software. >:(
You, me and a whole lot of other folks!! I've held back from upgrading my MacBook pro because I do not want to lose the old Capture NX2. Sooner or later I will have to abandon that strategy because nothing will work on Mountain Lion any more. I kinda hate Apple too for constantly making us upgrade. There is no way to keep a stable platform for 5 years or so.
The whole photo software thing in general is beginning to get me down. I'm tired of converting and editing raws in klunky, tedious software. But I don't really want to shoot JPGs either. These days I find that I'm still making lots of photos but they are just sitting there on the hard drive, unconverted and unedited. Why does this have to be so much work??
[end rant]
Sorry, I got a little rant-y there !!! ;D ;D ;D
Yes, processing is becoming a chore. I have a huge backlog. I have to send out some photos from a trip, and I am bogged down by the sheer quantity.
I am now going to try shooting raw + Jpeg fine, and only process a tiny number of photos, those that will really be worth the time. For the rest, jpegs will just have to do.
-
I'll wager these files will open just fine.
I would not take the chance. I would transfer my files with Finder and not touch the originals.
Not sure what View NX-1 is? Is that View NX-i or an older version. I'm running View NX2 on El Capitan without issues. I'm wondering if View NX-i is stable yet on this OS?
Capture NX-D works fine of my iMAC except it's deathly slow as my iMAC is up there in years. Capture NX-D works fine on my Windows 7 box and I generally prefer it now to Capture NX2. I still would like to have seen Capture NX3 but Google apparently killed that.
Anyway I would not bet on Nikon Transfer if it appears to be incompatible with your version of OS X.
Best,
Dave Hartman
-
Set up a powerful Linux box and run visual machines inside it. Then you can get stable OS ecosystems over really long time spans. No need to "upgrade" the OS continuously.
With decent hardware, the performance penalty of going the virtual route is minimal.
-
I upgraded my Mac to Sierra 10.12.2 this morning and experienced the same problem with my files as you did Kim. I am using the the latest editions of View NX-1 and Nikon Transfer 2. To my mind, the problem is that the latest Mac upgrade is not compatible with the latest Nikon software.
Exactly what happened to me ! At first I thought I had developed a shutter or mirror problem, then surmised that it had to be the software as I had a Nef+Jpeg setting and the jpegs were without the black stripe ! Seems like a memory problem for the Nikon Transfer 2...
Anyhow I've shifted to Lightroom for downloading and placing my files in my exterior hard disk while cataloguing them. Seems to work nicely !
-
I would not take the chance. I would transfer my files with Finder and not touch the originals.
Not sure what View NX-1 is? Is that View NX-i or an older version. I'm running View NX2 on El Capitan without issues. I'm wondering if View NX-i is stable yet on this OS?
I meant VX-i which I believe is the only viewing program that Nikon is still updating (assuming they continue to do so). Until I updated my Apple system software, VX-i worked slowly but worked nevertheless. Now I get the stripes. My contention is that once Nikon catches up in their upgrades to this program, it will be able to access these striped nef's. However, I will not be using it in the meantime and if there is a better way, I may throw in the towel on all Nikon software altogether. For the foreseeable future, I will be using the finder or some other software to transfer files as you suggest.
-
Exactly what happened to me ! At first I thought I had developed a shutter or mirror problem, then surmised that it had to be the software as I had a Nef+Jpeg setting and the jpegs were without the black stripe ! Seems like a memory problem for the Nikon Transfer 2...
Anyhow I've shifted to Lightroom for downloading and placing my files in my exterior hard disk while cataloguing them. Seems to work nicely !
Thanks for the advice. I have Lightroom but have never really used it so perhaps will give it a try. Something will eventually reveal itself as a good solution!
-
Set up a powerful Linux box and run visual machines inside it. Then you can get stable OS ecosystems over really long time spans. No need to "upgrade" the OS continuously.
With decent hardware, the performance penalty of going the virtual route is minimal.
Thanks Bjorn. I am sure you're right, but your solution is incomprehensible to me and setting up a whole new system of hardware and software is too daunting a prospect. It would probably reduce me to pulling out my hair in a fit of frustration and despair!
-
I believe the version of Nikon Transfer form VNX2 can modify the PICT information so the NEF(s) uploaded are not virgin. It seems this could be a problem.
Using VNX2 to add a few stars to an NEF causes sync software to want to update copies on a quick backup HD so an archive NEF is needed immediately on upload. I don't truly sync but rather contribute but I have the problem of possibly over-writing a Good NEF with one that's been corrupted. From there all saved copies could be corrupted. I need new procedures and hard drives.
Dave
-
Mine broke yesterday too. Any idea how to fix the corrupted files?
-
If you have not deleted the files on the memory card, you can just copy them to your computer with Finder or similar. It seems that only Nikon Transfer is broken. On my system View NX2 and Capture NX2 still works.
-
Mine broke yesterday too. Any idea how to fix the corrupted files?
It may be that Nikon Transfer 2 as included in ViewNX2 is the problem. ViewNX2 is NOT supported and the Nikon Transfer 2 included with it is NOT supported. Moreover it you check for an updated Nikon Transfer 2 from the one installed by the last ViewNX2 an UPDATED VERSION WILL NOT BE FOUND. It is probably time to install Nikon ViewNXi and use it rather than ViewNX2. If one is going to continue using Nikon Transfer 2 (which should be named Nikon Transfer 3, that is the one included with ViewNXi) install ViewNXi to get the latest Nikon Transfer 2.
Note that ViewNX2 writes to the NEF file when you do things like add stars. Since it is not supported at anytime it might start corrupting NEF(s).
Still using CaptureNX2 for NEF files? I recommend saving an NEF file for this specific use, e.g. copy D800_DSC9999.NEF to something like D800_DSC9999_CNX2.NEF. Now edit the copy. The original NEF will not be written to by ViewNXi and its Nikon Transfer 2 only a sidecar file such as D800_DSC9999.nksc. The same goes for CaptureNX-D. It will not write to the original NEF only to the associated *.nksc side car.
I have not fully tested this but I'm not finding that adding 5 stars to an NEF file in ViewNXi does not write to the NEF. This is all on Windows 7. I will install ViewNXi again on my iMAC and test it but my iMAC is running OS X v10.11.6 (El Capitan) and not OS X v10.12.x (Sierra).
Play it safe: upload NEF(s) with Finder FIRST and then try and see if ViewNXi and it's associated Nikon Transfer 2 cures the problem.
I hope this thread helps save someone's bacon!
Dave Hartman
I hope I found all the typos. I wrote this pretty fast. I'm reading on other forms about people having corrupted NEF(s). I'm trying to help so people don't loose valuable NEF(s)!
-
After a bit more poking I found this when I selected... Preferences> [X] Add additional information to files, XMP/IPTC Preset
Are you using the latest version of ViewNX-i?
Before using this setting, please make sure that this version of ViewNX-i is compatible with your camera. If you are using a version of ViewNX-i that is not compatible with your camera, RAW image files transferred with this setting turned on may not function properly.
Would you like to turn on this setting? [yes] [No]
--Nikon Transfer 2, v2.12.4
So when using this feature of the latest Nikon Transfer 2 it does write to the NEF under this condition so one should be careful to use a version of Nikon Transfer 2 that is as new or newer than the camera. If it's not as new as the camera it may cause problems with CaptureNX2 and or CaptureNX-D.
To play it safe use only the latest version of Nikon Transfer 2 that is installed with the latest version of ViewNXi
To play it even safer use Finder instead of Nikon Transfer 2.
Dave Hartman
OK, I think I've beat this horse long enough. If it doesn't get up and run it might be dead. :)
---
If memory serves me I lost a few early test photos with my D800 by using Nikon Transfer that shipped with my D300s. I think the damage was similar to that shown in the first post. I didn't save those damaged NEF(s). They were inconsequential. I solved the problem by installing Nikon ViewNX2 as shipped with my D800.
-
Here it is... :o
http://nikonrumors.com/2016/12/29/nikon-reports-possible-view-nx-i-image-data-corruption-when-using-nikon-transfer-2-on-the-latest-versions-of-macos-sierra.aspx/
-
I just did a bit by bit comparison of an NEF transfer to my iMAC with Nikon Transfer 2 v2.12.4 to the NEF still on my CF card. I added XMP/IPCT info using Add additional information under the Preferences tab. The copy with "additional information" was a perfect match to the one still on the CF card: no information was written to the NEF by Transfer 2 v2.12.4. Side car files were written.
Film at 11:00 :)
So if NEF are being corrupted it must be that a version of Nikon Transfer 2 that shipped with ViewNX2 2.10.3 or earlier is being used and not one that shipped with ViewNXi v1.2.4 which again is Transfer 2 v2.12.4. Nikon really should have called the VNXi version Transfer 3 as placing XMP/IPCT in a side car rather than in the NEF is a significantly different approach.
All this said I am testing with OS X 10.11.6 El Capitan on the MAC not Sierra.
Again: use Finder to be safest and look for a stand alone updated Transfer 2 from Nikon. If still on El Capitan Transfer 2 v2.12.4 is safe according to my tests. YMMV!
Finder! Finder! Finder! :)
Dave Hartman
The horse didn't get up and run yet but I want to save people some grief and possible loss of photographs.