I've been a huge supporter of Nikon cameras for 40 years and have also recommended NX2 many times. But I'm done. It is ####. It crashes all the time, takes forever to load images, if they load at all, and then won't restart after it crashes. Nikon should be ashamed of themselves and they owe me my money back. Am I pissed, yes. I'll stick with Lightroom.
#2. "RE: I've had It With Nikon Software" In response to Reply # 1
Aliso Viejo, US
It used to be for me also. Then View NX started acting up and now NX2. Both have had the latest updates and have been reloaded several times to see if that would fix it. I have a very fast computer running Windows 7 Ultimate and all other software runs perfect included CS5 and LR4. It just started doing this a few months ago and now it's not even usable. I used to be like you and now I'm one of them. I wouldn't care if it was $50 but anything priced like NX2 should run. I'll try to reload it again but that's it.
#3. "RE: I've had It With Nikon Software" In response to Reply # 2
Aliso Viejo, US
Well I reloaded everything including the updates for NX and it seems to be running OK. I also reloaded ViewNX2 again but it just won't run right so who knows. I hate to be a whiner but I just had it with Nikon software. I'll give it another try though. Thanks for responding.
#4. "RE: I've had It With Nikon Software" In response to Reply # 3
San Jose, US
Hecky we all get a bit mad at our computers from time to time. I am running a Win 7 Pro 64 bit machine too. I have an Intel i7 2600K processor, 16 GB of RAM and an XFX Radeon 6970 video card, all this mounted on an ASUS motherboard. I use both SATA 3 and SATA 2 internal drives and also have a Network attached drive and both USB3 and USB2 externals. I use a Wacom Intros 4 tablet and even with all this stuff and many many windows programs, my VNX2 and CNX2 run flawlessly in 64 bit mode. My images open quickly and I like Mik have been pretty much bug free since the 64 bit version came out. Perhaps it is something else on your computer that is conflicting with the Nikon Stuff. The fact that reinstalling seems to have fixed your problem makes that even more of a likelihood. I run Norton for my security system and use Diskeeper as my defragger. I am also using two backup programs Acronis and Retrospect for automatic backups. I also run Photoshop CS6 Extended and the rest of the programs in the CS6 Production Premium Suite. I am running my video card in conjunction with on board graphics using VIRTU that does an auto switch as needed and that usually gives some programs fits and the only program that had a problem with that until I made a simple change was Adobe Premier Pro CS6. If everything else on your computer is working without problem you may want to tell Nikon what you have running and see if they know of any conflicts. While I don't use LR it seems like I have seen some problems posted about it, so just changing SW may not really be a solution either. I hope you figure out what your problem could be.
#5. "RE: I've had It With Nikon Software" In response to Reply # 0
Bowling Green, US
I certainly agree with Bob. It sounds as if your problem is machine oriented. I have run it on several rigs which I have assembled without any problems over the last6 years. I cannot recall the last time it crashed. Loading time even for D800 NEF files are nearly instantaneous. Intel Core i7-3930K Sandy Bridge-E 3.2GHz LGA 2011 Corsair H100 CPU Cooler ASUS Rampage IV Formula LGA 2011 Intel X79 Corsair Vengeance 32GB (4 x 8GB) 240-Pin DDR3 EVGA GeForce GTX 580 (x2) SLI Thermaltake PSU TP-1000M 1000W ATX Crucial Real SSD C300 256GB SATA III x2 WD Caviar Black 1 TB 7.5K 1001FALS SATA II Samsung 12x BD-ROM 16X DVD-ROM SATA Internal Blu –ray Combo Model SH-B123L/RSBP Planar PX2611W 26" Widescreen LCD Monitor Logitech G15 Keyboard Logitech G9X Laser Mouse
#6. "RE: I've had It With Nikon Software" In response to Reply # 0 Fri 03-Aug-12 05:56 PM by gkaiseril
Much more information might be helpful.
I would also look at cleaning up and defragmenting your hard drive. Empty your systems trash can. Then check that you have your computer OS fully updated and update your Nikon software. You might want to check and adjust your systems virtual memory.
What brand of computer? What processor model, clock speed, and how many cores are you using? What OS are you running? What is the amount of RAM memory installed? What size is your virtual memory set at? What is the amount of free disk space that you have?
#7. "RE: I've had It With Nikon Software" In response to Reply # 6
Aliso Viejo, US
Thank you everyone. I understand it could be my computer but I haven't made any changes lately except for regular Windows updates. This time NX2 loaded OK and is running fast and properly. However, View NX2 won't run properly. While I can use Bridge or NX2 to browse images I kind of like View to do that so we'll see.
#11. "RE: I've had It With Nikon Software" In response to Reply # 7
San Jose, US
Hecky have you removed all traces of your old VNX2 and VNX installs? Nikon has a tool for doing this. You may have some crud left in your Registry that is causing conflicts. What is happening with VNX2 to make you say it is not running properly? Does the built in Transfer program work? Are the files loading slow? I too use VNX2 to browse my images before I move them to CNX2. I am running CEP 3.0 and have installed the patch to work with CNX2 64 bit. Again no issues.
#12. "RE: I've had It With Nikon Software" In response to Reply # 11 Sat 04-Aug-12 01:04 AM by gheck58
Aliso Viejo, US
Thanks Bob I'll check that out. It's not really what it does it's what it doesn't do. You can click on a file to open it up and the images will take forever to open or not open at all. Then it will crash and not allow you to close the program unless you shut the program down in Task Manager. Then even when you do that, it will still be running in Processes and you have to shut that down. This happened on both View and Capture. But so far Capture NX2 is OK again. And it is running fine on my 64 bit laptop.
#14. "RE: I've had It With Nikon Software" In response to Reply # 13
Aliso Viejo, US
Hey Bob, I looked around for the Nikon Registry Sweeper and can't find it. I see Nikon Rumors had a message about it but it's no longer on the European site and not on the USA site. Do you know where to find it?
#15. "RE: I've had It With Nikon Software" In response to Reply # 0
You might try downloading Microsoft's Process Explorer program. It's part of the old Sysinternal suite of tools. This link runs it from their cloud, which I've never used.
I'm old school so I just download the apps here . Put them in a folder and just click the app in explorer. You may need to add the folder to the user or system path although I think procexp.exe may not need it unless you want to access the help. Or you can drop what you need into d:\windows or some other folder that is always in the path (after a suitable battle with UAC of course).
You want to fire up ViewNX and then open up Process Explorer, looking at the (I suspect rather long) list of DLL's and other objects that ViewNX is loading. You're looking for something that "doesn't look right", either an old file date or especially something loaded from a folder that you wouldn't expect ViewNX to be looking at.
Years ago I had a problem with this, related to Nikon DLLs, and was able to diagnose it this way. The problem may not be Nikon at all, but some other app that is colliding with it by installing its own versions of Nikon's DLLs. Or an incomplete uninstall of some prior Nikon app version. Or some such related thing.
(I had something like 4 different versions of Nikon's DLLs on my machine, related to old Nikon versions, other apps, etc. It was a mess)
This is a good practice to diagnose any misbehaving app, not just Nikon's. Job #1 is to confirm the app is loading the right version of everything.
The registry cleanup is a good idea too, but this may fix the problem and if it is the problem then registry cleaning may not help. Unless the registry has some old obsolete path, for example, in which case Process Explorer would show you the symptom but not the cure
#16. "RE: I've had It With Nikon Software" In response to Reply # 15 Sun 05-Aug-12 06:20 AM by gheck58
Aliso Viejo, US
Thank You Neil. I ran CCleaner and cleaned a lot of stuff up and then reloaded View NX2 but it still locks up and crashes. I'm done. I'm sure glad my cameras and lenses work better then their software.
#20. "RE: I've had It With Nikon Software" In response to Reply # 16
>Thank You Neil. I ran CCleaner and cleaned a lot of stuff up >and then reloaded View NX2 but it still locks up and crashes. >I'm done. I'm sure glad my cameras and lenses work better >then their software.
You really should have taken a look at things with Process Explorer before throwing in the towel...
#21. "RE: I've had It With Nikon Software" In response to Reply # 0
Table Top, AU
Try something else. I use DxO Version 7.2 on a very old Mac with no problems. The defaults are excellent and it took very little time to learn. I use Graphic Converter for final sharpening and cropping.
#22. "RE: I've had It With Nikon Software" In response to Reply # 20
Southern CT, US
>Years ago I had a problem with this, related to Nikon DLLs, and was able to diagnose it this way. The problem may not be Nikon at all, but some other app that is colliding with it by installing its own versions of Nikon's DLLs. Or an incomplete uninstall of some prior Nikon app version. Or some such related thing.
I'll bet you're exactly right as this is a common issue with a lot of software. There are common utilities that are shared among programs. Some software installations will load and older or newer versions which may cause compatibility problems with the software apps that use them.
Does anyone know what programming language ViewNX and CaptureNX is written in?
#25. "RE: I've had It With Nikon Software" In response to Reply # 24 Mon 06-Aug-12 03:09 PM by gheck58
Aliso Viejo, US
Thanks again Neil. I am going to have my IT guy work with me today on your suggestions. I actually like what Nikon's software does (Capture NX2) but I do most everything in LR4 now. The profiles are pretty hard to distinguish from Nikon's and everything is way faster, especially batch processing. But I do like using View as a browser so I'm going to try and make it work. As to the previous post, I don't have a "rig" problem but I appreciate your comment.
#26. "RE: I've had It With Nikon Software" In response to Reply # 25
I use PhotoMechanic for most of my browsing but I find ViewNX very helpful for no other reason than that it gives access to certain maker notes that other browsers can't deal with. I'm thinking about focus distance and the focus point. So I consider it "worth salvaging".
It's a good browser but I bought PM years ago when the old View was not such a good browser and got accustomed to living the high life on the browser front .
Let us know how it turns out. My suspicion is that if it won't run then it is most likely referencing one or more wrong DLLs.
If you play around with Process Explorer you will learn a lot about how Windows apps are "put together" in terms of their modular structure that is so reliant on all this DLL versioning. Plus many other interesting and entertaining things that Task Manager won't show you . I always thought Microsoft should have integrated that into Task Manager as some sort of "Advanced" display off of the Processes tab.
I'll close by suggesting that the internet is full of people complaining about how their registry cleaners hosed their OS build ups or certain apps. Most of what they remove is unintelligible hex keys so it's hard to look over their shoulders.
I think it's better to use tools like Process Explorer to find a problem like this and use reg cleaners only as a final "Hail Mary Pass" when all else fails. I've kept OS builds going for up to 5 years without ever using them. But I use tools to revert the OS partition back to some known working state when I have a problem (and problems do always happen from time to time). Something like Acronis but I use a somewhat higher end app called ShadowProtect.
#27. "RE: I've had It With Nikon Software" In response to Reply # 25
San Jose, US
Wer you not able to use the link to the Nikon regsweeper that I sent you? One other choice is for your IT guy to just go into the Registry and search for all VNX, VNX2 references and delete them and then reload VNX2. I have used that brute force methods sometimes to get rid of pesky programs that snuck on my computer uninvited and would not actually get deleted when I uninstalled them with Windows tools.
#28. "RE: I've had It With Nikon Software" In response to Reply # 27 Tue 07-Aug-12 04:09 AM by gheck58
Aliso Viejo, US
That link to Nikon Rumors and then to the Nikon Reg Cleaner said it was no longer available. I would like to try Neil's suggestion also but I'm not hat software savvy. I'm in the electronics business an know the hardware backward and forward but not the software side. I'll have my IT guy try that and get back to you all. It's funny that Capture NX2 runs fine now but not View.
Oh, I was going to ask. Do you think having two NEF Codec's (Ardfry Imaging and Nikon's) would have any effect? Again neither Capture, LR, or CS5 are problematic. Only View.
#29. "RE: I've had It With Nikon Software" In response to Reply # 28
>> Do you think having two NEF Codec's (Ardfry Imaging and Nikon's) would have any effect?
That is called "intentionally creating DLL havoc"
Think about it. A NEF codec is an interface between image files and various apps that are displaying files to you. It is all done behind the scenes- you don't pick which codec you want to use each time your app displays an image.
You need to make that choice in terms of which (ONE)codec you run. You should only have one installed.
I use iMatch, which is an image cataloging app that is heavily reliant on these WIC codecs. I have seen iMatch problem reports similar to yours, and then resolved by uninstalling BOTH codecs. You should reboot in between uninstalls, just to make sure they are cleanly uninstalled.
I've bounced between the Nikon and FastPictureViewer codecs, trying to optimize my iMatch performance and resolve a strange bug iMatch seems to have with FPV, but I always uninstalled and rebooted in between installs. Never had both live at once. I'm not familiar at all with the codec you use.
Although CaptureNX and ViewNX may both use Codecs, they use them differently. Capture probably only uses codecs to show you the film strip thumbnails. ViewNX is likely using the Codecs to display the full size embedded JPG image - unless you configure it to always render NEFS, in which case it would act more like CaptureNX (and performs more like it too in that mode!).
Thinking about it, Nikon's apps may not use the WIC codecs at all - as I recall they run fine without installing it (Nikon's). But you should only have one installed and since you are having problems this is a good problem solving procedure just to eliminate this possibility.
I suspect Process Explorer will not help you with any codec problems because that runs through the Microsoft WIC dll (WindowsCodecs.dll). Having never delved into the innards of the WIC codec structure I'm not sure what else might show up in Process Explorer to point out some sort of codec collision (especially from running 2 different versions at once, as you are doing now).
#30. "RE: I've had It With Nikon Software" In response to Reply # 29
Aliso Viejo, US
Thank you again Neil, I'll uninstall one when I get home this evening. I have been using the additional Ardfry Imaging Codec so I can display the NEF thumbnails in Windows. Then, are you saying that I don't need either? Does Capture NX2 or View NX2 have the Nikon Codec built in or do I need to at least have the separate Nikon Codec installed?
#32. "RE: I've had It With Nikon Software" In response to Reply # 30
You should uninstall BOTH codecs, re-booting in between uninstalls. Then re-boot AGAIN after uninstalling the second one.
DO NOT uninstall just one, and DO NOT uninstall both without re-booting in between. Trust me on this.
When I researched codecs I ran into discussions involving people having issues because they did not uninstall both, or short cut the process by skipping the interim re-boot. When they finally did it "right", as I suggest here, their problems generally went away. I think this was mostly issues with iMatch but any app that uses them would have similar problems with "ghosts" left behind.
The double uninstall with boots between "jobs" prevents errant objects from getting "stuck" in Windows because they were locked by something. And codecs are "automatically" locked solid by Windows. The idea is to do everything reasonable to make sure you are fully cleansed of both codecs before re-installing the codec of your choice.
I really can't recall if Nikon apps need the codec installed separately and on a quick look do not see it listed as a requirement. If the thumbnails on the light table displays don't properly show the image thumbnail then you need it.
The codecs are mainly used by Windows built in apps. Windows Explorer, Media Viewer, etc., use them to display proper NEF thumbnails.
Some apps, like iMatch, have also used them. With iMatch it is optional but highly recommended by the developer (long story not important here).
The main advantage of a 3rd party codec pack is that you take care of all the major camera maker's codecs in one shot. Otherwise you would have to download and keep current Nikon's, Canon's, Sony's, etc. One stop shopping if you have the need.
A *possible* secondary advantage is that some codecs claim to be faster and more efficient, or users make that claim, which is why I tried FPV. I have some performance issues with iMatch that I wouldn't mind mitigating although I don't think FPV really helped in my case.
There might be other subtle benefits. But if you only want access to Nikon raw files then it is not clear to me what *obvious* benefits you get from a 3rd party codec. I have not had any problems with ViewNX2 or CaptureNX2 using FPV but I have no experience at all with your codec.
I know I'm raising more questions than answers but I guess I'm trying to say that it shouldn't hurt to stick with Nikon's codec unless you have a very well defined and compelling reason. And in your case, having problems with Nikon's apps, if it were me I would first do the clean uninstall and then install Nikon's codec, just to make 100.0000% sure that your 3rd party codec is not the problem.
Also make sure you have current versions of whatever you install. The WIC codec concept is fairly new so it went through the usual teething process. One advantage of Nikon's is that it is free, as well as continual updates.
#33. "RE: I've had It With Nikon Software" In response to Reply # 0
>I've been a huge supporter of Nikon cameras for 40 years and >have also recommended NX2 many times. But I'm done. It is >####. It crashes all the time, takes forever to load images,
I enjoyed Capture NX2 for a couple years but then grew tired of the bugs and aging interface and lack of innovation in new versions. The software is indeed buggy. I have well administered computers and found NX2 to do annoying things more times than desirable. I switched from CNX2 plus Photo Mechanic to Lightroom and haven't looked back. You may find this too is a good move.
#35. "RE: I've had It With Nikon Software" In response to Reply # 34 Wed 08-Aug-12 02:29 AM by gheck58
Aliso Viejo, US
Thank you Peter and Jon. yes I love LR4, I hardly use NX2 anymore but I do like the Black and White profile there much better than anything LR4 has or CS5. But I'll be getting Silver Efex Pro 2 soon so that's mute too.
Well Neil, I did exactly as you said. I had to re-install the Nikon Codec as RAW images wouldn't display in NX2. Then I re-installed View and it still does the same thing. The program will open but when you go to open a file of images, it just says it's Processing and they never open. I really appreciate your help but I'm done with it. I'll probably try the Photo Mechanic idea or wait until I get CS6 and see how Bridge works there.
#40. "RE: I've had It With Nikon Software" In response to Reply # 0 Fri 10-Aug-12 02:55 AM by Lighter
Looks like a case of conflict! Here is my two cents, you can give it a try and see if it helps- there is one free software: Revo Uninstaller. Download and install it. Now Run Revo. Choose either VNX2 or CNX2 from the list and hit "yes" to uninstall. Now Click "Advance" mode. This will make Revo search for all the related registry entries for that software uninstalled in every nook and corner of your system. Once you get a list, just review it to make sure and then Select All> Delete. Go to the next step and do the same for all related folders and files. Repeat this process for any other software you want to get rid off. Restart the PC, and try to make a fresh install of CNX2...
#45. "RE: I've had It With Nikon Software" In response to Reply # 44
I'm a Mac guy and I corrupted my Capture NX2 software (my bad, I installed some incompatible speed RAM and then crashed the program while in use for some intense editing). I corrupted something on my hard-drive in so doing.
In the Mac world I came across a solution that ultimately worked but was pretty severe. I had to create a completely separate User Account on my computer and then use that for photo processing.
Eventually I converted all my other programs and data over to the new account.