6/10/2023 0 Comments Nikon viewnx i problems![]() ![]() I believe the original View and Capture NX2 store all metadata in the files. Maybe there is some glitch related to handling of the labels across the two. The labeling in the 'i' versions is using side car files, whereas in the ViewNX2/CaptureNX2 it is stored in a separate directory away from the image files, as far as I know. ![]() I believe that when I downloaded View NX-i I did it separately from the NXD download. VERSION 1.2.1 OF NIKON VIEW NX-I HAS A BUG IN ITS "APPLY LABELS" SUBROUTINE. I DID NOT TRY AND APPLY LABELS OR STAR RATINGS JUST IN NXD. Same as 3 except that I added a colored label only (1-9) and did NOT apply a star rating. The tiff COULD NOT BE OPENED OR VIEWED as a THUMBNAIL IN CNX2. Same as 4 except that I added a colored label (1-9) using the drop box as well as a star rating. Tiff created in NXD could be opened in CNX2. Then proceeded with all of the other steps. Same as 3 and I added star ratings using the drop down box that appears near the bottom of the image when the mouse's arrow key triggers it. Then proceeded with all of the other steps in 2. Same as 2, except that I made additions to XMP/IPTC and saved them. Then I clicked on NXD icon within NX-i to load NX-D. Made no changes to XMP/IPTC data and made no ratings. I opened an image in Nikon View NX-i first. Used file convert to create my 16 bit tiff. Used NXD only to view the image and process it. I downloaded the images again to a different file folder. I did some controlled software tests today on the same D 500 images. Works very easy (just drag and drop), and does the job in a quiet way, but well It has been updated and now also works with a.o. Did find the whole 'saving as a Tiff in NXD and processing the Tiff in NX2' a bit of a pain anyway, considering the size the Tiff's would end up in (DF approx 95 MB, D800 approx 160+MB)īetter alternative IMO and experience is this (free) program (although the maker is open for donations as a sign of appreciation for his efforts :-) )īasically renames the files in such a way they becomes recognizable for NX2 (eg a D750 file becomes, in the exif, a D600 file, a D810 becomes a D800 file, etc), after which hey can be processed directly (as a NEF, no Tiff's) in NX2 (i.e. When the D500 was introduced, NXD was the only (free) option available But I ended up with similar problems when I installed NXD to play around a bit with in particular some D500 files, in my case I couldn't process DF and D800 files in NX2 anymore Never found out why, ended up just uninstalling and then again (re)installing NXD, but obviously vowed to stay away from NXD if possible. ![]() JoeĪlthough all my latest camera's (DF, D800) still work with NX2, I wanted to play around with some D750, D810 and later D500 NEF's to see what the improvements were. Guesses as to what is going on or causing this? What I need to do with Nikon or my retailer if anything? Ĭan anyone else with a D 500 try and replicate the situation with Nikon software? Any other diagnostic steps I should take? ĭoes anyone have any suggestions as to what may be causing this? I will remove the battery back and see if the problem remains or goes away. I think the chance that I did not use the battery that came with the camera is pretty low. If I did do this, the camera performed normally as far as I know. I may have used an Li-ion01 battery before I knew about the recall. I know that I used a Nikon Li-ion20 battery in both the camera and in the battery back. I know it was on the camera yesterday and maybe an earlier day too when I had the same tiff d500 problem. I cannot recall when I started to use the D500 MB-D17 battery pack from Nikon. The D500 tiffs from NX-D from yesterday can be opened in Adobe Bridge and NX-D, so I do not think there is anything wrong with the tiffs. On my desktop I even reloaded NX2 to see if that would fix things, but I got the same result. This D500 problem exists on both my laptop and desktop. However, tiffs made in NX-D from yesterday's D500 NEF's cannot be opened by Capture NX-2. Pictures I took yesterday with my D810 had no issues. Capture NX2 had no problems opening tiffs made in NX-D from NEFs in either body. I had no problems doing this in May, 2016. My workflow (until this week) had been to process NEF D810 and D500 images in NX-D, make a 16 bit Tiff in NX-D and then open the tiff in Nikon Capture NX2 for finishing touches with Control Points. I have been using NX-D to process NEF images from my D810 and D500 since NEF files from these two bodies cannot be opened in Capture NX2. ![]()
0 Comments
Leave a Reply. |