P: Make use of extra cores to process multiple photos in parallel

hi, could someone please tell me how to install the export in parallel scripts in lightroom? or even how to get it. i used to have it before but after i cleaned my hard drive and installed windows again i lost it and cant find it anywhere.

thanks

hopefully Adobe will be inspired by the real world results of your script and apply this to standard preview generation (smart previews build so much faster) and web pages and books and so on.

You bet Dan, and yeah: if you are memory-challenged in the first place (whether due to amount installed or non-optimal memory-management/bugs..), this script may make things worse.. - in addition to using more CPU, it will also use more memory doing exports in parallel than sequentially. Lr *should* release used memory, but as most of us know - it doesn't always..

FWIW: This script only supports (non-publishing) exports without post-process actions, it does not support publish services, nor web galleries.

Thanks for posting this here Rob. I'm trying the export script and LR is consistently using 95%+ of my processor and nearly 5GB of RAM. LR seems to have inefficient coding and on top of that it won't use available system resources. This at least solves the last problem. So, thank you!!

** as a reminder to anyone else using this, LR won't release RAM until it's been restarted. So, to keep everything running smoothly restart LR after a big export. WHY????

Thanks. and, I agree..

really great, Rob!!
But as this script can only speed up "mormal" export but for example not the export of a big web gallery with many pictures, I'm still hoping on Adobe to optimize Lightroom performance and multi-core usage in the Lightroom core code.

You're welcome - thanks Bryn.

One caveat: does not support export filters (post-process actions), so export preset must not include references to Lr/Mogrify or Exportant..

Otherwise, any export preset can be used, and it will work the same as if export preset chosen in export dialog box, except for the multiple tasks (and sequence number override).

Cheers,
Rob

I suspect it's that it's using a single export process and multithreading the filters it's applying but some are only single threaded. So it's 100% when it's a really efficient algorithm, and low when it's single threaded (zip compression for example)

very cool Rob! Thanks!

Here is a simple script you can use to divide export into multiple simultaneous tasks.

Export in Parallel:


Note: sequence numbers for filenaming purposes will be partitioned appropriately.

Free, written by me:
http://www.robcole.com/Rob/ProductsAn...

Rob