Since I upgraded to version 2.3 I get annoying pop-up warnings that the disk onto which Capture NX2 writes its temporary files is nearly full asnd I am recommended to do something about that. Is there a way to switch these warnings off?
For your background: I am on Windows XP SP3 - which is fast enough - and the temp folder is moved to a folder on a distinct high-speed disk I use for all caching and spooling. This disk is nearly empty (94Gb free space). Moving it back to C: doesn't help.
The issue pops-up when I already have quite a list of steps and want to return to a previously made step e.g. for adding another color point. Capture is fully able to process the change, but handling the tools is frustrated by the pop-up. A workaround is to switch off all following steps or to switch off 'keep all steps active'.
It is reported to Nikon but it could take until 2.3.x until it's solved.
Hi Mick, it is already good to know that I am not the only one heving this issue.
I am curious to know if moving to 64bit would be an answer. And possibly a clue for Nikon to solving the issue. Though, for me upgrading to Windows 7/64-bit (which persuasion I could resist thus far) would be quite a migration ...
I've had it happen just once on my 64 bit W7 install. I had the option to use the cache disabled at the time and the message was still displayed. I have since enabled the cache and I have not seen the message again. I think there is a possibility the message is not referring to the cache folder size on your hard drive but some other working memory the program is using but I am just guessing at this point.
In my case enabling or disabling the cache doesn't matter.
The issue pertains to the temp folder where Capture maintains edits onto the image that is in process. The folder contains no files anymore if you have Capture closed. This folder is mentioned on the preferences interface, under general at the bottom. There is a default (general) temp folder, but you can assign a different folder on another drive if you like.
The problem actually arises, like Michael confirmed, when you have a fair list of edit steps, more than six usualy. As is recalculating the edit steps take too much effort - although the application can certainly manage it.
Fri 20-Jan-12 06:15 PM | edited Sat 21-Jan-12 09:16 AM by gerphil
Yesterday evening I thought to have solved the issue by installing the optional .Net Framework 4 update KB2468871 (through Windows Update), that is intended for 'compatibility issues'.
In first instance it seemed to have solved the issue, however, some more testing revealed that the issue is still there, but that the behavior is just reliefed a bit (it takes now triggering/creating two or three color/selection points up in the edit list to trigger the behavior, where it used to appear straight away with the first one in my test images).
Sun 22-Jan-12 11:32 AM | edited Sun 22-Jan-12 07:06 PM by gerphil
Issue resolved ... by reverting back to 2.2.8. Petty of the gained speed, but the pop-ups are too annoying.
It surprised me, however, that apparently besides me there are only two who have experienced the issue. I'll wait for Nikon to come with a patch in 2.3.1.
Additional info: Capture NX2 2.3 doesn't clean up the temp folder after closure of the program as it should - and as 2.2.8 does. This may relate to the issue. Some files and folders are left and add up. Something you may want to check.
>It surprised me, however, that apparently besides me there are >only two who have experienced the issue.
I've seen this twice also (Windows 7 x64 & CNX 2.3.0 x64, of course) although it hasn't recurred (so far) since I re-enabled CNX2's caching over a week ago. (I acknowledge that at least one other person has reported seeing this recur after they'd re-enabled caching.)
>Additional info: Capture NX2 2.3 doesn't clean up the temp >folder after closure of the program as it should
Hmmmm! On my system, CNX version 2.3.0 clears everything up perfectly when I close it!
I re-direct my CNX's TEMP folder (Edit | Preferences | General) to a specific folder on one of my non-system internal drives (my 'D:' drive). When CNX is running I see assorted files and folders appear in there, and when it's closed (like it is now), that folder is completely empty.
I also re-direct CNX's cache folder (Edit | Preferences | Cache Settings) to a different folder on that same D: drive, and I limit its cache size to 7GB (95 images). The cache folder always retains its cache files of course (it's what the cache is for after all ), and unless CNX crashes, it also (in my experience, at least with previous CNX versions) behaves itself by honouring that 'maximum' cache size limit.
Could you give us some more details please Gerphil about where your Capture NX TEMP folder is located? Have you re-directed it from its default location? And what were the names of some of the left-over CNX TEMP files you mention? Am I missing some left-overs on my setup that I'd really prefer to tidy up?
(Coincidentally, I'm about to post a new thread about my CNX's "good behaviour" when I gave it an enormous .NEF file to handle ... and the thread title will be "Capture NX2 x64 trouble-free use of RAM in Windows 7.)(give me a few minutes to get it up and edited etc..)
Thanks for your reaction. I indeeed also use to redirect these folders. I redirect the temp folder to D:/CaptureNX2temp and my caching to D:/CaptureNX2cache (although I switched off caching). In 2.2.8 this works perfectly. The D: drive is a fast 10.000rpm Raptor disk that is largely used for all caching, spooling, etc.
Indeed I noticed that on my system the temp folder is not emptied. This behavior appears when I got those pop-up warnings. If I don't, the folder is emptied properly (I believe - suggesting there must be a relationship between the two). I cannot reproduce the file names as I am not behind my system and I reinstalled 2.2.8, but the left-overs include a folder with something like 'tile' in the name. Inside it I find an icc profile for the D300. And there are one or two tmp files created when editing as well, but these disappear when closing the application (I believe) - the folder(s) don't.
FYI: I am working in 32-bit mode on Windows XP SP3. It is reported to Nikon and there appear to be more complaints about it. People are working on it. Actually, they advised me to stick with the 32-bit version for the time being as it shouldn't appear there - which is funny as I was doing that actually. It suggests anyhow, that it's not limited to the 64- or 32-bit version.
Anyhow, reading your remark, this behavior is not consistent and may not be noticed by all and/or some time - until you decide to edit and add a few color/selection control points up in a long edit list of an image you want to re-edit... That's how I noticed it. I need to do this as part of the Capture NX2 training I give, working on practicing images, and when it appears it is quite embarrassing.
When I update Microsoft 4Net Framework (as suggested above) on my Win7-64 bit system, CNX 2.3-32bit stopped showing the temporary disk is full warning message.
I then upgraded to CNX 2.3-64bit and CEP 3.004. Initially I got the message when I had several control points in an edit step and was changing edit step values with the sliders. It didn't happen if I changed edit step values by entering a numerical value in the box adjacent to the slider.
However, I hadn't rebooted since installing teh 64bit CNX. Once I rebooted, the warning message has not reappeared (yet).
One odd thing that does happen, is when I use High Pass sharpening, I occasionally get a gray box covering part of the image after switching the Opacity Blending Mode from Normal to Overlay. Maybe by graphics adapter driver is due for an update.
Hi Mick, good to hear that thus far you managed to get rid of the pop-up warnings.
In my case unfortunately there was no reliable fix. Neither with the .Net4 upgrade, nor with switching on the caching, using the default temp folder, or disabling my wife's account on my computer. At best the pop-up appeared only after tweaking the second or third control point instead of more or less straight away (there is no real consistency in the behavior, it also depends how much you tweak a control point).
I didn't check if using numerical values would help, but I guess it helps as with using the slider Capture immediately seems to start recalculating. In general I believe the hassle is when Capture needs to recalculate all edits and then exceeding some thresholds in what it can read/write to temp/disk.
The only true workaround is to switch off the keeping edit steps alive when editing in the general preferences tab (don't know the English translation reads). But this is too much of a compromise for me - I then prefer to wait a bit longer using 2.2.8 (and for 2.3.1).
If you like you could do some testing with b/w conversion. First do your RAW processing (sharpening and contrast on 0, some shadows and exposure), then add 3 or 4 color points. Then a high-pass filter applied locally to strengthen some contrast. Then b/w conversion, playing with the filter. Then tweak your color points. Then add two locally applied levels & curves for locally increasing contrast (you may want to play with multiply blending mode). Then sharpening and finally add some grain or duotone. At the end you tweak both the color points and the amount of high-pass filtering again. Then close the image, open it again and tweak these color points and filtering again. This should give Capture the shivers. At least in my case.
>Indeed I noticed that on my system the temp folder is not >emptied. This behavior appears when I got those pop-up >warnings. (....)
Ahh! Yes, a good point. Following hiccups and crashes it's perhaps (perhaps!?) more understandable that our software might leave things behind. And it's probably a similar side effect to the more general instability and crashes in earlier CNX versions where it left orphaned cache files behind. Let's hope Nikon continues to resolve these glitches ... !
>FYI: I am working in 32-bit mode on Windows XP SP3.
And another "Ahh! Yes!" to that very good point, which would (or could) easily explain how CNX behaved differently on our respective systems. The days are long gone (sigh ...!!!!) when any of us could boast that we understood how every bit of software and every bit of hardware worked in depth on our systems, like I once did in the Windows 3.1 era !!!
>I need to do this (diagnosis/probing) as part of the Capture NX2 training I give, >working on practicing images, and when it appears it is quite embarrassing.
I see! In your position you clearly can't afford the luxury that I'm indulging in, of just suffering and tolerating the occasional "surprise" while editing! I salute your thoroughness and determination to be one step "ahead" of the hiccups when possible!!!
Although we have different systems, it is good to know that the behavior pops up across multiple variants, although apparently to a more or less degree. Knowing this might even make it easier to find the root cause. Hence, thank you and other for your feedback.
It seems, as far as I understand from reactions, to be Windows related, but appears both in Windows 7 and XP, and both in 64- and 32-bit. Could very well be related to the way .Net Framework 4 is used by Capture NX2 - as the patch does ease the issue a bit, and this framework is shared across the various Windows variants.
Anyhow, enough speculation, I have the impression that Nikon works on it now and I am sure it can be solved rather easily. Which would be greatly appreciated, because I am a big fan of the application.
And by the way, editing huge panoramas with it is a joy too - thanks for sharing your article!
I have just had the pop-up appear and also in a teaching situation when modifying a file with multiple previous edits. This is with version 2-3-0 on Vista 32bit. Generally it has all been very stable, so it is puzzling. Chris.
>It surprised me, however, that apparently besides me there are >only two who have experienced the issue. I'll wait for Nikon >to come with a patch in 2.3.1.
If there were only two people with this issue, nobody would expect a patch; best hope there are thousands out there experiencing this problem, all complaining to Nikon. Thankfully, NX2 2.3 64 bit on the Mac hasn't had this issue.
It becomes apparent that there are many more (but initially I got few reactions). It's a Windows-only bug as it seems (both 32- and 64-bit). Nikon confirmed that the issue is known and that they are working on it.
But as said elsewhere, for the rest 2.3 is very stable and even when the pop-up appears the program doesn't quit - actually the software can handle even the most laborious jobs very well, it is just that the indeed very annoying pop-up appears and prevents you from tweaking control point handles further. Which makes me believe that it is a minor issue for developers to solve.
Yes it will. I have Win 7 64 bit Pro and massive HD's the smallest being 2 TB. I have 16 GB of RAM and am running an i7 2600k processor. I never see more than 25 % of my memory being used and I am getting this message all the time. I have tried changing the location of the temp drive to variou disks and it continues. Perhaps I too should submit a report to Nikon.
Hi Bob, I would certainly do! Changing the location of your temp folder indeed doesn't help, regardless how big that one is. The only thing that really works is unchecking the box in 'preferences' that allows you to keep your edit steps alive while tweaking an edit step up in your list - but you won't want to do that. And don't let you suggest to return to 32 bit - that does'nt work either ...
Just noticed there is a version 2.3.1 of Capture NX2! However, the list of improvements doesn't include this issue. I issued another request to Nikon to give me an update on this new release, to get confirmed that it solves the issue (or not).
However, in the meantime, if you had the issue and upgrade to 2.3.1, it would be great if you could also notify me if you notice any difference with respect to the temp folder pop-up issue. Thank you very much!!!
Got a reply from Nikon NL by the way: they don't know about if this version gives a solution.
Which just stresses that anybody experiencing some bug should report it. Still, once 2.3.1 is available with you, please try it. I won't for the time being (unless I hear that it's OK) as I have another training to give tomorrow ...
Fixes listed: Modifications that apply to both the Windows and Macintosh versions
Support for RAW images captured with the D4, D800 and D800E has been added.
Extra High 1 (Extra High) and Extra High 2 items have been added to the Active D-Lighting pulldown menu under Camera Settings in the Develop section of the Edit List.
When "Always use the latest Color Reproduction Process" in the Picture Control Utility Preferences is selected for images captured with cameras released prior to the D4, these items will be displayed.
Event ID can now be displayed under File Info 2 in the File & Camera Information section of the Metadata palette for images captured by, and to which IPTC information has been added using the IPTC item in the cameras setup menu, the D4.
Display format for the following items in the Edit List has been modified.
Active D-Lighting under Camera Settings in the Develop section
Color Moiré Reduction under Camera & Lens Corrections in the Develop section
An issue that prevented sufficient application of vignette control enhancement for RAW (NEF) images captured with the Nikon 1 V1 and Nikon 1 J1 with A firmware Ver. 1.10 or 1.11 and B firmware Ver. 1.10 installed has been resolved.
An issue that prevented accurate display of lens information in the Metadata palette for images captured with the Nikon 1 V1 or Nikon 1 J1 and a 1 NIKKOR lens has been resolved.
When certain images with GPS information attached were saved in JPEG format, Capture NX 2 sometimes quit responding. This issue has been resolved.
Yes, I could test it myself. However, if the issue isn't resolved I would have spent a whole evening first installing 2.3 and 2.3.1, then deinstalling the whole thing, then re-installing 2.2.6 and 2.2.8.
Actually, I hope someone of you who had the issue and still had 2.3 on your system and did the upgrade could share your experience ...
I know of no reliable & repeatable way to force the warning message on my XP SP3 machine. I've found the pop-up warning issue to be so random & so infrequent that I could not say with any certainty that it was fixed. IOW I'd have to wait several weeks to be even reasonably sure. It may be that testing it yourself is the fastest and most reliable way for you to know.
FWIW The cpnx_tiledata folder is meant to hold a temp file named 0000000000000000.tmp. While the cpnx_tiledata folder is always created when CNX is first opened, the tmp file inside is not created until there is a need to do so. The creation of the tmp file depends on the content of the image file loaded into CNX and the amount of editing it received.
I've found that the cpnx_tiledata folder will be deleted when CNX is closed, but only **IF** the tmp file inside it was never created. In those CNX sessions where the tmp file was in fact created, when CNX is closed it will delete the tmp file inside the folder but not the folder itself. Thus leaving the empty cpnx_tiledata folder orphaned.
Try for yourself. Open CNX without an image file and observe your Temporary folder, the cpnx_tiledata folder will be created without a tmp file inside it. Close CNX and the folder is deleted.
Now open CNX and observe the "contents" of the cpnx_tiledata folder while you load an image file that has a lot of edit steps. It should cause CNX to generate the tmp file. If not, perform enough edit steps until it does. Then close CNX. The tmp file is deleted, but not its folder.
I've seen the same behavior in v2.2.8, so I don't think this has anything to do with the annoying pop-up warnings.
Hi Frank - thanks for youre reply! You are correct - also in 2.2.8 Capture leaves orphaned cpnx_tiledata folders in the temp folder. But in 2.3, if the pop-up appears, I remember Capture to leave a file in these folders that wasn't deleted.
In terms of testing: I have several files that trigger the behavior straight away and consistently, which behave without any problem in 2.2.8. But also new files in which I apply 6 or 7 or more edit steps, including several color points, trigger the behavior pretty consistently. When I convert to b&w I rapidly hit against the threshold because then my first or second edit step includes a few color control points before applying local contrast, conversion and a few more.
You are also correct that the faster way to get a test is to test it by myself. However, I can live with 2.2.8 and the hassle up upgrading, deinstalling and re-installing, incl. getting all my preferences and batch settings as I want them is not worth spending a full evening plus the frustration on.
On the other hand, there must be people who have similar test files (and otherwise I could sdhare one of mine) and 2.3.1 on their system - so I was hoping that someone could tell me. And otherwise Nikon ...
In my case it doesn't crash - you can continue tweaking the control, but with interruptions of the pop-up. The program can perfectly handle all the things you want do. By the way, have you tried the upgrade and does it resolve the issue?
I've not seen CNX crash as a result of the warning. But I have noticed other odd behavior.
-Once the warning appears, and I try to load a 2nd NEF into CNX without first closing & reopening CNX, I get a message saying CNX cannot load the file because there isn't enough memory. There is of course enough memory, and after closing CNX and reopening the same NEF, I can then load several more NEFs without incident.
-On one instance, where a NEF file predictably creates the 0000000000000000.tmp file, I received the warning but the tmp file wasn't created as expected. Though in other instances when I received the warning with other NEFs, the tmp file was created. So the warning may or may not be tied to the timing of this tmp file creation.
-The warnings are more likely to be repeated in the same CNX session, but not after closing & reopening CNX.
Even though CNX continues running without a crash when the warning appears, I would suggest closing CNX and starting a new session.
FWIW I suspect that when CNX is opened it calculates how much disk space is available even if it doesn't need to create that tmp file at that particular time. If the calculation is erroneous, and depending on the NEF file and edits it contains, the warning may be generated later in the same CNX session should the tmp file eventually need to be created. Just a hunch based on what I've observed so far.
It's not whether or not one works with multiple images loaded in CNX. But that doing so after receiving the "temporary folder disk is full" warning, and receiving yet another unexpected memory related message, indicates there's something else going on under the hood. IOW The Temp folder warning is not as benign as it appears.
>Hi Frank - thanks for youre reply! You are correct - also in >2.2.8 Capture leaves orphaned cpnx_tiledata folders in the >temp folder. But in 2.3, if the pop-up appears, I remember >Capture to leave a file in these folders that wasn't deleted.
Are you sure you're referring to the 0000000000000000.tmp file inside the cpnx_tiledata folder?
When CNX crashes, it will leave small .tmp files in your temporary folder, but not in the cpnx_tiledata folder. I've never had an instance where the 0000000000000000.tmp file was left behind, or where other tmp files were found inside the cpnx_tiledata folder. Even after a crash CNX manages to delete the file. Which is a good thing given that I've seen that file grow larger than 20g
FWIW after a crash, I've even found the small .tmp files in the folder containing the image being edited. But not recently, knock on woo
Before I made my first reply I tried what you mentioned in your original post with a NEF containing 17 edits steps and could not force the warning to trigger. I can understand your reluctance to upgrade. Been there myself with previous versions, I don't blame you one bit for holding out for the fix.
I haven't upgraded to 2.3.1 yet. Can you supply a link where I could download one of your problem NEFs, and tell me exactly what steps you take to predictably trigger the warning? If I can predictably reproduce the warning by following your steps in v2.3.0, I could upgrade to 2.3.1 and let you know if the warning still occurs.
Hi Frank, Excellent idea. The safest way would be if you could go to my website www.geja-vu.nl and press on Contact in the upper right corner to write me an email. I will then upload the NEF using WeTransfer and send you a notification that its ready for download. If you then could play with the color control points and possibly add one to two extra, in my case I get the pop- up. Thanks in advance! Kind regards, Gerphil
I downloaded your NEF but could not force the error. Nice image of a fox BTW
It seems the pop-up warning needs both your NEF and your machine to pop up with any regularity.
At a certain point it became clear it wasn't going to happen, certainly not as easily as it does on your machine. The notion of forcing it "reliably" faded away after adding the 65th CCP. I think your best bet for v2.3.2 is to hope to see it listed as a bug fix. Sorry things didn't work out.
FYI In Preferences I did have the box checked for "Keep All Steps Active in Edit List". Here's what I tried in CNX 2.3.0....
-edited a few of your CCPs -added 5 CCPs to each of your three existing CCP edit steps -added two more edit steps at the bottom of the edit list, with 5 CCPs each. -saved the file under a different name, closed CNX -opened the file in CNX and added 10 more CCPs to the edit steps I already added at the bottom. -then copied & pasted those edit steps to the bottom of the list -to the newly pasted edit steps I performed edits and added 5 new CCPs to each </ popup too pooped to pop>
Thank you very much for testing! You made your point .
I already noticed that after a compatibility patch of .Net Framework 4 (see above) the behavior improved on my machine. Where it used to trigger the pop-up straight when I tweaked the first CCP it then only did it after a few tweaks. It will indeed be a combination of machine and CNX2 that makes it behave differently on different machines.
I will await a new version of CN2 and may also give it anbother try after an update of .Net Framework 4 is released (which may also help).