"Swap problem" halts queue

general questions about Neat Image
Post Reply
taob
Posts: 119
Joined: Sat Feb 08, 2003 2:12 pm
Location: Toronto, ON
Contact:

"Swap problem" halts queue

Post by taob »

I fired up a queue of 68 images this morning and set it off while I headed out for the day. When I returned, I found that the queue had stopped at the 34th image with "swap problem" as the status. When I brought up the job in the editor, I could see the output image and flip between the "before" and "after" states. When exiting the editor, NI popped up an error dialog: "Swapping output image to temporary file has failed!". I quickly looked around my system and found one of my filesystems was down to 15MB free. The C:\WINDOWS\TEMP directory was full of 18MB temp files:

Code: Select all

-rw-r--r--  1 taob  taob  18874368 Feb  9 11:52 NIdst7-2.img
-rw-r--r--  1 taob  taob  18874368 Feb  9 11:59 NIdst7-3.img
-rw-r--r--  1 taob  taob  18874368 Feb  9 12:05 NIdst7-4.img
-rw-r--r--  1 taob  taob  18874368 Feb  9 12:11 NIdst7-5.img
-rw-r--r--  1 taob  taob  18874368 Feb  9 12:18 NIdst7-6.img
-rw-r--r--  1 taob  taob  18874368 Feb  9 12:25 NIdst7-7.img
-rw-r--r--  1 taob  taob  18874368 Feb  9 12:32 NIdst7-8.img
etc., etc....

I presume these are the completed images in the queue, given their size (exactly 3072*2048*3 bytes of a 24-bit 6-megapixel image)? Is there a more conservative way to deal with the temporary images? Compress them perhaps? Or maybe not even keep them around, and load in the actual saved JPEG (or TIFF or BMP) instead? For 68 6-megapixel images, I would need over 1.2 GB of temp space, which I don't have.

I see you can delete the jobs (I had Auto Save on, but not Auto Delete) which then removes the temporary files, but it is nice to be able to review the stats of each job (and of the complete queue) during processing.
NeatImage Pro Plus 5.0 + dual Opteron 244 + Windows XP SP2 + FreeBSD 5.2
NITeam
Posts: 3173
Joined: Sat Feb 01, 2003 4:43 pm
Contact:

Post by NITeam »

Well, you are right, you need free space for all those filtered images. Compression is not a good option (you can only expect twofold lossless compression at expense of considerable increase in processing time). Lossy compression is not an option. - You want to see the real filtration result, not the result of subsequent JPEG compression.

The simplest solution is to have more space available (in modern days, computers typically have at least 40-80GB of disk space) or to auto-save and auto-delete completed jobs.

Vlad
Post Reply