I tried both of them (CNX-D and ViewNX-I) and really could not like either one for a multitude of reasons. .....
The menu items seem to just mush together I am sure I could become more familiar with the icons overtime thus speeding up the workflow.
I never found the UI confusing enough to discount the software(Ps takes the cake here! :p)
Within a few minutes I find all I need to do and use effectively.
I really want to like NX-D, but am having a hard time doing so. VNX2 should have evolved into this software. I like the colour processing tools in NX-D and the simple sharpening tools, etc... where VNX2 was just a bit too basic in the tools it had. My major issue with NX-D is that it's so slow and buggy, and considering the shift from Nikon to using sidecar files to make the workflow process quicker, it's backfired massively on my PC .. VNX2 is near instantaneous on my PC(except on files now located on a NAS tho). All locally stored files(SATA and USB3 drives) are instantaneously edited in VNX2.
.... And while there may be a few gems there are simply too many hurdles for myself to overcome and venture into further use....
Like I said, VNX2 was just a touch too basic with it's tools, and I never liked the way it never cooperated properly with CNX2.
But I like that NX-D has the (basic) LCH, levels/curves, lens correction tools that VNX2 should have had years ago. And of course the sharpening and NR tools too.. all of which VNX2 didn't have, or were grossly inadequate.
But then Nikon in their wisdom, decide that adding or editing keyword/tagged/ITPC data was no longer necessary, even tho they try to pitch this software as their professional editing solution!
.. Then there is that voice in my head - when Nikon loses this contract or the company gets bought out like the last one... I fear I will be in the same boat. Looking for yet another raw processor/Image editor.
This scenario couldn't come quicker I reckon!
I've been looking for another software solution for ages .. basically ever since Nikon announced cessation of support for CNX2 and VNX2 and that VNX-i and CNX-D are now their prime software products.
If they announce some miracle new software to properly replace CNX2, hopefully I can stop trialing software that I know I won't fully get along with.
It does seem that this cycle of Nikon and their software keeps spinning and while they have mixed it up (made by nikon and 3rd parties) they seem to miss the mark more often than not. For my uses NX/NX2 really worked well for me and while I still use it, I am reminded constantly that may days are numbered which leads often leads me to go on download sprees to test trials of other products. The list continues to grow... I really hope that the current iteration of Nikon software matures (soon), but the real question is what will it mature into and will it be something I can use?
Your uses with the older NXes mirrors mine. I'm not a pro, but sometimes I had to deal with batchloads of images I wanted to process in bulk .. and both VNX and CNX were perfectly adequate for my usage.
I have no plans to update my cameras(mainly D800E, and occasionally D300) simply due to a complete lack of support for new cameras in the old software(which is what I still use).
I won't install VNX-i again, as Øivind says .. it uninstalls VNX2, which I rely on massively heavily! I need it for it's ability to tag my images with keywords, which are stored within the NEF file(which is where I want that metadata).
And another question. Do you think Nikon was better off developing their own software or do you think they are better off leaving it to others? I know at one time many people held the opinion that Nikon needed to give up the software end of it, I may have as well at times. Has your opinion on this (if you had one) changed? ...
Whether Nikon develop their own software or contract that process out isn't important! What's important is that whatever choice they make on software, it has to be an overall best option for us the customer.
That is, if they have no real commitment to an excellent software workflow process, then get out of it completely(not this half arsed, crapful SilkyPix rubbish) .. and give the people that actually do know about software all the necessary information required to fully and properly decode the NEF file type!
Otherwise do it properly themselves, that is themselves directly by employing software specialists .. or contract it out to one of the millions of software developers out there that are more than capable of doing it right!
