Lightroom: Queue! Ability set up JPEG, Web Gallery Export/upload into a queue to run at a specified time

  • 1
  • Idea
  • Updated 8 years ago
  • (Edited)
Merged

This conversation has been merged. Please reference the main conversation: Lightroom: Ability to set up a queue up and schedule several tasks at a time when you're not by your computer

Lightroom: Queue! Wouldn't it be great, if you could set up your JPEG Export, your Web Gallery Export and Web Gallery upload into a queue, then run them (or other processes, too) consecutively and automatically while you went for lunch? I know I would!
Photo of Steve Hockstein

Steve Hockstein

  • 20 Posts
  • 1 Reply Like

Posted 8 years ago

  • 1
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2675 Posts
  • 348 Reply Likes
Are you asking for these LR operations to occur outside of Lightroom, where Queue! is a separate product, or what do you mean, exactly?

The operations you describe do currently run in the background with LR is loaded, their progress being visible at the top left of the Menu bar, so you can do other things at the same time, including going to lunch.
Photo of Steve Hockstein

Steve Hockstein

  • 20 Posts
  • 1 Reply Like
Hi Steve,

I see this as a Lightroom feature, where you can set up multiple processes, save 'em and them run them all at once, one after another, without having to start each process individually.

For instance, for delivery, I need to provide a DVD with a folder of small sRGB JPEGs for web use, a folder of large Adobe JPEGs for print use and a web gallery, both for viewing online and for burning to the delivery disc (and then even burning the disc!). I'd like to set each of these for processes up in LR - without running them individually - and then have them run consecutively without having to monitor and start the next process manually. Lunch would be on me.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2675 Posts
  • 348 Reply Likes
You want to do a series of Export operations on the same set of images, and want LR to remember all the parameters of all those exports and not require you to be there to start the next one up, and you do these same series of Export operations for multiple clients so you don't want to have to respecify the parameters for every client.

In Photoshop terminology, one way to describe what you want is the ability to define and invoke Lightroom Export Action Scripts.

A couple questions:

1) How do you envision defining the set of operations to perform: recording sequence of Exports, or specify a list of Export presets, or typing in names of Export presets in a text file using some sort of language syntax, or what would you be comfortable with?

2) What is the purpose of the sequential nature of the operations: Is it so the computer doesn't get bogged down doing everything at once, or is it because the output of one operation feeds into the input of another, or because you want to reuse the same Export folders from one operation to the next and so you can't have multiple operations using the same folder simultaneously? The last thing could be alleviated by having ways to specify automatically-created folders for intermediate results.
--
I would argue that LR needs a way to script operations, not only Export operations but import and applying develop presets along with exporting and publishing and web-gallery-creation and printing and burning and flowing images into a book template or whatever else, not necessarily one script that does everything from import to print, but a script that can do things across multiple modules, so I can define the set of things to perform at a granularity that works for me.

Lightroom needs programmability or automation capabilities, in general, not just for Export, although it is obvious how that would be beneficial.
Photo of Steve Hockstein

Steve Hockstein

  • 20 Posts
  • 1 Reply Like
I really wasn't thinking that it had to be that complicated. My thought was that the LR Export dialog box would have a Start button and a Queue button. Obviously, the start button would begin the current process, but the Queue button would place the operation into the queue, after which you could set up another operation to place in the queue, or begin your queued processes. Being able to save a set of actions as a preset would be icing on the cake.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2675 Posts
  • 348 Reply Likes
So your request is the same as how Export works, now, except only zero or one export runs at a time, instead of all concurrently as happens now?

What is the reason for this: limiting the impact of simultaneous multiple exports on the system resources, or does the output of one job feed into another, or are they using folders in common, so only one job should use those folders at once or do you want to defer some of the Exports until you press another button, later, or what exactly is the reason for queuing the Export jobs instead of running them immediately and concurrently?
Photo of Steve Hockstein

Steve Hockstein

  • 20 Posts
  • 1 Reply Like
Primarily due to system resources. It's not going to take much longer to do the processes consecutively vs. concurrently, and it'll be easier on the hard drive. The dual-core laptop and eight-core desktop machines I'm using tend to get bogged down when Lightroom is only creating previews. The computer would be virtually unusable for light use such as email when LR has multiple processes running at once.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2675 Posts
  • 348 Reply Likes
So the simplest version of your request is a way to limit the number of background threads or processes in LR.

A number and up/down arrow along with a Play/Pause VCR-style button up next to the progress bar would suffice. Nothing specific to Export, just a globally accessible tuning setting.
Photo of Steve Hockstein

Steve Hockstein

  • 20 Posts
  • 1 Reply Like
No, I think that's simplifying things too much. LR should continue to support multiple concurrent processes, but also allow several processes to be saved and run at a later time. Maybe it could even have a timer built in to allow large batches to run at a specific time... overnight?