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
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".
-> Camera Files
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.
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.
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.
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.
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.
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.
I will still work on getting a screen recording of exactly where the problem is.
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.
This conversation is no longer open for comments or replies.
This conversation is no longer open for comments or replies.