LIGHTROOM: Queue to Export

  • 4
  • Idea
  • Updated 6 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

It would be wonderful if you could Queue to export. Right now we process a lot of photos per day for seniors and exporting slows our workflow down significantly. If we had the ability to go through and make our corrections then click export, add to queue, and then when we go to lunch or go home at night to start the queue so all the sources are used when we don't need the computer that would be wonderful.
Photo of Chris Golden

Chris Golden

  • 12 Posts
  • 0 Reply Likes
  • excited

Posted 6 years ago

  • 4
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 389 Reply Likes
Publish services provide a sort of queuing - have you tried publish services?

You can cancel publishing at any time, and what remains to be published will still be remembered. Also, you can have multiple collections (independently exportable), if you want some things to go out now, and others to go out later...

To be clear: the "add to queue" function is accomplished by adding photo(s) to a regular publish collection, or adding metadata so photo will be included in a smart publish collection. When you go home at night, click 'Publish', and if you want to "pause" the lunch-time "export" you started, click cancel (the 'x' button in upper left corner). To remove things from queue, remove smart-collection metadata or delete from publish collection, or context-click and select "mark as up to date".
Photo of Chris Golden

Chris Golden

  • 12 Posts
  • 0 Reply Likes
Maybe I'm doing something wrong but this doesn't appear to work for us. To give you a little background we are set up as follows for our folder structure.

School
-> Student
-> Camera Files
-> Jpegs

So when we export we click the school, then students name and then click into the jpegs folder and click export. We may be exporting from 15-100 files depending on the session size. With the smaller sessions it isn't that big of a deal but when we are exporting two 100 file sessions off a Canon Mark 3, we have some slowness issues where the 3rd student is almost impossible to work on unless exporting is done. We also work on a appointment schedule to view files so we never need the JPEGs same day so allowing all say 20 students to render to their Jpegs folder over night could speed us up to allow us to do 30 students vs 20.
Photo of Chris Golden

Chris Golden

  • 12 Posts
  • 0 Reply Likes
As far as I understand the publish service, the publish service puts them all in the same folder as to where they should be published, we need each student put into the students JPEGs folder, I might simply be setting it up incorrectly, but I can't seem to get it to export into each student.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 389 Reply Likes
Hmm - I see what you mean. I was not realizing that the hard disk publishing service requires a specific output folder - seems kinda limiting. Consider TreeSyncPublisher instead. If you want the exported photos in the catalog along-side the originals, just set the destination path the same as the source path, which is equivalent to "Same folder as original folder" (e.g. ala regular hard disk export). Note: I just tested that and it worked - just make sure you are using the latest version 4.5.1 or better if you do decide to go that route.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 389 Reply Likes
Any luck Chris? Do you need the 'Jpegs' folder (containing exported copies) to be a child folder of originals folder, or a sibling folder? It wasn't clear to me from your original problem statement - which folder contains the originals to be exported? - 'Camera Files'?. That would be the only fly in the ointment I see, but could be remedied. Tag: you're it...
Photo of Chris Golden

Chris Golden

  • 12 Posts
  • 0 Reply Likes
Rob, I haven't tried TreeSyncPublisher yet, however what I want to do is as follows.

When I process a student and I make my selections and finish my color correcting and cropping, I would like to go to Export, and then select the student's JPEGs folder and select my Export settings and click Export and have it go into like a queue system where I can start it up later, to my understanding Publish does that but it dumps all the published files into one area which would not work for me due to our file structure and studio structure.

As stated before our structure is as follows:

Network Attached Storage:
2014 Seniors
-> Mtn HS 14
-> Doe, John MtnHS 14
-> Camera Files
-> JPEGs
-> Web_JPEGs
-> Cola, Pepsi MtnHS 14
-> Camera Files
-> JPEGs
-> Web_JPEGs

-> Dew HS 14
-> Noodle, Ramen DewHS 14
-> Camera Files
-> JPEGs
-> Web_JPEGs
-> Cole, Rob DewHS 14
-> Camera Files
-> JPEGs
-> Web_JPEGs

We have multiple photographers and multiple Lightroom people and multiple sales people so we need to keep with our structure or everyone will lose their minds when attempting to find someone. However our biggest issue is our Lightroom people have complained (including myself) that when you render out 5 people at a time or so, Lightroom comes to such a crawl that you simply can't do a thing until those 5 renders are done.

Hope this explained a little better :-/
Photo of Chris Golden

Chris Golden

  • 12 Posts
  • 0 Reply Likes
Network Attached Storage:
2014 Seniors
----> Mtn HS 14
--------> Doe, John MtnHS 14
--------------> Camera Files
--------------> JPEGs
--------------> Web_JPEGs

---------> Cola, Pepsi MtnHS 14
--------------> Camera Files
--------------> JPEGs
--------------> Web_JPEGs

----> Dew HS 14
--------> Noodle, Ramen DewHS 14
--------------> Camera Files
--------------> JPEGs
--------------> Web_JPEGs

--------> Cole, Rob DewHS 14
--------------> Camera Files
--------------> JPEGs
--------------> Web_JPEGs
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 389 Reply Likes
Chris,

I understand, in general, what you want. And hopefully Adobe has heard and understood too. That said, the feature you are requesting may not be available until Lr6, or 7, or maybe never. Which sorta begs the question:

* What is the best work-around for the mean time?

I think the best answer lies in publish services, although due to the built-in hard disk publishing service limitations (specific folder required), such seems to be a non-starter for you - I get that.

The one thing I don't understand:

* Which folder are the original master files in (the ones to be exported I mean) - "JPEGs"?, "Camera Files"?

And which folder will the exported copies be in? the same? or "Web_JPEGs"?

As it stands, TreeSyncPublisher will, essentially, do what you want. However, @now, it won't support putting exported jpegs into a child folder or sibling folder.

I'll stop there for now.

Rob
Photo of Chris Golden

Chris Golden

  • 12 Posts
  • 0 Reply Likes
The masters are found in Camera Files, we shoot 100% raw. Where things change sometimes is if a client requests their files posts online, if so we render one into the JPEGs folder and the one into the Web_JPEGs with 72dpi and a watermark. But Don't get to concerned about the Web_JPEGs that isn't a big concern for us.

Our solution at the moment is to go through make our changes and cropping and then a hour before we leave, start going through our client list of those who we made adjustments to and selecting the files we want to render and rendering them out. This works... but it really is time consuming to go back and set each of those to render later on because Lightroom has to repull the files for us to select Export.

I will try TreeSyncPublisher this weekend and see if it will work for us to speed things up.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 389 Reply Likes
There are several advantages of a publish service, but if you are only going to export one time, those advantages may not be compelling enough to bother. I mean, it could be that simply tagging edited photos and/or using a smart collection so you don't have to re-select after the fact would be all you need. But maybe I don't really understand the problem - you say "Lightroom has to "repull" the files" - what does that mean?
Photo of Chris Golden

Chris Golden

  • 12 Posts
  • 0 Reply Likes
Maybe I should do a screen recording of what happens and our process.

Tagging wont work because each student has their own JPEGs folder for their CR2 files to be rendered into. If we did tags at least to my understanding then when we selected the "To be rendered tag" it would select every student not just the one we need.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 389 Reply Likes
Chris,

Based on my understanding of your situation, which, admittedly, may not be exactly correct...
===========================================================

Solution #1: Using regular (hard-disk) export service.
------------------------------------------------------------------
* After editing, "spray" with metadata or drag to collection.
* At end of day, export all files sprayed with such metadata, or in such collection. Make sure you "un-spray" in the morning, after successfully exporting, or remove from "to be exported" collection. (Jeffrey Friedl's "Snapshot on Export" plugin has options which would do this automatically).

Solution #2: Using (TreeSyncPublisher) publish service:
---------------------------------------------------------------------
* Define a smart publish collection which includes ALL photos in school tree, in Camera Files folders.
* Mark ALL of them as "already published", since, well, all of them already are published (i.e. already exported to their proper places).

Now, whenever you add new students, or new camera files, or change existing camera files..., they will be ripe for publishing and/or re-publishing (you can define a hold-off metadata item, which needs to be cleared in order to be ripe (or a metadata item which needs to be set, if you prefer), if you don't want everything new published right way........).

The only problem with solution #2, is that TreeSyncPublisher doesn't (yet) support exporting into a sibling folder, which is your current convention, so you'd either have to define a separate tree for the jpegs (and web_jpegs), or live with them in same folder as sources, at least until I have time to support your sibling. PS - I've got an outstanding message to Jeffrey Friedl to see if he has any ideas how to serve this need - he also writes plugins, e.g. FolderPublisher. I'll keep ya posted.

A word of caution: TreeSyncPublisher was NOT designed to support exporting to same tree as sources are in. I tried it before posting here, and had no problems, but I also fixed a potential problem (v4.5.1) that would have resulted in deletion of original masters, if an unlikely but not impossible problem occurred. As I said, I don't see a problem now, nor have I heard of anybody else with one, but it was NOT what I had in mind when I created it, and so I'm a little reticent... It might be safest to export (via publish I mean) to a separate tree, since that insulates sources from exported targets, granted it would require restructuring your existing work. As noted earlier, Adobe themselves opted not to support publishing to same folder as original, via their hard disk publishing service, perhaps to avoid any accidental deletion or overwriting of source files by publishing - dunno.

Cheers,
Rob
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 389 Reply Likes
I just heard back from Jeffrey, he does not recommend using FolderPublisher for this - it does support the sibling folder, but also is not designed for publishing back into source tree, and has no "add-to-catalog" option. So, I think you'll have to go with solution #1 (assuming a different folder tree for jpegs is, at this point, unacceptable) or whatever else you (or other forumers) can think of, at least for now.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 389 Reply Likes
Chris, I just enhanced TreeSyncPublisher to support the sibling (JPEGs and/or Web_JPEGs) folder which is consistent with your present convention. It's not yet released, but I believe this option will work well for you - wanna try it?

There are some quirks of exporting back into source tree, and you will need to take some care, for example:
* If you export a NEF into a folder which contains a JPG sidecar from your camera, that JPG sidecar might get overwritten when the NEF is exported, since tree-publishing requires exported file be overwritten when there is a file-naming "collision", for reasons that might be obvious if you think about it for a while. However you'll be exporting from one format to another and into a different folder, so you should never have such a problem. Also, if you delete the raw, it'll delete the published jpeg file, but it can't remove it from your catalog, so you'll have to remove "missing" published photos manually.

I would think these things would not be prohibitive, but it's your call..

PS - The check I added in v4.5.1 was to assure if you export a jpeg back to same folder in jpeg format with same filename (and same extension) it won't overwrite the source file. Ditto for any other format/extension.

Rob
Photo of Chris Golden

Chris Golden

  • 12 Posts
  • 0 Reply Likes
I would like to test this out, anything that can help speed our process up is wonderful :-)

I will still work on getting a screen recording of exactly where the problem is.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 389 Reply Likes
I went ahead and released v4.6 (which includes support for your JPEGs subfolder(s)):

TreeSyncPublisher

PS - I'm not sure a screen recording will be necessary, unless the publish service solution still doesn't cut it.

Chris - please contact me outside the forum for plugin-specific support - thanks.

~R.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 389 Reply Likes
Chris,

To be clear: you will need to set destination path equal to source path, and enter ..\something for destination subfolder, for example:


Note: I don't think the direction of the slash will matter, but it's conventional to use backslash on Windows, and forward slash on Mac.

Rob
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 389 Reply Likes
Any news Chris?

This conversation is no longer open for comments or replies.