Skip to main content
Known Participant
June 10, 2019
Question

Edit in PS... Then batch save and close?

  • June 10, 2019
  • 2 replies
  • 2445 views

I'm running into a unique problem that no amount of Google has been able to solve for me.
I do a bulk of my editing in LR Classic, but for certain groups of photos I give extra attention in PS.

Here's my issue:

If I create an action that includes SAVE and CLOSE in PS, those files DO NOT get sent back to LR.
But if I manually save each one they DO get sent back to LR.


Is there anything I can do to batch save my changes in PS so they get sent back to LR?
It would help my workflow tremendously. Thank you!

    This topic has been closed for replies.

    2 replies

    JohnTomBlack
    Participant
    July 18, 2024

    It was requested that this also get posted to the PS support page, so I went ahead and added it with a bit more information. I've been told they can replicate the issue and are working to resolve. 
    https://community.adobe.com/t5/photoshop-ecosystem-bugs/edit-in-ps-then-batch-save-and-close/idi-p/14746762#M107909 

    Just Shoot Me
    Legend
    June 10, 2019

    Not sure how you are saving but a simple Ctrl + s will save the file and send it back to LR then a Ctrl + w closes that image.

    Are you working on RAW files sent from LR?

    What is in your Action to Save and then Close each image?

    If it is a Batch Save & Close, Saving & Closing all at the same time that might be the problem.

    Known Participant
    June 10, 2019

    Thanks for the response.

    Yes, when I save individually using Ctrl+S those files are getting sent back into LR no problem.

    But if that Ctrl+S is included in my action so I can batch apply it to all of the open files LR is not getting those.

    gxZ8Drl.png

    Here you can see the action consists exclusively of CTRL+S
    And that in Automate->Batch I'm doing nothing but applying that to open files

    Community Expert
    May 31, 2024

    Any resolution here? This is a super annoying bug and I can't belive it's still happening. 


    one possible tactic: rather than initiating the PS edit of Raw normally (passing through ACR silently, image created in memory only at first), to use an external editing preset to initiate this. There then follows a different interaction between PS and LrC.

     

    In the standard workflow, PS gets an unsaved image and the subsequent Save needs to do several things at the same time: to create the file on disk but also to communicate to the Catalog that something new needs to be imported. It seems this latter part is what is failing to happen when save is invoked by a batch Action.

     

    In the workflow that an external preset produces (and the same will happen when a non-Adobe editor is  used, or if  LrC and PS are not version-compatible) the creation of the file on disk AND its import into the Catalog have already happened before PS sees anything. In this case if is LrC itself that has rendered the Raw conversion into pixels, not ACR, and therefore what is opened in PS is an already existing file. Therefore all that needs to happen when the image is subsequently saved by PS, is the update of a file on disk. LrC has that file already imported regardless of PS saving or not; it is "looking out for" any later re-saves in any case: however that re-save is being invoked at the PS end, should make zero difference to LrC AFAICT.

     

    The main difficulty of this method IMO, is training oneself to not use Ctrl+E shortcut - and remembering to choose Edit In... / [name of preset] instead!