Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/content/60/9972860/html/smf/Sources/Load.php(225) : runtime-created function on line 3
Image Processor Pro can only handle a low number of images
The DAM Forum
Welcome, Guest. Please login or register.
April 16, 2021, 10:02:14 AM

Login with username, password and session length
Search:     Advanced search
28033 Posts in 5147 Topics by 2903 Members
Latest Member: kbroch
* Home Help Search Login Register
+  The DAM Forum
|-+  Software Discussions
| |-+  Bridge/ Camera Raw
| | |-+  Image Processor Pro can only handle a low number of images
« previous next »
Pages: [1] Print
Author Topic: Image Processor Pro can only handle a low number of images  (Read 9688 times)
Mathew Farrell
Posts: 22

View Profile WWW Email
« on: November 29, 2013, 01:49:06 AM »

Hi everybody. So far, I've found that Dr Brown's Image Processor Pro is the most convenient way to resize a folder full of images (to create web sized JPGs, for example).

I say most convenient, however on my system Image Processor Pro won't process more than about 250 images at once. It get a "No images Processed. Perhaps Empty folder?" error (not verbatim). This number of images that can be processed varies, perhaps with RAM usage, but I'm not sure. Bridge CS6s canned Image Processor can handle all ~2900 images at once.

I'm using Bridge and Photoshop CS6 on a modern Windows 8 machine (16GB RAM, Intel Core i7 3930k CPU @ 3.2GHz) and a separate ~200GB scratch disk)
Whatever method I use to process this many images via Bridge+PS (Bridge Batch of my own scripts, Bridge Image Processor, Dr Brown's image Processor Pro) takes a long time to start (several minutes to bring up the batch/script dialogue then tens of minutes for PS to start working), and is potentially pretty unstable whilst processing. This is related to how many images I have selected to process. Is this standard behaviour?

On a related note, I have recorded several actions to batch common actions (such as adding a clipping path based on transparency). The trouble with some of these actions is that they won't work on all images (some have no transparency, in this example). These images remain open in PS, and eventually clog RAM and stall the process. Without delving into scripting, can anyone think of any ways to clear out these non-processed images?


Mathew Farrell
Flowstate Photography
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!