NikonGear'23
Gear Talk => Processing & Publication => Topic started by: Ilkka Nissilä on October 28, 2016, 21:30:20
-
I like to use Nikon browsers for going through the images for several reasons. One is that they follow the picture controls set in the camera. Another is that it is reasonably fast to browse and check focus quickly, and you get to see hardware details such as the active focus point, AF fine tune setting in use, etc. You cannot get all of these details in e.g. Adobe software.
However, for the past couple of years Nikon ViewNX-i has been available, it has been quite unreliable. It crashes from time to time, especially it seems to happen when accessing older directories which have seen use by Nikon ViewNX2. And sometimes when it crashes once, it will always crash when restarting the software.
I discovered a way to temporarily solve the problem of this program being in a seemingly permanent crash loop. I deleted the c:\users\username\AppData\Local\Nikon\ViewNX-i directory. After this the software seems to work normally again. For a time at least.
I always knew Nikon software had glitches, but the frequency of them occurring since ViewNX2 and Capture NX2 were discontinued, is alarming. I have to wonder if they have any competent software engineers working for them and whether they have any people whose primary task is to test and make sure that the software works correctly on any platform that is supported.
I sent Nikon a message about this, though I am not sure if it will do any good. Everyone seems to just use 3rd party software. But I want those device dependent data to be displayed when I'm browsing images.
-
I've found that images that are straitened and not cropped afterwards will crash ViewNX2 and CaptureNX-D when these create thumbnail views. I've also found that Photoshop CS2 can have registration errors when I've used the Canvas Size tool so I crop periodically when using canvas size. It seems these programs don't know what to do with the extra data and there is no error trapping for this problem so they go poof! I'm surprised at the problems with CS2. I though Adobe would do better.
Is it possible that ViewNX-i has a similar problem? I tried ViewNX-i on my MAC and had problems so I copied VNX2 from an old HD and it works fine on El Capitan. ViewNX-i deletes ViewNX2 so I stopped the install back a few months ago and haven't tried it.
I've found CaptureNX-D very reliable provided I crop after straitening so I'm hoping ViewNX-i will get reliable too. I really don't like today's software that is released in beta form as a finished project. In the early days of DOS I avoided version 1.00. It seems the companies have gotten worse not better. :(
Dave Hartman
-
I was just thinking that some of my files have been created using Helicon focus stacking software. I wonder if this could somehow be producing TIFFs which the Nikon software has problems with.
I crop and straighten using Photoshop. I don't think I've used those to edit these NEF files in Nikon software but I can't be sure.
-
My guess is there are limits. Measurable limits.
1) add NEF to a folder. NX-i will show the folder until the amount of NEFs exceeds a certrain limit. It is above 3000 somewhere. It does not read a folder with 8700 NEFs.
2) Same concerning amount of cached thumbnails. As soon as a certain number is exceeded *booom* and that is it. Delete Cache and you are back in business.
This all reminds me of the D70 counter. It overflowed at 64k .... everytime I hit this number. But it did not crash.
And Ilkka. No. There are either no decent engineers working at Nikon Software or they have no say....
-
So if I go through a certain number of files and then it crashes due to a full cache? Is this directory specific or cumulative?
Deleting the cache didn't put me back in business this time though. I had to go into the (normally hidden) AppData directory and delete it.
I think here should be some FAQ on these issues. ;-)
I have to say that from the early user feedback on the Snapbridge application for camera - mobile device connectivity, it does seem like the managers forced the product to the market when it was nowhere near ready. What's worse, they are heavily advertising the connectivity features which depend on this application, in the marketing material for the D3400.
The early user reviews on KeyMission 360 are also crushing. All of these problems seem to be software related.
I have to wonder about Nikon managers' thinking on these topics of software testing and quality and the impact of these factors on Nikon's reputation as a brand.
-
I think I discovered the primary culprit to my problem. I had > 2000 files in my directory of small jpgs that I use to post my recent work to others. It's been accumulating ...
This bug seems to exist in ViewNX2's latest version as well, but not the version before it, as far as I could tell. I kept using it as long as possible.
-
This bug seems to exist in ViewNX2's latest version as well, but not the version before it, as far as I could tell. I kept using it as long as possible.
It was not only the number of files, but I tracked it down to certain files that would crash the latest version of ViewNX2. I reverted back to the next last version and it has been working fairly well since.
I have so far kept from upgrading to bodies that require ViewNXi and CNX-D. During my latest practical test I found that launching files from in CNX-D from ViewNXi will cause the former to forget to filter/select files, even if the right tags and filtering parameters remain.
-
By "deleting the Cache" I mean to dive into hidden "AppData" and delete the Cache files in "Roaming" and "Local". Frankly, I do not know another method, sorry.
-
I have to say that from the early user feedback on the Snapbridge application for camera - mobile device connectivity, it does seem like the managers forced the product to the market when it was nowhere near ready. What's worse, they are heavily advertising the connectivity features which depend on this application, in the marketing material for the D3400.
The early user reviews on KeyMission 360 are also crushing. All of these problems seem to be software related.
I have to wonder about Nikon managers' thinking on these topics of software testing and quality and the impact of these factors on Nikon's reputation as a brand.
They would not want to end up like Blackberry or Nokia.
-
The release of KeyMission360 was once postponed due to the delay of the software development. Apparently the software is Nikon's major weak point.
The conventional wifi-only models seem to be orphaned. What has become of Wireless Mobile Utility?!
-
Does anyone truly believe that Nikon will produce an imaging software that works smoothly...ever?
-
Nikon seems to be struggling with both hardware and software.
I read something about a hardware issue regarding the DL series. The DL 18-50 sounds nice, but is still vapourware. :( I wonder now, if the DL series will turn out any better than the Keymission actioncameras? ???
The former D600 & D800 issues were hardware related....
-
Does anyone truly believe that Nikon will produce an imaging software that works smoothly...ever?
C-NX2 worked fairly well, and I think that program would have been very stable by today, if only it hadn't been killed.
-
Nikon seems to be struggling with both hardware and software.
I read something about a hardware issue regarding the DL series. The DL 18-50 sounds nice, but is still vapourware. :( I wonder now, if the DL series will turn out any better than the Keymission actioncameras? ???
The last official news wrt DL was released on April 20th which tells that the launch of DL serirs will be postponed for an "indefinite term", because they found a "significant problem" in the image processing IC.
I had never read such a "significant" news release before.
C-NX2 worked fairly well, and I think that program would have been very stable by today, if only it hadn't been killed.
Agreed. It was a bit slow but good enough that PS or PSE was not absolutely necessary for my use.
-
In 2011-2012 they were under tremendous pressure to put out new DSLR products; the demand was high and people were expecting the D800 and D4. However, their manufacturing capability had been destroyed by three major natural disasters. I can understand why they made mistakes that then that led to quality problems in some products due to the circumstances at the time. It must have been hard to work if the roads and plumbing do not work and people are being evacuated because of radiation contamination etc.
This year there was also an earthquake, which may partly explain why some of their products are not released on schedule. But the real problem is not a delayed product but the release of products which are obviously not properly tested (Snapbridge, Keymission). This is likely to kill the Nikon brand name and people will likely see it as something to be avoided if the current practice continues. Then they won't be able to sell their good products which do work correctly, either, since people won't trust that they will.
I don't believe the development of a browser and a raw conversion software is an insurmountable challenge for Nikon. I don't think that it is too difficult for them to develop mobile applications that control cameras and transfer images. The problem is not the development of the software per se, but the attitude of the managers that it is perfectly ok to release products which do not work yet correctly. It's not an engineering problem if you release a product that doesn't work, it shows that management is not up to their task. They make the call when to release a product. And they've made a lot of really bad calls in recent years.
Thankfully the top of the line DSLR products and lenses seem to work as advertised, apart from Snapbridge problems reported by D500 users. I haven't run into any significant problems with their cameras, flashes or lenses myself since the D800 (mine had AF consistency issues though not the infamous "left AF" point issue). I've been very happy with their recent products actually, but am deeply annoyed by the quality of the software that they've put out since the discontinuance of ViewNX2 and Capture NX2.
I would be happy to offer my help in testing and providing feedback on their software in my normal computing environment, but they don't seem to be interested in receiving feedback from users. I really want them to get their software right. I don't mind using Adobe tools which do work correctly apart from Lightroom which often has serious bugs, but I need to see key hardware dependent parameters that are stored in the files such as active AF point, fine tune setting, and others. I would also prefer to see the images as shot in the camera using the full picture control settings information obeyed by default by the browsers and raw converters. That these do not work in Adobe software is a major annoyance to me. I now use control points in Nik / Google plugins but their use is a lot slower than use in the Capture NX2 software and I find making local adjustments is a slow process now, and feels very primitive. The file sizes also become astronomical if I want to preserve the full bit depth and not subject my images to compression artifacts.
-
C-NX2 worked fairly well, and I think that program would have been very stable by today, if only it hadn't been killed.
I agree. For me it was a significant blow to my workflow that its development was stopped. I feel that I was sent to the stone age when doing local adjustments now. I've learned how to work with masks in Photoshop but it takes much more time now and the edited files consume a huge amount of disk space. I do not like the way Lightroom implements local adjustments and don't want to use it for that.
-
The last official news wrt DL was released on April 20th which tells that the launch of DL serirs will be postponed for an "indefinite term", because they found a "significant problem" in the image processing IC.
At least they haven't released the cameras with faulty chips.
I wonder how long it will take to fix them. The DL isn't all that different from a Nikon series 1 camera in terms of its sensor or the capabilities so I wonder why they couldn't just revert back to the processor in the J5 and redesign the camera around it.
-
CNX was NIK, and NX-D is Silkypix. Has Nikon ever "written" software?
Thom Hogan observes that the recent (post-earthquake/tsunami-era) hardware problems are most likely due to cost-cutting.
-
Before Capture NX, I believe Nikon developed Capture and View in house.
They do develop the firmware for their cameras which is basically software. In that area they do proper testing and bugs are quite rare. The algorithms for raw conversion that are implemented in Capture (any version) as well as in the cameras I believe to be Nikon's own code. Certainly they haven't changed all that much as Capture changed to Capture NX or NX2, or NX-D. In my opinion, Nikon's image processing algorithms are superb.
Anyway the Silkypix which came with my Fuji X100s was terrible beyond terrible so if that's the Silkypix contribution to Capture NX-D then the Nikon part is much more significant and far better. However, it is not properly tested and is terribly inefficient in the use of the computer's resources.
-
I wonder how long it will take to fix them. The DL isn't all that different from a Nikon series 1 camera in terms of its sensor or the capabilities so I wonder why they couldn't just revert back to the processor in the J5 and redesign the camera around it.
J5 is wifi only and not SnapBridge compatible. I wonder if the image processor in question might be integrated with the SnapBridge/wifi function which is causing that "significant" problem?
-
The firmware or the in-camera image processing algorithm/software runs on its proprietary platform. Nikon may find difficulty in coping with the more common Windows and MacOS.
-
J5 is wifi only and not SnapBridge compatible. I wonder if the image processor in question might be integrated with the SnapBridge/wifi function which is causing that "significant" problem?
I think the Bluetooth LE ought to be on a separate chip from the image processor. I don't think radio wave transmission and reception is going to be improved by having DSP happening on the same chip (the DSP would likely generate a lot of noise in the bluetooth signals).
-
I think the Bluetooth LE ought to be on a separate chip from the image processor. I don't think radio wave transmission and reception is going to be improved by having DSP happening on the same chip (the DSP would likely generate a lot of noise in the bluetooth signals).
Basically I don't disagree. But DL is a compact camera and also compatible with wifi and NFC in addition to Bluetooth, and thus some sort of challenging integration might be needed.
-
CNX was NIK, and NX-D is Silkypix. Has Nikon ever "written" software?
Thom Hogan observes that the recent (post-earthquake/tsunami-era) hardware problems are most likely due to cost-cutting.
A DSLR is built from many more parts than a mirrorless camera, so maybe they should move the entry level or DX format to mirrorless and save cost with fewer parts. Then with a new mount capable of supporting an FX sensor, but starting with DX sensors much like the Fuji X system. Nikon could take the opportunity to make decent DX mirrorless primes! (Buzz, buzz, buzz, as Thom Hogan says about DX primes.)
-
It's expensive to develop a new line of lenses, and I would expect this to be especially difficult after R&D cuts. Also then they risk losing their F mount customers as Sony did with A mount. Mirrorless buyers would wait for new higher end lenses in the native mount instead of upgrading to F mount lenses and using an adapter. So Nikon's existing lens sales would die off as people would hold off purchases. I think it would be better if each camera company specialize on something and do it well, instead of diluting their resources on a lot of different product lines. Perhaps Nikon will indeed make yet another mount. If they can now develop 5 lenses per average year, and if we divide that between three mounts (1, mirrorless large sensor, and FX) then each of the three lens systems will progress very slowly.
-
Basically I don't disagree. But DL is a compact camera and also compatible with wifi and NFC in addition to Bluetooth, and thus some sort of challenging integration might be needed.
I understand. Hopefully Nikon can sort the issues out and make these products available soon. I think that for a compact camera, the CX sensor size seems like a good choice.
Hopefully Nikon can take advantage of the delay in DL series hardware and improve the Snapbridge application in the meanwhile.
With regards to my original ViewNX-i problem, Nikon's response was very polite; they thanked me for reporting my findings and said they would pass the information on.
-
I understand. Hopefully Nikon can sort the issues out and make these products available soon. I think that for a compact camera, the CX sensor size seems like a good choice.
Hopefully Nikon can take advantage of the delay in DL series hardware and improve the Snapbridge application in the meanwhile.
With regards to my original ViewNX-i problem, Nikon's response was very polite; they thanked me for reporting my findings and said they would pass the information on.
I also think that 1-inch 2:3 sensor is more potent for a still-video hybrid mirrorless camera even than m4/3 in which the top and bottom are cut too much for the video.
As for the wireless, I wish Canon enable their W-E1 to be used with Nikon cameras. :o :o :o
-
I also think that 1-inch 2:3 sensor is more potent for a still-video hybrid mirrorless camera even than m4/3 in which the top and bottom are cut too much for the video.
As for the wireless, I wish Canon enable their W-E1 to be used with Nikon cameras. :o :o :o
I can remember when we would buy wifi cards as expansion cards to PCs and laptops. That's some development! :o
-
It's expensive to develop a new line of lenses, and I would expect this to be especially difficult after R&D cuts. Also then they risk losing their F mount customers as Sony did with A mount. Mirrorless buyers would wait for new higher end lenses in the native mount instead of upgrading to F mount lenses and using an adapter. So Nikon's existing lens sales would die off as people would hold off purchases. I think it would be better if each camera company specialize on something and do it well, instead of diluting their resources on a lot of different product lines. Perhaps Nikon will indeed make yet another mount. If they can now develop 5 lenses per average year, and if we divide that between three mounts (1, mirrorless large sensor, and FX) then each of the three lens systems will progress very slowly.
The Sony A mount died by itself and not because of the E mount. Rather the E mount pretty much restarted the Sony camera brand.
Nikon should have at the most two mounts, so Nikon 1 should be killed, if it already isn't. If Nikon can't afford to develop a DX/FX mirrorless system with a short flange distance, then they are in an unexpectedly bad position, I think. :( Canon seems to have embarked on the right track, albeit slowly.
-
Hello everyone,
I just joined this forum when came upon it after performing a search on ViewNX-i problems.
Last June I upgraded from the D7100 to the D500 and was forced to upgrade to ViewNX-i as the previous version couldn't read the D500 NEF files (can't remember what the previous version was).
Since I upgraded I haven't been able to use the software. When it launches it seem to default back to a specific folder on my compute and is never able to load the files. I'm so disappointed as this was my favourite software for viewing and adjusting NEFs.
Question: Does anyone know if any Nikon employees participate in this forum?
-
When it launches it seem to default back to a specific folder on my compute and is never able to load the files. I'm so disappointed as this was my favourite software for viewing and adjusting NEFs.
Can you move to a different folder (by selecting the folder in the tree on the left)? How many files do you have in that folder where it defaults to?
Which operating system are you using, and which version? How much RAM do you have and how much free disk space? Thanks.
Question: Does anyone know if any Nikon employees participate in this forum?
I have not noticed such participation on any online forum. But they do respond to customer feedback, in my experience. They might not be able to help directly (depending on the problem) but will pass comments on.
-
Question: Does anyone know if any Nikon employees participate in this forum?
I don't think so. At least there is nobody who will admit to it. ;D
You should be able to click Browse in the upper left corner and see the list of folders on your system. Click down to the folder which contains your images.
-
Unless I am wrong or missing something, ViewNXi cannot run on Mac OSC Sierra 10.12.x - at least it does not on my MacBook Pro. It worked until the upgrade (?) to OSX Sierra. Before I updated to OSX Sierra it was certainly buggy. It crashed often, and at times you have to re-select the folder of images that you wanted to look at. But, in the end, it worked.
I hope they update the software soon. Even though my images are in a Lightroom catalog-folders, I used ViewNXi often - primarily to look at the focus points to evaluae how my focus technique is doing (usually not so good). It is also useful when doing AF fine tuning as you can see the AF adjustment info with each file in the metadata if you selected that viewing option. Unfortuntely, I know of no other software that will display the focus point.
-
Since I upgraded I haven't been able to use the software. When it launches it seem to default back to a specific folder on my compute and is never able to load the files. I'm so disappointed as this was my favourite software for viewing and adjusting NEFs.
I do not know any Nikon emploees in this forum.
Yet for your problem I can say that on my notebook I could not install View NXi or Capture NX-D for a while. Then I did something that can be done with Windows 10 that could not be done before:
Clean reinstall without needing to reinstall the software.
After that I could install the newest versions and I am quite happy, esp with NX-D as RAW processor for my D500 files.
-
Previous version of ViewNX was simply ViewNX2.
....
Since I upgraded I haven't been able to use the software. When it launches it seem to default back to a specific folder on my compute and is never able to load the files. I'm so disappointed as this was my favourite software for viewing and adjusting NEFs.
Question: Does anyone know if any Nikon employees participate in this forum?
I reckon you're probably better off uninstalling ViewNXi and trying CaptureNX-D.
It has many more tools than ViewNX2 used to have.
But I find it's still buggy and slow(by way of comparison to VNX2).
I found ViewNXi to be one of the worst software I've had the misfortune to have experienced, and that includes the buggy and slow Capture NX-D.
The most annoying aspect was that it forced an uninstallation of VNX2(which is my most used software), so I had to install it again after I removed NX-i.
What I can't understand is why Nikon would waste resources(time/human effort/money) on NX-i, when those resources would have gone a long way to make CNX-D a slightly better program.
This is possibly the most accurate indication that Nikon are being mismanaged at some level, or at all levels!
-
Arthur, are you using Mac or Windows?
In its very first versions I felt ViewNX-i wasn't working reliably for me (I kept using ViewNX2 until I got a camera which wasn't supported by it) but in its latest versions I haven't had other problems than the crashing caused apparently by having too many files in one directory. I need a fast browser that shows me the images according to the picture control information set in the camera, the focus point that was used, and any device specific settings such as the fine tuning. I don't make any edits to the images in ViewNX-i although I do use the start rating system. I just hop from there into Photoshop CC for editing. I find the browsing software to be very fast and it renders the images better than e.g. Bridge (which doesn't properly resample the images for display, it shows some aliasing artifacts that aren't there in the files but a product of improper algorithms for resampling). Also I just can't make myself like the user interface in Bridge. For browsing Lightroom is too slow and lacks key features that I use in PS CC. However, I do use Lightroom for batch printing.
Capture NX-D is too slow on my computer to use and it stores the TIFFs in a directory specified in the settings. I want the TIFFs in the same directory as the NEFs and displayed side by side so I can browse and see the different versions. If I set the current directory as the directory to use for the TIFFs, it works but it doesn't display the TIFFs next to the NEFs. It seems very confused with what to do with these files. I often make several different edits and it's mandatory that I see them properly when browsing. ViewNX-i doesn't have any problems with having TIFFs and NEFs, by sorting by filename they are displayed side by side. To achieve this in NX-D I have to close the software and restart after editing, and even then there are problems where they are displayed in the wrong place. Sometimes the thumbnail grid goes completely haywire in NX-D.
However, I like Nikon's raw conversion algorithms and would like to use Capture NX-D once they sort it out. However, for now it is ViewNX-i, Photoshop CC and Lightroom that I use. I would like Nikon to put in more resources into their software as this is just not good enough.
-
Ikkla, well the requirement for ViewNX-i for the D500 really took the shine off shooting a new camera for the first time ;) . If I was happier with the D7100 I probably would not have bought the D500.
I also use viewNX as a browser and open Photoshop, LR or CNX2 from there. It even opens Sony and Olympus jpegs so I can do a quick Label/delete and then go to the file in Bridge. I was not paying enough attention.
I'll delete ViewNX-i for the moment and re-install viewNX2 unless I can figure a way to have them both on my Desktop. Nikon is getting less fun to shoot ;D
Edit: re-installed ViewNX2. It did not delete ViewNX-I. When I opened ViewNX2 the D500 files were there , both jpeg and nef :) . An extra step but at least my way of doing things does not really change. Funny, I almost bought a second Df instead of D500, shutter count 1 for 1,350 UK pounds (a grandfather's estate) .
-
Just a side remark: Photo Ninja has got a good and speedy browser in the last incarnation, plus it deals with TIFs as well. However, it'll only emulate NEF-specific edits.
-
Right, you can reinstall ViewNX2 after installation of ViewNX-i removes ViewNX2. ViewNX2 should display the NEF files correctly (even with D5 files) but some of the device dependent details are not shown, so it doesn't fully support the new cameras.
When Capture NX2 was discontinued, my heart really sunk as I feel it was the most elegant implementation of local adjustments in the raw conversion. It took a while for me to find other ways of doing things and those other ways are really time-consuming sometimes. I guess over time Nikon may recover a part of what was lost, but it doesn't look like they're pursuing this ambitiously enough. I find it very hard to understand how software technology can take a decade step back just like that.
-
@ Ilkka: I use Win 10 now, but previously Win7 and before that, WinXP.
When I first tried VNX-i it had no ability to do any edits at all(must have been the first incarnation) and my primary use for VNX2 is to keyword my images quickly.(maybe not as easily as it should be tho).
While many would argue otherwise, I prefer my keywords embedded in the NEF files, so that wherever I place the NEF file, the keyword is also there. Handy when browsing with just about any software with the ability to preview NEF files(predominantly Windows Explorer).
That was one major fail for me WRT ViewNX-i ... among a few others.(the other being that it did uninstall VNX2)
I use VNX2 in a similar manner, in that it's my ACR/Bridge equivalent. I tweak some settings, and then either open with CNX2 or CNX-D depending on what's needed.
Two things I don't like about VNX2:
1/. major dislike is the vignette correction whether you want too or not, and then the inability to adjust NR in any way.
2/. the inability to organize keywording to your liking. You have to use their idea of organization(which is subpar)
If CNX-D had the ability to set keyword data directly into the NEF file, I'd probably use that program more than VNX2 and just suffer it's limitations. It's basic editing ability is superior in every way.
..... When I opened ViewNX2 the D500 files were there , both jpeg and nef :) . An extra step but at least my way of doing things does not really change. Funny, I almost bought a second Df instead of D500, shutter count 1 for 1,350 UK pounds (a grandfather's estate) .
This is interesting in that I didn't even try to install VNX2 after VNX-i.
It gives me some cause to try VNX-i again. Although I assume that whenever an update is installed, it probably uninstalls VNX2 again.
Tommie, the reason you see your D500 files both jpg and NEF in VNX2 is that you have it set to view the jpg preview file.
Just above the browser window(LH corner) is a small box marked RAW.
1/. When it's coloured GREY, it only displays the embedded preview jpg within the NEF file. The default setting is for it to be set to jpg preview(faster loading of images).
2/. When you click on it, it changes colour to an orange-yellow tone. This is now set to view the decoded RAW file in itself. Slightly slower loading of the images (on my PC that slowness is measured in micro seconds), and you notice it if you scroll through the filmstrip repetitively using the arrow key. it eventually can't keep up as quickly as the jpg preview mode can. Also, you may(probably will) notice a ever so slight change in the histogram switching from raw mode to jpg mode on certain images.
So, if you click the raw tab to activate direct raw mode, on the D500 images(and any non supported images in VNX2) you will only get an 'unsupported file' message.
Obviously you can't do or set any parameters on raw files for non supported images.
I'll probably give VNX-i another chance(more out of curiosity) knowing that I may be able to re-install VNX2 concurrently.
-
Arthur, many thanks, yes you're correct but it does allow me to "Open With.... " so does work as an easy , fast catalogue . I still use CNX2 with all supported cameras. It is a shame that Nik and Nikon did not continue their relationship. The selective controls of Nik are the best I've found (or learned to use ;) . I hope the guys made lots of money from the Google sale since it looks, to me, that Google will kill it and go the Apps route.
For what , and how, I shoot I've never really worried about batch processing. For Sports , I normally have the controls for jpeg set up so that I normally do no, or just some quick L&C, shadows, highlights, and then post for the players/teams/Newspapers. I do sell some un-post processed RAW images and let someone else worry about the PP :) .
Cheers,
Tom
-
I've installed ViewNXi (Latest version) on both Windows 7 Professional and El Capitan OS X 10.11.6.
Windows: it's running reliability but, and it's a big one, when viewing at 100% as when checking focus on eyes it show a gray screen with "processing" when the NEF has a sidecar with development information this last a long time. The makes moving from one NEF to the next deathly slow and renders ViewNXi pretty much useless.
Does anyone know a way to force ViewNXi to use the imbedded JPG and ignore the sidecar files for previewing NEF(s)?
MAC OS X 10.11.6: ViewNXi (Latest version) crashes 100% on starting and I don't know where to start to cure this.
I've reinstalled ViewNX2 on Win7 and disabled its version of Transfer 2 which is unsupported and use only the Version installed by ViewNXi.
On the MAC I've copied ViewNX2 back into the applications folder with the help of AppCleaner.app to delete all the files use by VNX2 and rescue then from the Trash. Those files are then saved in a folder. Finally they are copied back to their rightful places here and there.
ViewNXi looks promising but when will it be fun to use?? ...or when will Nikon get its Stuff together?
Dave Hartman who seeks advice
I pecked this on a smartphone and I'll fix typos later. I hope it's understandable.
-
ViewNX-i moves from one image zoomed 100% in to the next very quickly (< 1s), clearly faster than Lightroom. However, I don't make adjustments in the browser; I load it into ACR and PS CC and PS uses its own sidecar files, so it doesn't affect ViewNX-i rendering. I would like all of this to be compatible of course, and ACR to recognize picture control settings made in the camera and the Nikon browser to recognize Adobe conversion settings, but I guess this isn't happening.
I can try applying some adjustments and seeing how that affects ViewNX-i speed the next time I do editing.
-
This afternoon, I bumped my ram to 24gb from 12gb so finally ViewNX-i (version 1.2.4) works much more quickly. Still, it can not transfer from a memory card without spoiling the images with those infernal streaks across the bottom two-thirds of the image rendering them of course unusable.
As David suggested, by manually moving them with the finder on my Apple iMac, they can be viewed and edited in ViewNX-i and transferred to Capture NXD for a more thorough job (if I so desire, but out of spite I'm not sure I do so desire).
What a pain using Nikon software has become, and it's really too bad.
-
I always move files manually from the card to the computer.
-
Tom,
Have you determined that you are using the version of Nikon Transfer that came with the latest version of ViewNXi? Peek under the hood and be sure.
You might try AppCleaner.app just to see were all the files are. You don't have to send them to the trash. You can quit AppCleaner at the dock to avoid a mistake.
Dave
-
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/
-
Dave, so far no problem. ViewNX2 is my primary catalogue (and my wife's) . All images show up in the folders for Sony and Olympus , as jpeg, and in Bridge in jpeg and RAW(what ever it is called).
It is a bit of a convoluted work flow since I normally have ViewNX2 and Bridge open. I can open the RAW Nikon images from ViewNX2 in PS CC2015. My wife has updated to CC 2017 but I had to find Nik entry from 2015 and paste it into her 2017 but it works. There are probably much easier ways of cataloguing images but these days I do not do any PP to more than 5/10 % of the shots and I am used to the workflow.
I did not use the disc which came with the D500 (nor have checked) , I just downloaded from Nikon Message Centre. I keep both ViewNX2 and View NX-i. I often use CNX2 for the older cameras and often do the Df images in both CNX2 and PS. I may spend some time with LR. I now automatically open the D500 files with View NX-i's Nikon Transfer and after all are downloaded I close it and open ViewNX2. I normally do my culling and then transfer the renamed folders to Externals. My wife's newest External ceased to function (trying to recover) so now use multiples. Bridge is very time consuming to cull. Need to work on that :) . I spent some time with CNX-D when it first came out but was not impressed.
Working out my preferred D500 settings for AF and metering is taking some time and I am taking more shots as a result. Deleting more from the camera. I rarely use group focus on the D750. D500 seems improved but am missing the head and eyes on too many BIF images so back to 25pt. Trying to see how 25Pt equates to 9Pt ;) . Before age and health issues caught up with me, my keeper rate for Eyes was highest using single point even with fast action.
I will continue to watch :)
-
Tom,
Have you determined that you are using the version of Nikon Transfer that came with the latest version of ViewNXi? Peek under the hood and be sure.
You might try AppCleaner.app just to see were all the files are. You don't have to send them to the trash. You can quit AppCleaner at the dock to avoid a mistake.
Dave
I knew I was using the latest ViewNXi (1.2.4) when I upgraded Sierra to 10.12.2, which of course is when all the problems began. It isn't difficult to use the finder, just more time consuming. After all is said and done, I had eight images corrupted none of them of any great value as I was just playing around with a new camera.
I count myself lucky.
And, I can live with the work-around until Nikon fixes the problem.
-
Everybody should know now that Nikon is not very good in producing end-user / consumer PP software. I stay away from it; the few times I'm using NX-i is to find back / verify shot parameters, in particular focusing information (which sensor the camera used to focus). The entry point of my importing goes through Lr (and ends for 5-10% of the time in Ps).
-
I discovered a way to temporarily solve the problem of this program being in a seemingly permanent crash loop. I deleted the c:\users\username\AppData\Local\Nikon\ViewNX-i directory. After this the software seems to work normally again. For a time at least.
Thanks! I had forgotten this. I puzzled over the path for a minute or two then realized this was Windows. I located...
Macintosh HD\users\username\library\application support\ViewNX-i and renamed the folder to ViewNX$i
ViewNX-i v1.2.4 64bit had been crashing 100% on me and now it booted up properly and as expected it created a new ViewNX-i folder. I deleted the old one and now ViewNX-i is working fine. We'll see if it keeps working. :)
Best,
Dave Hartman
I'm guessing there is a bit of error trapping code that's missing and when an error occurs the software can't recover and crashes. For example if there is a problem with thumbnails the software should rebuild them. If the cache folder is deleted then it rebuilds the thumbnails without the crash. I noted a Cache and DB folder in the ViewNX-i folder. Thumbnails is just a guess.
-
....
Windows: it's running reliability but, and it's a big one, when viewing at 100% as when checking focus on eyes it show a gray screen with "processing" when the NEF has a sidecar with development information this last a long time. The makes moving from one NEF to the next deathly slow and renders ViewNXi pretty much useless.
Does anyone know a way to force ViewNXi to use the imbedded JPG and ignore the sidecar files for previewing NEF(s)?....
ViewNX-i is similar to ViewNX2 with respect to viewing raw files in raw mode, or jpg preview mode:
Top left hand corner of the image review screen area is a small grey/yellow icon marked [raw]/
By default it should be grey, denoting jpg preview mode.
Click the icon and it turns yellow, denoting raw data mode.
I just tried it on my PC.
basic PC specs are: AMD FX8350(not the speediest, but plenty of grunt for what I need), RAM=32G DDR3, mainboard Gigabyte 990FX based.
Drives:
ageing HDD 2Tb from WD(black) average data transfer rates ~ 80-100Mb/s
On this drive, above, ViewNX-i loads the raw data mode images(D800E) in about 5sec. maybe half a sec of that grey screen processing, then the image(blurred), and then detailes.
in jpg preview mode, images loaded in about 1sec to detailed view, approx half a sec blurred, never the grey processing screen.
On the middle of the road speedy SSD(~ 500-600Mb/s) there is a very slight improvement, but only in that in raw data mode, I don't see the grey processing screen. All other times appear about the same.
My previous experience with Nikon's software is that faster storage + faster loading/processing times.
Having the 256Gb SSD now as my temp storage location has turned CaptureNX2 from fast to almost blistering!
I think ViewNX-i is simply too slow, basic and low featured to be of any value for every day usage. ViewNX2 is still my preferred choice(as I use compatible cameras).
I have ViewNX-i for those times when I want to view raw files from newer cameras only(ie. very little usage).
-
I've had problems with ViewNX2 (last version). It displays thumbnails for NEF(s) from the wrong folder. When I click the thumbnail the correct NEF is previewed. I could easily delete an NEF based on see the wrong thumbnail being displayed. I've stopped using ViewNX2 on Windows 7.
I strongly recommend against using Nikon Transfer 2 shipped with any version of ViewNX2. It's not supported and it can corrupt an NEF. I'm probably repeating myself regarding VNX2 and Transfer 2.
Dave Hartman
-
I've had problems with ViewNX2 (last version). It displays thumbnails for NEF(s) from the wrong folder. When I click the thumbnail the correct NEF is previewed. I could easily delete an NEF based on see the wrong thumbnail being displayed. I've stopped using ViewNX2 on Windows 7.
Although I never experienced that it displayed nefs from the wrong folder, I found that the latest version of ViewNX2 would consequently crash when it tried to generate thumbnail view of a certain file in a folder. There was really no system to what kind of files would cause the crash except for being specific to one or two specific files in a folder. I have consequently banned the latest ViewNX2 version from my computer and use v. 2.10.2 which is more stable.
-
...I found that the latest version of ViewNX2 would consequently crash when it tried to generate thumbnail view of a certain file in a folder. There was really no system to what kind of files would cause the crash except for being specific to one or two specific files in a folder.
I found photos that are straighened but not cropped will crash VNX2 The extra data must cause the crash. I also found that photos that are reduced in size by Canvas Size in Photoshop CS2 and not cropped can cause alignment problem with layers.
Now I always crop after straightening an image in CNX-D, CNX2 and after using Canvas Size in CS2. Now I don't have the crashes or alignment problems.
Dave Hartman
-
The new 1.2.5 version of ViewNX-i has just been released. It addresses image corruption issue on MacOS Sierra.
http://downloadcenter.nikonimglib.com/en/download/sw/89.html
Quote from the webpage avove:
• Fixed the following issues that affected Nikon Transfer 2 under macOS Sierra:
- Image data copied using Nikon Transfer 2 under macOS Sierra version 10.12.2 could sometimes be corrupted.
- Nikon Transfer 2 would quit unexpectedly when users attempted to transfer photos or movies.
- Users could not select slots in the Source panel when transferring pictures from cameras with two memory card slots.
- Pictures taken using the Smart Photo Selector available with cameras in the Nikon 1 series would be transferred as individual images rather than as a group.
-
I've had problems with ViewNX2 (last version). It displays thumbnails for NEF(s) from the wrong folder. When I click the thumbnail the correct NEF is previewed. I could easily delete an NEF based on see the wrong thumbnail being displayed. I've stopped using ViewNX2 on Windows 7.
....
I've had this a few times.
I think(not 100% sure) why this happens is the thumbnail cache becomes too large, and possibly corrupted/confused or something like that.
If you haven't configured the cache location, then Nikon usually places it in some user appdata type location of their choosing.
You can determine this by delving into the Options menu in VNX2(Edit->Options) and under the General tab up the top.
It'll be quite obvious once you're in this settings option.
They allow you to set the location of the cache to one of your own choice too.
VNX2 and CNX2 both operate better when all files being worked with are located on the fastest drive possible, so changing this from the default can always be a good thing.
If using mechanical drives, it's usually best to use a reasonably fast and separate drive to help speed those programs ability to render images quickly(HDD latency).
If you're working off SSD type storage, you won't see any benefit by using a separate drive.
Under this General tab in the Options menu, you will see an option to 'clear cache'.
I've found that this usually doesn't resolve the issue(quoted above), and that deleting the cache files manually is usually best.
If you can locate the cache, go to it manually in Windows file explorer and look for various files with the extension .nkd and .nki
There may be about 8 or 10 of them in total, and named variously such as file/folder/large/medium/small .. or words to those effects.
It's safe to delete them all as they are only thumbnail cache files.
Make sure VNX2 is not running at the time tho.
What will happen tho, is that upon opening VNX2 after you've deleted them all, it has to rebuild all the cache files from scratch(a good thing if the cache has become corrupted!).
So initial loading of all images is a bit slower. Once the new thumbnail cache is built up again, subsequent uses of VNX2 will show speedier rendering of images.
Hope that helps.
-
Nikon Transfer 2 does not work with Mac Sierra 10.12.3 and according to Nikon support, it is no longer supported. Odd though as ViewNX-i v1.2.5 installs it. Nikon really need to clean up their software and get it functional, in fact Launch Transfer is still in the menu dropdown.
Quoted from the ViewNX-i download page for v1.2.5:
• This software is distributed as a file named “S-VNXI__-010205MF-ALLIN-ALL___.dmg”. Download and run the file to perform the update.
• When performing the update, you will be prompted for the administrator password.
• Before beginning installation, exit ViewNX-i and all other applications, including any anti-virus software.
• Installing ViewNX-i uninstalls ViewNX, ViewNX 2, Nikon Transfer, and Nikon Transfer 2. To use any of these applications after installing ViewNX-i, uninstall ViewNX-i and reinstall the application.
• Users of macOS Sierra cannot use Nikon Transfer 2 to copy pictures from memory cards installed in a card reader or card slot. Copy pictures using the Finder or Image Capture.
• Read the information below before proceeding.
-
I noticed something about ViewNX-i that may actually not be a bug in Nikon's software but in the Windows 10, perhaps. Sometimes when doing a first round of grading my shots in a large directory (ca. 1000 images or a bit fewer than that), after I turn on Filter and try to click on the filtering criteria, it hangs and consumes one CPU core but it just never seems to finish, and will not respond to any attempt of mine to interact with the UI of the software. Yesterday I had the same thing happen with ACR in Photoshop CC, and now I actually realize it has been doing that quite often, but usually if I wait long enough, it'll start responding, but yesterday my patience wore off and I just killed the process. I think maybe this started to happen when I switched to using Windows 10. I can't be sure of course but it would be peculiar if a similar problem occurs both in Nikon's and Adobe's software.
-
Hello,
Working on an iMac and going from ViewNX2 to ViewNX-I. And going from El Captain to Sierra and ending up now with version 10.12.3. In the last update of ViewNX-I they 'fixed' the transfer problem by disabling the transfer function all together. Transferring and creating on the fly a folder with the date of today is my workflow. So I put back the old Nikon Tranfer2 to in my setup and it worked erratic. Couldn't properly read a SD-card and so the import was useless. Though no sign of corrupted NEF-files.
I did the complete tour of all the photo-management tools on the market and non covered my needs. No catalog, hiding the jpeg behind the NEF and non-destructive edit and import with folder creation.
And today I bumped on a work-around that works. The OSX Photoloader is setup to accept my cards and transfer the files to a directory. But I don't. Instead I now start Nikon Transfer 2 ( the old one) and it reads the entire SD-card of my D90 without a stutter. Transfers the whole lot, creates a folder, erases the files, ejects the card and starts ViewNX-I in the newly created folder. The only thing I do is complete the folder name with some description behind the date. And close the OSX Photoloader. I on't onderstaand what happens, but somehow the OSX Photoloader creates a situation where Nikon Transfer2 can do it's job.
-
And today I bumped on a work-around that works. The OSX Photoloader is setup to accept my cards and transfer the files to a directory. But I don't. Instead I now start Nikon Transfer 2 ( the old one) and it reads the entire SD-card of my D90 without a stutter. Transfers the whole lot, creates a folder, erases the files, ejects the card and starts ViewNX-I in the newly created folder. The only thing I do is complete the folder name with some description behind the date. And close the OSX Photoloader. I on't onderstaand what happens, but somehow the OSX Photoloader creates a situation where Nikon Transfer2 can do it's job.
Might this mean the fault is with the Apple OS rather than Nikon Transfer 2?
Dave
-
I updated to ViewNX-i 1.2.7 and it seems much improved. I have processed through thousands of images without crashing or weird behavior. Previously when I would delete an image it would move the cursor away from the thumbnail strip so I had to reactivate it by clicking on an image before it would let me move from one image to the next after deleting an image.
So far looks very good!
I have not yet tried the new version of Capture NX-D.
-
I updated to ViewNX-i 1.2.7 and it seems much improved. I have processed through thousands of images without crashing or weird behavior. Previously when I would delete an image it would move the cursor away from the thumbnail strip so I had to reactivate it by clicking on an image before it would let me move from one image to the next after deleting an image.
So far looks very good!
I have not yet tried the new version of Capture NX-D.
I updated to v1.2.7 also, but, only to be current. I don't use any of the Nikon software because I just don't like it. I keep it on hand, just in case I suppose, but I haven't opened any of it in years. It's really too bad that Nikon can make great hardware and not match that with great software.
I'm not making any claims about which editing program is the best, there's more than one capable post processing program, with new ones coming out regularly. Much of it comes down to personal choice. There are some folks that put considerable effort into finding alternatives to PS and LR for no more reason than they're pissed off at how Adobe has moved to subscriptions for it's software. Personally, I like PS/LR, which doesn't mean that I wouldn't like other programs. What it does mean, in my case, is that PS/LR work for me, and I don't care to learn every other program that hits the market just so that I can replace one that's serving me well and that I already like. I do like, and use, plugins that expand my use of PS/LR.
Then again, there are some people that want to try out every new program that they find, and I see nothing wrong with that, it's their time, trouble, and expense involved, not mine. Maybe it's a personality thing, for example there are certain foods that I like prepared in a certain manner, and I do not care to experiment with alternate preparations, just to be different. To some folks, I'd be missing out on a new experience, and to me I'd be avoiding an adulteration of cherished recipe.
The last group are the folks that want everyone to use what they use, certain that everyone will like what they use more than any other program. We hear a "Oh, you must try blah blah". But see the above paragraph, not everyone agrees on everything, not that these folks get that. Many people think that there's something wrong with people that don't like goat cheese, and I'm one that doesn't. They also think that there's something wrong with people that like Limburger, and I'm one that does. Different strokes for different folks.
-
Nikon software is the only one that shows active focus point and AF fine tune setting used. This is information I must be able to see. I use ViewNX-i for browsing, not for modifications to the images.
It shows images properly resampled for display; e.g. Adobe Bridge shows quite often additional aliasing that is not present in the original. ViewNx-i also follow camera settings for the appearance of NEF images which I also consider a must. Finally it is a lot faster for browsing than lightroom on my computer(s).
Anyway looks like most of the bugs that annoyed me are now fixed and I am a bit less stressed about Nikon software. Hopefully this signifies they understand the importance of correctly functioning software and put more resources into software development in the future.
-
Nikon software is the only one that shows active focus point and AF fine tune setting used. This is information I must be able to see. I use ViewNX-i for browsing, not for modifications to the images.
It shows images properly resampled for display; e.g. Adobe Bridge shows quite often additional aliasing that is not present in the original. ViewNx-i also follow camera settings for the appearance of NEF images which I also consider a must. Finally it is a lot faster for browsing than lightroom on my computer(s).
Anyway looks like most of the bugs that annoyed me are now fixed and I am a bit less stressed about Nikon software. Hopefully this signifies they understand the importance of correctly functioning software and put more resources into software development in the future.
Since it has been so long that I've looked at it, I opened up the new version. I saw the focus point info that you mentioned in the few old images that I was looking at. However, nowadays I import into LR from the card, and convert to dng at that time. That makes those images show up as Tiffs in ViewNX-1.2.7, so no focus info available like it is for NEFs. I guess I can go back to having NEFs and dng copies, but I'd have to consider that because of the extra space needed for the expanded file sizes to cover both versions.
Moreover, the NEF files that I looked at were from my D200, and that predates focus fine tune, so nothing for me to see there, and my D7200 pics were converted to dng on import, so nothing there either.
Anyway, when I closed View out I got an error message saying that it had quit unexpectedly. Of course that wasn't the case, so I opened and closed a few times more, and got the same error message each time. So, there's still at least one fly in the ointment with v1.2.7. This might be an issue only with MacOS, I dunno. I did not use it enough to find any more issues.
-
Well, I'm told that Adobe Illustrator exhibits the same behavior under MacOS 10.12.5, that is it crashes on the quit command. that from a fellow Mac & Nikon user. I hope that I've not besmirched Nikon with my comments suspecting that they were to blame for that behavior with ViewNX-i v1.2.7.
A "Mea Culpa" may well be in order here. :-[
-
I like to use Nikon browsers for going through the images for several reasons. One is that they follow the picture controls set in the camera. Another is that it is reasonably fast to browse and check focus quickly, and you get to see hardware details such as the active focus point, AF fine tune setting in use, etc. You cannot get all of these details in e.g. Adobe software.
However, for the past couple of years Nikon ViewNX-i has been available, it has been quite unreliable. It crashes from time to time, especially it seems to happen when accessing older directories which have seen use by Nikon ViewNX2. And sometimes when it crashes once, it will always crash when restarting the software.
I discovered a way to temporarily solve the problem of this program being in a seemingly permanent crash loop. I deleted the c:\users\username\AppData\Local\Nikon\ViewNX-i directory. After this the software seems to work normally again. For a time at least.
I always knew Nikon software had glitches, but the frequency of them occurring since ViewNX2 and Capture NX2 were discontinued, is alarming. I have to wonder if they have any competent software engineers working for them and whether they have any people whose primary task is to test and make sure that the software works correctly on any platform that is supported.
I sent Nikon a message about this, though I am not sure if it will do any good. Everyone seems to just use 3rd party software. But I want those device dependent data to be displayed when I'm browsing images.
I have Mac Pro with SSD. Now is ViewNX-i crashing every time I open it. This is the second time this happens. The first time I had to formate the whole SSD, load in everything and then the programme worked again. Do I have to do this now again? I don´t know if I have the energy for it. I have latest Mac OS. I have tried to uninstall it and load down the latest version from Nikon, but it didn´t help. I have also sent Nikon messages about this, to Nikon Nordic, but they couldn´t help me. And Nikon Transfer isn´t working either. It stopped working when MacOS Sierra came.
With regards
Pär Nordqvist, Sweden
-
There are a number of programs that crash when generating thumbnails. I found a couple of PDF files that crashed IrfanView 64 bit. I ran them through Adobe Acrobat Pro and it reported masks that were removed is reprocessing the PDF(s). The newly precessed PDF(s) no longer crashed IrfanView 64. It happens probably more often than people know. Now if a program crashes while creating thumbnails an irregular file is what I suspect first.
Dave who is suspicious of your thumbnails. :)
-
Just a single faulty file in a folder can be the cause of thumb-nail browsers crashing.
I beta-test software so have sometimes seen that happen.
If the files are RAW files, simply trashing all recent XMP metadata sidecars that are attached to those images is all that it takes to fix the problem.
-
Just a single faulty file in a folder can be the cause of thumb-nail browsers crashing.
I beta-test software so have sometimes seen that happen.
If the files are RAW files, simply trashing all recent XMP metadata sidecars that are attached to those images is all that it takes to fix the problem.
Have the developers forgotten or are they too lazy to implement error trapping? Besides crashing I've seen layer registration problems in Photoshop after straightening an image. I now crop, I have to trap the error after straitening images in CNX2, CNX-D and Photoshop. I also crop after using the Canvas Size tool in Photoshop. It's a solid habit now and saves me much grief.
Dave Hartman (who no longer pounds his keyboard with his fist). :)
-
Nikon software is the only one that shows active focus point and AF fine tune setting used. This is information I must be able to see. I use ViewNX-i for browsing, not for modifications to the images.
I just downloaded and installed ON1 Photo 10 (not RAW) and I think I'm going to like this browser. It does not show the focus points but it does show the EXIF data I want to see most often.
ON1 Photo 10 can easily hand off a NEF file to ViewNX-i where I can see the focus points and dig deeper into the EXIF data if I want. Some migh find this handoff useful if they use ON1 Photo 10.
Dave
-
If the files are RAW files, simply trashing all recent XMP metadata sidecars that are attached to those images is all that it takes to fix the problem.
Thanks for this information! I just noticed an XMP file and wondered what it was.
Dave
---
One more time: if thumbnail cache is crashing VNX-i here is how to delete the cache os VNX-i can build another one...
Nikon ViewNX-i Cache Location and Clearing For MAC OS X 10.11.6...
1) Open your "house" in Finder
2) Below the folders in a blank area right click and select "show view options"
3) Select "Show Library Folder"
4) Navigate to...
Macintosh HD> Users> User Name> Library> Application Support> ViewNX-i>
5) in the ViewNX-i folder locate the "Cache" and "DB" folders and move them to the trash.
Nikon ViewNX-i will create new Cache and DB folders when it needs them. The corrupted files in these folder will be gone and VNX-i will create new ones.
Nikon ViewNX-i Cache Location and Clearing For Windows 7 SP-1...
1) Right click Windows Explorer and select "Run as administrator"
2) In Windows Explorer click Tools> View Tab> and under "Hidden files and folders" set "(x) Show hidden files, folders and drives."
3)
4) Navigate to...
C:\Users\User Name\AppData\Local\Nikon\ViewNX-i
5) in the ViewNX-i folder locate the "Cache" and "DB" folders and delete or move them to the Recycle bin.
Dave Hartman
Please let me know if you are running OS X 11.x.x or 12.x.x and if the path and method is the same
Also those using Windows 10 please let me know if the path is the same as Windows 7. I'm guessing but not sure: I don't think one can get as far into Windows without an administrative account. I hope this helps someone. :)
---
I used to have problems with Photoshop 7.x getting its preferences messed up and I learned to backup the preference files so Nikon software is not alone in occasionally needing a cache or preference file deleted and replaced.
-
I today used the rating feature of my D850 to mark good pics between breaks in a figure skating competition. I can see the star ratings in ViewNX-i but if I choose a filter based on the stars, it only shows a few of those marked in camera. So the markings are there the filtering based on them just doesn't work. Windows 10.
-
Not sure if I can help in any way here, I was sure I had read a post asking for confirmation of the location of the pref's files for Nikon ViewNX-i, now I can't find that post.
Anyways, I have loaded Nikons ViewNX-i software which I found on the UK Nikon site. The version I downloaded was specific to my OS: 10.13.4.
(https://farm1.staticflickr.com/899/26252336967_594102c453_o.jpg)
This evening looking for a little excitement I decided to launch it and look at some of my less important images.
While the software seems very basic after Lr, it worked OK. I am trying to discover what file the location was being asked for in the library? Maybe tell me the the hierarchy? Then I will have a look. The files should now be in place since I have run the software.
If I can clear any queries up I will be happy.
-
I today used the rating feature of my D850 to mark good pics between breaks in a figure skating competition. I can see the star ratings in ViewNX-i but if I choose a filter based on the stars, it only shows a few of those marked in camera. So the markings are there the filtering based on them just doesn't work. Windows 10.
I don't use ViewNX-i(much) .. but about the only reason I can think of for the situation could be that you may have inadvertently also clicked one of the colour/number label settings as well?
I doubt that's why .. but the possibility is there.