Lightroom 5 publish services - order of published images

I have created several collections in which I have manually sorted the photos in a certain order. I am going to use them in a book (will be sending them to SmartBooks) and I don't want to reorder them once they are published to my hard drive. I have tried to publish them to my hard drive using publish services, but I can not find a way to rename the files so that they come out in the order I have selected in the collection. They appear by capture date or current filename with a jpg extension. Does anyone know of a way to do this?

Worth noting: the order of files outside Lightroom depends on how the device orders things (and no longer depends on Lightroom, once they've been pushed from the nest..).
That said, alphabetic ordering is the most common denominator - most devices are capable of displaying in alphabetic ordering.
Many devices will also display by date (usually capture date, but sometimes file-creation date..).
If you are publishing repeatedly the same photos, it get's very tricky indeed, since Lr will not re-order already exported files or take them into consideration. If you are re-exporting the whole lot, then it's much simpler.
Anyway, Lr5user-pt's method gives total control, but also has some drawbacks - you have to redo the copy names if/when you reorder photos (and then, re-export/publish all photos whose copy-names have changed).
TreeSyncPublisher will map in-Lr ordering to capture dates (in exported file metadata) or file-creation dates (by "touching" exported file dates on disk), so if devices support such ordering (by date), then published photos will remain ordered upon republishing, automatically. Granted, you have to be conscious of some stuff, and read the documentation, and learn to follow the rules..
(PS - a new version is coming out soon, which will have less "gotchas").
Exporder is like TreeSyncPublisher except it renames exported files to match in-Lr order - even trickier to use though, but works dandy if you're willing to learn where are the hoops to jump through..
The above mentioned plugins are free, and I wrote them - they only make sense if you will be re-ordering, or re-publishing changed photos.
If you are just exporting or publishing one-time/all-at-once, then the simplest method is just to prefix an ordering number to the export filenames:
Rob

Similar Messages

  • LR4: Publish Sort Order

    Hi,
    Can anyone let me into the secret of how to change the order of publishing images to the hard disk?
    I have created a "Published Folder" and placed a few images in it. I can display the images in the various sort orders and can even move images around to make a custom sort order.
    I have set up the Publish service to rename the images during publishing so hopefully they would reflect my sort order when viewed in filename order.
    Whatever I do, it always seems to process from the newest to the oldest image and so become out of order - I select them all to be republished.
    Can anyone tell me where I am going wrong.
    I might just try using export rather than publish.
    Brian

    Hi Brian,
    First, let me explain the root of the problem:
    When you first publish photos, they will be exported in order (e.g. custom sort order).
    So, *if* you export all of them, and add a sequence number prefix, then they will be in order (i.e. alphabetic, on disk). - so far so good...
    However, if you add a file or re-arrange them, then they may need to be exported again, completely from scratch (deleted first and removed from publishing...). Re-publishing may not suffice.
    There is a solution in the form of an emerging plugin:
    Exporder
    It renames published files to maintain user sort order. At the moment, it also mirrors master collection hierarchy (as exported folder tree) so if that's not acceptable - do tell.
    Rob

  • LR5 Publish Services does not honour 'Reload plug-in on every export'

    I am developing a custom export plug-in for adding backdrops and border to exported images.
    If I tick the 'Reload plug-in on every export' box then any changes I make to the plugin code get reloaded if I do a normal 'Export' from Lightroom 5.
    However if I use Publish Services to export the images it does not honour the 'Reload' checkbox and the old plugin code gets used.

    Hi, assuming your are referring to Jeffrey Freidl then can I just say that his plug-ins add so much more flexibility to any that might already exist in LR and I think he only expects the minimum set by Paypal as the minimum donation.
    You can try them for a number of days before deciding to donate.
    I did and I wouldn't be without them.

  • Using Lightroom publish service for either Flickr or SmugMug. I have many images with a keyword Madd

    Using Lightroom publish service for either Flickr or SmugMug. I have many images with a keyword Maddy. This frequently doesn't show up in SmugMug or Flickr. All my other keywords seem to work fine. Anybody experience anything like this?

    You only get one opportunity to set up the hard drive under publish and the folder cannot be changed unless you get a plug-in to provide a work around.
    However you could just create a generic publish folder - something like Photo Lab, or Print Job.
    But you could then right click on your publish folder and select “make target collection” - you will see the plus sign added.
    Simply highlight the photos you want to print and press B (the same as adding to a quick collection) and your Publish Services folder on your hard drive will be populated with the exports.
    The real problem is that you would need to edit the publish settings every time you required different dimensions etc (not sure possible). I use a similar system, which works well and I like how I can see what has already been published and what is still to be published but my prints are always the same size and resolution.
     

  • How to migrate publish service from Lightroom 4 to Lightroom 5?

    I have been upgrading from LR4 to LR5. Then I imported the LR4 catalog. But no Publish service was following to LR5.
    I have used the FLICKR plugin a lot - made more than 80 FLICKR-sets. Therefore I would be terribly sorry if I do not succeed in restoring the contact to the old service files. Does anybody know how to migrate publish services from Lightroom 4 to Lightroom 5? Very fine if it's going to be a kind of a workaround.
    Best regards
    Jimmy

    You'll need to backtrack a little, open your LR4 catalogue in LR5 and allow it to upgrade the catalogue with publish services.
    If you've done work on images in the "wrong move" catalogue, identify those images, select them, and do a File > Export as Catalog. in the "right move" catalogue, bring this work in by File > Import from Another Catalog.
    Alternatively, it may be worth looking at Jeffrey Friedl's Flickr plugin as he may have looked at this problem. Maybe someone here will know if it would help.
    John

  • Unable to upload photos to flickr using Lightroom 4.4 publish service feature

    I post process my images through LR and for several years published images to Flickr via Publish Services feature in LR.  The current version is LR4.4.  In the past two weeks I have been unable to publish new images on Flickr or update previously published images.  Instead, I received the following explanation:
      Can’t update this collection [ie., the Flickr collection in Publish Services]:
      An internal error has occurred: Error Domain=NSXMLParserErrorDomain Code=4 "Line 1: Document is empty
    " UserInfo=0x600010866bc0 {NSLocalizedDescription=Line 1: Document is empty
    A blog search shows that this problem has been reported for several years, but I have found no instruction from Adobe or Yahoo that provides a fix.  Thanks.  David Hawkins.  [email protected] 

    I have a friend who also can't get Lighroom's Publish Service to work with flickr. I don't use flickr but would suggest you try Jeffrey Friedl's Export to Flickr Lightroom plugin. I have used his plugins successfully to publish to other photo sites.

  • Custom collection order in publish service

    In my publish service i have a problem. There is some collections which named by date of some period, and they update periodically (create new/delete old ). I need to sort them by descending, but they always sorted by ascending (it does not depens of collection creation date)
    As example:
    There are 2 collections: "2014-01-01" , "2014-01-02" (exact order) when I create new collection (newer date)  "2014-01-03"  it always creates below by sort order, but  if i create "2013-12-30"  it will be created  higher
    How I can set my custom order ?

    I assume you are referring to the sort order of the collection names in the
    publish panel, not the images within the collections? If so I don't believe
    we can control this and it always sorts alphabetically.
    Matt

  • Published service from Lightroom to Behance

    It seems the only option in Lightroom with regard to published services to Behance, is "work in progress" which seems a bit restrictive.  Is there a plug-in for Lr or Be that allows one to publish and export PROJECTS as well?

    Hi everyone - very sorry for the confusion, I absolutely should have started at the beginning of the thread to understand the full context of the discussion.
    The feature request you're referring to - the ability to publish a Project directly from the Adobe apps as opposed to Works-in-Progress - has been made clear to our product team, and is something they're aware of. I'm sorry that I don't have more details to give on the process of how feature requests are handled, but what we do know is that the way the product team thinks about Projects is that they should be polished, finished pieces with a contextual intro, potentially captions on the images, and more. We don't want the easy "share to Behance" workflow to encourage users to publish projects of a single image, or a set of images with no context or additional information. The "share to Behance" feature is a better fit for WIP, which is why the Product Team made this decision.
    However, we fully understand that you're frustrated by this workflow, and I'll make sure to bring this feedback to the product team to let them know how much the Photographer Community would appreciate the ability to publish Projects directly from within Lightroom.
    Thanks for your feedback and sorry for the mis-interpretation of the original question on my part!

  • Lightroom and Creative Cloud: Publish Service?

    Will there be a "Publish Service" made available for those of us who already have Lightroom 4?  Trying to figure out how to use CC to access and share my Lightroom photographs...

    Hi Kmpeterson,
    Although it is certainly possible to upload your photos in Lightroom to Creative Cloud, the Creative Cloud storage was primarily intended to use for hosting projects from the desktop applications and not your entire Lightroom image library. There is no native functionality to export to the Creative Cloud from Lightroom 4. There is an export option for publishing to Adobe Revel (might have been what you were thinking of). Adobe Revel also uses cloud storage and was specifically designed to store image libraries online, on the cloud, to be able to view on different devices. Adobe Revel is not one of the products included with Creative Cloud Membership and is also a separate monthly subscription product. If Adobe Revel sounds like something you might be interested in, there is a 30 trial of Adobe Revel you could use to try it out before subscribing.
    Here is a link to learn more about Adobe Revel
    http://www.adobe.com/mena_en/products/revel.html?promoid=JCMJO
    -Dave

  • Lightroom 5 to Behance Publish Service doesn't recognize Creative Cloud login

    I'm trying to publish to my Behance service which I have access to via Creative Cloud. When I try to set up the publish service in Lightroom 5 it gives a wrong password error when I enter the Creativer Cloud name and password. I can log in to Behance with those credentials and have already set up a simple page.

    Sarahktrapp1,
    Quoting you (May 6) in another thread titled "I cannot link Lightroom CC to my Behance account".
    Unfortunately, a recent change made to the Lightroom integration has caused this feature to be inaccessible to some users.
    The feature should continue to work as normal for those who had previously used it, but new users won’t be able to authenticate.
    The Lightroom team is working hard to fix this as soon as possible, but it will be inaccessible for a number of weeks, so we suggest that you use Behance directly in order to share your work there. Simply login to Behance with your Adobe ID, and add a Project or WIP directly to your portfolio instead.
    Note that the other Creative Cloud integrations (Photoshop, InDesign, and Illustrator) will continue to work as normal - more instructions on how to use those here.
    Thank you so much for your patience.
    So apparently, you know why we can't login from Lightroom with valid credentials and you asked us to wait for a fix. The initial post in this thread reports the very same problem but you are giving us a different answer. Has this problem been fixed? Is it another problem with the same symptoms? I guess it's time to clear up the confusion.
    Thanks.

  • Lightroom 3 publish service: Sending 3 files from one photo

    Hi,
    I have created a lightroom 3 publish service that will export each photo as a huge TIFF file over a slow broadband connection to an external server. The external server creates 3 compressed JPEG files from the TIFF file.
    I think this is too slow and that it would be much better if the lightroom publish service created those three files and then sent them over the internet. Please note I am using Mac OS X 10.8.5 and Lightroom 3.
    My question is, what would be the best way to accomplish this task? Can lightroom compress the photo 3 times, or is it best to create another script on the local machine to accept each file, compress them, and then send them via the internet? What is the most secure and easy way to do this?

    Well, I don't see any reason to use an external script, since your Lightroom plugin can do this without it. Since you are controlling the code of the publish service, I recommend just doing this 3 times:
    local session = LrExportSession {
         photosToExport = { ... },
         exportSettings = { ... }.
    session:doExportOnCurrentTask() -- or new task.
    -- upload via FTP...
    PS - SDK forum would be better place to ask this question.
    Cheers,
    Rob

  • Why is Lightroom 5.4 so slow in Publish services and Book module?

    I've been using Lightroom 5 for a few months now. I'm using the latest version (5.4) and have been experiencing extremely slow performance in two main areas:
    1) When in the Library module and I select (or scroll down to) the Publish services on the left it pauses for 10+ seconds before displaying the valid services. Changing between different services also takes quite a while. I now have the services minimised unless I need them.
    2) When in the Book module and I try and change a page layout the first time I select the drop down the cursor changes to a spinning circle for a while. Sometimes it comes up with the dialog saying Lightroom has experienced problems and I can either close it or wait. It usually recovers without any input from me. However, the first time I select the drop down it will close without me being about to select anything. I then have to press it again and wait for the layouts to load before I can scroll through the list. This occurs on every page. It takes probably 10-20 seconds to be able to select a new page layout. Applying the layout is very quick.
    I have upgraded my PC from a 2.6GHz Core 2 Duo with 4 GB DDR2 RAM to an I5-4670 with 16 GB DDR3 RAM and not seen much improvement in either area. In both configurations I used an SSD for the application and catalog. The photos are stored on a NAS but this has not shown any performance issues in browsing/editing photos. A review of Task Manager's CPU and RAM loading during these operations does not indicate the CPU or RAM is maxed out. I've never seen the RAM go above ~7 GB used and CPU loading (average across all 4 cores) is usually less than 50%.
    Generally the upgraded PC is showing a significant improvement in Lightroom's performance but these two areas are still painfully slow.
    Is anyone else experiencing these issues or have any ideas on what I can do to try and improve its performance??
    Thanks,
    Brett

    Hi Brett,
    I got the same issue and I am very frustrated about it.
    Its the same thing I experienced in Lightroom 4 and its still not fixed. I cant use the book module because of that. So BLURB is not getting my money. :-(
    I am waiting for that fix since more than a year, but Adobe says its a Problem which appears only for a small group of users.
    HA HA just do a Google search!!!
    System:
    Lenovo W520
    Win 7 64Bit
    i7-2760 @ 2.4 GHz
    20 GB Ram
    1st HDD SSD 256GB         --> Catalog
    2nd HDD HGST 1.5TB        -->Pictures
    Nvidia Quadro 2000m

  • Lightroom 4 Publish Services will not connect to Flickr.

    I have been trying to set up Flickr in Lightroom 4 Publish Services but get an error message when I press "OK, I'll Authorise it" on the Flickr authorisation page.  The message is "The address wasn't understood.   Firefox dosen't know how to open this address".   Can anyone help?

    Unfortunately, there isn't anything we can really do on our side, as the problem here is that the expected behavior is not occuring and the failure is outside of Lightroom itelf.
    Here is what is supposed to happen:
    1. Lightroom sends a request to your web browser to open an authentication page that is already built in to the host web site.
    2. You authenticate, which gives permission for your account information to be sent back to Lightroom. This substitutes the need to enter a user name and password. It's a hall pass for Lightroom to send your files to your online account.
    3. With authentication complete, the web page sends a token (similar to a cookie) back to Lightroom, which is then used whenever Lightroom needs to access the web servers to upload a file.
    The problem occurs in step three. The token is not being sent to Lightroom. Instead, the web browser is keeping it for some reason and attempting to open it. This shouldn't happen, but Lightroom doesn't have any control over your browser. Some suggestions are to clear your temporary internet files and cookies to see if corruption there is changing the behavior. Also, the Facebook app for Lightroom may have some issues, try deleting this from your Facebook account (within your account settings on the website).

  • Lightroom: Publish Services have gone corrupt

    When I was trying to sync 500px with Lightroom 5, all the Publish Services have initialised.
    SmugMug, Facebook, 500px, Revel, all have reset, and ask to be set up.
    When I try to set up any of them, I get an error promptly, as below:
    ?:0: attempt to index field 'exportSettings' (a nil value)
    How can I straighten out the app? Thanks!

    I am having a similar problem. Were you able to find a fix. Thank You.

  • Lightroom 4.1: Publishing Service Flickr plugin; Using HTML in Caption field

    All,
    After hours of troubleshooting I have narrowed down a problem with an error message I’m getting when I try to export from Lightroom 4.1 using the Flickr Publishing service. The error msg is:
    Can't update this collection
    Could not contact the Flickr web service. Please check your Internet connection
    I have narrowed down the problem to my attempt to add basic HTML tags to the Caption (Description) Field of the Meta Data. This has worked perfectly well in all versions of Lightroom 3.6 and below (I didn’t try this type of export using Lightroom 4.0). I have also noticed that a simple page break, such as below, will also throw the same error:
    “Lorem ipsum @evansante.com dolor sit amet, consectetuer
    adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat veniam, quis nostrud exerci t”
    Flickr will recognize URL in simple text and format them properly so:
    “Lorem ipsum http://www.myurl.com dolor sit amet, consectetuer “
    Will work.
    Does anyone know of a work around that will allow including page breaks or HTML??? Thanks in advance - CES

    This bug, in a related way, has been noted by several users some time ago …
    http://forums.adobe.com/thread/999503?tstart=30
    and was reported as a bug a month ago during the release candidate period …
    http://feedback.photoshop.com/photoshop_family/topics/lightroom_4_1_rc2_a_cr_or_lf_n_the_m iddle_of_a_caption_causes_failure_to_connect_to_flickr  
    Although the above mentioned bug is raised specifically in relation to “Breaks” in the caption text I believe it may be symptomatic of either generically poor XML information encoding by LR when talking to Flickr or poor / incorrect use of Flickr Api’s which cannot cope with trivial complexity in the caption field.
    – in either case it needs fixing with some priority in my opinion, but possibly the philosophy of the on-going Flickr plugin support needs fixing too.  
    The LR Flickr publishing service has not been maintained very well in my opinion even when fixes may sometimes be trivial.     Perhaps Adobe would do well to employ or contract with JF for such plugins in future.    I use the excellent SmugMug plugin as the yardstick by which I measure the Flickr plugin.
    A fix should also be treated as priority because the LR error message takes aim at the reliability of your internet connection which may cause some to erroneously try to chase down non-existent problems with a perfectly good infra-structure or OS / Firewall configuration – that is seriously bad advice for a caption related LR bug and has scope to seriously compound the problem for the user!  
    Adobe, you have a responsibility to fix this before people mess with their reliable setups.
    Sorry, I am not aware of any work rounds to your problem with this and suspect it may be a windows only problem (please confirm if not).   
    Although not entirely exactly as per your problem (I believe it is generically the same) you may wish to add your vote to the above mentioned problem report or raise a new one.

Maybe you are looking for