I tend to do a lot of batch editing. Sometimes in a day I can take 1000+ pix at a sporting event. I have a scratch disk set up on c: and on d: for a total of bout 60gig.
If i set up a batch to process over night, inevitably come morning the batch will have failed due to the fact that both scratch disks were full. As soon as I close CS3 the space is freed and i can continue on from there. Is this normal behavior for CS3? I never recall having this issue with CS2. In CS2 if i recall I could batch 2000 pix and it would all be done come morning.
I have Bridge CS3 open with all the files I want to process and it runs a Fred Miranda plugin, plus a few other tweaks. This tends to get very annoying as to it filling up the disks, until there is about 340mb of free space. It would just error out and wait for the program to be restarted.
Is there a way to stop this from happening
If i set up a batch to process over night, inevitably come morning the batch will have failed due to the fact that both scratch disks were full. As soon as I close CS3 the space is freed and i can continue on from there. Is this normal behavior for CS3? I never recall having this issue with CS2. In CS2 if i recall I could batch 2000 pix and it would all be done come morning.
I have Bridge CS3 open with all the files I want to process and it runs a Fred Miranda plugin, plus a few other tweaks. This tends to get very annoying as to it filling up the disks, until there is about 340mb of free space. It would just error out and wait for the program to be restarted.
Is there a way to stop this from happening