I've found that this usually doesn't resolve the issue(quoted above), and that deleting the cache files manually is usually best. Under this General tab in the Options menu, you will see an option to 'clear cache'. If you're working off SSD type storage, you won't see any benefit by using a separate drive. 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). 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. They allow you to set the location of the cache to one of your own choice too. It'll be quite obvious once you're in this settings option. You can determine this by delving into the Options menu in VNX2(Edit->Options) and under the General tab up the top. ![]() If you haven't configured the cache location, then Nikon usually places it in some user appdata type location of their choosing. I think(not 100% sure) why this happens is the thumbnail cache becomes too large, and possibly corrupted/confused or something like that. I have ViewNX-i for those times when I want to view raw files from newer cameras only(ie. ViewNX2 is still my preferred choice(as I use compatible cameras). I think ViewNX-i is simply too slow, basic and low featured to be of any value for every day usage. Having the 256Gb SSD now as my temp storage location has turned CaptureNX2 from fast to almost blistering! My previous experience with Nikon's software is that faster storage + faster loading/processing times. 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. In jpg preview mode, images loaded in about 1sec to detailed view, approx half a sec blurred, never the grey processing screen. maybe half a sec of that grey screen processing, then the image(blurred), and then detailes. On this drive, above, ViewNX-i loads the raw data mode images(D800E) in about 5sec. Top left hand corner of the image review screen area is a small grey/yellow icon marked /īy default it should be grey, denoting jpg preview mode.Ĭlick the icon and it turns yellow, denoting raw data mode.īasic PC specs are: AMD FX8350(not the speediest, but plenty of grunt for what I need), RAM=32G DDR3, mainboard Gigabyte 990FX based.Īgeing HDD 2Tb from WD(black) average data transfer rates ~ 80-100Mb/s ViewNX-i is similar to ViewNX2 with respect to viewing raw files in raw mode, or jpg preview mode: Before age and health issues caught up with me, my keeper rate for Eyes was highest using single point even with fast action. D500 seems improved but am missing the head and eyes on too many BIF images so back to 25pt. Working out my preferred D500 settings for AF and metering is taking some time and I am taking more shots as a result. I spent some time with CNX-D when it first came out but was not impressed. My wife's newest External ceased to function (trying to recover) so now use multiples. I normally do my culling and then transfer the renamed folders to Externals. 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 often use CNX2 for the older cameras and often do the Df images in both CNX2 and PS. I did not use the disc which came with the D500 (nor have checked), I just downloaded from Nikon Message Centre. ![]() 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. 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. I can open the RAW Nikon images from ViewNX2 in PS CC2015. It is a bit of a convoluted work flow since I normally have ViewNX2 and Bridge open. 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). ViewNX2 is my primary catalogue (and my wife's).
0 Comments
Leave a Reply. |