Script does not save when batch processing small images

[winsburyUu4]

I have a whole bunch of batch scripts which have been running successfully for years on an XP pro machine.

After migrating to a much higher spec Windows 7 pro machine the scripts still run but only about half the files processed get saved when saving relatively small images (up to around 200x200 jpg.)
When saving larger sized processed images the saving process seems unaffected.

I suspect the problem is that small files get processed real fast and saving the changes is somehow running faster than the disk can keep up with and so some are being skipped. It has nothing to do with the number of files being processed either - whether I have 1000 or 2 files in a directory, only roughly half will get saved after processing.

Has anyone else had a similar problem and any suggestions how to fix?

I'm not keen on turning off the disk cache as it has other benefits and to be frank, I'm not why only PSP is affected, other batch file handling programs like (eg: Ken Rename) still work great.
Is there a 'pause' function that could introduce a few ms of delay after each file write event that could be added to the scripts to see if this works around the issue?

[LeviFiction]

All scripts are written in Python. So if you want to know if a function exists in python you can always do a search.

What version of PSP are you using? Since you mentioned a scratch disk I can assume X4 or X5 minimum?

If you want to try pausing. At the top of your script just below the "from PSPApp import * " line add "import time"

Code: Select all

from PSPApp import *
import time

Then just before any command that you want to wait on, use time.sleep(). This command takes a value in seconds. And Windows can only support sleeping for 10-13 milliseconds. So .013 is the smallest value you can put in there. Might as well put it at either half a second or a full second, depending on the number of images

Code: Select all

time.sleep(0.5)

[winsburyUu4]

Thanks , yes that seems to do as a workaround but I'm still hoping someone might have a more 'scientific' solution as to why Windows 7 64 pro throws up this anomaly and how to fix properly.

Adding 0.5 second to each file might not seem a lot but I process hundreds, often thousands of files per day and this adds up to a lot of lost productivity especially having to double check every file actually processed okay is together costing many hours.

Version is X2 ( yes, its old, but usually stable for what we do and supposedly compatible with W7pro.)

[JoeB]

Adding 0.5 second to each file might not seem a lot but I process hundreds, often thousands of files per day and this adds up to a lot of lost productivity especially having to double check every file actually processed okay is together costing many hours.

5000 files at an additional .5 seconds/file should only add less than 45 minutes over the course of a day. If some testing shows that this workaround actually works then you should be able to complete your projects without having to double check. Just a thought.